A Framework for Session Initiation Protocol User Agent Profile Delivery
RFC 6080

Internet Engineering Task Force (IETF)                         D. Petrie
Request for Comments: 6080                                     SIPez LLC
Category: Standards Track                          S. Channabasappa, Ed.
ISSN: 2070-1721                                                CableLabs
                                                              March 2011

A Framework for Session Initiation Protocol User Agent Profile Delivery

Abstract

   This document specifies a framework to enable configuration of
   Session Initiation Protocol (SIP) user agents (UAs) in SIP
   deployments.  The framework provides a means to deliver profile data
   that user agents need to be functional, automatically and with
   minimal or no User and Administrative intervention.  The framework
   describes how SIP user agents can discover sources, request profiles,
   and receive notifications related to profile modifications.  As part
   of this framework, a new SIP event package is defined for
   notification of profile changes.  The framework provides minimal data
   retrieval options to ensure interoperability.  The framework does not
   include specification of the profile data within its scope.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6080.

Petrie & Channabasappa       Standards Track                    [Page 1]
RFC 6080               SIP Configuration Framework            March 2011

Copyright Notice

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

Petrie & Channabasappa       Standards Track                    [Page 2]
RFC 6080               SIP Configuration Framework            March 2011

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  Reference Model  . . . . . . . . . . . . . . . . . . . . .  6
     3.2.  Motivation . . . . . . . . . . . . . . . . . . . . . . . .  7
     3.3.  Profile Types  . . . . . . . . . . . . . . . . . . . . . .  9
     3.4.  Profile Delivery Stages  . . . . . . . . . . . . . . . . .  9
     3.5.  Supported Device Types . . . . . . . . . . . . . . . . . . 10
   4.  Use Cases  . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     4.1.  Simple Deployment Scenario . . . . . . . . . . . . . . . . 10
     4.2.  Devices Supporting Multiple Users from Different
           Service Providers  . . . . . . . . . . . . . . . . . . . . 12
   5.  Profile Delivery Framework . . . . . . . . . . . . . . . . . . 14
     5.1.  Profile Delivery Stages  . . . . . . . . . . . . . . . . . 14
     5.2.  Securing Profile Delivery  . . . . . . . . . . . . . . . . 22
     5.3.  Additional Considerations  . . . . . . . . . . . . . . . . 24
     5.4.  Support for NATs . . . . . . . . . . . . . . . . . . . . . 33
   6.  Event Package Definition . . . . . . . . . . . . . . . . . . . 33