Manual Configuration of Interface ID

[Chad Kissinger]

Well, no other input yet, but through RFC 5375, I have compiled the following:

In manually choosing a 64 bit IPV6 Interface ID, you should follow the following rules (stated in terms of hexadecimal choices):

1.  Do not use all 0s. (interferes with Router Anycast)
2.  Do not use all 0s with one character at the end (interferes with Embedded-RP RFC 3956)
3.  Do not use all Fs followed by 80 through FF  I.e. do not use FFFF:FFFF:FFFF:FF80 through FFFF:FFFF:FFFF:FFFF (interferes with Anycast)
4.  Do not use something that begins with 0000:5EFE (interferes with ISATAP RFC5214)
5.  The second hexadecimal character of the 64 bit Interface ID must be 0, 4, 8 or C i.e. X8XX:XXXX:XXXX:XXXX where the 8 can be replaced with 0, 4 or C (71st and 72nd bit set to 0)


Any other input?  Corrections?  



chad kissinger  |  founder-vp  |  onramp access, llc 
p: 512.322.9200  |  f: 512.476.2878  |  www.onr.com
your internet operations  |  built  |  deployed  |  managed


-----Original Message-----
From: ipv6-ops-bounces+chad=onr.com at lists.cluenet.de [mailto:ipv6-ops-bounces+chad=onr.com at lists.cluenet.de] On Behalf Of Daniel Roesen
Sent: Monday, December 20, 2010 11:39 AM
To: ipv6-ops at lists.cluenet.de
Subject: Re: Manual Configuration of Interface ID

On Mon, Dec 20, 2010 at 11:27:53AM -0600, Chad Kissinger wrote:
> So, you are saying that I can choose any 64 bit combination for the
> Interface ID as long as the 71st and 72nd bits are 0.  Right?  

Except anycast, yes. I'm not aware of further limitations or
considerations, but this mailing list has more than 1000 subscribers,
let's wait for further input. :-)

Best regards,
Daniel

-- 
CLUE-RIPE -- Jabber: dr at cluenet.de -- dr at IRCnet -- PGP: 0xA85C8AA0