[rfc-dist] RFC 4827 on An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Manipulating Presence Document Contents

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Tue May 22 16:41:26 PDT 2007


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

        
        RFC 4827

        Title:      An Extensible Markup Language (XML) 
                    Configuration Access Protocol (XCAP) Usage for 
                    Manipulating Presence Document Contents 
        Author:     M. Isomaki, E. Leppanen
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    markus.isomaki at nokia.com, 
                    eva-maria.leppanen at nokia.com
        Pages:      11
        Characters: 22896
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-simple-xcap-pidf-manipulation-usage-02.txt

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

This document describes a usage of the Extensible Markup Language
(XML) Configuration Access Protocol (XCAP) for manipulating the
contents of Presence Information Data Format (PIDF) based presence
documents.  It is intended to be used in Session Initiation Protocol
(SIP) based presence systems, where the Event State Compositor can
use the XCAP-manipulated presence document as one of the inputs on
which it builds the overall presence state for the presentity.  
[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.


The RFC Editor Team
USC/Information Sciences Institute

...




More information about the rfc-dist mailing list