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

        RFC 3863

        Title:      Presence Information Data Format (PIDF)
        Author(s):  H. Sugano, S. Fujimoto, G. Klyne, A. Bateman,
                    W. Carr, J. Peterson
        Status:     Standards Track
        Date:       August 2004
        Mailbox:    [EMAIL PROTECTED],
                    [EMAIL PROTECTED], [EMAIL PROTECTED],
                    [EMAIL PROTECTED], [EMAIL PROTECTED],
                    [EMAIL PROTECTED]
        Pages:      28
        Characters: 56956
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-impp-cpim-pidf-08.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3863.txt


This memo specifies the Common Profile for Presence (CPP) Presence
Information Data Format (PIDF) as a common presence data format for
CPP-compliant Presence protocols, and also defines a new media type
"application/pidf+xml" to represent the XML MIME entity for PIDF.

This document is a product of the Instant Messaging and Presence
Protocol Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 [EMAIL PROTECTED]  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [EMAIL PROTECTED]

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [EMAIL PROTECTED] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [EMAIL PROTECTED]
        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 [EMAIL PROTECTED]  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
[EMAIL PROTECTED]  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
<ftp://ftp.isi.edu/in-notes/rfc3863.txt>
_______________________________________________
IETF-Announce mailing list
[EMAIL PROTECTED]
https://www1.ietf.org/mailman/listinfo/ietf-announce

Reply via email to