IETF Logo Mail Archive

Re: [P2PSIP] HIP: optional, mandatory?

Henning Schulzrinne <hgs@cs.columbia.edu> Tue, 22 January 2008 13:12 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 1JHIvy-0007kP-W4; Tue, 22 Jan 2008 08:12:59 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHIvy-0007jw-4M for p2psip@ietf.org; Tue, 22 Jan 2008 08:12:58 -0500
Received: from brinza.cc.columbia.edu ([128.59.29.8]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHIvx-0000aM-PJ for p2psip@ietf.org; Tue, 22 Jan 2008 08:12:58 -0500
Received: from Upstairs-Mac (pool-71-250-50-170.nwrknj.east.verizon.net [71.250.50.170]) (user=hgs10 mech=PLAIN bits=0) by brinza.cc.columbia.edu (8.14.1/8.14.1) with ESMTP id m0MDCqpk010101 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 22 Jan 2008 08:12:53 -0500 (EST)
Message-Id: <C4CA168C-0627-4EB9-818F-C88A4826412E@cs.columbia.edu>
From: Henning Schulzrinne <hgs@cs.columbia.edu>
To: Enrico Marocco <enrico.marocco@telecomitalia.it>
In-Reply-To: <4795A323.3080401@telecomitalia.it>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Subject: Re: [P2PSIP] HIP: optional, mandatory?
Date: Tue, 22 Jan 2008 08:13:06 -0500
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>
X-Mailer: Apple Mail (2.915)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.8
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: hsinnrei@adobe.com, 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

>

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.

It would be good to gather some statistics on the dynamics of  
PlanetLab nodes.

> Marcin, could you provide some more details about your mobile nodes
> joining a 600-peers overlay on PlanetLab?  As far as I know, PlanetLab
> is a federated testbed made of very stable public servers; how did you
> manage to make mobile devices part of it?  Or were the mobile nodes
> participating only as clients, through a XML-RPC-like interface?
>
> -- 
> Ciao,
> Enrico
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.ietf.org/mailman/listinfo/p2psip


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

v2.23.0 | Report a Bug | By Email