[stir] RFC 9060 on Secure Telephone Identity Revisited (STIR) Certificate Delegation
rfc-editor@rfc-editor.org Fri, 17 September 2021 23:00 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 BF8AF3A1A31; Fri, 17 Sep 2021 16:00:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, 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 rCMDc9ioYygI; Fri, 17 Sep 2021 16:00:36 -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 738A73A1A36; Fri, 17 Sep 2021 16:00:34 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 263C7F4085F; Fri, 17 Sep 2021 15:59:53 -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: <20210917225953.263C7F4085F@rfc-editor.org>
Date: Fri, 17 Sep 2021 15:59:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/4kXm_edrO8j1XPLUuZD1eaerdvQ>
Subject: [stir] RFC 9060 on Secure Telephone Identity Revisited (STIR) Certificate Delegation
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, 17 Sep 2021 23:00:41 -0000
A new Request for Comments is now available in online RFC libraries. RFC 9060 Title: Secure Telephone Identity Revisited (STIR) Certificate Delegation Author: J. Peterson Status: Standards Track Stream: IETF Date: September 2021 Mailbox: jon.peterson@team.neustar Pages: 12 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-stir-cert-delegation-04.txt URL: https://www.rfc-editor.org/info/rfc9060 DOI: 10.17487/RFC9060 The Secure Telephone Identity Revisited (STIR) certificate profile provides a way to attest authority over telephone numbers and related identifiers for the purpose of preventing telephone number spoofing. This specification details how that authority can be delegated from a parent certificate to a subordinate certificate. This supports a number of use cases, including those where service providers grant credentials to enterprises or other customers capable of signing calls with STIR. 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