RFC 7977 on The WebSocket Protocol as a Transport for the Message Session Relay Protocol (MSRP)
rfc-editor@rfc-editor.org Wed, 21 September 2016 23:17 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78B5412D1D3 for <ietf-announce@ietfa.amsl.com>; Wed, 21 Sep 2016 16:17:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.918
X-Spam-Level:
X-Spam-Status: No, score=-104.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
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 CSqxB6fxTEht for <ietf-announce@ietfa.amsl.com>; Wed, 21 Sep 2016 16:17:27 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C645412D0CB for <ietf-announce@ietf.org>; Wed, 21 Sep 2016 16:16:58 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B6381B80FDE; Wed, 21 Sep 2016 16:16:58 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7977 on The WebSocket Protocol as a Transport for the Message Session Relay Protocol (MSRP)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160921231658.B6381B80FDE@rfc-editor.org>
Date: Wed, 21 Sep 2016 16:16:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/tMoRqNlKIgSUXmzoh7nwm1FdR2Q>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Sep 2016 23:17:39 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7977
Title: The WebSocket Protocol as a
Transport for the Message Session Relay
Protocol (MSRP)
Author: P. Dunkley, G. Llewellyn,
V. Pascual, G. Salgueiro,
R. Ravindranath
Status: Standards Track
Stream: IETF
Date: September 2016
Mailbox: peter.dunkley@xura.com,
gavin.llewellyn@xura.com,
victor.pascual.avila@oracle.com,
gsalguei@cisco.com,
rmohanr@cisco.com
Pages: 28
Characters: 52078
Updates: RFC 4975, RFC 4976
I-D Tag: draft-pd-dispatch-msrp-websocket-15.txt
URL: https://www.rfc-editor.org/info/rfc7977
DOI: http://dx.doi.org/10.17487/RFC7977
The WebSocket protocol enables two-way real-time communication
between clients and servers in situations where direct access to TCP
and UDP is not available (for example, from within JavaScript in a
web browser). This document specifies a new WebSocket subprotocol as
a reliable transport mechanism between Message Session Relay Protocol
(MSRP) clients and relays to enable usage of MSRP in new scenarios.
This document normatively updates RFCs 4975 and 4976.
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/retrieve/bulk
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