Re: scope of derive

"Elwell, John" <[email protected]>
Newsgroups gmane.ietf.sip
Message-ID <0D5F89FAC29E2C41B98A6A762007F5D0015C3941@GBNTHT12009MSX.gb002.siemens.net>
 

> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On 
> Behalf Of Jiri Kuthan
> Sent: 11 December 2008 17:45
> To: Dean Willis
> Cc: Cullen Jennings; SIP List
> Subject: Re: [Sip] scope of derive
> 
> Dean Willis wrote:
> > 
> > On Dec 10, 2008, at 7:32 PM, Cullen Jennings wrote:
> > 
> >>
> >> I actually don't think that is the case. My recollection, could be 
> >> very wrong, what that SER edits outbound, not inbound SDP. 
> That said, 
> >> if SER editing my inbound SDP, it would check the signature before 
> >> doing so, and then go and execute my black list that 
> rejected calls at 
> >> 2 am form people other than a certain set, then send the 
> call down to 
> >> me. Once again, I not getting what is broken in this case.
> >>
> > 
> > It's not end to end. If your UAS is checking RFC 4474, it's 
> going to 
> > reject the call.
> > 
> > Now, did you WANT a DTLS-SRTP media fingerprint? If so, 
> then you need 
> > RFC 4474 end-to-end.
> 
> That I cannot counter.
[JRE] I am not sure you need RFC 4474 end-to-end - you just need
something end-to-end that binds the fingerprint of the DTLS-SRTP
certificate to a substantial part of the SIP message, but that need not
include the entire SDP.

John
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [email protected] for questions on current sip
Use [email protected] for new developments on the application of sip
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.