< draft-saintandre-sip-xmpp-core-00.txt   draft-saintandre-sip-xmpp-core-01.txt >
Network Working Group P. Saint-Andre Network Working Group P. Saint-Andre
Internet-Draft XMPP Standards Foundation Internet-Draft Cisco
Intended status: Informational A. Houri Intended status: Informational A. Houri
Expires: July 7, 2008 IBM Expires: September 9, 2009 IBM
J. Hildebrand J. Hildebrand
Jabber, Inc. Cisco
January 4, 2008 March 8, 2009
Interworking between the Session Initiation Protocol (SIP) and the Interworking between the Session Initiation Protocol (SIP) and the
Extensible Messaging and Presence Protocol (XMPP): Core Extensible Messaging and Presence Protocol (XMPP): Core
draft-saintandre-sip-xmpp-core-00 draft-saintandre-sip-xmpp-core-01
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79. This document may contain material
have been or will be disclosed, and any of which he or she becomes from IETF Documents or IETF Contributions published or made publicly
aware will be disclosed, in accordance with Section 6 of BCP 79. available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July 7, 2008. This Internet-Draft will expire on September 9, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
Copyright (C) The IETF Trust (2008). This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract Abstract
As a foundation for the definition of application-specific, bi- As a foundation for the definition of application-specific, bi-
directional protocol mappings between the Session Initiation Protocol directional protocol mappings between the Session Initiation Protocol
(SIP) and the Extensible Messaging and Presence Protocol (XMPP), this (SIP) and the Extensible Messaging and Presence Protocol (XMPP), this
document specifies the architectural assumptions underlying such document specifies the architectural assumptions underlying such
mappings as well as the mapping of addresses and error conditions. mappings as well as the mapping of addresses and error conditions.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Architectural Assumptions . . . . . . . . . . . . . . . . . . 3 2. Architectural Assumptions . . . . . . . . . . . . . . . . . . 4
3. Address Mapping . . . . . . . . . . . . . . . . . . . . . . . 4 3. Address Mapping . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. SIP to XMPP . . . . . . . . . . . . . . . . . . . . . . . 7 3.2. SIP to XMPP . . . . . . . . . . . . . . . . . . . . . . . 8
3.3. XMPP to SIP . . . . . . . . . . . . . . . . . . . . . . . 7 3.3. XMPP to SIP . . . . . . . . . . . . . . . . . . . . . . . 8
4. Error Condition Mapping . . . . . . . . . . . . . . . . . . . 8 4. Error Condition Mapping . . . . . . . . . . . . . . . . . . . 9
4.1. XMPP to SIP . . . . . . . . . . . . . . . . . . . . . . . 8 4.1. XMPP to SIP . . . . . . . . . . . . . . . . . . . . . . . 9
4.2. SIP to XMPP . . . . . . . . . . . . . . . . . . . . . . . 8 4.2. SIP to XMPP . . . . . . . . . . . . . . . . . . . . . . . 9
5. Security Considerations . . . . . . . . . . . . . . . . . . . 11 5. Security Considerations . . . . . . . . . . . . . . . . . . . 12
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
6.1. Normative References . . . . . . . . . . . . . . . . . . . 11 6.1. Normative References . . . . . . . . . . . . . . . . . . . 12
6.2. Informative References . . . . . . . . . . . . . . . . . . 11 6.2. Informative References . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13
Intellectual Property and Copyright Statements . . . . . . . . . . 14
1. Introduction 1. Introduction
The IETF has worked on two signalling technologies that can be used The IETF has worked on two signalling technologies that can be used
for multimedia session negotiation, messaging, presence, capabilities for multimedia session negotiation, messaging, presence, capabilities
discovery, notifications, and other application-level functionality: discovery, notifications, and other application-level functionality:
o The Session Initiation Protocol [SIP], along with various SIP o The Session Initiation Protocol [SIP], along with various SIP
extensions developed within the SIP for Instant Messaging and extensions developed within the SIP for Instant Messaging and
Presence Leveraging Extensions (SIMPLE) Working Group. Presence Leveraging Extensions (SIMPLE) Working Group.
skipping to change at page 12, line 29 skipping to change at page 13, line 29
Saint-Andre, P. and J. Hildebrand, "JID Escaping", XSF Saint-Andre, P. and J. Hildebrand, "JID Escaping", XSF
XEP 0106, May 2005. XEP 0106, May 2005.
[XMPP-IM] Saint-Andre, P., "Extensible Messaging and Presence [XMPP-IM] Saint-Andre, P., "Extensible Messaging and Presence
Protocol (XMPP): Instant Messaging and Presence", Protocol (XMPP): Instant Messaging and Presence",
RFC 3921, October 2004. RFC 3921, October 2004.
Authors' Addresses Authors' Addresses
Peter Saint-Andre Peter Saint-Andre
XMPP Standards Foundation Cisco
P.O. Box 1641
Denver, CO 80201
USA
Email: stpeter@jabber.org Email: psaintan@cisco.com
Avshalom Houri Avshalom Houri
IBM IBM
Building 18/D, Kiryat Weizmann Science Park Building 18/D, Kiryat Weizmann Science Park
Rehovot 76123 Rehovot 76123
Israel Israel
Email: avshalom@il.ibm.com Email: avshalom@il.ibm.com
Joe Hildebrand
Jabber, Inc.
1899 Wynkoop Street, Suite 600
Denver, CO 80202
USA
Email: jhildebrand@jabber.com
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Joe Hildebrand
assurances of licenses to be made available, or the result of an Cisco
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF Email: jhildebr@cisco.com
Administrative Support Activity (IASA).
 End of changes. 14 change blocks. 
79 lines changed or deleted 43 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/