> I am afraid I am slow.. I still don't get the need to publicly
> advertise DNS for ULA(-x) .. if your neighbor cannot route to your ULA
> he doesn't need to know what it's names are.. if you do allow him to
> enter your network via VPN or whatever there is either a dhcp-like
> process by which he is granted an address which will also give him a
> name server to use, or when he says "Hey, Can I have access to your
> network" you can say "Sure, here are your credentials and my DNS server
> is..."=20
Well firstly these address will appear outside of IPv6 packets
in environments where they will be automatically processed along
with every other IPv6 address that is being processed. The
place that it processing the addresses may or may not be able
to reach the ULA-C servers for the reverse lookup.
It really should be up to the *user* of the ULA-C addresses
to decide if they want to provide more than NXDOMAIN to
interested parties on the Internet. We shouldn't be
arbitarially limiting functionality if it is technically
possible to provide that functionality.
> Then of course because you can populate your DNS server with whatever
> zones you want when your neighbor queries your name server it will tell
> him what he wants to know.
>
> Aren't your DNS servers going to provide different views for clients
> coming from PI or PA than they do for clients coming from ULAx anyway?
> or is your network going to be a completely glass house? Typically
> "local" clients get more access and information than non-local clients.
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED]
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
