Song, >there are scenarios where only mobile devices are available. >In this case, more considerations need to be given to the >mobility of a "peer".
This is a valid scenario, for example in disasters or emergencies when access to the SIP network is not possible, but the mobile devices could still communicate on the same L2 radio network, say on the same WiFi network. One approach is described here and it does not require p2p: http://tools.ietf.org/html/draft-lee-sip-dns-sd-uri-00 Henry On 2/9/09 7:53 PM, "Song Haibin" <[email protected]> wrote: Hi Henry and Bin, >>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. As the co-author of this I-D (use my previous name Song Yongchao), I support that the mobile devices should be better to act as clients rather than peers whenever possible. But I guess there are scenarios where only mobile devices are available. In this case, more considerations need to be given to the mobility of a "peer". Bin, I don't know if this is what you concern about. BR Song Haibin
_______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
