We're going through AUTH48 with SVCB right now and reviewing edits from the
RFC Editor.  I think there is a good question of how to handle this.  Right
now it is "RESERVED (will be used for ECH)" for SvcParamKey "ech" (5) but
we also say:

New entries in this registry are subject to an Expert Review registration
policy ([RFC8126
<https://www.ietf.org/archive/id/draft-ietf-dnsop-svcb-https-12.html#RFC8126>],
Section 4.5 <https://rfc-editor.org/rfc/rfc8126#section-4.5>). The
designated expert MUST ensure that the Format Reference is stable and
publicly available, and that it specifies how to convert the
SvcParamValue's presentation format to wire format. The Format Reference
MAY be any individual's Internet-Draft, or a document from any other source
with similar assurances of stability and availability. An entry MAY specify
a Format Reference of the form "Same as (other key Name)" if it uses the
same presentation and wire formats as an existing key.

This puts this in a weird state given that the ECH specification is not
stable yet and did have some changes.
Perhaps a question for the dnsops chairs and Warren as well?

Should draft-ietf-tls-esni be referenced informationally?  It seems like
there's a risk of "ech=" (5) getting burned as a codepoint
given that implementations may exist with different interpretations...

      Erik



On Tue, Sep 19, 2023 at 11:22 AM Sean Turner <s...@sn3rd.com> wrote:

>
>
> > On Sep 18, 2023, at 21:39, Stephen Farrell <stephen.farr...@cs.tcd.ie>
> wrote:
> >
> > I wonder if we also need to say something about the ech= SVCB
> > parameter value 5 that's reserved at [1]? Not sure, but maybe
> > no harm to make that "official" at the same time if possible.
> > (There could be current code that assumes that 5 in a wire-
> > format HTTPS RR value maps to 0xff0d within an ECHConfigList
> > even if that isn't really right.)
>
> I’ll check with the dnsops chairs.
>
> spt
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls

Reply via email to