[stir] RFC 8224 on Authenticated Identity Management in the Session Initiation Protocol (SIP)
rfc-editor@rfc-editor.org Thu, 15 February 2018 01:34 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 32B0F12D864; Wed, 14 Feb 2018 17:34:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 cO6p8aNRujtq; Wed, 14 Feb 2018 17:34:17 -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 60DF4126CD6; Wed, 14 Feb 2018 17:34:17 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 69D14B81257; Wed, 14 Feb 2018 17:33:59 -0800 (PST)
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: <20180215013359.69D14B81257@rfc-editor.org>
Date: Wed, 14 Feb 2018 17:33:59 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/V-QHcj5k_9F8ac5_dvX4CK-gv_E>
Subject: [stir] RFC 8224 on Authenticated Identity Management in the Session Initiation Protocol (SIP)
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 15 Feb 2018 01:34:19 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8224
Title: Authenticated Identity Management in the
Session Initiation Protocol (SIP)
Author: J. Peterson,
C. Jennings,
E. Rescorla,
C. Wendt
Status: Standards Track
Stream: IETF
Date: February 2018
Mailbox: jon.peterson@neustar.biz,
fluffy@cisco.com,
ekr@rtfm.com,
chris-ietf@chriswendt.net
Pages: 46
Characters: 118924
Obsoletes: RFC 4474
I-D Tag: draft-ietf-stir-rfc4474bis-16.txt
URL: https://www.rfc-editor.org/info/rfc8224
DOI: 10.17487/RFC8224
The baseline security mechanisms in the Session Initiation Protocol
(SIP) are inadequate for cryptographically assuring the identity of
the end users that originate SIP requests, especially in an
interdomain context. This document defines a mechanism for securely
identifying originators of SIP requests. It does so by defining a
SIP header field for conveying a signature used for validating the
identity and for conveying a reference to the credentials of the
signer.
This document obsoletes RFC 4474.
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