Re: [MMUSIC] WGLC for draft-ietf-mmusic-data-channel-sdpneg

[Paul Kyzivat <[e-mail]>]

One thing occurred to me that we may have forgotten about:

This draft introduces the dcsa attribute, which allows other attributes 
to be used in this new scope. It notes that not all attributes are 
suitable for use this way.

ISTM that in the future other attribute definitions should include an 
indication of whether they can be used with dcsa, and the IANA 
registration of the attribute ought to include this. And then there is a 
need to update the iana registry for all the existing attributes.

	Thanks,
	Paul

On 11/25/15 4:52 AM, Bo Burman wrote:
> This is to announce a 4 week Working Group Last Call for
>
>                  draft-ietf-mmusic-data-channel-sdpneg-06
>
> as proposed standard.
>
> Please review and provide any comments you may have on the document by
> Wednesday, December 23, 2015. Comments should be sent to the document
> authors and the MMUSIC WG list. If you review the document but do not
> have any comments, please send a note to that effect as well.
>
> Please also forward this WGLC call to any other interested parties who
> may be able to review the draft, asking them to also direct their
> comments to the authors and the list as above.
>
> Thank you!
>
>          Bo Burman (MMUSIC co-chair)
>
> Draft information:
>
> This draft is a work item of the Multiparty Multimedia Session Control
> Working Group of the IETF.
>
>          Title           : SDP-based Data Channel Negotiation
>
> Authors         : Keith Drage
>
>                            Maridi R. Makaraju (Raju)
>
>                            Juergen Stoetzer-Bradler
>
> Richard Ejzak
>
>                            Jerome Marcon
>
>                  Filename        :
> draft-ietf-mmusic-data-channel-sdpneg-06.txt
>
>                  Pages           : 37
>
>                  Date            : 2015-10-19
>
> 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.
>
> The IETF datatracker status page for this draft is:
>
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-data-channel-sdpneg/
>
> There's also a htmlized version available at:
>
> https://tools.ietf.org/html/draft-ietf-mmusic-data-channel-sdpneg-06
>
> A diff from the previous version is available at:
>
> https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-data-channel-sdpneg-06
>
> Internet-Drafts are also available by anonymous FTP at:
>
> ftp://ftp.ietf.org/internet-drafts/
>
>
>
> _______________________________________________
> mmusic mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/mmusic
>