Re: [MMUSIC] New Version Notification for draft-ietf-mmusic-data-channel-sdpneg-05.txt

These changes mostly seem good. I have a couple of small points:

* Section 5.1.1.2:

This section starts with:

    The multiplexing category of the "a=dcmap:" attribute is SPECIAL.
    Usage of this attribute is only applicable when associated with
    UDP/DTLS/SCTP or TCP/DTLS/SCTP proto SDP "m" lines.

One issue is that usage of this attribute is also defined over pure 
SCTP. So I think it would be more accurate to say "*Multiplexing* of 
this attribute...".

Also, saying this is *only applicable* unnecessarily blocks future 
changes. I think it would be better to say *only defined*, or *outside 
the scope*.

* Section 5.1.2.2:

Analogous comment to that for 5.1.1.2.

* Section 8.2:

IIUC current practice is for documents coming through WGs to list the WG 
chair (e.g. mmusic-chairs@ietf.org) as the contact.

	Thanks,
	Paul

On 10/5/15 8:56 AM, Juergen Stoetzer-Bradler wrote:
> Hello,
>
> This version 05 adds the IANA registration sections for the dcmap and
> dcsa attributes
> and adds new mux category related sections for both attributes.
> It also adds [I-D.ietf-mmusic-sdp-mux-attributes] to the list of
> normative references,
> as that draft is referenced by the two new mux category sections.
>
> Additionally, this version updates section 5.1.1.5 regarding the dmap's
> 'subprotocol' parameter
> as per the related MMUSIC discussion initiated by Christian in August,
> http://www.ietf.org/mail-archive/web/mmusic/current/msg14946.html
>
> Thanks,
> Juergen
>
>
> On 05.10.2015 14:45, internet-drafts@ietf.org wrote:
>> A new version of I-D, draft-ietf-mmusic-data-channel-sdpneg-05.txt
>> has been successfully submitted by Juergen Stoetzer-Bradler and posted
>> to the
>> IETF repository.
>>
>> Name:        draft-ietf-mmusic-data-channel-sdpneg
>> Revision:    05
>> Title:        SDP-based Data Channel Negotiation
>> Document date:    2015-10-05
>> Group:        mmusic
>> Pages:        35
>> URL:
>> https://www.ietf.org/internet-drafts/draft-ietf-mmusic-data-channel-sdpneg-05.txt
>>
>> Status:
>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-data-channel-sdpneg/
>> Htmlized:
>> https://tools.ietf.org/html/draft-ietf-mmusic-data-channel-sdpneg-05
>> Diff:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-data-channel-sdpneg-05
>>
>>
>> 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 in-band Data Channel Establishment
>>     Protocol (DCEP) or using some out-of-band non-DCEP protocol.  This
>>     document specifies how the SDP offer/answer exchange can be used to
>>     achieve such an out-of-band non-DCEP 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.
>>
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> The IETF Secretariat
>>
>
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>