[stir] RFC 8443 on Personal Assertion Token (PASSporT) Extension for Resource Priority Authorization
rfc-editor@rfc-editor.org Sat, 01 September 2018 00:56 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00D57130EA7; Fri, 31 Aug 2018 17:56:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 mPu1IZI_92p0; Fri, 31 Aug 2018 17:56:28 -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 3D000130E84; Fri, 31 Aug 2018 17:56:28 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4B0ECB80831; Fri, 31 Aug 2018 17:56:07 -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, stir@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180901005607.4B0ECB80831@rfc-editor.org>
Date: Fri, 31 Aug 2018 17:56:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/DjKHcFoWFnppvTZ9U4_ryxlIkd0>
Subject: [stir] RFC 8443 on Personal Assertion Token (PASSporT) Extension for Resource Priority Authorization
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Sep 2018 00:56:35 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8443 Title: Personal Assertion Token (PASSporT) Extension for Resource Priority Authorization Author: R. Singh, M. Dolly, S. Das, A. Nguyen Status: Standards Track Stream: IETF Date: August 2018 Mailbox: rsingh@vencorelabs.com, md3135@att.com, sdas@vencorelabs.com, an.p.nguyen@hq.dhs.gov Pages: 10 Characters: 21623 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-stir-rph-06.txt URL: https://www.rfc-editor.org/info/rfc8443 DOI: 10.17487/RFC8443 This document extends the Personal Assertion Token (PASSporT) specification defined in RFC 8225 to allow the inclusion of cryptographically signed assertions of authorization for the values populated in the Session Initiation Protocol (SIP) 'Resource-Priority' header field, which is used for communications resource prioritization. This document is a product of the Secure Telephone Identity Revisited 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