Re: [Sipping] RE: Comments on draft-johnston-sipping-p2p-ipcom-01.txt

[Xiaotao Wu <[e-mail]>]

> > >     return more than just a simple Contact URI. In a pure Peer-to-peer
> > >     SIP network, if the user's phone is not reachable (e.g., it is a
> > >     wireless phone that is out of range), then we would still like
> > >     the call to follow the user's call handling preferences.
> > > This might
> > >     involve taking voicemail for the user, or forwarding the call to
> > >     another AoR. The user might have expressed these call handling
> > >     preferences by uploading a CPL script to the "network" somehow
> > >     beforehand.
> >
> > Yes - these are important requirements that we will want to meet with
> > this protocol.
>
> Why is this an important requirement ? If the goal of this draft is
> pure p2p, then there is no intelligent network inbetween that needs to
> be relied on from a service perspective. If CPL needs to be invoked,
> it would be a part of the User Agent either originating or terminating
> a call and not some node in between.

I agree with Arjun's point. In a P2P network, you cannot put your
service scripts in the network due to both reliability and privacy
concerns. If you want it to be reliable, you must have your scripts
distributed to all potential routing nodes, which you never know whether
they are trustable or untrustable, and the privacy will be a big concern.

There could be some exceptions, such as spam filtering, a user may like to
push it into the network so he does not have to keep a copy for all his
devices. But, keeping service script copies on every device and
synchronize the copies would not be a big problem in a P2P network.

For services on endpoints, we have extended CPL to the Language for End
System Services (LESS), which can be found at

http://www.ietf.org/internet-drafts/draft-wu-iptel-less-00.txt

The new language removes the 'proxy' action in CPL since you would not
expect your endpoints to proxy calls. The language will just fit the P2P
environment for services.

Thanks!

-Xiaotao

>
> --
> Arjun Roychowdhury
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use [e-mail] for questions on current sip
> Use [e-mail] for new developments of core SIP
>

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [e-mail] for questions on current sip
Use [e-mail] for new developments of core SIP