On Wed, 2020-06-03 at 19:36 -0700, internet-dra...@ietf.org 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
Hi,
> The DNSOP WG has placed draft-belyavskiy-rfc5933-bis in state
> Call For Adoption By WG Issued (entered by Tim Wicinski)
>
> The document is available at
> https://datatracker.ietf.org/doc/draft-belyavskiy-rfc5933-bis/
I support adoption of this document and I'll be happy to review it.
Re
The essence of this draft is the addition of once sentence to RFC 1034:
"If glue RRs do not fit set TC=1 in the header."
I worry that this is too ambiguous. Does it mean all glue? One glue? As much
as will fit?
AFAIK most software today is designed to fill up the additional section with as
On Friday, 5 June 2020 17:37:56 UTC Wessels, Duane wrote:
> ...
>
> There is also the question of in-domain vs sibling-domain glue. RFC 8499
> (Terminology) notes that "Glue records for sibling domains are allowed, but
> not necessary." Should in-domain glue take priority over sibling-domain
> g
On Jun 5, 2020, at 10:37 AM, Wessels, Duane
wrote:
>
> The essence of this draft is the addition of once sentence to RFC 1034:
>
> "If glue RRs do not fit set TC=1 in the header."
>
> I worry that this is too ambiguous. Does it mean all glue? One glue? As
> much as will fit?
>
> AFAIK mo
> On Jun 5, 2020, at 11:56 AM, Paul Hoffman wrote:
>
> On Jun 5, 2020, at 10:37 AM, Wessels, Duane
> wrote:
>>
>> The essence of this draft is the addition of once sentence to RFC 1034:
>>
>> "If glue RRs do not fit set TC=1 in the header."
>>
>> I worry that this is too ambiguous. Does i
In article <5e86e9ee-a022-44f0-9483-f498a03c3...@verisign.com> you write:
>> The current document is indeed ambiguous. I propose that it be changed to:
>> If all glue RRs do not fit, set TC=1 in the header.
>
>I believe this is contrary to how most authoritative DNS software works today,
>isn't
> On Jun 5, 2020, at 1:40 PM, John Levine wrote:
>
> In article <5e86e9ee-a022-44f0-9483-f498a03c3...@verisign.com> you write:
>>> The current document is indeed ambiguous. I propose that it be changed to:
>>> If all glue RRs do not fit, set TC=1 in the header.
>>
>> I believe this is contrar
Here's one example, 0124.org which has five in-domain name servers with glue:
You're right, that's what it does but it also seems seriously wrong.
$ for sz in `seq 604 16 700`; do echo -n "BUFSIZE $sz " ; dig +norec +ignore
+dnssec +bufsize=$sz @199.19.57.1 0124.org | grep ';; flags:' ; done
