Right, So now that we have progressed, let's try to figure out what the problems with this approach are (if any).
> -----Original Message----- > From: Cullen Jennings [mailto:[email protected]] > Sent: Saturday, April 04, 2009 04:58 > To: Audet, Francois (SC100:3055) > Cc: Dan Wing; Jonathan Rosenberg; Jiri Kuthan; Jon Peterson; > SIP IETF; Uzelac, Adam; Dean Willis > Subject: Re: [Sip] francois' comments and why RFC4474 not > used in the field > > > I can't remember which people thought this did not solve > their problem but I remember the characteristics of the > discussion were similar of being unclear where this would or > would not work and unclear on what the problem was this did not solve. > > Cullen <in my individual contributor role> > > On Apr 1, 2009, at 10:15 AM, Francois Audet wrote: > > > So, having re-read all these drafts... > > > > Cullen/Jon, > > > > Why is something like draft-wing-sip-identity-media (let's > focus just > > on the DTLS-SRTP version for now) not a proper solution to > the problem > > we are trying to solve? > > > > The problem being (I think): > > Identity Assertion of both the Signalling and the > Media, BUT allowing > > for relays? > > > > This has the advantage of being end-to-end. I guess the > alternative is > > to not have end-to-end media identity assertion, and instead have > > Alice-to- > > her-service-provider's relay, and > Bob-to-his-service-provider's-relay > > instead. > > > >> -----Original Message----- > >> From: Dan Wing [mailto:[email protected]] > >> Sent: Monday, March 30, 2009 21:16 > >> To: Audet, Francois (SC100:3055); 'Jonathan Rosenberg'; > 'Jiri Kuthan' > >> Cc: 'SIP IETF'; 'Uzelac, Adam'; 'Dean Willis' > >> Subject: RE: [Sip] francois' comments and why RFC4474 not > used in the > >> field > >> > >> > >> > >> > >>> -----Original Message----- > >>> From: Francois Audet [mailto:[email protected]] > >>> Sent: Monday, March 30, 2009 7:53 PM > >>> To: Jonathan Rosenberg; Jiri Kuthan; Dan WING > >>> Cc: SIP IETF; Uzelac, Adam; Dean Willis > >>> Subject: Re: [Sip] francois' comments and why RFC4474 not > >> used in the > >>> field > >>> > >>> For everybody's reference, can you point to Dan's draft? > >> > >> It is > >> http://tools.ietf.org/html/draft-wing-sip-identity-media-02 > >> > >> other proposals in the same sphere, > >> http://tools.ietf.org/html/draft-fischer-sip-e2e-sec-media-00 > >> http://tools.ietf.org/html/draft-kaplan-sip-asserter-identity-01 > >> > >> -d > >> > >> > >>> On Mar30 2009 19:12 , "Jonathan Rosenberg" > >> <[email protected]> wrote: > >>> > >>>> inline: > >>>> > >>>> Jiri Kuthan wrote: > >>>> > >>>> > >>>>>> From an end user perspective, I would assert that the > >>> most important > >>>>>> thing is probably the media. If the callerID says, "this > >>> is bob", what > >>>>>> is important to the user, is that when I pick up the > >>> phone and start > >>>>>> talking, it will be Bob who hears me, and Bob that I hear. > >>>>>> > >>>>>> Consider this litmus test: > >>>>>> > >>>>>> If the signaling actually came from Mary (perhaps as a > >>> third party), > >>>>>> but the media goes/comes to/from Bob, who should appear > >>> on the caller > >>>>>> ID? I say - Bob. > >>>>> > >>>>> 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). > >>>> > >>>> You can still have that. Just don't ring the phone until > >>> early media has > >>>> been exchanged and verified. Indeed if you were doing an > >>> ICE-style thing > >>>> per Dan's draft, you'd get that for free. > >>>> > >>>> -Jonathan R. > >>>> > >>>> > >>> > >> > >> > > _______________________________________________ > > 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 > > _______________________________________________ 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
