Authenticated Identity Management in the Session Initiation Protocol (SIP)
draft-jennings-stir-rfc4474bis-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-10-21
Replaced by rfc8224, draft-ietf-stir-rfc4474bis
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        J. Peterson
Internet-Draft                                                   NeuStar
Intended status: Standards Track                             C. Jennings
Expires: April 24, 2014                                            Cisco
                                                             E. Rescorla
                                                              RTFM, Inc.
                                                        October 21, 2013

  Authenticated Identity Management in the Session Initiation Protocol
                                 (SIP)
                   draft-jennings-stir-rfc4474bis-00

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 April 24, 2014.

Copyright Notice

   Copyright (c) 2013 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 April 24, 2014                 [Page 1]
Internet-Draft                SIP Identity                  October 2013

   (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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Intermediary Authentication Services  . . . . . . . . . .   6
   4.  Overview of Operations  . . . . . . . . . . . . . . . . . . .   6
   5.  Signature Generation and Validation . . . . . . . . . . . . .   7
     5.1.  Authentication Service Behavior . . . . . . . . . . . . .   7
       5.1.1.  Identity within a Dialog and Retargeting  . . . . . .  10
     5.2.  Verifier Behavior . . . . . . . . . . . . . . . . . . . .  11
   6.  Credentials . . . . . . . . . . . . . . . . . . . . . . . . .  13
     6.1.  Credential Use by the Authentication Service  . . . . . .  13
     6.2.  Credential Use by the Verification Service  . . . . . . .  14
     6.3.  Handling Identity-Info URIs . . . . . . . . . . . . . . .  14
   7.  Identity and Telephone Numbers  . . . . . . . . . . . . . . .  16
   8.  Considerations for User Agents  . . . . . . . . . . . . . . .  17
   9.  Considerations for Proxy Servers  . . . . . . . . . . . . . .  18
   10. Header Syntax . . . . . . . . . . . . . . . . . . . . . . . .  18
   11. Compliance Tests and Examples . . . . . . . . . . . . . . . .  22
     11.1.  Identity-Info with a Singlepart MIME body  . . . . . . .  22
     11.2.  Identity for a Request with No MIME Body or Contact  . .  25
Show full document text