[DNSOP] draft-hardaker-dnsop-rfc8624-bis

2024-03-21 Thread Tim Wicinski
Not wearing any hats, really

I want to thank Wes and Warren for putting this together and I think this
is a good way to build on the good work that RFC8624 produced.

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


[DNSOP] The DNSOP WG has placed draft-hardaker-dnsop-rfc8624-bis in state "Candidate for WG Adoption"

2024-03-21 Thread IETF Secretariat


The DNSOP WG has placed draft-hardaker-dnsop-rfc8624-bis in state
Candidate for WG Adoption (entered by Tim Wicinski)

The document is available at
https://datatracker.ietf.org/doc/draft-hardaker-dnsop-rfc8624-bis/


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


[DNSOP] updated agenda for DNSOP WG session on Friday, 22 March 2024

2024-03-21 Thread Benno Overeinder

Dear all,

We have added two /time permitting/ presentations to the DNSOP WG agenda 
for Friday 15:00-16:30 AEST/05:00-06:30 UTC.


For the latest DNSOP agenda, see 
https://datatracker.ietf.org/doc/agenda-119-dnsop/.


Best,

Suzanne, Tim and Benno

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


[DNSOP] BCP 219, RFC 9499 on DNS Terminology

2024-03-21 Thread rfc-editor
A new Request for Comments is now available in online RFC libraries.

BCP 219
RFC 9499

Title:  DNS Terminology 
Author: P. Hoffman,
K. Fujiwara
Status: Best Current Practice
Stream: IETF
Date:   March 2024
Mailbox:paul.hoff...@icann.org,
fujiw...@jprs.co.jp
Pages:  45
Obsoletes:  RFC 8499
Updates:RFC 2308
See Also:   BCP 219

I-D Tag:draft-ietf-dnsop-rfc8499bis-10.txt

URL:https://www.rfc-editor.org/info/rfc9499

DOI:10.17487/RFC9499

The Domain Name System (DNS) is defined in literally dozens of
different RFCs. The terminology used by implementers and developers
of DNS protocols, and by operators of DNS systems, has changed in the
decades since the DNS was first defined. This document gives current
definitions for many of the terms used in the DNS in a single
document.

This document updates RFC 2308 by clarifying the definitions of
"forwarder" and "QNAME". It obsoletes RFC 8499 by adding multiple
terms and clarifications. Comprehensive lists of changed and new
definitions can be found in Appendices A and B.

This document is a product of the Domain Name System Operations Working Group 
of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC

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