Owen Friel \(ofriel\) <ofriel=40cisco....@dmarc.ietf.org> wrote:
> This addresses all issues raised on the mailers. The issues and
> associated fixes can all be seen at:
> https://github.com/upros/acme-integrations/issues?q=is%3Aissue+
> The authors noticed one issues related to Joe Salowey's feedback on
> tls-unique channel binding:
> An update for TEAP is underway that can be used to address channel
> binding in TLS1.3 using RFC9266.
which I think is specified in draft-ietf-emu-tls-eap-types-04, section 2.2.
> However, there is no currently planned update for EST RFC7030 to
> specify how to use RFC9266. EST only references tls-unique. How should
> we proceed here?
AFAIK, a TLS1.3 exporter just needs a string to be specified somewhere.
Where should we specify this?
--
Michael Richardson <mcr+i...@sandelman.ca> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ Acme mailing list Acme@ietf.org https://www.ietf.org/mailman/listinfo/acme
