Third-Party Authentication for Session Initiation Protocol (SIP)
draft-yusef-sipcore-sip-authn-01

Document Type Active Internet-Draft (individual)
Last updated 2017-03-09
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
On Agenda sipcore at IETF-98
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
SIP Core                                             R. Shekh-Yusef, Ed.
Internet-Draft                                                     Avaya
Updates: 3261 (if approved)                                  C. Holmberg
Intended status: Standards Track                                Ericsson
Expires: September 10, 2017                                   V. Pascual
                                                                  Oracle
                                                           March 9, 2017

    Third-Party Authentication for Session Initiation Protocol (SIP)
                    draft-yusef-sipcore-sip-authn-01

Abstract

   This document defines an authentication mechanism for SIP, that is
   based on the OAuth 2.0 and OpenID Connect Core 1.0 specifications, to
   enable the delegation of the user authentication to a dedicated
   third-party IdP entity that is separate from the SIP network elements
   that provide the SIP service.

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 10, 2017.

Copyright Notice

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

Shekh-Yusef, et al.    Expires September 10, 2017               [Page 1]
Internet-Draft     Third-Party Authentication for SIP         March 2017

   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
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Roles . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  ID Token  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.4.  SIP User Agent Types  . . . . . . . . . . . . . . . . . .   5
     1.5.  Authentication Types  . . . . . . . . . . . . . . . . . .   5
   2.  Authentication using the Authorization Code Flow  . . . . . .   6
     2.1.  Public UA with Rich UI  . . . . . . . . . . . . . . . . .   6
       2.1.1.  Registration  . . . . . . . . . . . . . . . . . . . .   7
       2.1.2.  Shared-Key  . . . . . . . . . . . . . . . . . . . . .   8
       2.1.3.  Re-Registration Requests  . . . . . . . . . . . . . .   8
       2.1.4.  Token Refresh . . . . . . . . . . . . . . . . . . . .   9
     2.2.  Public UA with Limited UI . . . . . . . . . . . . . . . .  10
       2.2.1.  Registration  . . . . . . . . . . . . . . . . . . . .  10
       2.2.2.  Shared-Key  . . . . . . . . . . . . . . . . . . . . .  11
       2.2.3.  Token Refresh . . . . . . . . . . . . . . . . . . . .  11
       2.2.4.  Re-Registration Requests  . . . . . . . . . . . . . .  12
   3.  Authentication using the Resource Owner Password Credentials
       flow  . . . . . . . . . . . . . . . . . . . . . . . . . . . .  13
     3.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .  13
     3.2.  Registration  . . . . . . . . . . . . . . . . . . . . . .  13
     3.3.  Subsequent Requests . . . . . . . . . . . . . . . . . . .  14
Show full document text