[MMUSIC] New draft version: draft-ietf-mmusic-msrp-usage-data-channel-01

Juergen Stoetzer-Bradler <Juergen.Stoetzer-Bradler@alcatel-lucent.com> Mon, 09 March 2015 11:05 UTC

Return-Path: <juergen.stoetzer-bradler@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 57A8A1A879A for <mmusic@ietfa.amsl.com>; Mon, 9 Mar 2015 04:05:36 -0700 (PDT)
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 yFQK3Zb1JS4O for <mmusic@ietfa.amsl.com>; Mon, 9 Mar 2015 04:05:34 -0700 (PDT)
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 0C2D81A70FE for <mmusic@ietf.org>; Mon, 9 Mar 2015 04:05:34 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id 162523609A047 for <mmusic@ietf.org>; Mon, 9 Mar 2015 11:05:30 +0000 (GMT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id t29B5V5i023415 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <mmusic@ietf.org>; Mon, 9 Mar 2015 12:05:32 +0100
Received: from [135.244.193.138] (135.239.27.41) by FR711WXCHHUB01.zeu.alcatel-lucent.com (135.239.2.111) with Microsoft SMTP Server (TLS) id 14.3.195.1; Mon, 9 Mar 2015 12:05:30 +0100
Message-ID: <54FD7E79.8010600@alcatel-lucent.com>
Date: Mon, 09 Mar 2015 12:05:29 +0100
From: Juergen Stoetzer-Bradler <Juergen.Stoetzer-Bradler@alcatel-lucent.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: mmusic@ietf.org
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [135.239.27.41]
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/TP3VdL3uVwASX_G-QEa_dyfaeDU>
Subject: [MMUSIC] New draft version: draft-ietf-mmusic-msrp-usage-data-channel-01
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: Mon, 09 Mar 2015 11:05:36 -0000

Hello,

Have also submitted version -01 of draft-ietf-mmusic-msrp-usage-data-channel.
The changes as compared to version -00 are listed below and are related to corresponding recent 
email list discussions.
This list is also copied to the change log section 10.1.

Thanks,
Juergen


    o  Additional reference to [I-D.ietf-mmusic-data-channel-sdpneg] in
       list of normative references.

    o  Replacement of previous document title "MSRP over SCTP/DTLS data
       channels" with "MSRP over Data Channels" in order to align with
       the terminology used in [I-D.ietf-mmusic-data-channel-sdpneg].

    o  In Section 3 "WebRTC data channel" was defined as "A bidirectional
       channel consisting of paired SCTP outbound and inbound streams."
       Replacement of this definition with "Data channel: A WebRTC data
       channel as specified in [I-D.ietf-rtcweb-data-channel]", and
       consistent usage of either "data channel" or "MSRP data channel"
       in the remainder of the document."

    o  In the introduction replacement of references to
       [I-D.ietf-rtcweb-data-protocol] with a reference to
       [I-D.ietf-rtcweb-data-channel].

    o  Consistent usage of '"m" line' in whole document as per [RFC4566].

    o  In the gateway configuration section (Section 6) replacement of
       the first sentence "This section describes the network
       configuration where one endpoint runs MSRP over a WebRTC SCTP/DTLS
       connection, the other MSRP endpoint runs MSRP over one or more
       TLS/TCP connections, and the two endpoints interwork via an MSRP
       gateway" with "This section describes the network configuration
       where one MSRP endpoint uses data channels as MSRP transport, the
       other MSRP endpoint uses TLS/TCP connections as MSRP transport,
       and the two MSRP endpoints interwork via an MSRP gateway".