Re: [Sframe] Roman Danyliw's No Objection on draft-ietf-sframe-enc-07: (with COMMENT)

[Richard Barnes <[e-mail]>]

Hi Roman,

Fair point.  I filed a PR:

https://github.com/sframe-wg/sframe/pull/196

--Richard

On Tue, Apr 2, 2024 at 11:28 PM Roman Danyliw via Datatracker <
[e-mail]> wrote:

> Roman Danyliw has entered the following ballot position for
> draft-ietf-sframe-enc-07: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to
> https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/
> for more information about how to handle DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-sframe-enc/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Thank you to Linda Dunbar for the GENART review.  I reviewed this document
> for
> GEN area issues.
>
> ** Section 8.1.  Per the SFrame Cipher Suites registry, did the working
> group
> consider adding another column to the registry to capture the whether the
> IETF
> recommends the use of a given ciphersuite?  Consider the definition of a
> “Recommended” column in the TLS Ciphersuites and COSE Algorithms
> registries:
>
> --
>
> https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-parameters-4
> -- https://www.iana.org/assignments/cose/cose.xhtml#algorithms
>
> Could such a Recommendation column be added here?  It helps readers of the
> registry quickly understand which registrations have an IETF endorsement,
> while
> still making it easy to add code points.
>
>
>
>