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., If an evil node transmit the packet with odd Hdr.Ext.Len > >and zero Segment Left suddenly, the trouble will happen. > > The evil node can transmit the packet with an EVEN header ext len which is > WRONG and the new algorithm can still not catch it. So I guess it is not > worth it trying to change the algorithm as the cons outweigh the pros. I understand. My proposal will solve a half of this problem, but it will not clear the remaining half. It was not a wonderful solution to deserve to correct RFC. I will consider the better methods. Thank you. -- OOTOMO Hiroyuki <[EMAIL PROTECTED]> -------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
