RFC 9432 on DNS Catalog Zones

[rfc-editor]

A new Request for Comments is now available in online RFC libraries.


RFC 9432

Title:  DNS Catalog Zones 
Author: P. van Dijk,
L. Peltan,
O. Surý,
W. Toorop,
C.R. Monshouwer,
P. Thomassen,
A. Sargsyan
Status: Standards Track
Stream: IETF
Date:   July 2023
Mailbox:peter.van.d...@powerdns.com,
libor.pel...@nic.cz,
ond...@isc.org,
wil...@nlnetlabs.nl,
m...@monshouwer.eu,
pe...@desec.io,
a...@isc.org
Pages:  16
Updates/Obsoletes/SeeAlso:   None

I-D Tag:draft-ietf-dnsop-dns-catalog-zones-09.txt

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

DOI:10.17487/RFC9432

This document describes a method for automatic DNS zone provisioning
among DNS primary and secondary name servers by storing and
transferring the catalog of zones to be provisioned as one or more
regular DNS zones.

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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


___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

RFC 9419 on Considerations on Application - Network Collaboration Using Path Signals

[rfc-editor]

A new Request for Comments is now available in online RFC libraries.


RFC 9419

Title:  Considerations on Application - Network 
Collaboration Using Path Signals 
Author: J. Arkko,
T. Hardie,
T. Pauly,
M. Kühlewind
Status: Informational
Stream: IAB
Date:   July 2026
Mailbox:jari.ar...@ericsson.com,
ted.i...@gmail.com,
tpa...@apple.com,
mirja.kuehlew...@ericsson.com
Pages:  15
Updates/Obsoletes/SeeAlso:   None

I-D Tag:draft-iab-path-signals-collaboration-03.txt

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

DOI:10.17487/RFC9419

This document discusses principles for designing mechanisms that use
or provide path signals and calls for standards action in specific
valuable cases.  RFC 8558 describes path signals as messages to or
from on-path elements and points out that visible information will be
used whether or not it is intended as a signal. The principles in
this document are intended as guidance for the design of explicit
path signals, which are encouraged to be authenticated and include a
minimal set of parties to minimize information sharing. These
principles can be achieved through mechanisms like encryption of
information and establishing trust relationships between entities on
a path.

This document is a product of the Internet Architecture Board.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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


___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

NomCom 2023 Update on Volunteers

[NomCom Chair 2023]

A few minor things have come up since the list was announced.

Gunter van de Velde has withdrawn.  I will leave Gunter in the list, but 
immediately select a replacement if he is selected.  The same applies to those 
who might be ineligible, such as the two that were added late, whose status is 
still unknown to me.  If any others choose to withdraw, given the imminence of 
the first lottery draw, I will have to treat that as declining to serve instead.

On affiliations, as in the past, subsidiaries are regarded as the same 
affiliation as their parent company.  There are also a number of people who 
have unclear affiliation such that it might be difficult to easily (a blank 
field, "independent", or similar).  In all cases that are unambiguous, I will 
disqualify a selection as necessary and immediately select the next volunteer.

If affiliations are ambiguous, such that I need to make an inquiry, I will 
regard that person as having been selected and not replace them immediately.  
If the inquiry results in disqualification, their replacement will be selected 
using the process outlined in earlier mails, as if the disqualification were 
due to the person declining.

As always, if you believe an error was made, decisions can be challenged.  Any 
challenges will be announced and a redraw will occur with newly chosen random 
seeds.

Martin Thomson
nomcom-chair-2...@ietf.org

___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Formal IESG Teleconference WebEx and Dial-in Information: 13 July 2023

[IESG Secretary]

All members of the community are welcome to attend formal IESG 
telechats as observers. Observers are not invited to participate in the
discussion.

The next formal IESG telechat will be held on Thursday, July 13, 2023 at  
07:00 US/Canada Pacific (15:00 UTC). The meeting is scheduled for two 
hours (07:00-09:00 US/Canada Pacific). Webex and Dial-in information is 
at the bottom of this message.

The agenda for the upcoming telechat can be found at


A calendar of upcoming public telechats can be downloaded or subscribed
to at:
https://calendar.google.com/calendar/ical/ietf.org_egdabaf39ch5v8a13dt39mvee4%40group.calendar.google.com/public/basic.ics


Topic: IESG Formal Telechat
Date: July 13, 2023
Time:   07:00 US/Canada Pacific 
09:00 US/Canada Central
10:00 US/Canada Eastern
14:00 UTC
15:00 United Kingdom
16:00 Germany, France, Belgium, Sweden
17:00 Finland
17:00 Kenya
19:30 India

---
JOIN WEBEX MEETING
https://ietf.webex.com/ietf/j.php?MTID=m38beb3706c7e5a24dd749a50d7e87dfd
Meeting number: 642 944 708
Meeting password: 1234


JOIN BY PHONE
1-650-479-3208 Call-in toll number (US/Canada)
Access code: 642 944 708

___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

NomCom 2023 Final Announcement of Eligible Volunteers

[NomCom Chair 2023]

This is the announcement of the final set of volunteers for the 2023-2024 
volunteers.

Selection from this list will occur once the random seeds are available, very 
shortly.  As per RFC 8713, challenges to this list can be made, with the 
following additional constraints:

