>> Alexandru Petrescu wrote: >> I'm very curious if the suggested recommendation is really >> "no more than 64" or is it "exactly 64"?
> kre wrote: > It is currently probably exactly 64 - but there's no > reason for that. Actually, there are, but I will not get into that again. "more than 64" is not even debatable. "exactly 64" is today's status for most IPv6 addresses. "no more than 64" has some good arguments for it, mostly the following one: > A link layer that doesn't have a use for all 64 bits > shouldn't be required to pad them for no reason This is especially true with NBMA technologies such as frame relay, when using the MAC address of e0 on s0 is not always the best thing to do. My take on it is: IPv6 over ethernet: stick to exactly /64. Probably for TR and FDDI too. IPv6 over foo: it might be desirable to get a lower value (make it fit on a nibble or byte boundary) _if_ accompanied by RFC2373 modifications or new text that define a fixed aggregation boundary for routing purposes. Subneting below /64 must have defined boundaries just like above /64. Michel. -------------------------------------------------------------------- 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] --------------------------------------------------------------------
