#1: Proper source for an "Interface Identifier" Changes (by fg...@si6networks.com):
* status: new => closed * resolution: => fixed Comment: The "Interface Identifier" has now been replaced with a generic "Net_Iface" parameter, and we describe what are the required properties for this ID. Additionally, Appendix A is devoted to an analysis of possible sources for the Net_Iface parameter, and their pros and cons. From Section 3: RID = F(Prefix, Net_Iface, Network_ID, DAD_Counter, secret_key) [....] Net_Iface: An implementation-dependent stable identifier associated with the network interface for which the RID is being generated. An implementation MAY provide a configuration option to select the source of the identifier to be used for the Net_Iface parameter. A discussion of possible sources for this value (along with the corresponding trade-offs) can be found in Appendix A. [....] The Net_Iface is a value that identifies the network interface for which an IPv6 address is being generated. The following properties are desirable for the Net_Iface: o it MUST be constant across system bootstrap sequences and other network events (e.g., bringing another interface up or down) o it MUST be different for each network interface Since the stability of the addresses generated with this method relies on the stability of all arguments of F(), it is key that the Net_Iface be constant across system bootstrap sequences and other network events. Additionally, the Net_Iface must uniquely identify an interface within the node, such that two interfaces connecting to the same network do not result in duplicate addresses. Different types of operating systems might benefit from different stability properties of the Net_Iface parameter. For example, a client- oriented operating system might want to employ Net_Iface identifiers that are attached to the underlying network interface card (NIC), such that a removable NIC always gets the same IPv6 address, irrespective of the system communications port to which it is attached. On the other hand, a server-oriented operating system might prefer Net_Iface identifers that are attached to system slots/ ports, such that replacement of a network interface card does not result in an IPv6 address change. Appendix A discusses possible sources for the Net_Iface, along with their pros and cons. -- --------------------------------------+---------------------------- Reporter: fg...@si6networks.com | Owner: Fernando Gont Type: defect | Status: closed Priority: major | Milestone: Component: stable-privacy-addresses | Version: Severity: Active WG Document | Resolution: fixed Keywords: | --------------------------------------+---------------------------- Ticket URL: <http://tools.ietf.org/wg/6man/trac/ticket/1#comment:1> 6man <http://tools.ietf.org/wg/6man/> -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------