[rtcweb] rtcweb-transports, Suggested text for HTTP Connect usage.

["Hutton, Andrew" <[e-mail]>]

I promised in the Toronto meeting to provide suggested text for draft-ietf-rtcweb-transports once http://tools.ietf.org/html/draft-ietf-httpbis-tunnel-protocol-00 was adopted so here goes.

My suggestion is to replace the following text in http://tools.ietf.org/html/draft-ietf-rtcweb-transports-06#section-3.4

   Further discussion of the interaction of WebRTC with firewalls is
   contained in [I-D.hutton-rtcweb-nat-firewall-considerations].  This
   document makes no requirements on interacting with HTTP proxies or
   HTTP proxy configuration methods.

   The WebRTC implementation MAY support accessing the Internet through
   an HTTP proxy.  If it does so, it MUST support the "connect" header
   as specified in [I-D.hutton-httpbis-connect-protocol].


With the following

"In order to deal with the scenario in which the media must traverse a HTTP Proxy then the HTTP Connect request (Section 4.3.6 of [RFC7231]<http://tools.ietf.org/html/rfc7231>) MUST be supported.  The HTTP Proxy may require authentication and therefore proxy authentication as described in (Section 4.3.6 of [RFC7231]<http://tools.ietf.org/html/rfc7231>) and [RFC7235] MUST also be supported. In addition the HTTP Connect MUST include an indication of the protocol being used with the HTTP Connect initiated tunnel as described in [I.D.draft-ietf-httpbis-tunnel-protocol]".


Note:  I don't intend to maintain or progress [I-D.hutton-rtcweb-nat-firewall-considerations].


Regards
Andy