[rtcweb] [dispatch] [MMUSIC] FW: New Version Notification for draft-ejzak-dispatch-webrtc-data-channel-sdpneg-00.txt

"Ejzak, Richard P (Richard)" <richard.ejzak@alcatel-lucent.com> Sun, 13 October 2013 23:00 UTC

Return-Path: <richard.ejzak@alcatel-lucent.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id D0D4D11E812F; Sun, 13 Oct 2013 16:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.469
X-Spam-Status: No, score=-10.469 tagged_above=-999 required=5 tests=[AWL=-0.129, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Z=0.259]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id JzogSgXQi7S1; Sun, 13 Oct 2013 16:00:16 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com []) by ietfa.amsl.com (Postfix) with ESMTP id D2B4611E80EE; Sun, 13 Oct 2013 16:00:13 -0700 (PDT)
Received: from us70uusmtp3.zam.alcatel-lucent.com (h135-5-2-65.lucent.com []) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id r9DN0Bsc028960 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 13 Oct 2013 18:00:11 -0500 (CDT)
Received: from US70UWXCHHUB01.zam.alcatel-lucent.com (us70uwxchhub01.zam.alcatel-lucent.com []) by us70uusmtp3.zam.alcatel-lucent.com (GMO) with ESMTP id r9DN0AHG030789 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 13 Oct 2013 19:00:10 -0400
Received: from US70UWXCHMBA04.zam.alcatel-lucent.com ([]) by US70UWXCHHUB01.zam.alcatel-lucent.com ([]) with mapi id 14.02.0247.003; Sun, 13 Oct 2013 19:00:10 -0400
From: "Ejzak, Richard P (Richard)" <richard.ejzak@alcatel-lucent.com>
To: DISPATCH <dispatch@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [dispatch] [MMUSIC] [rtcweb] FW: New Version Notification for draft-ejzak-dispatch-webrtc-data-channel-sdpneg-00.txt
Thread-Index: AQHOyGf3HKB+ufbKaUuqcHLlUeseLg==
Date: Sun, 13 Oct 2013 23:00:09 +0000
Message-ID: <03FBA798AC24E3498B74F47FD082A92F3D86A163@US70UWXCHMBA04.zam.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on
Subject: [rtcweb] [dispatch] [MMUSIC] FW: New Version Notification for draft-ejzak-dispatch-webrtc-data-channel-sdpneg-00.txt
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Oct 2013 23:00:22 -0000

Please note the submission of draft-ejzak-dispatch-webrtc-data-channel-sdpneg.  It describes DataChannel external negotiation procedures based on SDP to set up DataChannel transport for well-known sub-protocols like MSRP, BFCP, T140, T38, and possibly the CLUE control protocol.  It makes no additional demands on the DataChannel design, although the document raises one small issue and suggests some clarifications in existing DataChannel documents. Please expect one more document soon that describes the application of the draft to negotiation of DataChannel transport for MSRP.

Richard Ejzak

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Sunday, October 13, 2013 5:45 PM
To: Ejzak, Richard P (Richard); MARCON, JEROME (JEROME)
Subject: New Version Notification for draft-ejzak-dispatch-webrtc-data-channel-sdpneg-00.txt

A new version of I-D, draft-ejzak-dispatch-webrtc-data-channel-sdpneg-00.txt
has been successfully submitted by Richard Ejzak and posted to the IETF repository.

Filename:	 draft-ejzak-dispatch-webrtc-data-channel-sdpneg
Revision:	 00
Title:		 SDP-based WebRTC data channel negotiation
Creation date:	 2013-10-14
Group:		 Individual Submission
Number of pages: 14
URL:             http://www.ietf.org/internet-drafts/draft-ejzak-dispatch-webrtc-data-channel-sdpneg-00.txt
Status:          http://datatracker.ietf.org/doc/draft-ejzak-dispatch-webrtc-data-channel-sdpneg
Htmlized:        http://tools.ietf.org/html/draft-ejzak-dispatch-webrtc-data-channel-sdpneg-00

   The Real-Time Communication in WEB-browsers (RTCWeb) working group is
   charged to provide protocols to support direct interactive rich
   communication using audio, video, and data between two peers' web-
   browsers.  For the support of data communication, the RTCWeb working
   group has in particular defined the concept of bi-directional data
   channels over SCTP, where each data channel might be used to
   transport other protocols, called sub-protocols.  Data channel setup
   can be done using either the in-band WebRTC Data Channel protocol or
   some external (in-band or out-of-band) negotiation.  This document
   specifies how the SDP offer/answer exchange can be used to achieve
   such an external negotiation.


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat