Suresh Krishnan wrote:
Hi Folks,
Some RFCs (I know of at least 2, RFC2526 and RFC4214) reserve a set of interface identifiers on all prefixes. These identifiers need to be excluded when a node autoconfigures an address. This problem occurs with privacy addresses but is equally applicable to other address assigment methods like dhcpv6, cga etc. As Bernie suggested in a mail it would be good to maintain a list of such identifiers. This is possible by either listing the currently assigned IIDs in a document, or by creating an IANA registry. The former is useful if there will be no such allocations in the future and the later is useful if there will be future allocations. I have written a draft regarding this and I was wondering if the wg considers this to be useful work worth pursuing. I would also like to know if there are any other RFCs/drafts which depend on using specific IIDs.

Not sure whether Teredo 64bit Node Identifier qualifies as something to be reserved by IANA, because it's variably derived from IPv4 address and port number. But the same is true with ISATAP as well, and you consider ISATAP.

I think two things are here:
-hardcoded IIDs: anycast rfc2526, maybe IPv6-over-linkswoMAC, other(?)
-list of methods to derive 64bit IIDs (EUI64, ISATAP, TEREDO, maybe
 IPv6-over-foo, maybe others).

I think only the hardcoded IIDs can be concerned by IANA reservation. The list of methods to derive 64bit IIDs is very good to maintain centrally, it's useful knowledge to many local designs.

Finally, isn't rfc2526 anycast address already assigned by IANA?

Alex


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email ______________________________________________________________________

--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to