Re: [MMUSIC] WGLC for draft-ietf-mmusic-duplication-grouping-01

[Ari Keränen <[e-mail]>]

On 4/25/13 11:19 AM, Ali C. Begen (abegen) wrote:
>
> On Apr 25, 2013, at 6:07 AM, Ari Keränen <[e-mail]> wrote:
>
>> On 4/24/13 9:36 AM, Ali C. Begen (abegen) wrote:
>>>
>>> On Apr 24, 2013, at 7:27 AM, Ari Keränen <[e-mail]> wrote:
>>>>    Alternatively, one could be more explicit
>>>>    and insert an "a=duplication-delay:0" line before the "a=mid:Ch1"
>>>>    line.
>>>>
>>>> This is quite vague. Could add an RFC2119 SHOULD/MUST/RECOMMEND here (and same in the next section) and tell when/why (not) to do it.
>>>>
>>>
>>> I think a MUST would be too strong since it is not really a must. I also think making it a SHOULD would require us to explain when it could be ignored (which is really any time since nothing will break if it is ignored). Putting it would be more like informational purposes. I think "MAY" would be appropriate here.
>>>
>>> Would that address your concern?
>>
>> I think the important part is to tell why you should (or may) put it there. Is it, e.g., informational for a human reading the SDP or is there some corner case where this would help?
>
> It is informational line for humans. Are you ok if we say:
>
> "Alternatively, one MAY explicitly insert an "a=duplication-delay:0" line before ... for informational purposes."
>
>
>> If there's no real value adding it there, perhaps it's better to not talk about this alternative at all since it will potentially just results in unnecessary differences how it ends up implemented.
>>
> Even if we dont mention this, one can use this and the SDP would be valid unless we say one MUST NOT be explicit (I think this would be worse to say)

Sure, and I wouldn't say MUST NOT either. IMHO, the comment makes the 
text a bit confusing. However, if you see value of having it there, your 
proposed text work for me.


Cheers,
Ari