Hi Derek,
> The contents of the 54 bits are only a should,  as such one can use whatever
> one wants in there.
        Where did you get/see the SHOULD? Please point me to the right location in 
RFC3513 which says this, because I can't find anything like that. All I see in an 
unambiguous/unconditional ascii art picture in section 2.5.6 with 0s in these 54 bits. 

Regards
Suresh


-----Original Message-----
From: Derek Fawcus [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 27, 2003 12:19 PM
To: [EMAIL PROTECTED]
Subject: Re: What is the length of the Link-Local prefix?


On Wed, Aug 27, 2003 at 09:57:23AM -0500, Suresh Krishnan (QB/EMC) wrote:
> Hi Chirayu,
>       No. You cannot use fe81::/16 as a link local address

Of course you can.

> Even though the RFC states that the prefix is fe80::/10 it really should be 
> fe80::/64. Section 2.5.6 of RFC3513 explicitly states that the 54 bits following 
> 1111111010 should be set to 0 and thus the only allowable prefix is fe80::/64.

The contents of the 54 bits are only a should,  as such one can use whatever
one wants in there.

Nothing breaks (wrt normal LL address usage) if those 54 bits have non zero
values.

Certainly a given platform shouldn't object to finding non zero values in
a LL packet it receives (e.g. say a src address of fe80:1910::10).

DF
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
--------------------------------------------------------------------
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]
--------------------------------------------------------------------

Reply via email to