| To: | "David S. Miller" <davem@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] IPv6: Fix Prefix Length of Link-local Addresses |
| From: | Derek Fawcus <dfawcus@xxxxxxxxx> |
| Date: | Thu, 10 Oct 2002 00:29:02 +0100 |
| Cc: | sekiya@xxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, usagi@xxxxxxxxxxxxxx |
| In-reply-to: | <20021009.161414.63434223.davem@redhat.com>; from davem@redhat.com on Wed, Oct 09, 2002 at 04:14:14PM -0700 |
| References: | <20021009170018.H29133@edinburgh.cisco.com> <uwuor9tg7.wl@sfc.wide.ad.jp> <20021009234421.J29133@edinburgh.cisco.com> <20021009.161414.63434223.davem@redhat.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Wed, Oct 09, 2002 at 04:14:14PM -0700, David S. Miller wrote: > > I think the change was made because some TAHI test > failed without it, USAGI people is this right? > > Most of USAGI changes are of this nature. :-) There are areas where the TAHI tests expect a certain behaviour when more than one behaviour is acceptable. As I recall there is an issue around the behaviour of a packet being received with a zero length payload. The TAHI tests seem to expect one type of ICMPv6 response, whereas depending upon the value of next header and the order in which header field validations occur, two different types of ICMP error can be generated. Specifically parameter problem identifying the payload field or the next header field. I seem to remember this being triggered when a jumbo header is received by a node that doesn't understand jumbograms. DF |
| Previous by Date: | Re: [PATCH] IPv6: Fix Prefix Length of Link-local Addresses, David S. Miller |
|---|---|
| Next by Date: | Re: [PATCH] IPv6: Fix Prefix Length of Link-local Addresses, David S. Miller |
| Previous by Thread: | Re: [PATCH] IPv6: Fix Prefix Length of Link-local Addresses, David S. Miller |
| Next by Thread: | Re: [PATCH] IPv6: Fix Prefix Length of Link-local Addresses, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |