Re: WG Last Call: draft-ietf-httpbis-secondary-server-certs-02 (Ends 2026-09-06)

Thanks to everyone who took the time to review this and provide feedback. Apologies for the slow response here; I’ve been out for a few months and just picking this back up this week.

Much of the feedback here is reasonable and actionable; I’ll be looking to get some changes up based on it in the coming days.

Martin’s point that a server-sent setting is unnecessary if there is no mechanism for clients to solicit the certificates makes sense. I’m tempted to just go ahead and remove it in -03…if anyone has objections to this, feel free to make them known.

Thanks again,
Eric

> On Sep 10, 2026, at 4:23 AM, Lucas Pardue <lucas@lucaspardue.com> wrote:
> 
> Hi,
> 
> On Thu, Sep 10, 2026, at 06:31, 
>> 
>> p.s., I'm starting to really hate reading what LLMs spit out.  If I use this tool in future, I'll ask for it to be written in pirate or Jane Austen or something less annoying.  I'll definitely play meat proxy for that.  This email is 100% human-generated, so it being annoying is entirely my fault.
> 
> I didn't see a review from Mark posted anywhere, perhaps I missed it. For completeness, and in the spirit of the upcoming international speak like a pirate day:
> 
> I be gobsmacked that nary a scallywag has yet hollered about the codepoints all bein' TBD, which be affectin' how much cross-vendor testin' could've been done, arrr! I'd be a fair bit more at ease with codepoints declared before we go declarin' Working Group consensus, savvy!
> 
> Cheers
> Lucas
> 
>> 
>> p.p.s., The tokens I used cost $2.45; my time probably cost a lot more.  I'm going to start to encourage people who are seeking WGLC to run this tool for themselves first, so that others don't have to.
>> 
>> On Thu, Sep 10, 2026, at 09:05, Mark Nottingham wrote:
>> > Hi everyone,
>> >
>> > We're extending this WGLC by two weeks to gather more feedback and 
>> > signs of support, since folks have been away from offices for various 
>> > reasons.
>> >
>> > Cheers,
>> >
>> >
>> >> On 17 Aug 2026, at 3:58 pm, Mark Nottingham via Datatracker <noreply@ietf.org <mailto:noreply@ietf.org>> wrote:
>> >> 
>> >> This message starts a WG Last Call for:
>> >> draft-ietf-httpbis-secondary-server-certs-02
>> >> 
>> >> This Working Group Last Call ends on 2026-09-06
>> >> 
>> >> Abstract:
>> >>   This document defines a way for HTTP/2 and HTTP/3 servers to send
>> >>   additional certificate-based credentials after a TLS connection is
>> >>   established, based on TLS Exported Authenticators.
>> >> 
>> >> File can be retrieved from:
>> >> https://www.ietf.org/archive/id/draft-ietf-httpbis-secondary-server-certs-02.txt
>> >> 
>> >> Please review and indicate your support or objection to proceed with the
>> >> publication of this document by replying to this email keeping
>> >> ietf-http-wg@w3.org <mailto:ietf-http-wg@w3.org> in copy. Objections should be explained and suggestions
>> >> to resolve them are highly appreciated.
>> >> 
>> >> Authors, and WG participants in general, are reminded of the Intellectual
>> >> Property Rights (IPR) disclosure obligations described in BCP 79 [1].
>> >> Appropriate IPR disclosures required for full conformance with the provisions
>> >> of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
>> >> Sanctions available for application to violators of IETF IPR Policy can be
>> >> found at [3].
>> >> 
>> >> Thank you.
>> >> 
>> >> [1] https://datatracker.ietf.org/doc/bcp78/
>> >> [2] https://datatracker.ietf.org/doc/bcp79/
>> >> [3] https://datatracker.ietf.org/doc/rfc6701/
>> >> 
>> >> The IETF datatracker status page for this Internet-Draft is:
>> >> https://datatracker.ietf.org/doc/draft-ietf-httpbis-secondary-server-certs/
>> >> 
>> >> There is also an HTML version available at:
>> >> https://www.ietf.org/archive/id/draft-ietf-httpbis-secondary-server-certs-02.html
>> >> 
>> >> A diff from the previous version is available at:
>> >> https://author-tools.ietf.org/iddiff?url2=draft-ietf-httpbis-secondary-server-certs-02
>> >> 
>> >
>> > --
>> > Mark Nottingham   https://mnot.net <https://mnot.net/>/

Received on Monday, 21 September 2026 17:55:45 UTC