Some things needed
Definitely, some sourcing, and some specific examples, are needed. As the creator, you get to assign the language variant. A definition will be needed.
While it is possible to go to approval without all links being blue, it helps to minimize them. Definitely, the crypto-specific terms used in the definition, such as active attack, need definitions. You may want to have some graphics explaining the sequence; while the article itself is very much in draft, look at Domain Name System security for examples of showing how threats build up, or a simpler step-by-step in anycast -- they are in a PowerPoint file if you'd like it as a template.
Especially when devices such as ATM switches or routers are in the path, and themselves may not run any of the crypto, you need to show how the flow goes to a proxying man-in-the-middle box.
Howard C. Berkowitz 10:59, 15 October 2008 (UTC)
Looks pretty good
If we follow the principle of putting specific techniques/case study detail in subarticles, this is about ready other than flow and copy edit. Howard C. Berkowitz 08:22, 14 June 2010 (UTC)