This draft is adopted. Authors, please post draft-rswg-rfc9280bis-00. In addition, please list the topics agreed in a Changes since RFC 9280 section. We will know that we are ready for a consensus call when all of this topics are addressed in the document.
For the RSWG Co-chairs, Russ > On Feb 13, 2025, at 2:01 PM, Russ Housley <hous...@vigilsec.com> wrote: > > The authors have asked the RSWG to adopt this I-D. > > The Internet-Draft is here: > https://datatracker.ietf.org/doc/draft-hoffman-rfc9280-updates/ > > Since the agreement is to produce a complete replacement for RFC 9280 at the > end of the discussion of updates, the document, if adopted, will become > draft-rswg-rfc9280bis. > > Please voice your support or concerns for the RSWG adoption of this document > by 28 February 2025. > > For the RSWG Co-chairs, > Russ > > >> On Feb 12, 2025, at 3:19 PM, Paul Hoffman <paul.hoff...@icann.org> wrote: >> >> Alexis and I have updated draft-hoffman-rfc9280-updates again to reflect the >> WG discussion from last week. Please see: >> https://datatracker.ietf.org/doc/draft-hoffman-rfc9280-updates/ >> The diffs can be found at: >> https://author-tools.ietf.org/iddiff?url2=draft-hoffman-rfc9280-updates-02 >> >> We heard positive comments on this becoming a WG draft (that still needs >> work). RSWG chairs: can you please start a call for adoption of this draft? >> >> --Paul and Alexis > -- rswg mailing list -- rswg@rfc-editor.org To unsubscribe send an email to rswg-le...@rfc-editor.org
