Re: [TLS] [Editorial Errata Reported] RFC8996 (7739)

[Rebecca VanRheenen <[e-mail]>]

Greetings,

FYI - this report has been deleted as junk (identical text is listed in Original Text, Corrected Text, and Notes, and this text does not even appear in this RFC).

Thank you.

RFC Editor/rv


> On Dec 21, 2023, at 7:02 PM, RFC Errata System <[e-mail]> wrote:
> 
> The following errata report has been submitted for RFC8996,
> "Deprecating TLS 1.0 and TLS 1.1".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid7739
> 
> --------------------------------------
> Type: Editorial
> Reported by: mohamed abdurahman hassan <[e-mail]>
> 
> 96
> 
> Original Text
> -------------
> 
>   application.  The authorization server should take special care when
>   enabling this grant type and only allow it when other flows are not
>   viable.
> 
>   This grant type is suitable for clients capable of obtaining the
>   resource owner's credentials (username and password, typically using
>   an interactive form).  It is also used to migrate existing clients
>   using direct authentication schemes such as HTTP Basic or Digest
>   authentication to OAuth by converting the stored credentials to an
>   access token.
> 
> 
> Corrected Text
> --------------
> 
>   application.  The authorization server should take special care when
>   enabling this grant type and only allow it when other flows are not
>   viable.
> 
>   This grant type is suitable for clients capable of obtaining the
>   resource owner's credentials (username and password, typically using
>   an interactive form).  It is also used to migrate existing clients
>   using direct authentication schemes such as HTTP Basic or Digest
>   authentication to OAuth by converting the stored credentials to an
>   access token.
> 
> 
> Notes
> -----
> application.  The authorization server should take special care when
>   enabling this grant type and only allow it when other flows are not
>   viable.
> 
>   This grant type is suitable for clients capable of obtaining the
>   resource owner's credentials (username and password, typically using
>   an interactive form).  It is also used to migrate existing clients
>   using direct authentication schemes such as HTTP Basic or Digest
>   authentication to OAuth by converting the stored credentials to an
>   access token.
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". (If it is spam, it 
> will be removed shortly by the RFC Production Center.) Please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party  
> will log in to change the status and edit the report, if necessary.
> 
> --------------------------------------
> RFC8996 (draft-ietf-tls-oldversions-deprecate-12)
> --------------------------------------
> Title               : Deprecating TLS 1.0 and TLS 1.1
> Publication Date    : March 2021
> Author(s)           : K. Moriarty, S. Farrell
> Category            : BEST CURRENT PRACTICE
> Source              : Transport Layer Security
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG