Re: [OAUTH-WG] OAuth Digest, Vol 181, Issue 56

ارجو منكم حذف وحضر yxz والعنواين الاخرى المشتبهة التي لاتنتمي الى معاملاتي

في الأربعاء، ٢٩ نوفمبر ٢٠٢٣, ١١:٠٢ م <oauth-request@ietf.org> كتب:

> Send OAuth mailing list submissions to
>         oauth@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://www.ietf.org/mailman/listinfo/oauth
> or, via email, send a message with subject or body 'help' to
>         oauth-request@ietf.org
>
> You can reach the person managing the list at
>         oauth-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of OAuth digest..."
>
>
> Today's Topics:
>
>    1. Re: [Editorial Errata Reported] RFC6749 (7716)
>       (Rebecca VanRheenen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 29 Nov 2023 11:14:44 -0800
> From: Rebecca VanRheenen <rvanrheenen@amsl.com>
> To: Roman Danyliw <rdd@cert.org>
> Cc: hello@alexwilson.io, dick.hardt@gmail.com, oauth@ietf.org, RFC
>         Editor <rfc-editor@rfc-editor.org>
> Subject: Re: [OAUTH-WG] [Editorial Errata Reported] RFC6749 (7716)
> Message-ID: <6AFED015-73A0-4E0A-9AB9-8869DD557B5C@amsl.com>
> Content-Type: text/plain;       charset=utf-8
>
> Hi Roman,
>
> We are unable to verify this erratum that the submitter marked as
> editorial. Please note that we have changed the ?Type? of the following
> errata report to ?Technical?.  As Stream Approver, please review and set
> the Status and Type accordingly (see the definitions at
> https://www.rfc-editor.org/errata-definitions/).
>
> Note that this errata report has two parts. One part states that "
> example.com should be client.example.com?. This is a duplicate of EID
> 4819, which is still in Reported state (see
> https://www.rfc-editor.org/errata/eid4819). Keep this in mind during your
> review.
>
> You may review the report at:
> https://www.rfc-editor.org/errata/eid7716
>
> Please see https://www.rfc-editor.org/how-to-verify/ for further
> information on how to verify errata reports.
>
> Further information on errata can be found at:
> https://www.rfc-editor.org/errata.php
>
> Thank you.
>
> RFC Editor/rv
>
>
>
> > On Nov 29, 2023, at 8:56 AM, RFC Errata System <
> rfc-editor@rfc-editor.org> wrote:
> >
> > The following errata report has been submitted for RFC6749,
> > "The OAuth 2.0 Authorization Framework".
> >
> > --------------------------------------
> > You may review the report below and at:
> > https://www.rfc-editor.org/errata/eid7716
> >
> > --------------------------------------
> > Type: Editorial
> > Reported by: Alex Wilson <hello@alexwilson.io>
> >
> > Section: 4.2.2
> >
> > Original Text
> > -------------
> >   For example, the authorization server redirects the user-agent by
> >   sending the following HTTP response (with extra line breaks for
> >   display purposes only):
> >
> >     HTTP/1.1 302 Found
> >     Location: http://example.com/cb#access_token=2YotnFZFEjr1zCsicMWpAA
> >               &state=xyz&token_type=example&expires_in=3600
> >
> >
> > Corrected Text
> > --------------
> >   For example, the authorization server redirects the user-agent by
> >   sending the following HTTP response (with extra line breaks for
> >   display purposes only):
> >
> >     HTTP/1.1 302 Found
> >     Location:
> http://client.example.com/cb?access_token=2YotnFZFEjr1zCsicMWpAA
> >               &state=xyz&token_type=example&expires_in=3600
> >
> >
> > Notes
> > -----
> > - Host example.com should be client.example.com to be consistent with
> other examples.
> > - A hash is used for the query parameters when a question mark should
> have been used.
> >
> > 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.
> >
> > --------------------------------------
> > RFC6749 (draft-ietf-oauth-v2-31)
> > --------------------------------------
> > Title               : The OAuth 2.0 Authorization Framework
> > Publication Date    : October 2012
> > Author(s)           : D. Hardt, Ed.
> > Category            : PROPOSED STANDARD
> > Source              : Web Authorization Protocol
> > Area                : Security
> > Stream              : IETF
> > Verifying Party     : IESG
> >
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
>
> ------------------------------
>
> End of OAuth Digest, Vol 181, Issue 56
> **************************************
>