Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>>>>> "Robert" == Robert Sayre <sayrer@xxxxxxxxx> writes:

    Robert> On 9/5/06, Sam Hartman <hartmans-ietf@xxxxxxx> wrote:
    >>  I want to be able to give you a URL and have you resolve it.
    >> That only works if we speak the same transport protocol.

    Robert> Disagree. The Internet is pretty compelling, so proxies
    Robert> can and do bridge transport protocols. Applications using
    Robert> the HTTP stack don't need to know or care about the lower
    Robert> level.
I wouldn't mind writing the language in such a way that this
requirement could be met by proxies.  I don't see how to do that as an
implementation requirement though--and deployment requirements about
supporting the same transport would be completely inappropriate for
the IETF to make for HTTP.


_______________________________________________

Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]