>Frequent changes has to be managed in order to route messages efficiently.
>It is not the same as churn, but it introduces similar challenges, IMHO.

This makes sense and is the reason the present work in the P2P SIP WG we have 
peer nodes and client nodes.

There was an I-D (now expired) on this:
Pascual, V., Matuszewski, M., Shim, E., Zhang, H., and S. Yongchao, "P2PSIP 
Clients",
<draft-pascual-p2psip-clients>

It was preceded and followed by many discussions on this topic, such as that 
frequent p2p protocol messages for peer nodes will quickly exhaust the battery.

Victor: What has happened to the I-D on p2p clients?

Reload Base also specifies:

   Peer:  A host that is participating in the overlay.  Peers are
      responsible for holding some portion of the data that has been
      stored in the overlay and also route messages on behalf of other
      hosts as required by the Overlay Algorithm.

   Client:  A host that is able to store data in and retrieve data from
      the overlay but which is not participating in routing or data
      storage for the overlay.

Given this protocol work to make P2P SIP work for mobile devices, I may be 
excused for not liking the marketing term "mobile p2p". As for other, non-SIP 
applications, the above protocol work also applies quite well, as the the 
Reload authors have said.

Please let us know if the above definitions meet your requirements or not.

Henry


On 2/9/09 1:40 AM, "David Artuñedo Guillén" <[email protected]> wrote:

Henry,

I guess it is related to the fact that in mobility your device gets different 
IPs in short periods of time. Frecuent changes has to be managed in order to 
route messages efficiently. It is not the same as churn, but it introduces 
similar challenges, IMHO.

BR

Enviado desde mi iPhone

El 08/02/2009, a las 21:22, "Henry Sinnreich" <[email protected]> escribió:

Please help me understand the technical (not marketing) meaning of mobile p2p.
Mobility is inherent on the Internet and can be implemented in several ways.

Or are you referring to to mobile phones not connected to the Internet?
Where is the protocol capability difference between a laptop, a netbook and a 
smart phone?

This sounds simplistic, but wireless to me is a wire into the Internet, unless 
we talk about some closed network, and please tell me why would I buy it?

Henry


On 2/7/09 2:57 AM, "longbwe longbwe" <[email protected] 
<mailto:[email protected]> > wrote:

Sheery,

Thanks very much for your reply.Maybe it is a little early to set a seperate WG 
for Mobile P2P, I am  wondering whether the work of P2PSip can be extensible to 
wireless scenarios, e.g. its architecture.Mobility management is certainly one 
of our interested fields, which also include the network topology, 
architecture, peer protocol, private issue, security and so on.We would like to 
discuss one or more such related topics with you and any one else.  The 
underlying fact is that with the issue of  3G lisences in China and emergence 
of more and more cell phone applications, our team think we should do some work 
to extend the P2P technic from PC to mobile devices.

Best wishes,
Bin Long

On Sat, Feb 7, 2009 at 12:40 AM, Wang, Sherry <[email protected] 
<mailto:[email protected]> > wrote:
Bin,

It's out of question that we should do it. I have seen mobile P2P researches 
and discussions existing for a while. Should we have a separate WG because of 
its technical significance and complexity, I am not sure. Important is that we 
need to work on it. Are you interested in mobility management only, e.g. 
handover, or more?

Thanks,
Sherry Wang

________________________________
From: [email protected] <mailto:[email protected]>  
[mailto:[email protected] <mailto:[email protected]> ] On Behalf Of 
longbwe longbwe
Sent: Friday, February 06, 2009 1:39 AM
To: [email protected] <mailto:[email protected]>
Subject: [P2PSIP] mobile p2p in p2psip

Hi all,
We want to know if mobile p2p can be discussed in this WG, or the p2psip is 
also appropriate for the wireless scenarios, because we are intrested in mobile 
p2p now and wish to do some communication with the ones who also research on it.
Any feedback is appreciated!
Best Regards,
     Bin Long


_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip

_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip

Reply via email to