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

The information below is for an old version of the document
Document Type Active Internet-Draft (stir WG)
Last updated 2015-03-10
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: September 9, 2015                                         Cisco
                                                             E. Rescorla
                                                              RTFM, Inc.
                                                           March 8, 2015

  Authenticated Identity Management in the Session Initiation Protocol
                                 (SIP)
                   draft-ietf-stir-rfc4474bis-03.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 new
   SIP header fields 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 September 9, 2015.

Copyright Notice

   Copyright (c) 2015 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

Peterson, et al.        Expires September 9, 2015               [Page 1]
Internet-Draft                SIP Identity                    March 2015

   (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  . . . . . . . . . . . . . . . . . . .   5
   4.  Signature Generation and Validation . . . . . . . . . . . . .   6
     4.1.  Authentication Service Behavior . . . . . . . . . . . . .   6
     4.2.  Verifier Behavior . . . . . . . . . . . . . . . . . . . .   9
   5.  Credentials . . . . . . . . . . . . . . . . . . . . . . . . .  10
     5.1.  Credential Use by the Authentication Service  . . . . . .  10
     5.2.  Credential Use by the Verification Service  . . . . . . .  12
     5.3.  Handling Identity-Info URIs . . . . . . . . . . . . . . .  12
     5.4.  Credential Systems  . . . . . . . . . . . . . . . . . . .  13
   6.  Identity Types  . . . . . . . . . . . . . . . . . . . . . . .  14
     6.1.  Telephone Numbers . . . . . . . . . . . . . . . . . . . .  14
       6.1.1.  Canonicalization Procedures . . . . . . . . . . . . .  15
     6.2.  Domain Names  . . . . . . . . . . . . . . . . . . . . . .  16
   7.  Header Syntax . . . . . . . . . . . . . . . . . . . . . . . .  17
   8.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  20
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  21
     9.1.  Handling of digest-string Elements  . . . . . . . . . . .  21
       9.1.1.  Protection of the To Header and Retargeting . . . . .  24
     9.2.  Securing the Connection to the Authentication Service . .  25
     9.3.  Authorization and Transitional Strategies . . . . . . . .  26
     9.4.  Display-Names and Identity  . . . . . . . . . . . . . . .  27
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  27
     10.1.  Header Field Names . . . . . . . . . . . . . . . . . . .  27
     10.2.  Identity-Info Parameters . . . . . . . . . . . . . . . .  28
     10.3.  Identity-Info Algorithm Parameter Values . . . . . . . .  28
   11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  28
   12. Changes from RFC4474  . . . . . . . . . . . . . . . . . . . .  28
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .  29
Show full document text