Re: [Int-area] Resubmit - requesting WG Adoption draft-moskowitz-intarea-schc-ip-protocol-number

[Robert Moskowitz <[e-mail]>]

Oh, and although HIP has NH as the first byte in its header, that is NOT 
for something within the HIP datagram.  Rather this was a design to 
allow a "Piggybacking" of something else after HIP within the IP 
datagram.  For example a HIP R2 packet can have a NH of ESP where the 
ESP is in transport mode carrying a TCP SYN to start the TCP exchange, 
thus saving one packet in the exchange.



On 9/7/22 17:35, Joel Halpern wrote:
> My reading of 8200 is that an extension header MUST start with a one 
> byte "Next Header" field.  SCHC does not.  Therefore, it is a carried 
> / upper layer protocol, not an extension header.  Much like IPv6 (in 
> IPv6).  Or UDP (with carrying an application protocol or carrying some 
> routing header like GRE, LISP, ...) or ...
>
> Yours,
>
> Joel
>
> PS: I grant we are not fully consistent in this regard.  ESP does not 
> have a next-header field.  (AH does).   But if we are going to pretend 
> that some headers are extensions headers and some are not, we should 
> try to be consistent with the description in 8200 (and 2460).
>
> On 9/7/2022 4:57 PM, Robert Moskowitz wrote:
>>
>>
>> On 9/7/22 16:35, Carsten Bormann wrote:
>>> On 7. Sep 2022, at 22:04, Bob Hinden <[e-mail]> wrote:
>>>> To clarify my question, it only relates to if SCHC should be added 
>>>> to the IPv6 Extension Header Types registry.   I continue to think 
>>>> that adding it to the IP Protocol Number registry is fine.
>>> I believe the answer should be the same as for 142 (RFC 5858), which 
>>> is not in the list.
>>>
>>> I couldn’t find out quickly what an IPv6 Extension Header Type 
>>> is(*), so maybe that is an oversight for 142.
>>
>> From my limited understanding and which Protocols are listed as 
>> Extension Header Types and which not (other than 142), it is a 
>> Protocol that transports other Protocols.
>>
>> Though with that definition, I wonder how HIP got in the list.
>>
>> It is fun to open a can of worms!
>>
>>>
>>> Grüße, Carsten
>>>
>>> (*) An IP protocol number, apparently.
>>> But what specifically does it make an IPv6 Extension Header Type as 
>>> well?
>>> The references given in the registry don’t seem to say.
>>>
>>
>> _______________________________________________
>> Int-area mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/int-area