Pars:

This is sounding like it's less and less a SIP problem at all. Based on what you say below, I think all you need is some additional vCard fields (one for voice SIP URIs, and maybe one for home IPv6 addresses -- but I'd pursue these as separate efforts, if I were you). You can then send these vCards around in OBEX, email, web pages, or whatever else makes sense. Note that OBEX over Bluetooth, IrDA, and/or SMS completely satisfies the requirements you describe below -- and these are already well-defined, mature, and widely deployed technologies.

Look at RFC 4770 to see how vCard extensions look.

/a

Pars Mutaf wrote:


On 10/12/07, *Spencer Dawkins* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    > The privacy problem: normally I shouldn't be able to discover
    your SIP URI.

    I'm guessing that if you can't tell people your SIP AOR, then SIP
    is not for
    you.


Hello,

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

The point is that, if I give you my SIP URI (using the pairing procedure)
then I can also give you my Mobile IPv6 home address using the same
pairing procedure. In other words, there is _no more resolution_ from
SIP URI to home IP address. You get them **concurrently**.

We have each other's SIP URIs and home addresses.
->SIP application is happy, it has the target SIP URI.
->Routing problem is solved by mobile IPv6.

My question was: do we need the SIP trapezoid in this case.

Thanks,
pars




    Thanks,

    Spencer




    _______________________________________________
    Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
    This list is for NEW development of the core SIP Protocol
    Use [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]> for questions on current sip
    Use [EMAIL PROTECTED] <mailto:[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



_______________________________________________
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

Reply via email to