[DNSOP] [IANA #1286187] Re: expert review for draft-ietf-dnsop-dns-error-reporting (Underscored and Globally Scoped DNS Node Names)

2023-10-31 Thread David Dong via RT 
Dear Dear Authors/Chairs/ADs,

Please see below for a comment from from one of the experts.

Best regards,

David Dong
IANA Services Sr. Specialist

On Tue Oct 31 23:39:26 2023, p...@nohats.ca wrote:
> On Oct 31, 2023, at 19:17, Frederico A C Neves 
> wrote:
> >
> > Dear David,
> >
> > Section 7 of the draft is sufficiently clear, precise, and complete.
> >
> > This registration at the time it is approved by the IESG, taking in
> > account the fact that currently there is no other request for TXT _er
> > on the "virtual request queue", is reviewed as OK and approved.
> 
> I agree, although I do wonder what “er” stands for. Error Report? Why
> not use “_err” which is more intuitively an error ?
> 
> Paul

___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Re: [DNSOP] [IANA #1285116] expert review for draft-ietf-dnsop-dns-error-reporting (Underscored and Globally Scoped DNS Node Names)

2023-10-31 Thread Paul Wouters 
On Oct 31, 2023, at 19:17, Frederico A C Neves  wrote:
> 
> Dear David,
> 
> Section 7 of the draft is sufficiently clear, precise, and complete.
> 
> This registration at the time it is approved by the IESG, taking in
> account the fact that currently there is no other request for TXT _er
> on the "virtual request queue", is reviewed as OK and approved.

I agree, although I do wonder what “er” stands for. Error Report? Why not use 
“_err” which is more intuitively an error ?

Paul
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Re: [DNSOP] DNS IPv6 Transport Operational Guidelines (draft-momoka-dnsop-3901bis-00)

2023-10-31 Thread Wessels, Duane 
Hi Momoka,

I see that your draft often uses “in-bailiwick” or “out-of-bailiwick”.  If you 
are not already aware, the latest version of the DNS terminology document 
(draft-ietf-dnsop-rfc8499bis) notes that “bailiwick” should be considered 
historic at this point.  The preferred language is to refer to the relationship 
between the NS record owner name, the name in the NS RDATA and the zone origin 
as either in-domain, sibling domain, or unrelated.

DW

From: DNSOP  on behalf of Momoka Yamamoto 

Date: Sunday, October 22, 2023 at 11:13 AM
To: dnsop 
Cc: "tfie...@mpi-inf.mpg.de" 
Subject: [EXTERNAL] [DNSOP] DNS IPv6 Transport Operational Guidelines 
(draft-momoka-dnsop-3901bis-00)


Caution: This email originated from outside the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.

Hello DNSOP Working Group,

My name is Momoka Yamamoto and I've recently submitted an Internet-Draft titled 
"DNS IPv6 Transport Operational Guidelines" (draft-momoka-dnsop-3901bis-00) 
with my co-author Tobias tfie...@mpi-inf.mpg.de. 
This draft discusses the operational guidelines for operating authoritative and 
recursive DNS servers in mixed IPv4 and IPv6 environments, expanding on RFC3910 
to address the progressing IPv4 exhaustion and the long-term necessity of 
IPv6-only resolvers.

I would greatly appreciate any feedback, comments, or questions you may have 
regarding this draft. I believe this document could contribute significantly to 
the current discussions and work of the DNSOP working group, especially in 
light of the wide adoption of IPv6 over the last 20 years since BCP91 was 
written.

The draft is open for discussion and I am looking forward to engaging with the 
community to refine and improve it.
Momoka Y

-- Forwarded message -
From: mailto:internet-dra...@ietf.org>>
Date: Mon, Oct 23, 2023 at 3:02 AM
Subject: New Version Notification for draft-momoka-dnsop-3901bis-00.txt
To: Momoka Yamamoto mailto:momoka@gmail.com>>, Tobias 
Fiebig mailto:tfie...@mpi-inf.mpg.de>>


A new version of Internet-Draft draft-momoka-dnsop-3901bis-00.txt has been
successfully submitted by Momoka Yamamoto and posted to the
IETF repository.

Name: draft-momoka-dnsop-3901bis
Revision: 00
Title:DNS IPv6 Transport Operational Guidelines
Date: 2023-10-20
Group:Individual Submission
Pages:9
URL:  
https://www.ietf.org/archive/id/draft-momoka-dnsop-3901bis-00.txt
Status:   
https://datatracker.ietf.org/doc/draft-momoka-dnsop-3901bis/
HTML: 
https://www.ietf.org/archive/id/draft-momoka-dnsop-3901bis-00.html
HTMLized: 
https://datatracker.ietf.org/doc/html/draft-momoka-dnsop-3901bis


Abstract:

   This memo provides guidelines and documents Best Current Practice for
   operating authoritative and recursive DNS servers given that queries
   and responses are carried in a mixed environment of IPv4 and IPv6
   networks.  It expands beyond [RFC3910] in so far that it now
   considers the reality of progressing IPv4 exhaustion, which will make
   IPv6-only resolvers necessary in the long-term.

Discussion Venues

   This note is to be removed before publishing as an RFC.

   Source for this draft and an issue tracker can be found at

Re: [DNSOP] [IANA #1285116] expert review for draft-ietf-dnsop-dns-error-reporting (Underscored and Globally Scoped DNS Node Names)

2023-10-31 Thread Frederico A C Neves 
Dear David,

On Tue, Oct 24, 2023 at 07:39:27PM +, David Dong via RT wrote:
> Dear Frederico A C Neves and Paul Wouters (cc: dnsop WG),
> 
> As the designated experts for the Underscored and Globally Scoped DNS Node 
> Names registry, can you review the proposed registration in 
> draft-ietf-dnsop-dns-error-reporting-06 for us? Please see:
> 
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-dns-error-reporting/
> 
> The due date is November 7th.
> 
> If this is OK, when the IESG approves the document for publication, we'll 
> make the registration at:
> 
> https://www.iana.org/assignments/dns-parameters/
> 
> Unless you ask us to wait for the other reviewer, we’ll act on the first 
> response we receive.
>

Section 7 of the draft is sufficiently clear, precise, and complete.

This registration at the time it is approved by the IESG, taking in
account the fact that currently there is no other request for TXT _er
on the "virtual request queue", is reviewed as OK and approved.

> With thanks,
> 
> David Dong
> IANA Services Sr. Specialist

Regards,
Frederico Neves

___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

[DNSOP] [Errata Verified] RFC8806 (7692)

2023-10-31 Thread RFC Errata System 
The following errata report has been verified for RFC8806,
"Running a Root Server Local to a Resolver". 

--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7692

--
Status: Verified
Type: Editorial

Reported by: Deliang Chang 
Date Reported: 2023-10-31
Verified by: RFC Editor  

Section: 3

Original Text
-
   There is a risk that a system using a local authoritative server for
   the root zone cannot refresh the contents of the root zone before the
   expire time in the SOA.  A system using a local authoritative server
   for the root zone MUST NOT serve stale data for the root zone.  To
   mitigate the risk that stale data is served, the local root server
   MUST immediately switch to using non-local root servers when it
   detects that it would be serving state data.

Corrected Text
--
   There is a risk that a system using a local authoritative server for
   the root zone cannot refresh the contents of the root zone before the
   expire time in the SOA.  A system using a local authoritative server
   for the root zone MUST NOT serve stale data for the root zone.  To
   mitigate the risk that stale data is served, the local root server
   MUST immediately switch to using non-local root servers when it
   detects that it would be serving stale data.

Notes
-
Based on the context, it seems that in the last sentence the intended word is 
"stale" as in stale data, instead of "state". So, I believe there might be a 
typo in the text, and the correct interpretation would be to swith back to the 
non-local root when stale data is detected.

--
RFC8806 (draft-ietf-dnsop-7706bis-12)
--
Title   : Running a Root Server Local to a Resolver
Publication Date: June 2020
Author(s)   : W. Kumari, P. Hoffman
Category: INFORMATIONAL
Source  : Domain Name System Operations
Area: Operations and Management
Stream  : IETF

___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

[DNSOP] [IANA #1285116] expert review for draft-ietf-dnsop-dns-error-reporting (Underscored and Globally Scoped DNS Node Names)

2023-10-31 Thread David Dong via RT 
Dear Frederico A C Neves and Paul Wouters (cc: dnsop WG),

Following up on this; as the designated experts for the Underscored and 
Globally Scoped DNS Node Names registry, can you review the proposed 
registration in draft-ietf-dnsop-dns-error-reporting-06 for us? Please see:

https://datatracker.ietf.org/doc/draft-ietf-dnsop-dns-error-reporting/

The due date is November 7th.

If this is OK, when the IESG approves the document for publication, we'll make 
the registration at:

https://www.iana.org/assignments/dns-parameters/

Unless you ask us to wait for the other reviewer, we’ll act on the first 
response we receive.

With thanks,

David Dong
IANA Services Sr. Specialist

On Tue Oct 24 19:39:27 2023, david.dong wrote:
> Dear Frederico A C Neves and Paul Wouters (cc: dnsop WG),
> 
> As the designated experts for the Underscored and Globally Scoped DNS
> Node Names registry, can you review the proposed registration in
> draft-ietf-dnsop-dns-error-reporting-06 for us? Please see:
> 
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-dns-error-reporting/
> 
> The due date is November 7th.
> 
> If this is OK, when the IESG approves the document for publication,
> we'll make the registration at:
> 
> https://www.iana.org/assignments/dns-parameters/
> 
> Unless you ask us to wait for the other reviewer, we’ll act on the
> first response we receive.
> 
> With thanks,
> 
> David Dong
> IANA Services Sr. Specialist

___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Re: [DNSOP] [Editorial Errata Reported] RFC8806 (7692)

2023-10-31 Thread Joe Abley 
Verified. 

> On 31 Oct 2023, at 04:10, RFC Errata System  wrote:
> 
> The following errata report has been submitted for RFC8806,
> "Running a Root Server Local to a Resolver".
> 
> --
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid7692
> 
> --
> Type: Editorial
> Reported by: Deliang Chang 
> 
> Section: 3
> 
> Original Text
> -
>   There is a risk that a system using a local authoritative server for
>   the root zone cannot refresh the contents of the root zone before the
>   expire time in the SOA.  A system using a local authoritative server
>   for the root zone MUST NOT serve stale data for the root zone.  To
>   mitigate the risk that stale data is served, the local root server
>   MUST immediately switch to using non-local root servers when it
>   detects that it would be serving state data.
> 
> Corrected Text
> --
>   There is a risk that a system using a local authoritative server for
>   the root zone cannot refresh the contents of the root zone before the
>   expire time in the SOA.  A system using a local authoritative server
>   for the root zone MUST NOT serve stale data for the root zone.  To
>   mitigate the risk that stale data is served, the local root server
>   MUST immediately switch to using non-local root servers when it
>   detects that it would be serving stale data.
> 
> Notes
> -
> Based on the context, it seems that in the last sentence the intended word is 
> "stale" as in stale data, instead of "state". So, I believe there might be a 
> typo in the text, and the correct interpretation would be to swith back to 
> the non-local root when stale data is detected.
> 
> Instructions:
> -
> This erratum is currently posted as "Reported". (If it is spam, it 
> will be removed shortly by the RFC Production Center.) Please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party  
> will log in to change the status and edit the report, if necessary.
> 
> --
> RFC8806 (draft-ietf-dnsop-7706bis-12)
> --
> Title   : Running a Root Server Local to a Resolver
> Publication Date: June 2020
> Author(s)   : W. Kumari, P. Hoffman
> Category: INFORMATIONAL
> Source  : Domain Name System Operations
> Area: Operations and Management
> Stream  : IETF
> Verifying Party : IESG
> 
> ___
> 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