Authenticated Identity Management in the Session Initiation Protocol (SIP)
draft-ietf-stir-rfc4474bis-12

The information below is for an old version of the document
Document Type Active Internet-Draft (stir WG)
Last updated 2016-09-09
Replaces draft-jennings-stir-rfc4474bis
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
Stream WG state In WG Last Call
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: March 13, 2017                                            Cisco
                                                             E. Rescorla
                                                              RTFM, Inc.
                                                                C. Wendt
                                                                 Comcast
                                                       September 9, 2016

  Authenticated Identity Management in the Session Initiation Protocol
                                 (SIP)
                   draft-ietf-stir-rfc4474bis-12.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 March 13, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Peterson, et al.         Expires March 13, 2017                 [Page 1]
Internet-Draft                SIP Identity                September 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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Architectural Overview  . . . . . . . . . . . . . . . . . . .   4
   4.  Identity Header Field Syntax  . . . . . . . . . . . . . . . .   6
     4.1.  PASSporT Construction . . . . . . . . . . . . . . . . . .   7
       4.1.1.  'canon' and PASSporT  . . . . . . . . . . . . . . . .   9
   5.  Example of Operations . . . . . . . . . . . . . . . . . . . .  10
     5.1.  Example Identity Header Construction  . . . . . . . . . .  11
   6.  Signature Generation and Validation . . . . . . . . . . . . .  13
     6.1.  Authentication Service Behavior . . . . . . . . . . . . .  13
     6.2.  Verifier Behavior . . . . . . . . . . . . . . . . . . . .  16
       6.2.1.  Authorization of Requests . . . . . . . . . . . . . .  17
       6.2.2.  Response Codes Sent by a Verification Service . . . .  18
       6.2.3.  Handling 'canon' parameters . . . . . . . . . . . . .  19
   7.  Credentials . . . . . . . . . . . . . . . . . . . . . . . . .  20
     7.1.  Credential Use by the Authentication Service  . . . . . .  20
     7.2.  Credential Use by the Verification Service  . . . . . . .  21
     7.3.  'info' parameter URIs . . . . . . . . . . . . . . . . . .  22
     7.4.  Credential System Requirements  . . . . . . . . . . . . .  22
   8.  Identity Types  . . . . . . . . . . . . . . . . . . . . . . .  24
     8.1.  Differentiating Telephone Numbers from URIs . . . . . . .  24
     8.2.  Authority for Telephone Numbers . . . . . . . . . . . . .  25
     8.3.  Telephone Number Canonicalization Procedures  . . . . . .  25
     8.4.  Authority for Domain Names  . . . . . . . . . . . . . . .  26
     8.5.  URI Normalization . . . . . . . . . . . . . . . . . . . .  27
   9.  Extensibility . . . . . . . . . . . . . . . . . . . . . . . .  28
   10. Backwards Compatibililty with RFC4474 . . . . . . . . . . . .  29
   11. Privacy Considerations  . . . . . . . . . . . . . . . . . . .  29
Show full document text