[GNAP] Re: RFC 9767 on Grant Negotiation and Authorization Protocol Resource Server Connections

[Deb Cooley <[e-mail]>]

I second Yaron's thought.  Thank you for all the hard work.

Deb

On Wed, Apr 23, 2025 at 3:37 AM Yaron Sheffer <[e-mail]> wrote:

> Thank you Justin and Fabien for the hard work on this RFC and bringing it
> to the finish line.
>
>
>
> The working group has concluded, but this mailing list remains open for
> any discussion of the GNAP protocol.
>
>
>
> Best regards,
>
>
>
>                 Yaron
>
>
>
>
>
> On 23/04/2025, 3:41, "[e-mail]" <
> [e-mail]> wrote:
>
> A new Request for Comments is now available in online RFC libraries.
>
>
>
>
>
>         RFC 9767
>
>
>
>         Title:      Grant Negotiation and Authorization Protocol
>
>                     Resource Server Connections
>
>         Author:     J. Richer, Ed.,
>
>                     F. Imbault
>
>         Status:     Standards Track
>
>         Stream:     IETF
>
>         Date:       April 2025
>
>         Mailbox:    [e-mail],
>
>                     [e-mail]
>
>         Pages:      35
>
>         Updates/Obsoletes/SeeAlso:   None
>
>
>
>         I-D Tag:    draft-ietf-gnap-resource-servers-09.txt
>
>
>
>         URL:        https://www.rfc-editor.org/info/rfc9767
>
>
>
>         DOI:        10.17487/RFC9767
>
>
>
> The Grant Negotiation and Authorization Protocol (GNAP) defines a
>
> mechanism for delegating authorization to a piece of software (the
>
> client) and conveying the results and artifacts of that delegation to
>
> the software. This extension defines methods for resource servers
>
> (RSs) to connect with authorization servers (ASs) in an interoperable
>
> fashion.
>
>
>
> This document is a product of the Grant Negotiation and Authorization
> Protocol Working Group of the IETF.
>
>
>
> This is now a Proposed Standard.
>
>
>
> STANDARDS TRACK: This document specifies an Internet Standards Track
>
> protocol for the Internet community, and requests discussion and
> suggestions
>
> for improvements.  Please refer to the current edition of the Official
>
> Internet Protocol Standards (https://www.rfc-editor.org/standards) for
> the
>
> standardization state and status of this protocol.  Distribution of this
>
> memo is unlimited.
>
>
>
> This announcement is sent to the IETF-Announce and rfc-dist lists.
>
> To subscribe or unsubscribe, see
>
>   https://www.ietf.org/mailman/listinfo/ietf-announce
>
>   https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>
>
>
> For searching the RFC series, see https://www.rfc-editor.org/search
>
> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
>
>
>
> Requests for special distribution should be addressed to either the
>
> author of the RFC in question, or to [e-mail].  Unless
>
> specifically noted otherwise on the RFC itself, all RFCs are for
>
> unlimited distribution.
>
>
>
>
>
> The RFC Editor Team
>
>
>
>
>
> --
>
> TXAuth mailing list -- [e-mail]
>
> To unsubscribe send an email to [e-mail]
>
>
> --
> TXAuth mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
>