Thanks for the feedback on my routing header questions.
I think it would be meaningful to include an example of what I was
referring to in my original question..
Original source A
First hop B
2nd hop C
3rd hop D
Final Dest E
*
Roy Brabson/Raleigh/IBM wrote on 04/22/2004 09:46:15
AM:
> > > The only problematic case, as far as I can see, would be
ICMPv6 too
> > > big messages for path MTU discovery. In this case,
however, we can
> > > still update the MTU information gradually; we first update
the MTU
> > > information
> The only problematic case, as far as I can see,
would be ICMPv6 too
> big messages for path MTU discovery. In this case, however,
we can
> still update the MTU information gradually; we first update the MTU
> information to the intermediate destination stored in the destination
> address field
I have a question about Routing Headers
(type 0), more specifically what happens when we receive an ICMPv6 msg
where the offending packet contained a routing header. From RFC 3542,
a routing header can contain 127 IPv6 next hop addresses. Therefore,
if a packet specified the maximum number of e
T NOT be set if the NA is destined for a
multicast address.
Can you please clarify if a NA sent to all-nodes multicast address with
solicited bit ON is considered valid or invalid. Thanks!
Lori Napoli
IETF IPv6 working
