In message <3e811936-349d-49dd-b8c7-4af99739f...@vpnc.org>, Paul Hoffman writes
:
> On May 4, 2015, at 12:03 PM, Steve Crocker <st...@shinkuro.com> wrote:
> > Thanks. I agree it=92s good to explain this. I=92d rather it were expla=
> ined in a document that purported to explain how things work instead of sli=
> pping it into a terminology document, but getting it written down somewhere=
> is better than nowhere.
>
> Agree about "somewhere else". The terminology document is meant to describe=
> terms briefly, not describe fully how the technology behind the term works=
> . I'm sure that the community would benefit from a "How To Glue" document, =
> and I doubt it would be only a few paragraphs, and I hope it would have lot=
> s of examples.
>
> --Paul Hoffman
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
B.T.W. named uses "manditory glue" and "sibling glue"
manditory glue: glue records beneath the zone being delegated which are
referenced in the delegation.
sibling glue: is glue records that are in / below a sibling zone.
The source of bad instances of both of these are easy to track down as you
just check the parent zones.
Named allows both manditory and sibling glue.
Then there is "other glue" (if/when) we sign glue then these become
viable.
Named currently doesn't support other glue and removes it from
incoming zone transfers.
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
