Re: RoHC Profile 4 Static chain termination
Vivek Soni <[email protected]> Sat, 2 Apr 2011 14:58:40 +0900
| Newsgroups | gmane.ietf.rohc |
|---|---|
| Message-ID | <[email protected]> |
--===============0621392109== Content-Type: multipart/alternative; boundary=bcaec543192ce7ede2049fe937e7 --bcaec543192ce7ede2049fe937e7 Content-Type: text/plain; charset=ISO-8859-1 Hello Carl, Thanks for the clarification. As I understand from your reply, 1. If the static chain is implicitly terminated by the next header field, the compressor MAY or MAY NOT mark the MSB. In case the compressor does marks the MSB, it just becomes redundant and is not a problem. 2. In case the compressor tries to compress only few IP headers, it explicitly marks the MSB to indicate the end of static chain. I felt the text of RFC 3843 section 3.1 is not very clear about this. Hence the confusion. Regards, Vivek On Mon, Mar 28, 2011 at 10:43 PM, Carl Knutsson <[email protected]>wrote: > Hi Vivek, > > I guess you are referring to profile 0x0004 in RFC 3843 section 3.1. > > I don't think I understand exactly what you are trying to change or > clarify with your suggestion. > > The version field MSB is used to terminate the static chain when it > isn't implicitly given by the next header/protocol field. For example if > you want to compress only the IPv4 header for an IPv4/IPv6 packet. Or do > you want to disqualify the use of the version field static chain > termination in those cases were the end is implicitly given by the > protocol field? In that case the MSB in the IP version field may be > redundant but the compression will function correctly. > In any case I can't really see that this requires a correction or > clarification to the RFC. > > Note that this RFC that was published some years ago, so we are not > likely to change it for smaller editorial fixes. We could file an > errata, but at this point I can't see anything in the static chain > termination section that needs a clarification or correction. > > cheers, > > /Calle > > > On 03/28/2011 04:24 AM, Vivek Soni wrote: > > 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 > > > > > > > > _______________________________________________ > > Rohc mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/rohc > > --bcaec543192ce7ede2049fe937e7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello Carl,<div><br></div><div>Thanks for the clarification.=A0As I underst= and from your reply,</div><div><br></div><div>1. If the static chain is imp= licitly terminated by the next header field, the compressor MAY or MAY NOT= =A0mark the MSB.=A0</div> <div>In case the compressor does marks the MSB, it just becomes redundant a= nd is not a problem.</div><div><br></div><div>2. In case the compressor tri= es to compress only few IP headers, it explicitly marks the MSB to indicate= the end of=A0static chain.</div> <div><br></div><div>I felt the text of=A0=A0RFC 3843 section 3.1 is not ver= y clear about this. Hence the confusion.</div><div><br></div><div>Regards,<= /div><div>Vivek</div><div><br><br><div class=3D"gmail_quote">On Mon, Mar 28= , 2011 at 10:43 PM, Carl Knutsson <span dir=3D"ltr"><<a href=3D"mailto:c= [email protected]">[email protected]</a>></span> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex;">Hi Vivek,<br> <br> I guess you are referring to profile 0x0004 in RFC 3843 section 3.1.<br> <br> I don't think I understand exactly what you are trying to change or<br> clarify with your suggestion.<br> <br> The version field MSB is used to terminate the static chain when it<br> isn't implicitly given by the next header/protocol field. For example i= f<br> you want to compress only the IPv4 header for an IPv4/IPv6 packet. Or do<br= > you want to disqualify the use of the version field static chain<br> termination in those cases were the end is implicitly given by the<br> protocol field? In that case the MSB in the IP version field may be<br> redundant but the compression will function correctly.<br> In any case I can't really see that this requires a correction or<br> clarification to the RFC.<br> <br> Note that this RFC that was published some years ago, so we are not<br> likely to change it for smaller editorial fixes. We could file an<br> errata, but at this point I can't see anything in the static chain<br> termination section that needs a clarification or correction.<br> <br> cheers,<br> <br> /Calle<br> <div><div></div><div class=3D"h5"><br> <br> On 03/28/2011 04:24 AM, Vivek Soni wrote:<br> > Hello,<br> ><br> > I understand that the compressor can terminate the static chain at any= <br> > header by explicity setting the MSB of version field. But I am not cle= ar<br> > when exactly should compressor do this.<br> ><br> > My understanding is that it is applicable only when there are multiple= <br> > IP headers and compressor decides to compress only few of them.<br> ><br> > Whereas in other cases for example<br> > 1. The packet has only one IP header ("Protocol"/"next = header" field is<br> > other than IPinIP or IPv6)<br> > 2. The packet has multiple IP headers and the compressor compresses al= l<br> > of them.<br> ><br> > In both these cases, the static chain termination is implicit. Therefo= re<br> > the compressor need not (SHOULD NOT)<br> > indicate the end of static chain explicitly by setting MSB of version = field.<br> ><br> > Is this understanding of mine correct. In that case, would be it be<br= > > better if RFC is more clear about it by using<br> > stronger text like "SHOULD NOT" instead of "Alternative= ly".<br> ><br> > Regards,<br> > Vivek<br> ><br> ><br> ><br> </div></div>> _______________________________________________<br> > Rohc mailing list<br> > <a href=3D"mailto:[email protected]">[email protected]</a><br> > <a href=3D"https://www.ietf.org/mailman/listinfo/rohc" target=3D"_blan= k">https://www.ietf.org/mailman/listinfo/rohc</a><br> <br> </blockquote></div><br></div> --bcaec543192ce7ede2049fe937e7-- --===============0621392109== 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 --===============0621392109==--