Big fan of this document and feel it is good. I have only one small nit:

See also "domain name" in [RFC8499].


Should this not be "Domain name"  (per 8499) ?

I have a deeper question on using "ext" for extension - it feels like an
abbreviation which doesn't feel useful.  But I'm no expert on matters of
the written word.

tim



On Thu, Feb 9, 2023 at 8:30 AM Hollenbeck, Scott <shollenbeck=
40verisign....@dmarc.ietf.org> wrote:

> This may be of interest to dnsop folks, too. At least two of the terms
> included in this dictionary ("Domain Name" and "NS") are commonly used in
> DNS specifications.
>
> Scott
>
> > -----Original Message-----
> > From: regext <regext-boun...@ietf.org> On Behalf Of James Galvin
> > Sent: Monday, February 6, 2023 9:40 AM
> > To: REGEXT WG <reg...@ietf.org>
> > Subject: [EXTERNAL] [regext] WGLC: draft-ietf-regext-datadictionary-03
> >
> > The document editors have indicated that the following document is ready
> for
> > submission to the IESG to be considered for publication as a Proposed
> Standard:
> >
> > Registration Data Dictionary
> > https://datatracker.ietf.org/doc/draft-ietf-regext-datadictionary/
> >
> > Please indicate your support or no objection for the publication of this
> > document by replying to this message on list (a simple “+1” is
> sufficient).
> >
> > If any working group member has questions regarding the the publication
> of
> > this document please respond on the list with your concerns by close of
> > business everywhere, Monday, 20 February 2023.  If there are no
> objections the
> > document will be submitted to the IESG.
> >
> > The Document Shepherd for this document is Stéphane Bortzmeyer.
> >
> > Thanks,
> >
> > Antoin and Jim
> > REGEXT WG Co-Chairs
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to