RFC 7701 on Multi-party Chat Using the Message Session Relay Protocol (MSRP)
rfc-editor@rfc-editor.org Tue, 15 December 2015 05:08 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6EE51B2AD1; Mon, 14 Dec 2015 21:08:21 -0800 (PST)
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 X7E7UuWTX664; Mon, 14 Dec 2015 21:08:20 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id BFE621B2AFD; Mon, 14 Dec 2015 21:08:02 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 24797181D1B; Mon, 14 Dec 2015 21:05:40 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7701 on Multi-party Chat Using the Message Session Relay Protocol (MSRP)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20151215050540.24797181D1B@rfc-editor.org>
Date: Mon, 14 Dec 2015 21:05:40 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/IE3y9atkOZdfhsMhWgKtxu8a71M>
Cc: drafts-update-ref@iana.org, simple@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 15 Dec 2015 05:08:22 -0000
A new Request for Comments is now available in online RFC libraries. RFC 7701 Title: Multi-party Chat Using the Message Session Relay Protocol (MSRP) Author: A. Niemi, M. Garcia-Martin, G. Sandbakken Status: Standards Track Stream: IETF Date: December 2015 Mailbox: aki.niemi@iki.fi, miguel.a.garcia@ericsson.com, geirsand@cisco.com Pages: 42 Characters: 99607 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-simple-chat-18.txt URL: https://www.rfc-editor.org/info/rfc7701 DOI: http://dx.doi.org/10.17487/RFC7701 The Message Session Relay Protocol (MSRP) defines a mechanism for sending instant messages (IMs) within a peer-to-peer session, negotiated using the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP). This document defines the necessary tools for establishing multi-party chat sessions, or chat rooms, using MSRP. This document is a product of the SIP for Instant Messaging and Presence Leveraging Extensions 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