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

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
>