Cluster Details

• draft-ietf-jose-json-web-signature-41.txt  RFC7515  PUB
• draft-ietf-jose-json-web-encryption-40.txt  RFC7516  PUB
• draft-ietf-jose-json-web-key-41.txt  RFC7517  PUB
• draft-ietf-jose-json-web-algorithms-40.txt  RFC7518  PUB
• draft-ietf-oauth-json-web-token-32.txt  RFC7519  PUB
• draft-ietf-jose-cookbook-08.txt  RFC7520  PUB
• draft-ietf-oauth-assertions-18.txt  RFC7521  PUB
• draft-ietf-oauth-saml2-bearer-23.txt  RFC7522  PUB
• draft-ietf-oauth-jwt-bearer-12.txt  RFC7523  PUB
• draft-ietf-oauth-dyn-reg-30.txt  RFC7591  PUB
• draft-ietf-oauth-dyn-reg-management-15.txt  RFC7592  PUB
• draft-ietf-kitten-sasl-oauth-23.txt  RFC7628  PUB
• draft-ietf-tram-turn-third-party-authz-16.txt  RFC7635  PUB

Instructions to author(s):

Please see the AUTH48 notification email from the RFC Editor that contains links to the edited files and other information. To send your approval of or changes for a specific document, please Reply All to the message for the given RFC-to-be in question.

If cluster-wide questions were received, please Reply All to that email so each of the relevant parties may partake in the decision process.

See information below for the status of documents within the cluster that are in AUTH48.

When all approvals for a given document have been received, publication will continue once its normative references have completed the AUTH48 process as well. Upon publication of the cluster, this AUTH48 status page will no longer be available.