Last Call: <draft-ietf-sipcore-sip-token-authnz-12.txt> (Third-Party Token-based Authentication and Authorization for Session Initiation Protocol (SIP)) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Wed, 01 April 2020 14:02 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-sipcore-sip-token-authnz-12.txt> (Third-Party Token-based Authentication and Authorization for Session Initiation Protocol (SIP)) to Proposed Standard
Auto-Submitted: auto-generated
Precedence: bulk
CC: superuser@gmail.com, Jean Mahoney <mahoney@nostrum.com>, sipcore-chairs@ietf.org, draft-ietf-sipcore-sip-token-authnz@ietf.org, mahoney@nostrum.com, sipcore@ietf.org
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <158574974391.30773.6545584405944524603@ietfa.amsl.com>
Date: Wed, 01 Apr 2020 07:02:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/g2SFJg6Y8r9KI82gLjMiJTh8LKY>

The IESG has received a request from the Session Initiation Protocol Core WG
(sipcore) to consider the following document: - 'Third-Party Token-based
Authentication and Authorization for Session
   Initiation Protocol (SIP)'
  <draft-ietf-sipcore-sip-token-authnz-12.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2020-04-15. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   This document defines the "Bearer" authentication scheme for the
   Session Initiation Protocol (SIP), and a mechanism by which user
   authentication and SIP registration authorization is delegated to a
   third party, using the OAuth 2.0 framework and OpenID Connect Core
   1.0.  This document updates RFC 3261 to provide guidance on how a SIP
   User Agent Client (UAC) responds to a SIP 401/407 response that
   contains multiple WWW-Authenticate/Proxy-Authenticate header fields.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-sipcore-sip-token-authnz/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-sipcore-sip-token-authnz/ballot/


No IPR declarations have been submitted directly on this I-D.

Last Call: <draft-ietf-sipcore-sip-token-authnz-1… The IESG