Re: [MMUSIC] AD evaluation: draft-ietf-mmusic-rtsp-nat-20

[Magnus Westerlund <[e-mail]>]

On 2014-05-28 01:24, Alissa Cooper wrote:
>>>
>>> Sec 4.4:
>>> "The RTSP client SHOULD send the feature tag "setup.ice-d-m" in the
>>>    "Supported" header in all SETUP requests that contain the "D-ICE"
>>>    lower layer transport.”
>>>
>>> What are the situations where the SETUP request contains “D-ICE” but
>>> where
>>> the feature tag should not be included? Is it for SETUP requests issued
>>> after media is already playing (as described in Sec 6.13)?
>>
>> I would classify this SHOULD as: we have no good reason why you would
>> not include the feature tag. But if you have one, we don't see a reason
>> for making the implementation violate a MUST.
> 
> Would help to explain that rationale in the document.
> 

I propose the following:

   The RTSP client SHOULD send the feature tag "setup.ice-d-m" in the
   "Supported" header in all SETUP requests that contain the "D-ICE"
   lower layer transport.  Note, this is not a "MUST" due to that an
   RTSP client always can attempt to perform an SETUP using ICE to see
   if it functions or fails.  But including the feature tag in the
   "Supported" header do ensure that proxies supporting this
   specification do explicitly indicate such support, see Section 7.


Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  [phone]
Färögatan 6                 | Mobile [phone]
SE-164 80 Stockholm, Sweden | mailto: [e-mail]
----------------------------------------------------------------------