[Standards] Fwd: RFC 7081 on CUSAX: Combined Use of the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP)

Peter Saint-Andre stpeter at stpeter.im
Mon Dec 2 20:53:46 UTC 2013


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

FYI.


- -------- Original Message --------
Subject: RFC 7081 on CUSAX: Combined Use of the Session Initiation
Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP)
Date: Wed, 27 Nov 2013 12:06:33 -0800 (PST)
From: rfc-editor at rfc-editor.org
Reply-To: ietf at ietf.org
To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org
CC: drafts-update-ref at iana.org, rfc-editor at rfc-editor.org

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


        RFC 7081

        Title:      CUSAX: Combined Use of the
                    Session Initiation Protocol (SIP) and the
                    Extensible Messaging and Presence Protocol (XMPP)
        Author:     E. Ivov, P. Saint-Andre,
                    E. Marocco
        Status:     Informational
        Stream:     IETF
        Date:       November 2013
        Mailbox:    emcho at jitsi.org,
                    psaintan at cisco.com,
                    enrico.marocco at telecomitalia.it
        Pages:      19
        Characters: 46772
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ivov-xmpp-cusax-09.txt

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

This document suggests some strategies for the combined use of the
Session Initiation Protocol (SIP) and the Extensible Messaging and
Presence Protocol (XMPP) both in user-oriented clients and in
deployed servers.  Such strategies, which mainly consist of
configuration changes and minimal software modifications to existing
clients and servers, aim to provide a single, full-featured,
real-time communication service by using complementary subsets of
features from SIP and from XMPP.  Typically, such subsets consist of
telephony capabilities from SIP and instant messaging and presence
capabilities from XMPP.  This document does not define any new
protocols or syntax for either SIP or XMPP and, by intent, does not
attempt to standardize "best current practices".  Instead, it merely
aims to provide practical guidance to those who are interested in the
combined use of SIP and XMPP for real-time communication.


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/search/rfc_search.php
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
Association Management Solutions, LLC




-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSnPNaAAoJEOoGpJErxa2puY0QAJilOzrD3UTmz6SFP01wS5bg
kRFxA3MhKKEoI7Qhduqicx9O57GZPrTxZLowGOJ4uBLRAFJE5q5MmjrJBmNboGku
+bwD5JYN8D1VJtjHt5ugTj39srM4QcPkqZBmnBz/ZB2mafPDVNDaBakVEEKSga3l
V58aJZdjUKUYVVswjKljPA4NMR5+BdQ8+EML26pUpQwk4/5o5bYtWXHC+69glujP
q66PKjXusPcR+7xUhXb7NTUbicC8Q228CAx0ydLXfTjiJK9yaR6pAKaSC29dGLsZ
UDiHP1WYKF1fsFMXR41vvFSfig+kwR8T4+Yfn9Iq4fxgcEi1px5/HHuFf7YtlR+P
eYDlb5KyFrUHMByI+s/fxYbCwgTlMC+yQOepl3gJGgoQU1VHHy/5MX+Xb6+datgz
frT9BUy+i9wyP3VvT7fSbv7/HZHtwi/km1tMLYLqR1+CaPNZcq1QXtMWwCeh+ViZ
VI3q9/MOF8J/c25mPbUgxCrIylZ40uxkJzSjJDJHm/9etYzKvEN0DBO3Y7oYPjRo
KWKOgXintHVjXAzYjSmdkIYx4Fa/+g7iD0w/jQ0Y/Rxe64FmuPYp9WAUufCcxltf
/bPKItEWvw5Sv3OK+otRRf26KKC6L5rzvYM2IDMv9DFLUio9uGkJelaDqvuVbk8/
3b4kthBKRfKXQobM5+gt
=T855
-----END PGP SIGNATURE-----



More information about the Standards mailing list