Mark,

> Why does this method have to be limited to SLAAC, or rather, wouldn't 
> describing it as SLAAC related imply that this or a similar technique can't 
> be used with DHCPv6 or any other address configuration methods?
> 
> While DHCPv6 assigned addresses are naturally per-subnet, I'd think the IID 
> generation techniques described should be an option for DHCPv6 provided 
> addresses e.g., different IIDs are generated for different subnets by the 
> DHCPv6 server even when the client provides the same DUID.
> 
> It's starting to seem to me that more clearly separating address generation 
> methods from address configuration methods would be worth while. If I 
> statically configure an address that complies with this algorithm (perhaps 
> because my host doesn't yet implement the SLAAC method of configuring them), 
> is it a "stable privacy address" (or what ever name it ends up with)? In 
> practice I'd probably still call it a "stable privacy address".

That's a good point, the same issues apply to SLAAC and DHCPv6 generated 
addresses.  The next version of Privacy Considerations for IPv6 Address 
Generation Mechanisms will hopefully address the issues in DHCP.

Regarding the title, of this draft, how about:

  Stable Temporary Per-Subnet Interface Identifiers

My thinking behind this suggestion is that the draft is about a new type of 
Interface Identifiers, addresses are somewhat separate.  The are temporary as 
they are not tied to a hardware token like an IEEE MAC address.  They are 
stable as they intended to be used for a long while on the same subnet and 
don't change per connection/application.  It is a bit of an oxymoron :-)

Another choice:

  Pseudo-Random Per-Subnet Interface Identifiers

They are pseudo-random and intended to be used on a single subnet.

Personally, I would prefer something like these titles because "privacy" is 
once of several characteristics and the privacy characteristic depend a lot on 
how they are used and other factors like if they are put in the DNS, shared at 
the application layer, the prefix remains constant, etc.

Bob



 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to