I have to agree with this MUST NOT. |+ Advertising locally assigned ULA AAAA records in the global DNS |+ MUST NOT occur as they are not globally unique and will lead |+ to unexpected connections.
Although there is a good chance that someone else in the world has my same name, they don't receive their mail at my home address. OK, Bad example (reversed). But if there is a chance of overlap; allowing this insures there is a chance of misdirection. $.02 -Brian http://consult.tavian.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Lanciani Sent: Friday, December 03, 2004 12:15 PM To: [EMAIL PROTECTED] Subject: Re: I-D ACTION:draft-ietf-ipv6-unique-local-addr-08.txt Mark Andrews <[EMAIL PROTECTED]> wrote: |+ Advertising locally assigned ULA AAAA records in the global DNS is |+ MUST NOT occur as they are not globally unique and will lead |+ to unexpected connections. I strongly object to making this a "MUST NOT," especially with the growing uncertainty that there will ever be a _permanent_ centrally assigned flavor of ULA available without recurring fees. An important feature of even locally assigned ULAs is that they are globally unique "enough" for many/most purposes that have been discussed. After months of analysis to that end, their lack of absolute uniqueness is insufficient to justify adding new prohibition on a particular range of uses at this late date. Dan Lanciani [EMAIL PROTECTED] -------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 -------------------------------------------------------------------- -------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
