You are welcome, but the authors (especially Mohamed) made it easy as they stayed on top of it and there was little for me to do.
- Bernie > On Aug 17, 2023, at 2:16 AM, Joe Clarke (jclarke) <[email protected]> wrote: > > > Well done, authors and WG contributors! Thank you to Bernie for shepherding > this. > > Joe > > From: OPSAWG <[email protected]> on behalf of [email protected] > <[email protected]> > Date: Wednesday, August 16, 2023 at 17:40 > To: [email protected] <[email protected]>, [email protected] > <[email protected]> > Cc: [email protected] <[email protected]>, > [email protected] <[email protected]>, [email protected] > <[email protected]> > Subject: [OPSAWG] RFC 9445 on RADIUS Extensions for DHCP-Configured Services > > A new Request for Comments is now available in online RFC libraries. > > > RFC 9445 > > Title: RADIUS Extensions for DHCP-Configured Services > Author: M. Boucadair, > T. Reddy.K, > A. DeKok > Status: Standards Track > Stream: IETF > Date: August 2023 > Mailbox: [email protected], > [email protected], > [email protected] > Pages: 18 > Updates: RFC 4014 > > I-D Tag: draft-ietf-opsawg-add-encrypted-dns-12.txt > > URL: https://www.rfc-editor.org/info/rfc9445 > > DOI: 10.17487/RFC9445 > > This document specifies two new Remote Authentication Dial-In User > Service (RADIUS) attributes that carry DHCP options. The > specification is generic and can be applicable to any service that > relies upon DHCP. Both DHCPv4- and DHCPv6-configured services are > covered. > > Also, this document updates RFC 4014 by relaxing a constraint on > permitted RADIUS attributes in the RADIUS Attributes DHCP suboption. > > This document is a product of the Operations and Management Area Working > Group 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 [email protected]. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > > The RFC Editor Team > Association Management Solutions, LLC > > > _______________________________________________ > OPSAWG mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/opsawg
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
