[sipcore] RFC 8898 on Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)
rfc-editor@rfc-editor.org Thu, 10 September 2020 18:19 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AC783A0BE9; Thu, 10 Sep 2020 11:19:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Flq_W4iIk8e8; Thu, 10 Sep 2020 11:19:14 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C29113A0BCD; Thu, 10 Sep 2020 11:19:14 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 16731F4076D; Thu, 10 Sep 2020 11:18:52 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, sipcore@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200910181852.16731F4076D@rfc-editor.org>
Date: Thu, 10 Sep 2020 11:18:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/BlqdhOGGstdBS1knsuMG4K75FC8>
Subject: [sipcore] RFC 8898 on Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2020 18:19:18 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8898
Title: Third-Party Token-Based Authentication
and Authorization
for Session Initiation Protocol (SIP)
Author: R. Shekh-Yusef,
C. Holmberg,
V. Pascual
Status: Standards Track
Stream: IETF
Date: September 2020
Mailbox: rifaat.s.ietf@gmail.com,
christer.holmberg@ericsson.com,
victor.pascual.avila@gmail.com
Pages: 15
Updates: RFC 3261
I-D Tag: draft-ietf-sipcore-sip-token-authnz-17.txt
URL: https://www.rfc-editor.org/info/rfc8898
DOI: 10.17487/RFC8898
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.
This document is a product of the Session Initiation Protocol Core 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 rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC