Re: [arch-d] Call for Comment: <draft-iab-arpa-authoritative-servers-00> (Nameservers for the Address and Routing Parameter Area ("arpa") Domain)

Hi, IAB;

> The Call for Comment will last until 2021-06-03. Please send comments to
> architecture-discuss@ietf.org and iab@iab.org.

I have a technical comment.  Section 3.1 of this describes as follows:

---
   Because these nameservers are completely in-bailiwick of the "arpa"
                                            ^^^^^^^^^^^^
   zone, they will require glue records in the root zone.  This is
   consistent with current practice and requires no operational changes
   to the root zone.
---

This "in-bailiwick" is must be "in-domain".
Section 7 of RFC 8499 (DNS Terminology) defines it as I quoted below:

---
   Bailiwick:  "In-bailiwick" is a modifier to describe a name server
      whose name is either a subdomain of or (rarely) the same as the
      origin of the zone that contains the delegation to the name
      server.  In-bailiwick name servers may have glue records in their
      parent zone (using the first of the definitions of "glue records"
      in the definition above).  (The word "bailiwick" means the
      district or territory where a bailiff or policeman has
      jurisdiction.)

      "In-bailiwick" names are divided into two types of names for name
      servers: "in-domain" names and "sibling domain" names.

      *  In-domain: a modifier to describe a name server whose name is
         either subordinate to or (rarely) the same as the owner name of
         the NS resource records.  An in-domain name server name needs
         to have glue records or name resolution fails.  For example, a
         delegation for "child.example.com" may have "in-domain" name
         server name "ns.child.example.com".

      *  Sibling domain: a name server's name that is either subordinate
         to or (rarely) the same as the zone origin and not subordinate
         to or the same as the owner name of the NS resource records.
         Glue records for sibling domains are allowed, but not
         necessary.  For example, a delegation for "child.example.com"
         in "example.com" zone may have "sibling" name server name
         "ns.another.example.com".
---

Rrgards,

-- 
Yasuhiro 'Orange' Morishita <yasuhiro@jprs.co.jp>
URI: <http://jprs.co.jp/en/> | <http://www.dns.jp/>

From: IAB Executive Administrative Manager <execd@iab.org>
Subject: Call for Comment: <draft-iab-arpa-authoritative-servers-00> (Nameservers for the Address and Routing Parameter Area ("arpa") Domain)
Date: Thu, 06 May 2021 11:48:04 -0700

> This is an announcement of an IETF-wide Call for Comment on 
> draft-iab-arpa-authoritative-servers-00.
> 
> The document is being considered for publication as an Informational RFC 
> within the IAB stream, and is available for inspection at:
> <https://datatracker.ietf.org/doc/draft-iab-arpa-authoritative-servers/>
> 
> The Call for Comment will last until 2021-06-03. Please send comments to
> architecture-discuss@ietf.org and iab@iab.org.
> 
> Abstract:
> 
>    This document describes revisions to operational practices to
>    separate function of the "arpa" top-level domain in the DNS from its
>    historical operation alongside the DNS root zone.
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
> 