Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP)
RFC 5367

Document Type RFC - Proposed Standard (October 2008; No errata)
Updates RFC 3265
Last updated 2013-03-02
Replaces draft-ietf-sipping-uri-list-subscribe
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 5367 (Proposed Standard)
Telechat date
Responsible AD Cullen Jennings
Send notices to sip-chairs@ietf.org, gonzalo.camarillo@ericsson.com
Network Working Group                                       G. Camarillo
Request for Comments: 5367                                      Ericsson
Updates: 3265                                                 A.B. Roach
Category: Standards Track                                        Tekelec
                                                                O. Levin
                                                   Microsoft Corporation
                                                            October 2008

           Subscriptions to Request-Contained Resource Lists
                in the Session Initiation Protocol (SIP)

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Abstract

   This document specifies a way to create subscription to a list of
   resources in SIP.  This is achieved by including the list of
   resources in the body of a SUBSCRIBE request.  Instead of having a
   subscriber send a SUBSCRIBE request for each resource individually,
   the subscriber defines the resource list, subscribes to it, and gets
   notifications about changes in the resources' states using a single
   SUBSCRIBE dialog.

Table of Contents

   1. Introduction ....................................................2
   2. Terminology .....................................................2
   3. User Agent Client Procedures ....................................2
      3.1. Response Handling ..........................................2
      3.2. Subsequent SUBSCRIBE Requests ..............................3
   4. URI-List Document Format ........................................3
   5. Resource List Server Behavior ...................................4
      5.1. Subsequent SUBSCRIBE Requests ..............................4
   6. Providing a URI to Manipulate a Resource List ...................4
   7. Example .........................................................5
   8. Security Considerations .........................................6
   9. IANA Considerations .............................................6
      9.1. List-Management Purpose Parameter Value ....................6
      9.2. recipient-list-subscribe Option-Tag ........................7
   10. Acknowledgments ................................................7
   11. Normative References ...........................................7

Camarillo                   Standards Track                     [Page 1]
RFC 5367               SUBSCRIBE-Contained Lists            October 2008

1.  Introduction

   [RFC4662] specifies how to establish subscriptions to a homogeneous
   resource list in SIP (which is specified in [RFC3261]) and defines
   the procedures for getting notifications about changes in the state
   of the associated resources.  Yet, list creation is outside the scope
   of [RFC4662].

   This document specifies a way to create a list with a set of
   resources and subscribe to it using a single SIP request.  This is
   achieved by including the list of resources (as defined in [RFC5363])
   in the body of the SUBSCRIBE request.

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

3.  User Agent Client Procedures

   A UAC (User Agent Client) that wants to create a resource list and
   subscribe to it using the mechanism described in this document
   constructs a SUBSCRIBE request with at least one body, whose
   disposition is type "recipient-list" as defined in [RFC5363], that
   contains the URI list.  Additionally, the UAC MUST include the
   'recipient-list-subscribe' option-tag (which is registered with the
   IANA in Section 9) in a Require header field.  The UAC MUST build the
   rest of the SUBSCRIBE request following the rules in [RFC3265].

   The UAC MUST support the "rlmi+xml" format defined in [RFC4662] and
   signal this by including "rlmi+xml" in the Accept header.  The UAC
   MAY support additional formats and include them in the Accept header
   field of the SUBSCRIBE request.

3.1.  Response Handling

   The status code in the response to the SUBSCRIBE request does not
   provide any information about whether or not the resource list server
   was able to successfully subscribe to the URIs in the URI list.  The
Show full document text