Date: Tue, 01 May 2001 18:35:41 +0900
From: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
| however, it is not always possible to know peer's address beforehand:
| - we don't always know peer's address (think about linklocal address
| - fe80::/10), and
| - we don't run NS/NA on L2 without hardware address, so
| - we don't know the peer's address.
Then what use is installing the route? If you don't know the link
local address of the remote end, simply don't install a route to it.
On a p2p link the only people who are going to be able to send to a
link local addr are the 2 end points, by definition you don't know his
address to send to, thus you can't be sending any packets to him.
If he sends packets to you (hoping that you will loop them back to him)
then whether you fail to do that because of your proposed rule that
makes a special case for p2p links, or whether you do it because there's
no route to his link local, seems to make little practical difference.
If you do, via a routing protocol, or any other way, manage to discover
what the remote end's LL address is for the P2P link, then you can install
the route, and then you would be able to send to it.
| actually, "use the default route" can be dangerous here.
Yes, without doubt, default routes cause problems (they also make life
easy, so they're not going away...)
| i hope to help people configure the boxes right,
| but if there are millions people (i guess there will be) i can't
| keep up.
Certainly the default setup, what "just happens" should be the safe way.
I'm even trying hard to imagine what kind of config screwup could cause
the effects that you are describing (though I guess we should have considered
that as a likely possibility back when the coin toss was made to decide
whether NS etc would be an ICMP protocol or a link level protocol (like ARP)).
The point is that if you force the safe way, rather than just defaulting
to it, you immediately kill the possibility that some future clever
invention can ever be made to work. If people just need to change their
configs to allow something new it is easy - but if code changes need to be
made, it gets so hard that the whole thing is a write-off.
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]
--------------------------------------------------------------------
