[rfc-dist] RFC 4662 on A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists

[rfc-editor@rfc-editor.org]

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

        
        RFC 4662

        Title:      A Session Initiation Protocol (SIP) 
                    Event Notification Extension for Resource Lists 
        Author:     A. B. Roach, B. Campbell,
                    J. Rosenberg
        Status:     Standards Track
        Date:       August 2006
        Mailbox:    adam at estacado.net, 
                    ben at estacado.net, 
                    jdrosen at cisco.com
        Pages:      39
        Characters: 82778
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-simple-event-list-07.txt

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

This document presents an extension to the Session Initiation
Protocol (SIP)-Specific Event Notification mechanism for subscribing
to a homogeneous list of resources.  Instead of sending a SUBSCRIBE
for each resource individually, the subscriber can subscribe to an
entire list and then receive notifications when the state of any of
the resources in the list changes.  [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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...