> Thus spake "Brian Haberman" <[EMAIL PROTECTED]>
> > Geoff Huston wrote:
> >
> > > Thanks for your comments Margaret  - I have a clearer understanding of
> > > the line of thinking here after reading your note.
> > >
> > > One  comment I have here relates to the DNS section of the draft
> > > includes the provision of inclusion of PTR entries in the global
> > > 0.0.d.f.ip6.arpa (reverse)  DNS domain. Presumably this is a First Come
> > > First Served open delegation process that allows anyone to enter a
> > > delegation record into the parent zone file for their self-drawn prefix
> > > - yes? Are there any concerns regarding potential abuse of such an open
> > > delegation process, and, if so, what form of operational management of
> > > this domain would be appropriate here?
> >
> > The reference to PTR entries was originally added to the combined draft
> > for the centrally allocated addresses.  I am not sure if they are
> > appropriate for the locally-allocated prefixes.
> 
> When I made the suggestion, my intent was that centrally-assigned prefixes
> could be (optionally) added to the global reverse tree, but locally-assigned
> prefixes would only be added to a local reverse tree.  Given the
> inevitability of collisions in the locally-assigned space, it doesn't seem
> logical to allow them in the global reverse tree.
> 
> > If someone with more operational DNS experience has suggestions, I am
> > more than willing to listen to them. :)
> 
> Particularly someone with experience doing split-horizon DNS service for
> RFC1918 addresses.
> 
> S
> 
> Stephen Sprunk      "Those people who think they know everything
> CCIE #3723         are a great annoyance to those of us who do."
> K5SSS                                             --Isaac Asimov

        Well I don't know where those zeros are coming from.  The
        DNS suffix is D.F.IP6.ARPA.  I would actually recommend
        that every nameserver be configured to swallow this suffix
        with the ability to override if needed.

        This will stop the IP6.ARPA servers being swamped by leaking
        queries in the way the IN-ADDR.ARPA servers were being swamped
        by reverse queries for RFC 1918 space.

        A simple empty zone (SOA and NS records only) will do this.
 
        Mark
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> [EMAIL PROTECTED]
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
--
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
--------------------------------------------------------------------

Reply via email to