Hi Markku, I totally agree with you on this.
As there is no way to distinguish between an IPv6 extension header and an upper layer header (TCP/ UDP) there is no way to find this out. Also the upper layer header is not be IPv6 specific, but common for IPv4 and IPv6. Thanks, Vishwas On Thu, Mar 20, 2008 at 1:21 PM, Markku Savela <[EMAIL PROTECTED]> wrote: > > > From: Suresh Krishnan <[EMAIL PROTECTED]> > > > Manfredi, Albert E wrote: > > >> " o Extension headers must be processed in any order they appear" > > > > > > Why isn't the wording in RFC 2460 even clearer? Quoting: > > > > > > Therefore, extension headers must > > > be processed strictly in the order they appear in the packet; a > > > receiver must not, for example, scan through a packet looking for a > > > particular kind of extension header and process that header prior to > > > processing all preceding ones. > > > > It is very clear. And that is exactly the problem I am talking about in > > the draft. The real issue is that when you reach an unknown header of an > > unknown format you have no way of proceeding any further with the > > processing. The text Hemant was quoting is not from the meat of the > > draft but from the future work section. > > And, if you hit unknown header, there is *NO WAY* to skip over it. You > have no idea whether it is an extension header (following the standard > format), or something totally different. > > This seems moot all text in the draft... > > -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