1. Someone who is listed but ineligible will simply be noted as ineligible.  
Then if they are selected, another draw will be made and the next volunteer 
will be selected instead.  Please make these challenges early, but there

2. Someone who is NOT listed, but who believes they have volunteered and are 
eligible, please let me know before Friday 2023-07-07.  If I receive a valid 
challenge regarding a missing volunteer after the first random seeds become 
available, that will delay the process because new random seeds will be need to 
be selected.

Note that there were technical issues this year with the system.  People who 
volunteered through the IETF meeting registration were not initially added to 
the list of volunteers.  The lists have been merged manually.

Two people were added very late (these are marked with a *) and I have been 
unable to confirm whether they registered before the deadline; if they were 
not, then they will be skipped.  A second technical error appears to have eaten 
my first announcement, apologies for the short notice on this revised list.

Finally, thank you to everyone who volunteered.  This is an important 
responsibility and we appreciate all these people being willing to serve our 
community in this way.

The full list of 268 volunteers with name and affiliation follows at the bottom 
of this email.  This is exactly in the order that will be used for the RFC 3797 
selection process.

Martin Thomson
nomcom-chair-2...@ietf.org


---
Dr. Bernard D. AbobaMicrosoft Corporation
Melchior AelmansJuniper Networks
Zaid AlBannaVerisign
Zafar Ali   Cisco Systems
Hirochika Asai  Preferred Networks / WIDE Project
Michael B   UK NCSC
Ignas Bagdonas
Mary Barnes Transunion
Richard Barnes  Cisco
Alison Becker   NSA - CCSS
Vishnu Pavan Beeram Juniper Networks
Ali C. BegenOzyegin University
Dieter Beller   Nokia Solutions and Networks GmbH & Co. KG
Sergio Belotti  Nokia
Vittorio BertolaOpen-Xchange
Benjamin Beurdouche Mozilla
Hooman Bidgoli  Nokia
Mike Bishop Akamai Technologies
Marek Blachut   UK DSIT
Matthew Bocci   Nokia
Dean Bogdanović Alef Edge, Inc.
Ron Bonica  Juniper Networks
Chris Box   BT
Bob Briscoe independent
Luc André BurdetCisco
Randy Bush  Arrcus & IIJ Research
Italo Busi  Huawei
Pablo Camarillo Cisco Systems
Andrew Campling 419 Consulting Ltd
Daniele Ceccarelli  Cisco
Sofia Celi  University of London / Brave
Danyang ChenChina Mobile
Ran ChenZTE
Xia Chenhuawei
Mach Chen   Huawei Technologies Co., Ltd.
Huaimo Chen
Weiqiang Cheng  China Mobile
Laurent Ciavaglia   Nokia
Francois Clad   Cisco
Alexander Clemm Futurewei
Nabeel Cocker   Red Hat
Jane R Coffin   Independent Expert
Luis M. Contreras   Telefonica I+D
Alissa Cooper   Cisco
James Cumming   Nokia
Florence D  UK National Cyber Security Centre
Koen De SchepperNokia Bell Labs
Jie DongHuawei Technologies
Lijun Dong  Futurewei Technologies Inc.
John Drake  Juniper Networks
Zongpeng Du china mobile
Fanghong Duan   Huawei
Linda DunbarFuturewei
Donald E. Eastlake 3rd  Futurewei Technologies
Charles Eckel   Cisco
Toerless Eckert Futurewei USA
Reese Enghardt  Netflix
Dawei Fan
Adrian Farrel   Old Dog Consulting
Stephen Farrell Trinity College Dublin
Giuseppe Fioccola   Huawei Technologies
Jessica Fitzgerald-McKayNSA CCSS
Sergey FominNokia
Thomas Fossati  arm
Antoine FressancourtHuawei Technologies France S.A.S.U.
Rakesh Gandhi   Cisco Systems
Qiangzhou Gao   huawei
Nan GengHuawei
Xuesong GengHuawei
Bron Gondwana   Fastmail
Fernando Gont   SI6 Networks
Vengada Prasad Govindan Cisco Systems India Pvt Ltd
John Gray   Entrust
Sri Gundavelli  Cisco
Aihua Guo   Futurewei
Yangfei Guo ZGC Lab
Jianfei(Jeffrey) HE City University of Hong Kong
Jeffrey HaasJuniper Networks
Wassim Haddad   Ericsson
Britta Hale NPS
Phillip Hallam-BakerThreshold Secrets LLC
Lin Han Futurewei Technologies, Inc.
Dick Hardt  Hello Identity Co-op
Susan Hares Huawei
Tom HarrisonAPNIC
Jordan Head Juniper Networks
Shraddha Hegde  Juniper Networks
Giles Heron Cisco Systems
Simon Hicks Digital Standards, DCMS (UK Government)
Bob Hinden  Check Point Software
Christian Hopps LabN Consulting
Russ HousleyVigil Security, LLC
Jonathan HoylandCloudflare
Zhibo HuHuawei
Cheng Huang ZTE Corporation
Daniel HuangNanjing Zhongxingxin Software Company Limited
Christian Huitema   Private Octopus Inc.
Shumon HuqueSalesforce
Geoff HustonAPNIC
Luigi Iannone   Huawei Technologies France
Christopher Inacio  CERT / Carnegie Mellon Univers