IPv6 Type 0 Routing Header issues

Gert Doering gert at space.net
Wed Apr 25 12:10:01 CEST 2007


On Wed, Apr 25, 2007 at 10:46:54AM +0200, Remi Denis-Courmont wrote:
> On Wed, 25 Apr 2007 10:24:08 +0200, Gert Doering <gert at space.net> wrote:
> > Well, one could argue that the standard isn't very well-written then - a
> > machine that is a *host* should NEVER forward packets, period.
> That's a BSD bug, not a standard bug.
> The IPv6 specification says host must process RT0. It does not say they must
> forward packets as if they were routers on the sole basis of RT0 presence.
> By the current spec (as far as I understand), if a host receives a RT0, it
> must process it. Then it must apply the same rules to the "new" packet
> destination as it would do to any packet it receives; in particular, if the
> packet cannot be delivered locally, it is dropped. You do the exact same
> thing when you receive a packet from link-layer while you are not the
> destination at network-layer.

Thanks for the clarification.  Indeed, this explains the necessity to
process the RH0 header locally (it might point to a different address on the 
*same host*).

Gert Doering
        -- NetMaster
Total number of prefixes smaller than registry allocations:  113403

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 305 bytes
Desc: not available
Url : http://lists.cluenet.de/pipermail/ipv6-ops/attachments/20070425/a7b70ad1/attachment.bin

More information about the ipv6-ops mailing list