Works for me. Paul
On Mon, Mar 2, 2026 at 6:10 PM Sandy Ginoza <[email protected]> wrote: > Correct - our understanding is that an updated xml2rfc will be released > later tonight, so we should be able to publish these RFCs this week: > > draft-ietf-tls-esni (RFC-to-be 9849) > draft-ietf-tls-svcb-ech (RFC-to-be 9848) > draft-farrell-tls-pemesni (RFC-to-be 9934) > > Thanks, > Sandy Ginoza > RFC Production Center > > > > > On Mar 2, 2026, at 1:57 PM, Eric Rescorla <[email protected]> wrote: > > > > I agree. As far as I know, we're just waiting for xml2rfc to ship with > this fix so that the RFC can be emitted > https://github.com/ietf-tools/xml2rfc/pull/1292 > > > > > > On Mon, Mar 2, 2026 at 1:55 PM Stephen Farrell < > [email protected]> wrote: > > > > Hiya, > > > > On 02/03/2026 18:23, Sandy Ginoza wrote: > > > 1) We understand there is some urgency to getting RFC 9849 <draft- > > > ietf-tls-esni> published, so it will retain its normative reference > > > to RFC 8446. We believe the following three documents should be > > > published and released together, as soon as possible. > > > > From my POV, that's the correct approach, compared to risking > > potential further delay. > > > > Thanks, > > S. > > > > > >
-- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
