[rfc-dist] RFC 5367 on Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP)

A new Request for Comments is now available in online RFC libraries.

        RFC 5367

        Title:      Subscriptions to Request-Contained Resource Lists 
                    in the Session Initiation Protocol (SIP) 
        Author:     G. Camarillo, A.B. Roach,
                    O. Levin
        Status:     Standards Track
        Date:       October 2008
        Mailbox:    Gonzalo.Camarillo at ericsson.com, 
                    Adam.Roach at tekelec.com, 
                    oritl at microsoft.com
        Pages:      9
        Characters: 18329
        Updates:    RFC3265

        I-D Tag:    draft-ietf-sip-uri-list-subscribe-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5367.txt

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.  [STANDARDS TRACK]

This document is a product of the Session Initiation Protocol Working 
Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
USC/Information Sciences Institute