RFC 8816 on Secure Telephone Identity Revisited (STIR) Out-of-Band Architecture and Use Cases
rfc-editor@rfc-editor.org Thu, 11 February 2021 19:50 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21EE83A18C2; Thu, 11 Feb 2021 11:50:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 F_VE-AE5YEp4; Thu, 11 Feb 2021 11:49:58 -0800 (PST)
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 8B6FC3A18BF; Thu, 11 Feb 2021 11:49:58 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id DA07DF40737; Thu, 11 Feb 2021 11:49:27 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8816 on Secure Telephone Identity Revisited (STIR) Out-of-Band Architecture and Use Cases
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: <20210211194927.DA07DF40737@rfc-editor.org>
Date: Thu, 11 Feb 2021 11:49:27 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/CCvasa54-5pQTYkSUpw4-iJxssk>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2021 19:50:00 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8816
Title: Secure Telephone Identity Revisited (STIR)
Out-of-Band Architecture and Use Cases
Author: E. Rescorla,
J. Peterson
Status: Informational
Stream: IETF
Date: February 2021
Mailbox: ekr@rtfm.com,
jon.peterson@team.neustar
Pages: 24
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-stir-oob-07.txt
URL: https://www.rfc-editor.org/info/rfc8816
DOI: 10.17487/RFC8816
The Personal Assertion Token (PASSporT) format defines a token that
can be carried by signaling protocols, including SIP, to
cryptographically attest the identity of callers. However, not all
telephone calls use Internet signaling protocols, and some calls use
them for only part of their signaling path, while some cannot
reliably deliver SIP header fields end-to-end. This document
describes use cases that require the delivery of PASSporT objects
outside of the signaling path, and defines architectures and
semantics to provide this functionality.
This document is a product of the Secure Telephone Identity Revisited Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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