|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Manral, Vishwas (VishwasM_at_NETPLANE.COM)
Date: Tue Feb 18 2003 - 06:35:33 CST
Hi Yasu,
You are right about "FE80" part of it. Good catch !!!
However two small corrections in what you said. The 11th to the 64th bit are
all 0's(54 bits in all). Besides even in the latest architecture draft
http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-addr-arch-v3-11.txt
Link-local unicast is still defined as
Link-local unicast 1111111010 FE80::/10 2.5.6
Check section 2.4
Thanks,
Vishwas
-----Original Message-----
From: Yasuhiro Ohara [mailto:yasu
SFC.WIDE.AD.JP]
Sent: Tuesday, February 18, 2003 5:51 PM
To: OSPF
DISCUSS.MICROSOFT.COM
Subject: typo in RFC2740 about link-local unicast address
In RFC 2740 section 2.5 "Use of link-local addresses" I might have
found a typo ...
IPv6 link-local addresses are for use on a single link, for purposes
of neighbor discovery, auto-configuration, etc. IPv6 routers do not
forward IPv6 datagrams having link-local source addresses [Ref15].
Link-local unicast addresses are assigned from the IPv6 address range
FF80/10.
Link-local unicast addresses are fe80::/64, aren't they ?
E -> F may be typo, but the prefix length may be a consideration.
# RFC2373 says that bits from 11th to 54th in link-local unicast address
# must be zero.
Sorry if it's already pointed out.
regards,
yasu
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]