Re: [P2PSIP] mobile p2p in p2psip
Henry Sinnreich <hsinnrei@adobe.com> Tue, 10 February 2009 04:18 UTC
Return-Path: <hsinnrei@adobe.com>
X-Original-To: p2psip@core3.amsl.com
Delivered-To: p2psip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E3FF73A67DD for <p2psip@core3.amsl.com>; Mon, 9 Feb 2009 20:18:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.939
X-Spam-Level:
X-Spam-Status: No, score=-5.939 tagged_above=-999 required=5 tests=[AWL=0.359, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9a6T7d6oBbfF for <p2psip@core3.amsl.com>; Mon, 9 Feb 2009 20:18:06 -0800 (PST)
Received: from exprod6og116.obsmtp.com (exprod6og116.obsmtp.com [64.18.1.37]) by core3.amsl.com (Postfix) with ESMTP id F09C93A68EB for <p2psip@ietf.org>; Mon, 9 Feb 2009 20:17:51 -0800 (PST)
Received: from source ([192.150.8.22]) by exprod6ob116.postini.com ([64.18.5.12]) with SMTP ID DSNKSZD/4uOJTYv+XcUryNGqEUJOHzHtDd0h@postini.com; Mon, 09 Feb 2009 20:18:09 PST
Received: from inner-relay-3.eur.adobe.com (inner-relay-3b [10.128.4.236]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id n1A4HXE0011637; Mon, 9 Feb 2009 20:17:33 -0800 (PST)
Received: from nacas01.corp.adobe.com (nacas01.corp.adobe.com [10.8.189.99]) by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id n1A4HPY4000571; Mon, 9 Feb 2009 20:17:30 -0800 (PST)
Received: from fe01.corp.adobe.com (10.8.192.82) by nacas01.corp.adobe.com (10.8.189.99) with Microsoft SMTP Server (TLS) id 8.1.336.0; Mon, 9 Feb 2009 20:17:26 -0800
Received: from nambx05.corp.adobe.com ([10.8.189.124]) by fe01.corp.adobe.com ([10.8.192.82]) with mapi; Mon, 9 Feb 2009 20:17:26 -0800
From: Henry Sinnreich <hsinnrei@adobe.com>
To: Song Haibin <melodysong@huawei.com>, David Artu?edo Guillén <dag@tid.es>, Victor Pascual ávila <victor.pascual.avila@gmail.com>
Date: Mon, 09 Feb 2009 20:17:23 -0800
Thread-Topic: [P2PSIP] mobile p2p in p2psip
Thread-Index: AcmKiaz2weRjgudzS9eFn+7ychuCJgASCHkRABNHV1AABeMtSA==
Message-ID: <C5B65BF3.B4BC%hsinnrei@adobe.com>
In-Reply-To: <009401c98b22$687903c0$100ca40a@china.huawei.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C5B65BF3B4BChsinnreiadobecom_"
MIME-Version: 1.0
Cc: longbwe longbwe <longbwee@gmail.com>, "Wang, Sherry" <Sherry.Wang@jhuapl.edu>, "p2psip@ietf.org" <p2psip@ietf.org>
Subject: Re: [P2PSIP] mobile p2p in p2psip
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Feb 2009 04:18:08 -0000
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" <melodysong@huawei.com> 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] mobile p2p in p2psip longbwe longbwe
- Re: [P2PSIP] mobile p2p in p2psip Wang, Sherry
- Re: [P2PSIP] mobile p2p in p2psip longbwe longbwe
- Re: [P2PSIP] mobile p2p in p2psip Henry Sinnreich
- Re: [P2PSIP] mobile p2p in p2psip Henry Sinnreich
- Re: [P2PSIP] mobile p2p in p2psip David Artuñedo Guillén
- Re: [P2PSIP] mobile p2p in p2psip Song Haibin
- Re: [P2PSIP] mobile p2p in p2psip longbwe longbwe
- Re: [P2PSIP] mobile p2p in p2psip Kurt Tutschku
- Re: [P2PSIP] mobile p2p in p2psip Victor Pascual Ávila
- Re: [P2PSIP] mobile p2p in p2psip Bruce Lowekamp
- Re: [P2PSIP] mobile p2p in p2psip Henry Sinnreich
- Re: [P2PSIP] mobile p2p in p2psip Henry Sinnreich
- Re: [P2PSIP] mobile p2p in p2psip Song Haibin
- Re: [P2PSIP] mobile p2p in p2psip Henry Sinnreich
- Re: [P2PSIP] mobile p2p in p2psip Xiao, Lin (NSN - CN/Beijing)
- Re: [P2PSIP] mobile p2p in p2psip Das, Saumitra
- Re: [P2PSIP] mobile p2p in p2psip longbwe longbwe
- Re: [P2PSIP] mobile p2p in p2psip Xiao, Lin (NSN - CN/Beijing)
- [P2PSIP] Interoperability vs Pluggability (was Re… Dan York
- Re: [P2PSIP] Interoperability vs Pluggability (wa… Victor Pascual Ávila
- Re: [P2PSIP] Interoperability vs Pluggability (wa… Dan York
- Re: [P2PSIP] Interoperability vs Pluggability (wa… Victor Pascual Ávila
- Re: [P2PSIP] mobile p2p in p2psip Henry Sinnreich
- Re: [P2PSIP] Interoperability vs Pluggability (wa… Dan York
- Re: [P2PSIP] mobile p2p in p2psip Wang, Sherry
- Re: [P2PSIP] Interoperability vs Pluggability (wa… David A. Bryan
- Re: [P2PSIP] mobile p2p in p2psip Wang, Sherry
- Re: [P2PSIP] mobile p2p in p2psip David A. Bryan
- Re: [P2PSIP] mobile p2p in p2psip Erkki Harjula
- Re: [P2PSIP] Interoperability vs Pluggability (wa… Bruce Lowekamp
- Re: [P2PSIP] Interoperability vs Pluggability (wa… Bruce Lowekamp
- Re: [P2PSIP] mobile p2p in p2psip Henry Sinnreich
- Re: [P2PSIP] mobile p2p in p2psip Wang, Sherry
- Re: [P2PSIP] mobile p2p in p2psip Das, Saumitra
- Re: [P2PSIP] mobile p2p in p2psip Minh Nguyen
- Re: [P2PSIP] mobile p2p in p2psip Victor Pascual Ávila
- Re: [P2PSIP] Interoperability vs Pluggability (wa… Song Haibin
- Re: [P2PSIP] Interoperability vs Pluggability (wa… Dan York
- Re: [P2PSIP] mobile p2p in p2psip Xiao, Lin (NSN - CN/Beijing)
- Re: [P2PSIP] mobile p2p in p2psip Minh Nguyen
- Re: [P2PSIP] Interoperability vs Pluggability (wa… Xiao, Lin (NSN - CN/Beijing)
- Re: [P2PSIP] Interoperability vs Pluggability (wa… Bruce Lowekamp
- Re: [P2PSIP] Interoperability vs Pluggability (wa… Bruce Lowekamp
- Re: [P2PSIP] Interoperability vs Pluggability (wa… Roni Even