What RFC 2460 means (was: Re: RFC 2434 term "IESG approval" (Re: IANA Action: Assignment ofan IPV6 Hop-by-hop Option))

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

 




--On Wednesday, 06 July, 2005 17:28 +0200 Brian E Carpenter
<brc@xxxxxxxxxxxxxx> wrote:

>> It isn't really that bad, the option with 17 in the low 5
>> bits and 0 in the upper 3 is a different option than the one
>> with 17 in the low 5 bits and 7 in the upper 3.
>> 
>> So, really there are 8 distint groups of 32 options each.
> 
> Well, that is not how I read the text in RFC 2460. It's pretty
> clear
> to me that there are only 32 option codes and that the other
> three bits
> don't extend the code space, but rather they modify the
> meaning of the
> 32 basic options. (e.g. the same option can have a hop-by-hop
> flavour
> and an e2e flavour).

Brian,

Please set aside, at least temporarily, the issues that got us
to this point.   It seems to me that, if you and kre, both of
whom have considerable experience reading these sorts of
documents, can't agree on what 2460 means and how these bits are
to be interpreted, we have a really urgent need for some
clarification.

Can you get the appropriate AD to sign up for that job and get
it assigned to a WG as appropriate?

   john




_______________________________________________

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]