> Can you point me to the name of the referenced I-D? ... http://www.ietf.org/internet-drafts/draft-ietf-dnsop-default-local-zones-02.txt
> > what's wrong with this picture? is there a use case we can all study? > > Maybe the I-D answers this, but how do you resolve PTRs for some random > section of .arpa if you don't have glue NS records pointing you to the name > servers for that subdomain? by asking for a use case, i'm pointing out that if you can't be reached by an ip packet from "there", then your need to look up a PTR corresponding to an address in "there" is unfathomable. > I guess what it comes down to is that the intended use case for ULA-C is to > connect a bunch of companies with private address space on a private > network. the idea that someone would only need PI for "public networking" is bizarre. quite a lot of normal IPv4 space is never advertised into the "default free zone" but it's universally unique and used "privately" with passion & verve, and there is no reason to expect that IPv6 PI won't be used the same way. a global RIR policy to support this "private network" use case would suggest that each RIR lay aside a /32 worth of space that was meant to be carved up in /48 chunks for folks who needed smaller chunks of address space for private networking, with advice to the community that no address space in these /32's be advertised to the DFZ, and that it be filtered out if seen in the DFZ. an RIR could theoretically come up with a "private space only" membership class with lower fees. whois and PTR-space NS RRsets would be managed normally. i think the disconnect here is that a lot of folks are assuming that the RIR system only allocates "public" address space. that's not true today, and it never has been true (compare historical allocations vs. DFZ advertisements), and there's no reason to try to make it true or to assume that it ever will be true. RIRs allocate universally unique space. how it's used (public vs. private) is not an RIR concern. -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
