Re: Is there any provision in privacy addressing, autoconfiguration, or ND specifications to have privacy address and *not have* autoconfigured addresses?

> On Thu, 17 Aug 2006 12:50:51 -0400, > "John Spence" <[EMAIL PROTECTED]> said: > I would like the capability to have an interface construct a link-local > address via some mechanism (EUI-64 from MAC, as an example) as normal, > then configure a privacy address, all without autoconfigurin

RE: Is there any provision in privacy addressing, autoconfiguration, or ND specifications to have privacy address and *not have* autoconfigured addresses?

Hi Bob - thanks for the quick reply. Three things: 1) If I have autoconfiguration enabled, and I autoconfigure a global-scope address from an RA where the valid lifetime is greater than zero (the usual case certainly), I would normally respond to connections from other nodes at that address. I g

Re: Is there any provision in privacy addressing, autoconfiguration, or ND specifications to have privacy address and *not have* autoconfigured addresses?

John, I would like the capability to have an interface construct a link- local address via some mechanism (EUI-64 from MAC, as an example) as normal, then configure a privacy address, all without autoconfiguring a global-scope address from the RA being sent on the subnet (there would be no vali

RE: Is there any provision in privacy addressing, autoconfiguration, or ND specifications to have privacy address and*nothave* autoconfigured addresses?

I am not trying to anything like NAT. My question does not involve translation at all. I am interested in improving the hiding capability of "client" nodes on any network by not autoconfiguring a global-scope address that incorporates any portion of any unique identifier (like a MAC address) on

Re: Is there any provision in privacy addressing, autoconfiguration, or ND specifications to have privacy address and *nothave* autoconfigured addresses?

Comment at the end. John Spence wrote: So, let me revise my comment, focusing on requirements. I would like the capability to have an interface construct a link-local address via some mechanism (EUI-64 from MAC, as an example) as normal, then configure a privacy address, all without autoconfig

RE: Is there any provision in privacy addressing, autoconfiguration, or ND specifications to have privacy address and *nothave* autoconfiguredaddresses?

James, I'm looking at (RFC3315, Section 22.5), and it seems that there is an "Identity Association for Temporary Addresses" (IA_TA) using RFC3041. I assume this will implicitly also support RFC3041(bis)? Fred [EMAIL PROTECTED] -Original Message- From: James Kempf [mailto:[EMAIL PROTECT

RE: Is there any provision in privacy addressing, autoconfiguration, or ND specifications to have privacy address and *not have* autoconfigured addresses?

Thanks so much for your prompt and thoughtful reply. I do not quite understand yet, though, so let me seek clarification. I understand that privacy addresses are not for the link-local prefix, but for address scopes greater than link-local. I would like to be able to have an interface construct

Re: Is there any provision in privacy addressing, autoconfiguration, or ND specifications to have privacy address and *nothave* autoconfiguredaddresses?

RFC 3041 specifies privacy for autoconfiguration only. If DHCP is in use, the node can simply request multiple addresses from DHCP, and to the extent that the DHCP server allows a node to have more than one address, different addresses can be used for different transactions. jak --

RE: Is there any provision in privacy addressing, autoconfiguration, or ND specifications to have privacy address and *not have* autoconfiguredaddresses?

Hi Suresh, > Autoconfiguration IS still IN USE even with privacy addresses. The > prefix can be invalidated just as well with privacy addresses as with > non-privacy addresses. I do not see any issues in this regard. In short > privacy addresses just extend stateless autoconf, and hence will r

Re: Is there any provision in privacy addressing, autoconfiguration, or ND specifications to have privacy address and *not have* autoconfigured addresses?

Hi John, Please find comments inline Cheers Suresh John Spence wrote: My reading of the current and proposed specs are that privacy addresses may be generated in addition to autoconfigured addresses (of scope greater than link-local). Is there any provision for having **only** privacy addr

Is there any provision in privacy addressing, autoconfiguration, or ND specifications to have privacy address and *not have* autoconfigured addresses?

My reading of the current and proposed specs are that privacy addresses may be generated in addition to autoconfigured addresses (of scope greater than link-local).  Is there any provision for having *only* privacy addresses, and no autoconfigured addresses?  This would make it more difficu