[ipv6-wg] IPv6 on P2P links

Gunter Van de Velde (gvandeve) wrote on 26/05/2011 17:59:
> Some work a while ago was to deliver some considerations on address
> planning at IETF:
> http://tools.ietf.org/html/rfc5375
>
> As you mention the /64 has for P2P a severe issue due to no ND process
> the
> Link resulting in ping-pong problem, and by doing that I have tested I
> can
> generate spikes of few Gig on a p2p with a single laptop connection,
> which is
> quite unfortunate. Imho this is the biggest driver for the /127 on a p2p
> connection
> from technological perspective.
>    
>
Shouldn't that (the ping-pong problem) be avoided by default, according 
to (standards track) RFC 4443?

If the reason for the failure to deliver cannot be mapped to any of
    other codes, the Code field is set to 3.  Example of such cases are
    an inability to resolve the IPv6 destination address into a
    corresponding link address, or a link-specific problem of some sort.

    One specific case in which a Destination Unreachable message is sent
    with a code 3 is in response to a packet received by a router from a
    point-to-point link, destined to an address within a subnet assigned
    to that same link (other than one of the receiving router's own
    addresses).  In such a case, the packet MUST NOT be forwarded back
    onto the arrival link.


--
Tassos