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

Christian Groves <Christian.Groves@nteczone.com> Tue, 10 March 2015 03:26 UTC

Return-Path: <Christian.Groves@nteczone.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 EB8251AD26E for <mmusic@ietfa.amsl.com>; Mon, 9 Mar 2015 20:26:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 Ud9uDLY9Oq9c for <mmusic@ietfa.amsl.com>; Mon, 9 Mar 2015 20:26:09 -0700 (PDT)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 713C81AD291 for <mmusic@ietf.org>; Mon, 9 Mar 2015 20:26:02 -0700 (PDT)
Received: from ppp118-209-228-24.lns20.mel8.internode.on.net ([118.209.228.24]:56930 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <Christian.Groves@nteczone.com>) id 1YVAlj-00040e-LP for mmusic@ietf.org; Tue, 10 Mar 2015 14:23:43 +1100
Message-ID: <54FE6446.7020007@nteczone.com>
Date: Tue, 10 Mar 2015 14:25:58 +1100
From: Christian Groves <Christian.Groves@nteczone.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
References: <54FD7E79.8010600@alcatel-lucent.com>
In-Reply-To: <54FD7E79.8010600@alcatel-lucent.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/YO8HvHmf4Ipf9Zfn859wW9fpTbg>
Subject: Re: [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: Tue, 10 Mar 2015 03:26:12 -0000

Hello Juergen,

Thanks for the update. Some comments:
5.1.1.1 - The section indicates that the max-retr, max-time and
    ordered parameters shall not be used. I take it then that the SCTP 
Stream used for MSRP must be DATA_CHANNEL_RELIABLE? If so it might be 
better to say what is used rather than what is not.

5.1.1.1 - The text regarding the SCTP port can be removed because of 
recent changes to draft-ietf-mmusic-sctp-sdp removing the concept of 
default port.

5.1.1.2 1st paragraph - I propose to re-order to make it clear there's 
one dcsa line per MSRP specific attribute:

    The SDP offer shall also include within the media description
    for the SCTP association a dcsa attribute line (defined in
    [I-D.ietf-mmusic-data-channel-sdpneg]) for each MSRP-specific SDP 
attribute to be
    negotiated for each MSRP data channel being negotiated.

5.1.1.2: MSRP "max-size" would it be worth to note that this must be 
less than the SCTP SDP max-message-size value?

5.1.1.2: "Setup" is this relevant for MSRP using data channel? The 
SCTP-SDP draft etc. give rules as to which endpoint establishes 
different parts of the transport connection?

5.1.1.3: a=sctp-port 5000 should have a colon e.g. a=sctp-port:5000

5.1.5: This section indicates that closing is done as per 
I-D.ietf-mmusic-data-channel-sdpneg. However clause 
5.2.4/I-D.ietf-mmusic-data-channel-sdpneg indicates that closure is 
sub-protocol specific. Its not clear to me whether this the sub-protocol 
should indicate the use of the SCTP reset or the use of SDP O/A?

Regards, Christian


On 9/03/2015 10:05 PM, Juergen Stoetzer-Bradler wrote:
> 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".
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>