RoHC Profile 4 Static chain termination
Vivek Soni <[email protected]> Mon, 28 Mar 2011 11:24:02 +0900
| Newsgroups | gmane.ietf.rohc |
|---|---|
| Message-ID | <[email protected]> |
--===============0475902908==
Content-Type: multipart/alternative; boundary=20cf303ea6ea135fca049f81a3a7
--20cf303ea6ea135fca049f81a3a7
Content-Type: text/plain; charset=ISO-8859-1
Hello,
I understand that the compressor can terminate the static chain at any
header by explicity setting the MSB of version field. But I am not clear
when exactly should compressor do this.
My understanding is that it is applicable only when there are multiple IP
headers and compressor decides to compress only few of them.
Whereas in other cases for example
1. The packet has only one IP header ("Protocol"/"next header" field is
other than IPinIP or IPv6)
2. The packet has multiple IP headers and the compressor compresses all of
them.
In both these cases, the static chain termination is implicit. Therefore the
compressor need not (SHOULD NOT)
indicate the end of static chain explicitly by setting MSB of version field.
Is this understanding of mine correct. In that case, would be it be better
if RFC is more clear about it by using
stronger text like "SHOULD NOT" instead of "Alternatively".
Regards,
Vivek
--20cf303ea6ea135fca049f81a3a7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div>Hello,</div><div><br></div><div><div>I understand that the compressor =
can terminate the static chain at any header by explicity setting=A0the MSB=
of version field. But I am not clear when exactly should compressor do thi=
s.=A0</div>
<div><br></div><div>My understanding is that it is applicable only when the=
re are multiple IP headers and compressor decides to=A0compress only few of=
them.=A0</div><div><br></div><div>Whereas in other cases for example</div>
<div>1. The packet has only one IP header ("Protocol"/"next =
header" field is other than IPinIP or IPv6)</div><div>2. The packet ha=
s multiple IP headers and the compressor compresses all of them.</div><div>
<br></div><div>In both these cases, the static chain termination is implici=
t. Therefore the compressor need not (SHOULD NOT)=A0</div><div>indicate the=
end of static chain explicitly by setting MSB of version field.</div><div>
<br></div><div>Is this understanding of mine correct. In that case, would b=
e it be better if RFC is more clear about it by using</div><div>stronger te=
xt like "SHOULD NOT" instead of "Alternatively".</div>
<div><br></div><div>Regards,</div><div>Vivek</div></div><div><br></div>
--20cf303ea6ea135fca049f81a3a7--
--===============0475902908==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Rohc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/rohc
--===============0475902908==--