RE: what problem is solved by proscribing non-64 bit prefixes?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: what problem is solved by proscribing non-64 bit prefixes?
- To: <alexandru.petrescu at gmail.com>, <pekkas at netcore.fi>
- Subject: RE: what problem is solved by proscribing non-64 bit prefixes?
- From: <michael.dillon at bt.com>
- Date: Fri, 3 Oct 2008 10:58:52 +0100
- Cc: ksherman at mitre.org, ipv6 at ietf.org, rbonica at juniper.net, Steve_Eiserman at ao.uscourts.gov, Pasi.Eronen at nokia.com, cemartin at mitre.org, draft-ietf-v6ops-addcon at tools.ietf.org, ralph.liguori at disa.mil, night at nist.gov, dougm at nist.gov, v6ops-chairs at tools.ietf.org, brian.e.carpenter at gmail.com
- Delivered-to: ietfarch-ipv6-web-archive at core3.amsl.com
- Delivered-to: ipv6 at core3.amsl.com
- In-reply-to: <48E4C365.6090603 at gmail.com>
- List-archive: <https://www.ietf.org/mailman/private/ipv6>
- List-help: <mailto:ipv6-request@ietf.org?subject=help>
- List-id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
- List-post: <mailto:ipv6@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
- Sender: ipv6-bounces at ietf.org
- Thread-index: AcklOspPz71xeD1iS/GwmqlJDyF74gAA2B4A
- Thread-topic: what problem is solved by proscribing non-64 bit prefixes?
> I'm aware of several IEEE link layers and none uses 64bit addresses.
> IEEE tries to have them all 48bit. Even non-IEEE (like USB)
> tries to be 48bit.
Have you ever heard of EUI-64?
<http://standards.ieee.org/regauth/oui/tutorials/EUI64.html>
One notable IEEE protocol which uses EUI-64 is Firewire (IEEE 1394). For
more info see RFC 3146.
--Michael Dillon
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6 at ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.