Re: [MMUSIC] Draft new version: T140-data-channel -02 - Reference RFC 4566 for direction attributes and not RFC 3264

[Gunnar Hellström <[e-mail]>]

Hi,

Den 2019-09-05 kl. 07:04, skrev Christer Holmberg:
> Hi,
>
>> I have created a number of pull requests to the GitHub repository for  draft-holmberg-mmusic-t140-usage-data-channel-02
>>
>> Many are editorial. A few require discussion in the list.
>>
>> This is one that requires discussion:
>>
>> I suggest that RFC 3264 is deleted as reference for how the direction attributes 'sendonly' etc. RFC 4566 is already also used as reference
>> for how to handle the direction attributes. This is in section 3.2.3
>> I think that RFC 3264 just adds confusion and a lot of detail for RTP use of the direction attributes that is irrelevant for the T.140 data channel case.
> This can be split into two parts:
>
> First, since we do mention "offer/answer" (as we define the o/a T.140 data channel procedures for the direction attributes), we DO at least need a reference to 3264 for terminology purpose.
>
> Second, the draft DOES define the offer/answer procedures for the T.140 direction attributes, so from that perspective we do not need a reference the procedures in 3264. However, I DO think it is a good idea to indicate that the procedures are based on the procedures in 3264. It makes it more clear for implementers etc.

Yes, "the procedures are based on the procedures in 3264" sounds 
suitable. The wording about the direction attributes in RFC 3264 is full 
of wording about ports and payload types etc. In many cases, but not 
all, it mentions what is only valid for RTP transport, so it would not 
be right to say that it is the RFC 3264 procedures that are used. But OK 
for referencing RFC 3264 in a mild way. I hope you can propose wording.

Regards

Gunnar

>
> Regards,
>
> Christer
>
>
>
>
>
> Den 2019-09-03 kl. 14:10, skrev Christer Holmberg:
> Hi,
>   
> I have mereged the following PR:
>   
> https://protect2.fireeye.com/url?k=b96a065f-e5e3dc4f-b96a46c4-0cc47ad93e2a-665164b51729ecbf&q=1&u=https://github.com/cdh4u/draft-datachannel-t140/pull/6
>   
> …and submitted a new version (-02) of draft-holmberg-mmusic-t140-usage-data-channel.
>   
> The main changes are:
>   
> - IANA registry update for SDP attributes that can be included in dcsa attributes
> - Detailed procedures on usage of the direction attributes inside dcsa attributes
>   
> Regards,
>   
> Christer
>
>
> _______________________________________________
> mmusic mailing list
> mailto:[e-mail]
> https://www.ietf.org/mailman/listinfo/mmusic

-- 
-----------------------------------------
Gunnar Hellström
Omnitor
[e-mail]
[phone]