Date: Thu, 26 Apr 2001 15:15:30 +0900
From: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
| which one is wrong. my original queestion is, "if we are taking
| cisco model, (P::/64 points to p2p interfaces), what is the right
| behavior for us?"
Just forward the packet.
If there is a mis-config, and a routing loop happens, the packet will
ping pong till the hop count expires, then be trashed. Other than
deliberate DoS attacks, there shouldn't be many of these. Where there's
no response, apps will try again for a short while, then generally they
give up, and eventually some human debugs .. seeing the ping pong from
a traceroute is a dead easy way to identify the problem - much easier
than having to try to figure out why that other router over there is
claiming there's no route (especially when I can see the route in its
routing table when I look).
Further, forwarding the packet allows the behaviour of nodes that
deliberately send packets to themselves in order to test correct
functioning of the link.
It's relatively harmless, eliminates the need for a special case test,
and actually easier to diagnose.
So, just send the packet (send a redirect if you want as well).
kre
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
