Hi Peter, On Thu, Sep 08, 2011 at 10:35:00AM -0600, Peter Saint-Andre wrote: > Willy, I appreciate the proposed text. Here is a slightly tweaked version. > > ### > > The WebSocket protocol is designed to supersede existing > bidirectional communication technologies which use HTTP as a > transport layer to benefit from existing infrastructure > (proxies, filtering, authentication). Such technologies > were implemented as trade-offs between efficiency and reliability > because HTTP was not initially meant to be used for bidirectional > communication (see [RFC6202] for further discussion). The > WebSocket protocol attempts to address the goals of existing > bidirectional HTTP technologies in the context of the existing > HTTP infrastructure; as such, it is designed to work over HTTP > ports 80 and 443 as well as to support HTTP proxies and > intermediaries, even if this implies some complexity specific to > the current environment. However, the design does not limit > WebSocket to HTTP, and future implementations could use a > simpler handshake over a dedicated port without revinventing > the entire protocol. This last point is important because the > traffic patterns of interactive messaging do not closely match > standard HTTP traffic and can induce unusual loads on some > components. > > ### > > I shall enter an RFC Editor Note in the datatracker with that text as a > placeholder, with the understanding that the text might change based on > further discussion. Looks fine to me. Thanks, Willy _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf