[stir] RFC 9027 on Assertion Values for Resource Priority Header and SIP Priority Header Claims in Support of Emergency Services Networks
rfc-editor@rfc-editor.org Fri, 04 June 2021 06:02 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 1292E3A2A31; Thu, 3 Jun 2021 23:02:09 -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=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 I0R8-HkIVX9r; Thu, 3 Jun 2021 23:02:04 -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 1CE8A3A2981; Thu, 3 Jun 2021 23:02:03 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D9B62F40725; Thu, 3 Jun 2021 23:01:37 -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: <20210604060137.D9B62F40725@rfc-editor.org>
Date: Thu, 03 Jun 2021 23:01:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/TaFcfFxJfTvNDmv8jDEVyjBkIdM>
Subject: [stir] RFC 9027 on Assertion Values for Resource Priority Header and SIP Priority Header Claims in Support of Emergency Services Networks
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 04 Jun 2021 06:02:10 -0000
A new Request for Comments is now available in online RFC libraries. RFC 9027 Title: Assertion Values for Resource Priority Header and SIP Priority Header Claims in Support of Emergency Services Networks Author: M. Dolly, C. Wendt Status: Standards Track Stream: IETF Date: June 2021 Mailbox: md3135@att.com, chris-ietf@chriswendt.net Pages: 7 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-stir-rph-emergency-services-07.txt URL: https://www.rfc-editor.org/info/rfc9027 DOI: 10.17487/RFC9027 This document adds new assertion values for a Resource Priority Header ("rph") claim and a new SIP Priority Header ("sph") claim for protection of the "psap-callback" value as part of the "rph" Personal Assertion Token (PASSporT) extension in support of the security of emergency services networks for emergency call origination and callback. 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