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

Christian Groves <> Tue, 10 March 2015 03:26 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id EB8251AD26E for <>; Mon, 9 Mar 2015 20:26:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Ud9uDLY9Oq9c for <>; Mon, 9 Mar 2015 20:26:09 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 713C81AD291 for <>; Mon, 9 Mar 2015 20:26:02 -0700 (PDT)
Received: from ([]:56930 helo=[]) by with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <>) id 1YVAlj-00040e-LP for; Tue, 10 Mar 2015 14:23:43 +1100
Message-ID: <>
Date: Tue, 10 Mar 2015 14:25:58 +1100
From: Christian Groves <>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
References: <>
In-Reply-To: <>
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 -
X-AntiAbuse: Original Domain -
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain -
X-Get-Message-Sender-Via: authenticated_id:
Archived-At: <>
Subject: Re: [MMUSIC] New draft version: draft-ietf-mmusic-msrp-usage-data-channel-01
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 10 Mar 2015 03:26:12 -0000

Hello Juergen,

Thanks for the update. Some comments: - 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. - 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. 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. MSRP "max-size" would it be worth to note that this must be 
less than the SCTP SDP max-message-size value? "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? 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