Hi, On Wed, Feb 12, 2003 at 05:16:21PM +0100, Gert Doering wrote:
but there is no need for a /64 here. => there is no choice in the standard: all prefixes on a link are /64s.
Please quote the RFC that *mandates* /64s for all links. As far as I remember, it's a SHOULD for multiaccess links, and voluntary for ptp links.
OK, I stand corrected, RFC 2373 actually doesn't differenciate between multiaccess and point-to-point links, and requires /64s on every single link (section 2.4 and 2.5.1). --- snip --- In a number of the format prefixes (see section 2.4) Interface IDs are required to be 64 bits long and to be constructed in IEEE EUI-64 format [EUI64]. --- snip --- While I agree that it is written in there, I won't change our current addressing scheme. /64s for point-to-point link is just so useless when compared to other schemes (like "encoding the peer AS number in the network part of the addresses used"). If one wants to do useful addressing with putting /64s on ptp links, it would mean "waste a /44 or so" on transit networks - which isn't permitted either. People, get real. This policy sucks big time. Change it if you cant't live with people not accepting it. (*All* this /64 stuff sucks big time, but for multiaccess networks with up-to-64 bit identifiers [firewire], it makes some certain amount of sense) Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 56029 (55671) SpaceNet AG Mail: netmaster@Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299