RE: [P2PSIP] HIP: optional, mandatory?

<marcin.matuszewski@nokia.com> Wed, 23 January 2008 12:16 UTC

Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHeXJ-0007jD-Hj; Wed, 23 Jan 2008 07:16:57 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHeXI-0007j6-Ba for p2psip@ietf.org; Wed, 23 Jan 2008 07:16:56 -0500
Received: from smtp.nokia.com ([192.100.105.134] helo=mgw-mx09.nokia.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHeXH-00050L-Jy for p2psip@ietf.org; Wed, 23 Jan 2008 07:16:55 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id m0NCHMGl019033; Wed, 23 Jan 2008 06:17:45 -0600
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 23 Jan 2008 14:16:30 +0200
Received: from esebe102.NOE.Nokia.com ([172.21.138.217]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 23 Jan 2008 14:16:30 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [P2PSIP] HIP: optional, mandatory?
Date: Wed, 23 Jan 2008 14:20:57 +0200
Message-ID: <3F18E76823C95E4795181D74BAC7664F05BE1985@esebe102.NOE.Nokia.com>
In-Reply-To: <24CCCC428EFEA2469BF046DB3C7A8D223AE562@namail5.corp.adobe.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [P2PSIP] HIP: optional, mandatory?
Thread-Index: Achc/81qfVF32UzhRmudgRKC0cbLWwACy4iwAABm/HA=
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com><20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com><77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com><7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com><77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com><10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu><4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com><465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com><284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com> <DD40D2FF-809B-4B1F-B43B-0E8F41ED21DB@quinthar.com> <24CCCC428EFEA2469BF046DB3C7A8D223AE531@namail5.corp.adobe.com> <3F18E76823C95E4795181D74BAC7664F05B951F1@esebe102.NOE.Nokia.com> <4795A323.3080401@telecomitalia.it> <C4CA168C-0627-4EB9-818F-C88A4826412E@cs.columbia.edu> <4795F8A9.9090206@telecomitalia.it> <24CCCC428EFEA2469BF046DB3C7A8D223AE562@namail5.corp.adobe.com>
From: <marcin.matuszewski@nokia.com>
To: <hsinnrei@adobe.com>, <enrico.marocco@telecomitalia.it>
X-OriginalArrivalTime: 23 Jan 2008 12:16:30.0391 (UTC) FILETIME=[C913CC70:01C85DB9]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: p2psip@ietf.org
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

The mobile phones implement the P2PP protocol
(http://tools.ietf.org/id/draft-baset-p2psip-p2pp-01.txt) and Kademlia
DHT. Depending on a situation a mobile phone may act as a peer or a
client. If it becomes a client it connects to some of P2PP peers and
uses a subset of the P2PP protocol, called a "client protocol" (mainly
PublishObject, RemoveObject, LookupObject), to perform PUT/GET
operations. If a mobile phone can act as a peer then it uses the full
P2PP protocol and runs Kademlia code (the clients do not run DHT).

In addition the demo includes TURN like relays that publish their
contact information in the overlay and help clients and peers to
traverse NATs/Firewals.

Marcin 

>-----Original Message-----
>From: ext Henry Sinnreich [mailto:hsinnrei@adobe.com] 
>Sent: 22 January, 2008 17:30
>To: Enrico Marocco; Matuszewski Marcin (Nokia-NRC/Helsinki)
>Cc: p2psip@ietf.org; Henning Schulzrinne
>Subject: RE: [P2PSIP] HIP: optional, mandatory?
>
>Enrico,
>
>>So, if I understand correctly, Marcin's mobile devices 
>connect directly 
>>to P2PP peers running on PlanetLab nodes without effectively 
>being part 
>>of PlanetLab, establishing an overlay made of both PL and 
>non-PL nodes,
>
>The mobile devices run the _client protocol_ that has been the 
>topic of many discussions on this list.
>
>Maybe Marcin can give us the reference to the latest 
>description of the client protocol for P2PP implemented for 
>this trial. 
>
>Thanks, Henry
>
>-----Original Message-----
>From: Enrico Marocco [mailto:enrico.marocco@telecomitalia.it]
>Sent: Tuesday, January 22, 2008 6:08 AM
>To: Henning Schulzrinne
>Cc: marcin.matuszewski@nokia.com; Henry Sinnreich; p2psip@ietf.org
>Subject: Re: [P2PSIP] HIP: optional, mandatory?
>
>Henning Schulzrinne wrote:
>> PlanetLab is many things, but stable is not the adjective I would
>use...
>> These are generally servers run on a volunteer basis by graduate 
>> students in various university labs; they routinely get 
>disconnected, 
>> crash or get overloaded with other experiments.
>> 
>> Relative to consumer nodes, they do tend to have public IP addresses.
>
>So, if I understand correctly, Marcin's mobile devices connect 
>directly to P2PP peers running on PlanetLab nodes without 
>effectively being part of PlanetLab, establishing an overlay 
>made of both PL and non-PL nodes, right?
>
>--
>Ciao,
>Enrico
>

_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www1.ietf.org/mailman/listinfo/p2psip