Authenticated Identity Management in the Session Initiation Protocol (SIP)
draft-ietf-stir-rfc4474bis-07
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (stir WG)
|
|
Last updated |
|
2016-02-03
|
|
Replaces |
|
draft-jennings-stir-rfc4474bis
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized
bibtex
|
|
Reviews |
|
|
Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
No shepherd assigned
|
IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group J. Peterson
Internet-Draft NeuStar
Intended status: Standards Track C. Jennings
Expires: August 6, 2016 Cisco
E. Rescorla
RTFM, Inc.
C. Wendt
Comcast
February 3, 2016
Authenticated Identity Management in the Session Initiation Protocol
(SIP)
draft-ietf-stir-rfc4474bis-07.txt
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.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 6, 2016.
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
Peterson, et al. Expires August 6, 2016 [Page 1]
Internet-Draft SIP Identity February 2016
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://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. Background . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Overview of Operations . . . . . . . . . . . . . . . . . . . 6
4. Signature Generation and Validation . . . . . . . . . . . . . 7
4.1. Authentication Service Behavior . . . . . . . . . . . . . 7
4.2. Verifier Behavior . . . . . . . . . . . . . . . . . . . . 9
5. Credentials . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.1. Credential Use by the Authentication Service . . . . . . 11
5.2. Credential Use by the Verification Service . . . . . . . 12
5.3. Handling 'info' parameter URIs . . . . . . . . . . . . . 13
5.4. Credential System Requirements . . . . . . . . . . . . . 13
6. Identity Types . . . . . . . . . . . . . . . . . . . . . . . 15
6.1. Telephone Numbers . . . . . . . . . . . . . . . . . . . . 15
6.1.1. Canonicalization Procedures . . . . . . . . . . . . . 15
6.2. Domain Names . . . . . . . . . . . . . . . . . . . . . . 17
7. Header Syntax . . . . . . . . . . . . . . . . . . . . . . . . 18
8. Extensibility . . . . . . . . . . . . . . . . . . . . . . . . 21
9. Gatewaying to PASSporT for non-SIP Transit . . . . . . . . . 22
10. Privacy Considerations . . . . . . . . . . . . . . . . . . . 22
11. Security Considerations . . . . . . . . . . . . . . . . . . . 24
11.1. Protected Request Fields . . . . . . . . . . . . . . . . 24
11.1.1. Protection of the To Header and Retargeting . . . . 26
11.2. Unprotected Request Fields . . . . . . . . . . . . . . . 26
11.3. Malicious Removal of Identity Headers . . . . . . . . . 27
11.4. Securing the Connection to the Authentication Service . 28
11.5. Authorization and Transitional Strategies . . . . . . . 29
11.6. Display-Names and Identity . . . . . . . . . . . . . . . 30
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
Show full document text