[rfc-dist] RFC 5344 on Presence and Instant Messaging Peering Use Cases

[rfc-editor@rfc-editor.org]

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

        
        RFC 5344

        Title:      Presence and Instant Messaging Peering 
                    Use Cases 
        Author:     A. Houri, E. Aoki,
                    S. Parameswar
        Status:     Informational
        Date:       October 2008
        Mailbox:    avshalom at il.ibm.com, 
                    aoki at aol.net, 
                    Sriram.Parameswar at microsoft.com
        Pages:      9
        Characters: 18389
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-speermint-consolidated-presence-im-usecases-05.txt

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

This document describes several use cases of peering of non-VoIP
(Voice over IP) services between two or more Service Providers.  These
Service Providers create a peering relationship between themselves,
thus enabling their users to collaborate with users on the other
Service Provider network.  The target of this document is to drive
requirements for peering between domains that provide the non-VoIP
based collaboration services with presence and, in particular, Instant
Messaging (IM).  This memo provides information for the Internet community.

This document is a product of the Session PEERing for Multimedia INTerconnect Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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