[xmpp] RFC 7395 on An Extensible Messaging and Presence Protocol (XMPP) Subprotocol for WebSocket

rfc-editor@rfc-editor.org Fri, 31 October 2014 00:17 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7B2D1A8A4C; Thu, 30 Oct 2014 17:17:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 7LskLK0Q-s06; Thu, 30 Oct 2014 17:17:00 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 0CF4E1A8981; Thu, 30 Oct 2014 17:16:55 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A02DC181C86; Thu, 30 Oct 2014 17:16:05 -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: <20141031001605.A02DC181C86@rfc-editor.org>
Date: Thu, 30 Oct 2014 17:16:05 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/xmpp/1xjSIv1H1fllBxbzOr_H8klqYDY
Cc: drafts-update-ref@iana.org, xmpp@ietf.org, rfc-editor@rfc-editor.org
Subject: [xmpp] RFC 7395 on An Extensible Messaging and Presence Protocol (XMPP) Subprotocol for WebSocket
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Oct 2014 00:17:03 -0000

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

        
        RFC 7395

        Title:      An Extensible Messaging and Presence 
                    Protocol (XMPP) Subprotocol for WebSocket 
        Author:     L. Stout, Ed.,
                    J. Moffitt,
                    E. Cestari
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2014
        Mailbox:    lance@andyet.net, 
                    jack@metajack.im, 
                    eric@cstar.io
        Pages:      18
        Characters: 36795
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-xmpp-websocket-10.txt

        URL:        https://www.rfc-editor.org/rfc/rfc7395.txt

This document defines a binding for the Extensible Messaging and
Presence Protocol (XMPP) over a WebSocket transport layer.  A
WebSocket binding for XMPP provides higher performance than the
current HTTP binding for XMPP.

This document is a product of the Extensible Messaging and Presence Protocol 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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://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