On 10/12/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > From: "Pars Mutaf" <[EMAIL PROTECTED]> > > I won't publish my SIP URI in a phone book allowing anyone to see it. > We already agreed on that. > > I'll tell it to people that I know only. I'll tell it using a user > friendly > mechanism called "pairing" : We meet each other with our cell phones, > and agree to exchange our contact information. So, the procedure is > under our control. Pairing is good for us also because it allows us to > exchange a secret key (note that this is already enough motivation for > the pairing idea). > > So your usage model is that you will only want to communicate with > people that you already know, and in most cases, have personally met. > This means that you have no need of a directory, as your SIP device > will be used to remember the URI of every person that you can call.
Right. This model is the one being used today. Note that Bluetooth already comes with a pairing solution. We should make this idea technology independent and hopefully allow users to pair their devices through the Internet, i.e. over long distances. There are important motivations for that. Note that this is much like how many mobile phone users use their > mobiles, but the opposite of the normal model of landline telephones, > where it is expected that the public can discover and contact you. > > My question was: do we need the SIP trapezoid in this case. > > If you assume that each mobile has a fixed IPv6 address, then the > address-based URI will always reach the mobile. And in that case, you > don't need a home proxy that translates an AOR into a contact URI -- > in effect, that translation process has been moved down into the > network layer by the process of routing to that IPv6 address. > > But it seems unlikely that an individual will have a fixed IPv6 > address over the long term. For one, it seems unlikely that *every* > network will provide uniform IPv6 mobility. For another, what if the > user replaces his mobile? OK. We should use DNS perhaps to meet these requirements. You can change your mobile IPv6 home address whenever you want I have the DNS name of your device (obtained via pairing). Is it acceptable to have fixed DNS name over long term? There are also other interesting issues: With the proposed model, I'm not sure if the operator needs to know my SIP URI. Note also that the SIP URI is never transmitted in clear-text, we have IPsec between the peers from the beginning (thanks to pairing). But I guess these issues need to be discussed in more detail. https://www1.ietf.org/mailman/listinfo/humanresolvers Thanks, pars Dale > > > _______________________________________________ > Sip mailing list https://www1.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://www1.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
