Authenticated Identity Management in the Session Initiation Protocol (SIP)
RFC 8224
| Document | Type |
RFC - Proposed Standard
(February 2018; Errata)
Obsoletes RFC 4474
|
|
|---|---|---|---|
| Last updated | 2018-12-19 | ||
| Replaces | draft-jennings-stir-rfc4474bis | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Robert Sparks | ||
| Shepherd write-up | Show (last changed 2016-10-18) | ||
| IESG | IESG state | RFC 8224 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Adam Roach | ||
| Send notices to | "Robert Sparks" <rjsparks@nostrum.com> | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) J. Peterson
Request for Comments: 8224 NeuStar
Obsoletes: 4474 C. Jennings
Category: Standards Track Cisco
ISSN: 2070-1721 E. Rescorla
RTFM, Inc.
C. Wendt
Comcast
February 2018
Authenticated Identity Management
in the Session Initiation Protocol (SIP)
Abstract
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8224.
Peterson, et al. Standards Track [Page 1]
RFC 8224 SIP Identity February 2018
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction ....................................................3
2. Terminology .....................................................4
3. Architectural Overview ..........................................5
4. Identity Header Field Syntax ....................................7
4.1. PASSporT Construction ......................................8
4.1.1. Example Full and Compact Forms of PASSporT
in Identity ........................................10
5. Example of Operations ..........................................11
5.1. Example Identity Header Construction ......................13
6. Signature Generation and Validation ............................14
6.1. Authentication Service Behavior ...........................14
6.1.1. Handling Repairable Errors .........................16
6.2. Verifier Behavior .........................................17
6.2.1. Authorization of Requests ..........................19
6.2.2. Failure Response Codes Sent by a
Verification Service ...............................19
6.2.3. Handling Retried Requests ..........................21
6.2.4. Handling the Full Form of PASSporT .................21
7. Credentials ....................................................22
7.1. Credential Use by the Authentication Service ..............22
7.2. Credential Use by the Verification Service ................23
7.3. "info" Parameter URIs .....................................24
7.4. Credential System Requirements ............................25
8. Identity Types .................................................26
8.1. Differentiating Telephone Numbers from URIs ...............26
8.2. Authority for Telephone Numbers ...........................27
8.3. Telephone Number Canonicalization Procedures ..............28
8.4. Authority for Domain Names ................................29
8.5. URI Normalization .........................................30
9. Extensibility ..................................................31
10. Backwards Compatibility with RFC 4474 .........................32
Show full document text