Re: [MMUSIC] draft-ejzak-mmusic-data-channel-sdpneg and draft-ejzak-mmusic-msrp-usage-data-channel

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Sun, 02 November 2014 15:07 UTC

Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E95801A891D for <mmusic@ietfa.amsl.com>; Sun, 2 Nov 2014 07:07:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 ffQS6EtT6R6v for <mmusic@ietfa.amsl.com>; Sun, 2 Nov 2014 07:07:26 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2778D1A8834 for <mmusic@ietf.org>; Sun, 2 Nov 2014 07:07:26 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id 61B03F1C27E20 for <mmusic@ietf.org>; Sun, 2 Nov 2014 15:07:20 +0000 (GMT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id sA2F7NUv028562 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <mmusic@ietf.org>; Sun, 2 Nov 2014 16:07:23 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.25]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Sun, 2 Nov 2014 16:07:23 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: draft-ejzak-mmusic-data-channel-sdpneg and draft-ejzak-mmusic-msrp-usage-data-channel
Thread-Index: Ac/x88lK6mpn4HE9TuemRholN7+6tQEucedQ
Date: Sun, 02 Nov 2014 15:07:22 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B26DC50@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/X6sBSGfNTZ6TOAHUwvyRq6kf9YI
Subject: Re: [MMUSIC] draft-ejzak-mmusic-data-channel-sdpneg and draft-ejzak-mmusic-msrp-usage-data-channel
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Nov 2014 15:07:30 -0000

At the London IETF meeting, we were not quite at the point of asking for adoption of draft-ejzak-mmusic-data-channel-sdpneg. There was a request that certain revisions should be made and a couple of issues addressed.

That has now occurred.

I would like to ask if we can now moved forward to adoption of this draft as a working group item. While it is the responsibility of the chairs to make a formal call, I have asked for a small amount of time in Honolulu with this intent, and it would be useful if people could start to express their opinions one way or other on the list, i.e. whether they think the draft is generally useful, or alternatively, just a bad idea!

Regards

Keith

> -----Original Message-----
> From: DRAGE, Keith (Keith) 
> Sent: 27 October 2014 14:39
> To: mmusic@ietf.org
> Subject: draft-ejzak-mmusic-data-channel-sdpneg and 
> draft-ejzak-mmusic-msrp-usage-data-channel
> 
> Based on the discussion on list over the last few days, I 
> have submitted revised versions of the two SDP negotiation 
> over data channel drafts as follows:
> 
> A new version of I-D, draft-ejzak-mmusic-data-channel-sdpneg-02.txt
> has been successfully submitted by Keith Drage and posted to 
> the IETF repository.
> 
> Name:		draft-ejzak-mmusic-data-channel-sdpneg
> Revision:	02
> Title:		SDP-based "SCTP over DTLS" data channel 
> negotiation
> Document date:	2014-10-27
> Group:		Individual Submission
> Pages:		22
> URL:            
> http://www.ietf.org/internet-drafts/draft-ejzak-mmusic-data-ch
> annel-sdpneg-02.txt
> Status:         
> https://datatracker.ietf.org/doc/draft-ejzak-mmusic-data-chann
> el-sdpneg/
> Htmlized:       
> http://tools.ietf.org/html/draft-ejzak-mmusic-data-channel-sdpneg-02
> Diff:           
> http://www.ietf.org/rfcdiff?url2=draft-ejzak-mmusic-data-chann
> el-sdpneg-02
> 
> Abstract:
>    The Real-Time Communication in WEB-browsers (RTCWeb) 
> working group is
>    charged to provide protocols to support direct interactive rich
>    communications 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 internal in-band band (also 
> referred to
>    as 'internal' for the rest of the document) WebRTC Data Channel
>    Establishment Protocol or some external out-of-band simply referred
>    to as 'external negotiation' in the rest of the document . This
>    document specifies how the SDP offer/answer exchange can be used to
>    achieve such an external negotiation.  Even though data 
> channels are
>    designed for RTCWeb use initially they may be used by 
> other protocols
>    like, but not limited to, the CLUE protocol.  This document is
>    intended to be used wherever data channels are used.
> 
> 
> A new version of I-D, 
> draft-ejzak-mmusic-msrp-usage-data-channel-01.txt
> has been successfully submitted by Keith Drage and posted to 
> the IETF repository.
> 
> Name:		draft-ejzak-mmusic-msrp-usage-data-channel
> Revision:	01
> Title:		MSRP over SCTP/DTLS data channels
> Document date:	2014-10-27
> Group:		Individual Submission
> Pages:		11
> URL:            
> http://www.ietf.org/internet-drafts/draft-ejzak-mmusic-msrp-us
> age-data-channel-01.txt
> Status:         
> https://datatracker.ietf.org/doc/draft-ejzak-mmusic-msrp-usage
> -data-channel/
> Htmlized:       
> http://tools.ietf.org/html/draft-ejzak-mmusic-msrp-usage-data-
> channel-01
> Diff:           
> http://www.ietf.org/rfcdiff?url2=draft-ejzak-mmusic-msrp-usage
> -data-channel-01
> 
> Abstract:
>    This document specifies how the Message Session Relay 
> Protocol (MSRP)
>    can be instantiated as a data channel sub-protocol, using 
> the the SDP
>    offer/answer exchange-based external negotiation defined in
>    [I-D.ejzak-mmusic-data-channel-sdpneg].  Two network configurations
>    are documented: a WebRTC end-to-end configuration (connecting two
>    MSRP over data channel endpoints), and a gateway configuration
>    (connecting an MSRP over data channel endpoint with an 
> MSRP over TCP
>    endpoint).