Re: francois' comments and why RFC4474 not used in the field

"Dan Wing" <[email protected]>
Newsgroups gmane.ietf.sip
Message-ID <[email protected]>
 

> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On 
> Behalf Of Dean Willis
> Sent: Thursday, April 02, 2009 8:50 PM
> To: Jiri Kuthan
> Cc: SIP List; Uzelac, Adam
> Subject: Re: [Sip] francois' comments and why RFC4474 not 
> used in the field
> 
> 
> On Apr 1, 2009, at 5:46 PM, Jiri Kuthan wrote:
> 
> > Dean Willis wrote:
> >> On Mar 30, 2009, at 8:03 PM, Jiri Kuthan wrote:
> >>>
> >>> There is a timing aspect in favor of placing identity in 
> signaling  
> >>> --
> >>> I would like to know whose call is ringing before I answer (if I  
> >>> do).
> >> So, we need identity in signaling, we need identity in media, and  
> >> we need the two identity expressions to match.
> >
> > I'm personally happy with having it only in signaling. Should there
> > be some in media too, I would be in favor of keeping those two
> > separate -- I'm not a particular fan of protocol dependencies.
> > That's just not about aesthetic expression -- once a protocol
> > begins to depend on other protocol, which one possibly does not
> > need, the cost and adaptability decreases. Single-purpose
> > things without dependencies have a much sounder chance of
> > deployment.
> >
> 
> So you're okay with knowing who dialed you, but not knowing who you  
> are actually talking to?
> 
> Personally, I want something that at least correlates the signaling  
> and media streams.

All 5 techniques described in 
http://tools.ietf.org/html/draft-wing-sip-identity-media-02#section-4
accomplish that using TLS, DTLS-SRTP, ICE, HIP, or ZRTP -- any of
those choices has different tradeoffs.

-d

_______________________________________________
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.