[TLS] Re: Opsdir last call review of draft-ietf-tls-rfc8447bis-11

[Sean Turner <[e-mail]>]

> On Apr 3, 2025, at 10:54 AM, Giuseppe Fioccola via Datatracker <[e-mail]> wrote:
> 
> Reviewer: Giuseppe Fioccola
> Review result: Has Nits
> 
> This document updates the changes in RFC 8447 and requests IANA to make changes
> to a number of TLS and DTLS registries. In particular, it updates the
> "Recommended" column in TLS registries by defining a third value "D" for items
> that are discouraged and adds a "Comment" column to the registries that do not
> already have it. This document updates several RFCs: RFC 3749, RFC 5077, RFC
> 4680, RFC 5246, RFC 5705, RFC 5878, RFC 6520, RFC 7301, and RFC 8447.
> 
> I think that the document has a well defined scope and is quite clear. However,
> I have few suggestions:
> 
> - In the Abstract, I suggest to replace 'adds a Comments column to all active
> registries' with 'adds a Comment column to all the registries that do not
> already have it'.

Done via:
https://github.com/tlswg/rfc8447bis/pull/76

> - In section 3, I suggest to replace 'The permitted values are' with 'The
> permitted values of the Recommended column are', just to avoid any confusion.

Done via:
https://github.com/tlswg/rfc8447bis/pull/76

> - In the sections from 4 to 14, I suggest to add some explanation on why
> specific registries are changed to discouraged. Some insight would help the
> reader.

We had other comments along these lines. I went through and looked at whether there were links to the drafts that gave info on why D; see https://github.com/tlswg/rfc8447bis/pull/74. Mostly, we added a ref back to this document which includes the info.

> - I would also add some observations on the operational and interoperability
> impacts, if any, of the changes proposed in the document.
> 
> - Currently, the section on "IANA Considerations" simply says that the document
> is entirely about changes to TLS-related IANA registries, as per RFC 8447.
> Instead, I would put all the relevant sections on IANA requests (i.e. sections
> from 4 to 14) under an "IANA Considerations" section. In this way you can avoid
> the IANA section with no content.

On these, two we’ll take them under advisement. On the ops and inerop impacts, I am not sure there is much more to say beyond hey make sure your implementation is updatable and configurable. On the last point, we could do that, but this draft has been in this format for 4 years and RFC 8447 before it has the same format.

Cheers,
spt