[Top] [All Lists]

Re: [PATCH] IPv6: Fix Prefix Length of Link-local Addresses

To: Yuji Sekiya <sekiya@xxxxxxxxxxxxxx>
Subject: Re: [PATCH] IPv6: Fix Prefix Length of Link-local Addresses
From: Derek Fawcus <dfawcus@xxxxxxxxx>
Date: Wed, 9 Oct 2002 23:44:21 +0100
Cc: linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, usagi@xxxxxxxxxxxxxx
In-reply-to: <uwuor9tg7.wl@xxxxxxxxxxxxxx>; from sekiya@xxxxxxxxxxxxxx on Thu, Oct 10, 2002 at 06:46:16AM +0900
References: <20021008.000559.17528416.yoshfuji@xxxxxxxxxxxxxx> <20021009170018.H29133@xxxxxxxxxxxxxxxxxxx> <uwuor9tg7.wl@xxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On Thu, Oct 10, 2002 at 06:46:16AM +0900, Yuji Sekiya wrote:
> At Wed, 9 Oct 2002 17:00:18 +0100,
> Derek Fawcus <dfawcus@xxxxxxxxx> wrote:
> > Without reading the kernel routing table code a bit more,  I'm not certain
> > what that change does,  but it looks as if it might be changing the
> > connected route for a link local from fe80::/10 to fe80::/64.
> Why do you want to use /10 prefix for link-local address ?
> RFC2373 defines link-local address format as below.

It also states that all fe80::/10 are link local and all fec0:/10 are
site local (sect 2.4)

>    |   10     |
>    |  bits    |        54 bits          |          64 bits           |
>    +----------+-------------------------+----------------------------+
>    |1111111010|           0             |       interface ID         |
>    +----------+-------------------------+----------------------------+

and for site local it says use the following:

   |   10     |
   |  bits    |   38 bits   |  16 bits  |         64 bits            |
   |1111111011|    0        | subnet ID |       interface ID         |

whereas draft-ietf-ipngwg-addr-arch-v3-10.txt says:

   |   10     |
   |  bits    |         54 bits         |         64 bits            |
   |1111111011|        subnet ID        |       interface ID         |

So we've already changed what is recommended in the top bits for site
local,  if someone can think of a use for the top bits in link local
they'll probably be defined.  (Do you arbitrarily restrict the bits
in site local addresses?)

However link locals are a bit different.  Once you have matched fe80:/10
then by definition the rest of the address specifies a directly
connected neighbour.  As that's what link locals are - host routes
to directly connected neighbours.  There isn't really a connected
prefix as such,  that is only there to trigger ND.

Making a restriction that all link local neighbour entries have to match
fe80::/64 rather than the full fe80::/10 is pointless,  it gains nothing
and makes an arbitrary restriction for no real purpose.

> > All link local's are currently supposed to have those top bits
> > ('tween 10 and 64) zero'd,  however any address within the link local
> > prefix _is_ on link / connected and should go to the interface.
> If you wan to use /10 prefix for link-local address, you can add the
> link-local address with /10 prefix to interfaces and routing table
> manually at your own risk, but it should not  be a default behavior.

My point is that it isn't really a route.  Once you've matched fe80::/10
then you know that you've got a link local address,  and you switch
to looking up a connected neighbour entry in the conceptual neighbour

Other than allowing the use of the whole address field,  the only
difference in behaviour between the two forms would possibly
be in the type of ICMPv6 error generated for a non existant neighbour
addressed by a link local with those high bits set.

If the prefix to match link locals is /10 then type 1 code 3 would
be generated,  whereas if /64 is used (together with a /10 drop) then
type 1 code 0 would be generated.

Anyway,  I'll not bother following up again in this thread.

If you don't see the point,  then forget it.


<Prev in Thread] Current Thread [Next in Thread>