On Wed, Mar 26, 2008 at 10:11 AM, IAB Chair <iab-chair@xxxxxxxx> wrote: > What Makes For a Successful Protocol? > draft-iab-protocol-success-03 > > as an informational RFC.Before doing so the IAB wants to solicit from > the community any last comments on this document. ... > The document can be found at: > http://www.ietf.org/internet-drafts/draft-iab-protocol-success-03.txt The first illustration in section 1.2.1 is misleading. The narrative about the success of HTTP is correct, but the selection of "VPN" and "Firewall traversal" for inclusion is troubling. To start with, I don't see why VPN is included at all, and there's no explanatory text. Second, it seems to me that perhaps the most interesting/important success for HTTP outside its original design space is in software integration in general and "Web Services" in particular. As for firewall traversal... while accurate, this is not something that the IETF is very comfortable with. A.1.1 "HTML encumbrance only surfaced later". What HTML encumbrance? _______________________________________________ IETF mailing list IETF@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf