[Stox] RFC 7247 on Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Architecture, Addresses, and Error Handling
rfc-editor@rfc-editor.org Thu, 22 May 2014 01:30 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: stox@ietfa.amsl.com
Delivered-To: stox@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6906F1A005A; Wed, 21 May 2014 18:30:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level:
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J5bzqoyBVlqi; Wed, 21 May 2014 18:30:45 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 6AAC21A0059; Wed, 21 May 2014 18:30:45 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0D4A118000D; Wed, 21 May 2014 18:30:31 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140522013031.0D4A118000D@rfc-editor.org>
Date: Wed, 21 May 2014 18:30:31 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/stox/W7HayFROrFfbR0mPwKznuiPNFAg
Cc: drafts-update-ref@iana.org, stox@ietf.org, rfc-editor@rfc-editor.org
Subject: [Stox] RFC 7247 on Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Architecture, Addresses, and Error Handling
X-BeenThere: stox@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP-TO-XMPP Working Group discussion list <stox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stox>, <mailto:stox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/stox/>
List-Post: <mailto:stox@ietf.org>
List-Help: <mailto:stox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stox>, <mailto:stox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 May 2014 01:30:51 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7247
Title: Interworking between the Session Initiation
Protocol (SIP) and the Extensible Messaging
and Presence Protocol (XMPP): Architecture,
Addresses, and Error Handling
Author: P. Saint-Andre, A. Houri, J. Hildebrand
Status: Standards Track
Stream: IETF
Date: May 2014
Mailbox: ietf@stpeter.im,
avshalom@il.ibm.com,
jhildebr@cisco.com
Pages: 24
Characters: 57218
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-stox-core-11.txt
URL: http://www.rfc-editor.org/rfc/rfc7247.txt
As a foundation for the definition of bidirectional protocol mappings
between the Session Initiation Protocol (SIP) and the Extensible
Messaging and Presence Protocol (XMPP), this document specifies the
architectural assumptions underlying such mappings as well as the
mapping of addresses and error conditions.
This document is a product of the SIP-TO-XMPP Working Group of the IETF.
This is now a Proposed Standard.
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-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
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@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