Re: [DNSOP] I-D Action: draft-ietf-dnsop-glue-is-not-optional-02.txt

[Puneet Sood <[e-mail]>]

Couple of comments and a readability suggestion

* +1 to Geoff Huston's request to provide justification for why
sibling glue is desirable in a response. Also would prefer to not make
it mandatory in a referral response. If the sibling glue is referring
to a dns operator, it is possible that the resolver already has seen
the nameserver names before and has the needed A/AAAA records in
cache. Truncation in this case would require a redundant query.

* Section 5: Promoted or orphan glue
The considerations for handling orphan glue will be different for a
TLD vs a lower level zone within a domain. I would think that orphan
glue in a TLD context should go away when a zone is deleted/expired.
Maybe even have sanity checking to prevent such an operation.

A readability suggestion
* Move the description of all types of glue upfront before getting
into recommendations.
- real glue
- sibling glue
- loops with sibling
- orphaned glue
* Describe the recommendations for including glue.
This should also call out the scenario where different kinds of
glue/referrals are present in a response (glue, sibling glue). This is
implicit in the wording now.

-Puneet


On Mon, Jul 26, 2021 at 5:06 PM <[e-mail]> wrote:
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Domain Name System Operations WG of the IETF.
>
>         Title           : Glue In DNS Referral Responses Is Not Optional
>         Authors         : M. Andrews
>                           Shumon Huque
>                           Paul Wouters
>                           Duane Wessels
>         Filename        : draft-ietf-dnsop-glue-is-not-optional-02.txt
>         Pages           : 7
>         Date            : 2021-07-26
>
> Abstract:
>    The DNS uses glue records to allow iterative clients to find the
>    addresses of nameservers that are contained within a delegated zone.
>    Authoritative Servers are expected to return all available glue
>    records in referrals.  If message size constraints prevent the
>    inclusion of all glue records in a UDP response, the server MUST set
>    the TC flag to inform the client that the response is incomplete, and
>    that the client SHOULD use TCP to retrieve the full response.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-glue-is-not-optional/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-dnsop-glue-is-not-optional-02.html
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-glue-is-not-optional-02
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>
> _______________________________________________
> DNSOP mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/dnsop