Re: [Technical Errata Reported] RFC5225 (2703)

Similar to Kristofer, I am also no longer subscribed to the ROHC list and no 
longer follow discussions in that forum. I also agree with the proposed 
update.

///Ghyslain

--------------------------------------------------
From: "Kristofer Sandlund" <[email protected]>
Sent: Thursday, February 03, 2011 8:26 AM
To: "Lars Eggert" <[email protected]>; <[email protected]>
Cc: "David Harrington" <[email protected]>; <[email protected]>
Subject: RE: [Technical Errata Reported] RFC5225 (2703)

> Ongoing discussion? I'm no longer subscribed to the rohc list (and I'm 
> quite sure my co-author doesn't read it either), so I don't know of 
> anything that has been discussed there.
>
> But I have previously discussed the below issue with Calle and I agree 
> with his suggested update.
>
> /Kristofer
>
> at den 3 februari 2011 13:52, Lars Eggert wrote :
>> Based on the ongoing discussion, I assume the community
>> consensus is to approve this?
>>
>> On 2011-2-3, at 14:22, RFC Errata System wrote:
>>
>> >
>> > The following errata report has been submitted for
>> > RFC5225, "RObust Header Compression Version 2 (ROHCv2):
>> > Profiles for
>> RTP, UDP, IP, ESP and UDP-Lite".
>> >
>> > --------------------------------------
>> > You may review the report below and at:
>> > http://www.rfc-editor.org/errata_search.php?rfc=5225&eid=2703
>> >
>> > --------------------------------------
>> > Type: Technical
>> > Reported by: Carl Knutsson <[email protected]>
>> >
>> > Section: 6.6.11
>> >
>> > Original Text
>> > -------------
>> > o  ip_id_behavior, one octet for each IP header in the
>> > compressible
>> >
>> >   header chain starting from the outermost header.
>> > Each octet
>> >
>> >   consists of 2 bits padded with 6 MSBs of zeroes.
>> >
>> > Corrected Text
>> > --------------
>> > o  ip_id_behavior_outer, one octet for each IPv4 header
>> > except the
>> >
>> >   innermost in the compressible header chain starting
>> > from
>> the outermost
>> >
>> >   header. Each octet consists of 2 bits padded with 6
>> > MSBs
>> of zeroes.
>> >
>> >
>> >
>> > o  ip_id_behavior_innermost, one octet if the innermost
>> header is an
>> >
>> >   IPv4 header. The octet consists of 2 bits padded with
>> > 6
>> MSBs of zeroes.
>> >
>> > Notes
>> > -----
>> > There is no control field called ip_ip_behavior in the
>> document. There are two control fields related to IP-ID
>> behavior, ip_id_behavior_innermost and
>> ip_id_behavior_outer. For IPv6, only the
>> ip_id_behavior_innermost field exists and its value is
>> always IP_ID_BEHAVIOR_RANDOM according to the FN. This
>> makes it impossible to include ip_id_behavior_outer when
>> calculating the crc for IPv6 headers. Furthermore, since
>> the ip_id_behavior_innermost is constant it makes no
>> sense to include it in the crc calculation.
>> >
>> > Instructions:
>> > -------------
>> > This errata is currently posted as "Reported". If
>> > necessary, please use "Reply All" to discuss whether it
>> > should be verified or rejected. When a decision is
>> > reached, the verifying party (IESG) can log in to
>> > change the status and edit the report, if necessary.
>> >
>> > --------------------------------------
>> > RFC5225 (draft-ietf-rohc-rfc3095bis-rohcv2-profiles-06)
>> > --------------------------------------
>> > Title               : RObust Header Compression Version
>> > 2
>> (ROHCv2): Profiles for RTP, UDP, IP, ESP and UDP-Lite
>> > Publication Date    : April 2008
>> > Author(s)           : G. Pelletier, K. Sandlund
>> > Category            : PROPOSED STANDARD
>> > Source              : Robust Header Compression
>> > Area                : Transport
>> > Stream              : IETF
>> > Verifying Party     : IESG