LCE has been leaked, potential for service interruption It appears that LCE has been leaked faster then anticipated in document A332. This is a concern for operational effectiveness. In the immediate span we have the issue of determining if the rotation of algorithms should be continued as originally defined in A332 or if we should immediately react to LCE’s compromise by cycling to LLJK. Forcing the cycle early is dangerous as defined in A74 and current distribution methods are inadequate to ensure X continued cohesion. We could potentially see inline functionaries reduced by 40%. In the later operational term if we adjust the rotation schedule we need to address the original operation schedule. If the algorithms continue to be exposed at a rate reflected with LCE we can see a potential hijack of final implanted algorithm and disruption of signal by March 2009. This is obliviously not a sufficient amount of time to accomplish the schedule as defined in document A441. As it stands I purpose to force the cycle early and create supplementary copy to address the overall schedule. Also additional copy is needed to address the leak of LCE. The implant method as defined in document A39 needs a specification audit as it appears functionaries may be responsible for the leak. Please remember to use procedures defined in document A1045 before replying.