On 10/12/07, Paul Kyzivat <[EMAIL PROTECTED]> wrote:
>
>
>
> Pars Mutaf wrote:
> > Hello,
> >
> > Is the SIP trapezoid needed in cellular networks?
> > This is a deployment question. The very simple logic
> > of my question is as follows:
> >
> > For privacy reasons:
> > - cellular users don't publish their SIP URIs in a
> > phonebook.
> > - unpredictable and long SIP URIs are recommended.
> >
> > Thus the SIP URI will be:
> >
> > [EMAIL PROTECTED]
> >
> > which may be too long to read/type as we do
> > today when two cell phone users meet each other?
>
> We may have a different usage model in mind.
>
> AFAIK cellular users are identified by their phone number, which is used
> for humman interchange of addresses all the time. When rendered as a
> URI, it can be a TEL URI, or a sip uri. When a sip URI it has a
> particular domain, which may not normally be known to the caller. But in
> that case they start with a TEL uri and it gets translated along the way
> - typically with ENUM. In any case it isn't the caller's concern.
>
> The mobile *device* has a different, contact, address. But callers are
> never expected to know that. It is the point of the sip trapezoid
> (actually just part of it - the home proxy) to do this translation.
In my simplistic view:
I need my packets routed from my device to the other device.
Mobile IPv6 home address does that (including location
management, i.e. locating the target device when I make a call).
I'm not saying that Mobile IPv6 home address corresponds to the
telephone number. We still have a SIP URI for the SIP application.
Thanks,
pars
Paul
>
> > If so:
> > Any solution is welcome (e.g. pairing) to help
> > users exchange their SIP URIs easily. For example,
> > user names are locally published, I choose the name
> > of my friend in a wireless network, and get the SIP URI.
> >
> > If such solution exists:
> > Why not use it also for exchanging a Mobile IPv6
> > home address. I.e., I get my friend's SIP URI and
> > home address concurrently. [bonus result: we can
> > establish IPsec since we already know our IP addresses].
> >
> > Conclusion:
> > By the basic SIP privacy requirement we also came to
> > solving the routing problem.
> >
> > What I am missing?
> >
> > Thanks,
> > pars
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > 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
