During the IETF108 meeting, it was brought up by the chairs that we have
been talking to the authors of RFC8499 on updating the document. We
propose these steps:
- Update some of the current language in the existing RFC8499
- Add new terms draft-ietf-dnsop-terminology-ter on which the WG agrees
All
When the chairs discussed sending out the call for adoption, we originally
planned to request for people to speak up if they had objections. However,
this part was dropped when I sent the email out.
The chairs would like to do a ONE week second call for adoption on
RFC8499-bis.
The Current
I recently noticed that the bailiwick-related definitions are wrong and
muddled.
I have always understood in-bailiwick to mean that a nameserver name is a
subdomain of its zone apex. That is, exactly the cases where glue is
required by the DNS protocol. The term comes from the discussion of
gluele
> From: Tony Finch
> I recently noticed that the bailiwick-related definitions are wrong and
> muddled.
>
> I have always understood in-bailiwick to mean that a nameserver name is a
> subdomain of its zone apex. That is, exactly the cases where glue is
> required by the DNS protocol. The term com
fujiw...@jprs.co.jp wrote:
>
> We need four types of glue names.
> Please propose new names.
I thought this was supposed to be documenting existing terminology, not
inventing new terminology.
There are two kinds of glue:
* glue required by the DNS, for in-bailiwick nameservers
* siblin
