[rfc-dist] RFC 4661 on An Extensible Markup Language (XML)-Based Format for Event Notification Filtering

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Tue Sep 26 16:15:15 PDT 2006


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

        
        RFC 4661

        Title:      An Extensible Markup Language (XML)-Based 
                    Format for Event Notification Filtering 
        Author:     H. Khartabil, E. Leppanen,
                    M. Lonnfors, J. Costa-Requena
        Status:     Standards Track
        Date:       September 2006
        Mailbox:    hisham.khartabil at telio.no, 
                    eva-maria.leppanen at nokia.com, 
                    mikko.lonnfors at nokia.com,  
                    jose.costa-requena at nokia.com
        Pages:      24
        Characters: 48890
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-simple-filter-format-05.txt

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

The SIP event notification framework describes the usage of the
Session Initiation Protocol (SIP) for subscriptions and notifications
of changes to a state of a resource.  The document does not describe
a mechanism whereby filtering of event notification information can
be achieved.  Filtering is a mechanism for defining the preferred
notification information to be delivered and for specifying triggers
that cause that information to be delivered.  In order to enable
this, a format is needed to enable the subscriber to describe the
state changes of a resource that cause notifications to be sent to it
and what those notifications are to contain.  This document presents
a format in the form of an XML document.  [STANDARDS TRACK]

This document is a product of the SIP for Instant Messaging and Presence 
Leveraging Extensions 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

...




More information about the rfc-dist mailing list