On Aug 1, 2013, at 3:47 PM, Hosnieh Rafiee wrote: >> All sources of Internet public services need to have DNS names, but that's >> it. >> Other than that, "names" are only needed in higher layer communications, and >> can be handled there. For example, your laptop doesn't need a name to open >> communication with a SIP server, but once it does it can use one or more SIP- >> level identifiers for its end of the SIP-level communication. > > That is the actual case. I assume that the node who are clients would use > Privacy Extension RFC. I do not think you use it for your servers.
I do not think it is appropriate to assume that nodes are either clients or servers. Nodes can (and routinely do) support several applications in which the local protocol engine acts as a client, a server, or a peer, depending on the needs of each application. > This is > why I said that nodes who wants to have privacy should not have "DNS names" > or addresses that are defined in DNS but if they want to have they MUST not > generate it based on MAC address. > Of course it is "should" and not 'must". However, if you have wording issue, > I can change it to "Might". I recommend removing the text, or replacing it with something like "The choice of whether to list a node's address in DNS properly depends on many factors, including the set of applications to be run on the host. Not listing a node's address in the public DNS may increase the node's privacy, but may also impair its ability to support certain applications." Keith
-------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
