logo       
Google Custom Search
    AddThis Social Bookmark Button
-->

Re: protocol field according to RFC1661: msg#00011

Subject: Re: protocol field according to RFC1661
At 08:07 PM 3/29/2004, Pavel Zeldin wrote:
RFC1661 states (page 6):
"The Protocol field is one or two octets,.."
and further down
"the least significant bit of the least significant octet MUST
equal "1".  Also, all Protocols MUST be assigned such that the
least significant bit of the most significant octet equals "0"."

This does not quite work when protocol field is only one octet.

The Protocol Field is one octet only when Protocol Field Compression is applied (see section 6.5), which means the most significant octet of the Protocol ID is zero and has been omitted.

John




_______________________________________________
Pppext mailing list
Pppext@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/pppext


_______________________________________________
Pppext mailing list
Pppext@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/pppext



<Prev in Thread] Current Thread [Next in Thread>