Re: WGLC: p2 MUSTs

Amos Jeffries <> Sun, 04 August 2013 02:52 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 634B721E8084 for <>; Sat, 3 Aug 2013 19:52:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.561
X-Spam-Status: No, score=-10.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id kXPLDVsDbBQQ for <>; Sat, 3 Aug 2013 19:52:08 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id D37E521F9DDB for <>; Sat, 3 Aug 2013 19:52:07 -0700 (PDT)
Received: from lists by with local (Exim 4.72) (envelope-from <>) id 1V5oP4-0007m1-0N for; Sun, 04 Aug 2013 02:50:42 +0000
Resent-Date: Sun, 04 Aug 2013 02:50:42 +0000
Resent-Message-Id: <>
Received: from ([]) by with esmtp (Exim 4.72) (envelope-from <>) id 1V5oOs-0007lE-LN for; Sun, 04 Aug 2013 02:50:30 +0000
Received: from ([] by with esmtp (Exim 4.72) (envelope-from <>) id 1V5oOq-0004FL-FU for; Sun, 04 Aug 2013 02:50:29 +0000
Received: from [] ( []) by (Postfix) with ESMTP id 14C5EE6F85 for <>; Sun, 4 Aug 2013 14:50:03 +1200 (NZST)
Message-ID: <>
Date: Sun, 04 Aug 2013 14:50:03 +1200
From: Amos Jeffries <>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
References: <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass client-ip=;;
X-W3C-Hub-Spam-Status: No, score=-0.0
X-W3C-Hub-Spam-Report: SPF_HELO_PASS=-0.001, SPF_PASS=-0.001
X-W3C-Scan-Sig: 1V5oOq-0004FL-FU 28fa1500e5eb508ee40b637a5b2e60e4
Subject: Re: WGLC: p2 MUSTs
Archived-At: <>
X-Mailing-List: <> archive/latest/19051
Precedence: list
List-Id: <>
List-Help: <>
List-Post: <>
List-Unsubscribe: <>

On 4/08/2013 1:48 p.m., Roy T. Fielding wrote:
> On Apr 30, 2013, at 1:46 PM, Alex Rousskov wrote:
>>> The CONNECT method requests that the recipient establish a tunnel to
>>> the destination origin server [...], until the connection is closed.
>> The "until the connection is closed" part is misleading and inaccurate.
>> There are two connections in a CONNECT tunnel: (a) between a CONNECT
>> sender and CONNECT recipient and (2) between CONNECT recipient the the
>> next HTTP hop. The tunnel termination condition is rather complex and is
>> detailed later in the same section. It may be a good idea to drop the
>> "until..." part. At least I cannot suggest a way to describe it
>> correctly as an ending of an already long sentence :-).
> Changed to "until the tunnel is closed".
>>> When a tunnel intermediary detects that either side has closed its
>>> connection, any outstanding data that came from that side will first
>>> be sent to the other side and then the intermediary will close both
>>> connections. If there is outstanding data left undelivered, that data
>>> will be discarded.
>> These "will"s should be rephrased as intermediary MUSTs IMO. I also
>> suggest moving them higher, before the informal risk discussion.
> Moved, fixed, and rephrased to "A tunnel is closed when ..."
>>> A client MUST NOT send header fields in a TRACE request containing
>>> sensitive data
>> The above rule seems too onerous to proxies. Replace "MUST NOT send"
>> with "MUST NOT generate"?
> Fixed.
>>> Use of the 100 (Continue) Status
>>> Requirements for HTTP/1.1 clients:
>>> ...
>>> Requirements for HTTP/1.1 proxies:
>> Should we explicitly exclude proxies from the first group of
>> requirements by saying "Requirements for user agents" instead of
>> "Requirements for clients"?
> No, the first set applies to proxies that want to use 100-continue
> for their own reasons.
>>> MUST contain an updated Max-Forwards field with a value decremented by one (1).
>> A lot of proxies violate this MUST because they cannot grok and, hence,
>> cannot decrement large integer values. Interoperability problems might
>> happen when a client generates Max-Forwards with a maximum value it can
>> store (e.g., to count the number of hops to the origin server) but the
>> proxy cannot store such a large value (e.g., 64bit vs 32bit).
>> Perhaps we can relax this rule by allowing proxies to decrement by "at
>> least one", so that a huge value can be replaced with the maximum value
>> the proxy can represent?
> Changed to
>    If the received Max-Forwards value is greater than zero,
>    the intermediary MUST generate an updated Max-Forwards field
>    in the forwarded message with a field-value that is the lesser of:
>    a) the received value decremented by one (1), or
>    b) the recipient's maximum supported value for Max-Forwards.

Isn't Max-Forwards used for sending OPTIONS and such to a specific hop?

I know these limits are theoretically supposed to be absurdly high. But 
if the implementation decided that the limit would be 2 or something the 
above rules would break tracing. For example the client would get back a 
constant response gnenerated from hop X+2 when it was querying hop X+3 
to X+N.

I think an error response would be better if Max-Forwards is bigger than 
the implementation can support.

FWIW: there are big-math tricks that can be implemented to increment or 
decrement arbitrarily large numeric values using a counter counter as 
small as 8-bit if neccesary so while the speed issue is relevant the 
X-bit overflow shodul not be. The old Co-Advisor test for this was to 
send a 72-bit numeric value in the header and expect successful decrement.