On May 19, 2013, at 10:33 , Fernando Gont <[email protected]> wrote:
>
> The rev is available at:
> <http://tools.ietf.org/html/draft-ietf-6man-stable-privacy-addresses-07>.
>
> A diff from the previous version of the I-D is available at:
> <tools.ietf.org//rfcdiff?url1=http://tools.ietf.org/id/draft-ietf-6man-stable-privacy-addresses-06.txt&url2=http://tools.ietf.org/id/draft-ietf-6man-stable-privacy-addresses-07.txt>.
I have a problem with the following set of requirements:
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
Some hosts have dynamic logical network interfaces (distinguishable from
physical interface), which are created every time the host joins a network, and
destroyed when the host separates from a previously joined network. Examples
are typically interfaces that involve signaling systems, point-to-point
connection semantics for the link layer, e.g. virtual private networks,
automatic tunnels, et cetera.
According to these requirements, such hosts MUST NOT reuse previously generated
stable privacy addresses when joining the same network with a new logical
interface. That seems counter to the goal of this standard.
I think hosts need some latitude in these requirements to allow for temporally
different network interfaces associated with the same network service from the
host's view to have the same identity for the purpose of generating stable
privacy addresses.
--
james woodyatt <[email protected]>
core os networking
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
