Hi, Suresh.
> >e.g., If all routers via which the packet goes have broken
> >(although it is a very rare case) and overlook the invalid
> >Hdr.Ext.Len, the trouble will happen.
>
> Even if we check the header length before checking the segments left we
> can still have a problem.
>
> >
> >e.g.
Hi Ootomo
See comments inline.
Regards
Suresh
On Thu, 20 May 2004, OOTOMO Hiroyuki wrote:
>Hi Shresh.
>
>> This packet will NEVER reach host-4. Consider the packet when it
>> reaches router-1
><<< snipped >>>
>> router-1 will follow the algorithm for RH processing. The Segments Left is
Hi Shresh.
> This packet will NEVER reach host-4. Consider the packet when it
> reaches router-1
<<< snipped >>>
> router-1 will follow the algorithm for RH processing. The Segments Left is
> greater than 0. So it will check the header ext len and find it to be odd.
> It will drop the packet an
Hi Ootomo,
See comments inline.
Regards
Suresh
On Tue, 18 May 2004, OOTOMO Hiroyuki wrote:
>Hi, all.
>
>I found a problem in RFC2460, about error processing of Routing Header.
>It does not define the behavior of End Node when the End Node received
>the packet which has odd Hdr.Ext.Len.
>
>
>(S
Hi, all.
I found a problem in RFC2460, about error processing of Routing Header.
It does not define the behavior of End Node when the End Node received
the packet which has odd Hdr.Ext.Len.
(Section 4.4)
>A Routing header is not examined or processed until it reaches the
>node identified
