RE: Media Security Requirements Draft: New Requirement

["Christer Holmberg (JO/LMF)" <christer.holmberg@xxxxxxxxxxxx>]

Hi, 

>>>Cullen mentioned any media arriving before 200 would fail -- 
>>>including country-specific ringback tones, music played as the 
>>>ringback tone, and IVRs ("1-800-Fedex", "Wecome to United Airlines, 
>>>please select the following code describing the reason for your 
>>>call").
>>>
>>>Are those invalid use cases for RTP?  Or is IMS going to 
>>>change how SIP handles that stuff (forcing a 200?  Redefine the
meaning of 200?)
>> 
>>I don't think the cases above would necessarily fail, because the 
>>backward media direction is often opened before 200 OK, in order to 
>>allow announcements and other type of early media.
> 
>And DTMF tones, which are transmitted to interact with IVRs, is carried
via INFO or NOTIFY or RFC2833?

I don't think that is specified.
 
>>>>>In some sense you seem to say that key management for media
security
>>>>>has to be done along the signaling path and not along the media
path.
>>>> 
>>>>I think that option should be considered, yes.
>>> 
>>>They were considered, and found to be deficient.  
>>> 
>>>If there was an inaccuracy in the analysis
(draft-wing-rtpsec-keying-eval-02.txt) please do point out
>>>the inaccuracy.  To my knowledge that analysis is accurate and
reached the conclusion that no existing exclusive
>>>signaling-path SRTP keying mechanism met the requirements stated at
the time. 
>> 
>>I am not familiar with that draft (neither am I aware of any other 
>>requirements than the ones currently being worked on in the reqs 
>>draft).
> 
>draft-wing-rtpsec-keying-eval-02.txt was the basis for my 
>presentation at the first RAI open area meeting a couple of 
>years back, and the basis for my presentation at the first RTPSEC BoF.

Ok. So, does that draft take the issues currently discussed into
consideration?

Regards,

Christer