On Thu, May 20, 2021 at 6:30 AM Salz, Rich <rsalz=
40akamai....@dmarc.ietf.org> wrote:

> Look at RFC 701, it says: the precise set of octet values that identifies
> the protocol. This could be the UTF-8 encoding of the protocol name.
>
> So I changed my mind and think it's okay to leave as-is but wouldn't mind
> if it became less general or more specific. For example, what if a protocol
> string matches a truncated UTF8 string?  It makes me think of SNI which
> could have any format, but really is "any format as long as it's a DNS name"
>

One intermediate option might be to keep the ALPN TLS extension 8-bit
clean, but change the IANA instructions for the ALPN registry to tighten
the registration requirements.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls

Reply via email to