From p2psip-bounces@ietf.org  Wed Apr  2 11:23:18 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 07D923A6EAD;
	Wed,  2 Apr 2008 11:23:18 -0700 (PDT)
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 DBF7728C17D
	for <p2psip@core3.amsl.com>; Wed,  2 Apr 2008 11:23:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 YcfyCSgUqdqY for <p2psip@core3.amsl.com>;
	Wed,  2 Apr 2008 11:23:16 -0700 (PDT)
Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.177])
	by core3.amsl.com (Postfix) with ESMTP id 8BD563A696B
	for <p2psip@ietf.org>; Wed,  2 Apr 2008 11:23:13 -0700 (PDT)
Received: by py-out-1112.google.com with SMTP id x19so3679827pyg.24
	for <p2psip@ietf.org>; Wed, 02 Apr 2008 11:23:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth;
	bh=4Fh28kaHk4Cn7iSnzR52Z7baOZLdNP1hhboVTOXzsEQ=;
	b=Es9SqltxMIZq3fOfzcIPzpZ8NLff6RWi2keOyGh96j5P2vr6NdoRp7EeJciiVCNXseK7EYMsjZn1q4+GYGALrDhU6/IIrmt7HEgE7MV2O+t+YgamOMBdvt+/Lsh9ltIDcxUsu4TVEmgw88yW5zrkEogy6+YyDARy9o4UR2vSpyc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=message-id:date:from:sender:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth;
	b=BurmVsexpNW7lZxGYPcox770tD5sk8WShvXk1savjAFQRUn0bJjW9I0hMGvdsknVlFeb0V3bLKUPBvWPnA8finEYGJVABjD1/h45S6STQRY+2F46d05f8YHhNLbmb1nuo/a4Tt7WThbn5JiUNs8BR1BOuw1wJ1N6n+euaHgjBGw=
Received: by 10.65.231.8 with SMTP id i8mr6090422qbr.14.1207160593246;
	Wed, 02 Apr 2008 11:23:13 -0700 (PDT)
Received: by 10.65.133.10 with HTTP; Wed, 2 Apr 2008 11:23:13 -0700 (PDT)
Message-ID: <4d4304a00804021123j5aaeb2d6n1ab220f417b61f5a@mail.gmail.com>
Date: Wed, 2 Apr 2008 14:23:13 -0400
From: "David A. Bryan" <dbryan@sipeerior.com>
To: "P2PSIP Mailing List" <p2psip@ietf.org>, "Brian Rosen" <br@brianrosen.net>
MIME-Version: 1.0
Content-Disposition: inline
X-Google-Sender-Auth: cd537b35d499295d
Subject: [P2PSIP] Draft meeting minutes and materials from IETF-71
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

Folks,

The draft minutes of the IETF 71 P2PSIP meeting are up here:

http://www.ietf.org/proceedings/08mar/minutes/p2psip.txt

Thanks to Ted Hardie for putting them together. My apologies for them
not being up sooner (chair's fault, not Ted -- he got them to us). I
thought they were up a few weeks ago but discovered they were not.
Explains why I hadn't heard any comments!

The overall meeting materials page (slides, agenda, etc.) is here:

https://datatracker.ietf.org/meeting/71/materials.html

Again, please take a look and let me know if anything is wrong or
missing. The final date for revisions is April 11.

Thanks!

David

-- 
David A. Bryan
dbryan@SIPeerior.com
+1.757.565.0101 x101
+1.757.565.0088 (fax)
www.SIPeerior.com
_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www.ietf.org/mailman/listinfo/p2psip


From p2psip-bounces@ietf.org  Wed Apr  2 12:01:17 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7797928C367;
	Wed,  2 Apr 2008 12:01:17 -0700 (PDT)
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 C4FE928C634;
	Wed,  2 Apr 2008 12:01:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, 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 ku0FGEmV0A+x; Wed,  2 Apr 2008 12:01:14 -0700 (PDT)
Received: from exprod6og103.obsmtp.com (exprod6og103.obsmtp.com [64.18.1.185])
	by core3.amsl.com (Postfix) with ESMTP id 41D8328C367;
	Wed,  2 Apr 2008 11:59:44 -0700 (PDT)
Received: from source ([192.150.11.134]) by exprod6ob103.postini.com
	([64.18.5.12]) with SMTP; Wed, 02 Apr 2008 11:59:45 PDT
Received: from inner-relay-3.eur.adobe.com ([192.150.8.236])
	by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	m32IuqG3015405; Wed, 2 Apr 2008 11:56:52 -0700 (PDT)
Received: from fe1.corp.adobe.com (fe1.corp.adobe.com [10.8.192.70])
	by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id
	m32IxfqJ003553; Wed, 2 Apr 2008 11:59:42 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 2 Apr 2008 11:59:40 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 2 Apr 2008 11:58:37 -0700
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D22019E0954@namail5.corp.adobe.com>
In-Reply-To: <47F3642C.8050909@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] HIP NAT Traversal using NICE
Thread-Index: AciUr7sFDcnV89i3SL2ucA9JIg7RdgAQs8mg
References: <47F3642C.8050909@ericsson.com>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>,
	"mmusic" <mmusic@ietf.org>, "P2PSIP Mailing List" <p2psip@ietf.org>
X-OriginalArrivalTime: 02 Apr 2008 18:59:40.0948 (UTC)
	FILETIME=[B4B05D40:01C894F3]
Cc: internet-ads@tools.ietf.org, mmusic-chairs@tools.ietf.org,
	rai-ads@tools.ietf.org, David Ward <dward@cisco.com>
Subject: Re: [P2PSIP] [MMUSIC] HIP NAT Traversal using NICE
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

Gonzalo,

I would be interested in an updated evaluation from you on the practical
(near term) potential of using HIP NAT traversal for P2PSIP.  
There was even talk of running code.

Can you (and anyone else) share a few key thoughts, references and links
to running code?

Henry

-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
Of Gonzalo Camarillo
Sent: Wednesday, April 02, 2008 5:47 AM
To: mmusic
Cc: internet-ads@tools.ietf.org; mmusic-chairs@tools.ietf.org;
rai-ads@tools.ietf.org; David Ward
Subject: [MMUSIC] HIP NAT Traversal using NICE

Folks involved in the MMUSIC WG,

the HIP WG is developing a NAT traversal solution that is based on NICE:

http://www.ietf.org/internet-drafts/draft-ietf-hip-nat-traversal-03.txt

http://www.ietf.org/internet-drafts/draft-rosenberg-mmusic-ice-nonsip-00
.txt

This means that we depend on the NICE draft to have a working NAT 
traversal solution for HIP. However, from the presentation of this draft

in the last IETF, it is not clear to us whether or not the MMUSIC WG is 
going to work on this draft.

The HIP WG would like to encourage the MMUSIC WG to work on this 
specification, since we need it. If the MMUSIC WG decides not to do so, 
the HIP WG will most likely copy/paste the contents of the NICE draft in

our NAT traversal spec. However, we believe that having a stand-alone 
NICE specification can be useful for protocols other than HIP that will 
decide to use ICE for NAT traversal in the future.

A clarification of the status of this work in the MMUSIC WG would be 
appreciated.

Thanks,

Gonzalo
HIP WG co-chair
_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic
_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www.ietf.org/mailman/listinfo/p2psip


From p2psip-bounces@ietf.org  Sat Apr  5 11:01:48 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 304093A6D94;
	Sat,  5 Apr 2008 11:01:48 -0700 (PDT)
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 99C113A6A0F
	for <p2psip@core3.amsl.com>; Sat,  5 Apr 2008 11:01:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.351
X-Spam-Level: 
X-Spam-Status: No, score=0.351 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HELO_EQ_FR=0.35]
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 BQA-KTlFL3ME for <p2psip@core3.amsl.com>;
	Sat,  5 Apr 2008 11:01:45 -0700 (PDT)
Received: from smtp2b.orange.fr (smtp2b.orange.fr [80.12.242.145])
	by core3.amsl.com (Postfix) with ESMTP id CE08128C1A1
	for <p2psip@ietf.org>; Sat,  5 Apr 2008 11:01:44 -0700 (PDT)
Received: from me-wanadoo.net (localhost [127.0.0.1])
	by mwinf2b11.orange.fr (SMTP Server) with ESMTP id 581BF30000F1;
	Sat,  5 Apr 2008 20:01:52 +0200 (CEST)
Received: from puffy.lan (LPuteaux-151-41-30-75.w217-128.abo.wanadoo.fr
	[217.128.82.75])
	by mwinf2b11.orange.fr (SMTP Server) with ESMTP id DB24C30000EF;
	Sat,  5 Apr 2008 20:01:50 +0200 (CEST)
X-ME-UUID: 20080405180150897.DB24C30000EF@mwinf2b11.orange.fr
Message-ID: <47F7BE8E.7040100@orange.fr>
Date: Sat, 05 Apr 2008 20:01:50 +0200
From: FORTAINE Guillaume <gui.fortaine@orange.fr>
User-Agent: Thunderbird 2.0.0.6 (X11/20071225)
MIME-Version: 1.0
To: "Roy, Radhika R Dr CTR USA USAMC" <radhika.r.roy@us.army.mil>
References: <47F00353.8090807@orange.fr> <ddb0a6cc2778f.47f0ad4f@us.army.mil>
In-Reply-To: <ddb0a6cc2778f.47f0ad4f@us.army.mil>
Cc: p2psip@ietf.org, siwu@hrz.tu-chemnitz.de, dbryan@p2psip.org,
	axel@open-mesh.net, preston.marshall@darpa.mil,
	steve.stewart@navy.mil, lindner_marek@yahoo.de
Subject: Re: [P2PSIP] P2P SIP - Real-time Multimedia Services
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/pipermail/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>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

Dear Mister Roy,

You are Excellence and it's definitely an honor for me to be in contact =

with You Today

There are various ways for P2P Networking :

-US Army :

DirecNet Portal <http://direcnet.org/>


-DARPA :

Home - *Delay Tolerant Networking Research Group* <http://www.dtnrg.org/>


-Open Source :

B.A.T.M.A.N. =97 *open-mesh* <https://www.open-mesh.net/batman>


What I really appreciate in Navy SBIRs are their pragmatic approach and =

their low-level details (including Publications & Quantitative =

measurements) :

(SBIR) Navy - *High Throughput and Low Latency Multi-Hop Mobile Ad* =85 =

<http://www.navysbir.com/n08_1/N081-102.htm>

OBJECTIVE: While MANET promises to significantly increase the available =

Navy bandwidth, existing MANET throughput decreases exponentially as the =

number of hops increases (hops > 4). This research will enable: 1) a =

multimedia stream to hop over hundreds of nodes without quality =

degradation and 2) hundreds of multimedia steams to cross a single node =

without quality degradation; 3) an advance in the state-of-the art =

videoconferencing and legacy application virtualization.
Develop an end-to-end software solution (based on low-cost commodity =

hardware) that allows a multimedia stream (voice-over-internet-protocol =

[VoIP], videoconferencing, screen/application sharing, file transfer, =

and biological/chemical sensor data) to hop over a large number of nodes =

without quality degradation as defined by psychological human factor =

quality-of-service (QoS) requirements.

DESCRIPTION: Existing MANET solutions have difficulty delivering a =

multimedia stream over a large number of hops. This research will =

develop novel software solutions to maintain high throughput and low =

latency for multimedia delivery over a large number of hops. The =

solution should: allow >1 Mbps and <500 msec of delay over 100 hops and =

be able to handle the cross-stream interference from multiple steams =

flowing over a particular node; and allow low-bandwidth =

videoconferencing for multiple sites (>100); exploit the difference in =

human factor requirements for QoS for different multimedia (audio vs. =

video, vs. sensor data, etc) to optimize the streaming of different =

media types; use advanced compression and networking techniques to =

achieve a significant reduction (10X) in bandwidth compared to existing =

commercial solutions; advance in the state-of-the art videoconferencing =

and legacy application virtualization; adapt to a variety of networks =

(available bandwidth, packet loss rate and jitter); support FIPS 140-2 =

256 bit AES encryption; record the training sessions; and be able to run =

as a web-service or as a stand-alone program on segmented/closed/MANET =

networks.





During the past Years, I have benchmarked all the various approaches and =

I have always been convinced by the superiority of P2P Networking and =

its potential in the Commercial Sector, especially in emerging countries.

To quote :

PRIVATE SECTOR COMMERCIAL POTENTIAL/DUAL-USE APPLICATIONS:
If this SBIR can demonstrate that high throughput and low latency =

multi-hop MANET multimedia streaming is possible, it would solve a =

parallel need in the business and education communities. It could =

provide networks to developing countries (e.g. in Africa) where =

infrastructure-based networks is not cost-effective. The resulting =

network could deliver distance education, just-in-time remote training =

and telemedicine. The capability is critical to First Responders in =

hastily formed networks, where the Internet is not available due to =

natural or man-made disasters. The system could play an important role =

in government. In the event of a natural or man-made disaster in the =

Nation=92s Capital, it might be necessary for Congress to meet virtually. =

The capability would allow Congress members to meet from their home =

office to carry out their duties.






QoS is maybe one of the most elusive (not to say a buzzword) in the =

Network Engineering World that's why I will propose a bottom-up approach =

to try to follow the Navy SBIR Requirements, ensuring compliance to the =

OSI Model, by reducing the latency time at each layer, and around a =

common Kernel (Linux) and an underlying COTS platform ( that I am =

currently defining with my suppliers) to be able to have common denominator.


Layer 1 :

*Channel Access over Path Segments* for Ultra Low Latency MANETs =

<http://www.ir.bbn.com/%7Eramanath/pdf/caps-milcom07.pdf>




Layer-2 :

-MAC :

http://www.rts.uni-hannover.de/rtnet/roadmap.html

RTmac : WLAN-Specific MAC Discipline




-Routing :

24C3: *Wireless Kernel Tweaking* =

<http://events.ccc.de/congress/2007/Fahrplan/events/2292.en.html>


Wireless Kernel Tweaking

or how B.A.T.M.A.N. learned to fly

Kernel hacking definitely is the queen of coding but in order to bring =

mesh routing that one vital step further we had to conquer this, for us, =

unchartered territory. Working in the kernel itself is a tough and =

difficult task to manage, but the results and effectivity to be gained =

justify the long and hard road to success. We took on the mission to go =

down that road and the result is B.A.T.M.A.N. advanced which is a kernel =

land implementation of the B.A.T.M.A.N. mesh routing protocol =

specifically designed to manage Wireless MANs.

During the last years the number of deployed mesh networks has increased =

dramatically and their constant growth drove us around the edge of what =

we thought was possible. To cope with this rapid development we had to =

leave the slow and limited track of tweaking existing approaches and =

take an evolutionary step forward by porting the B.A.T.M.A.N. protocol =

into the kernel land and going down to layer 2. Using B.A.T.M.A.N. =

advanced as a showcase we will, in our lecture, deliver a detailed =

review on how one can go about developing linux kernel modules, give =

insights in what difficulties to expect and provide practical tips on =

how to go about this challenge without experiencing a damaging kernel =

freeze in due process. We will describe what problems we faced migrating =

down to layer 2 and how we went about solving them for example how we =

moved away from the kernel routing and handle the actual routing and =

data transport in B.A.T.M.A.N. itself. Also moving to layer 2 meant to =

leave IPs behind and solely rely on MAC-routing enabling features like =

DHCP, IPX, IPv6, etc which up to now was not possible and therefore =

comes as a big plus. On the other hand there were little if none =

diagnostic tools at all for routing on that level so we had to go back =

one step and develop the tools we needed ourselves.

These and other things we will cover in our presentation and also give =

an outlook into the future of mesh-routing, which will bring it even =

closer to the source of wifi - the wireless stack and its drivers and =

thereby improving the overall performance even more.





Layer-3 :

TNRL Projects <http://www.cs.ou.edu/%7Enetlab/sigma.html>

*SINEMO (_S_eamless _I_P-diversity based _NE_twork _MO_bility)* **
SINEMO is an extension of SIGMA architecture for NEtwork MObility =

(NEMO). IETF has proposed NEMO basic support protocol based on Mobile =

IPv6 to support mobile networks. NEMO basic support protocol inherits =

all the drawbacks of Mobile IPv6, such as inefficient routing path, =

single point bottleneck, increased handover latency and packet loss =

rates, and increased packet overhead etc. To address those problems, we =

propose a novel IP-diversity based mobile network architecture called =

SINEMO. The basic idea of SINEMO is to exploit IP diversity to keep the =

old path alive during the process of setting up the new path, thus =

achieving seamless handover of mobile networks between adjacent cells. =

In addition to seamless handover, SINEMO has a number of advantages such =

as easier deployment in the Internet infrastructure, co-operation with =

Internet's security protocols, efficient utilization of network =

bandwidth, etc. SINEMO's design incorporates a number of desirable =

features (for example, complete transparency of network mobility to the =

nodes in the mobile network and efficient utilization of the wireless =

links (i.e. minimum signaling)) for mobile networks.






Layer-4 :

http://sourceforge.net/projects/lksctp


Stream Control Transmission Protocol (SCTP) is a reliable, =

message-oriented, multihomed transport protocol. Developed by the IETF =

SIGTRAN working group to transport SS7 over IP, it is now the third =

general-purpose transport developed by the IETF.




Layer-5 :

*Real*-*time Multimedia Services Using Hybrid P2P SIP* =

<http://ieeexplore.ieee.org/iel5/4141327/4084518/04141533.pdf?tp=3D&isnumbe=
r=3D&arnumber=3D4141533>

*Real-time Multimedia Services Using Hybrid P2P SIP*
Mo, Yijun; Wang, Fei; Huang, Benxiong; Luo, Fu
Communications and Information Technologies, 2006. ISCIT apos;06. =

International Symposium on
Volume , Issue , Oct. 18 2006-Sept. 20 2006 Page(s):157 - 161
Digital Object Identifier   10.1109/ISCIT.2006.339907
*Summary:*SIP becomes one most poplar protocol in real-time multimedia =

services, but the central server becomes the single point of failure, =

While P2P becomes "killing level application" in Internet because of its =

robust and low cost. Combing P2P and SIP, we propose hybrid P2P SIP =

framework in the paper, and describe several important procedures, such =

as node registration, user registration and call procedure. But current =

P2P searching and routing arithmetic does not meet the requirement for =

low time delay in real-time multimedia applications. Then, we present a =

novel SOMCO arithmetic, which decreases the call delay and media =

forwarding delay to some extend. Simulation verifies that SOMCO is =

practical to support real-time multimedia services







I look forward to Your Answer,

Best Regards,



Roy, Radhika R Dr CTR USA USAMC wrote:
> Hi, Fortain:
>
> I think that you can start working for all those QOS mechanisms within th=
e framework of P2PSIP. Let me explain as follows:
>
> 1. Mobile Ad Hoc networks need P2P networking. As result, the application=
s also need to be P2P. P2PSIP WG is working for facilitating in building of=
 P2PSIP applications.
>
> 2. The ad hoc mobility part is primarily related to the topology control =
of MANETs and MANET WG and AUTOCONFIG WG are working in the layers 2-throug=
h 3/4. The QOS-mechanisms of the network layer are being taken care of by t=
hose WGs.
>
> 3. The application layer QOS for SIP in peer-to-peer mode can best be wor=
king within the framework of P2PSIP WG because, I believe, you do not need =
to do anything explicitly related to mobility assuming that the lower MAC a=
nd network layer of MANET are being taken care of by those WGs (e.g. topolo=
gy control, routing, QOS) and we can plug those things from the application=
 layer to the lower network to work cooperatively.
>
> 4. It is true that we may have to do something in the P2P application lay=
er like P2PSIP for QOS as well as for taking care of the ad hoc mobility, i=
t is still not well understood by all of us. Once the P2PSIP signaling prot=
ocol is taken care of, we will gain more experiences what we have to do nex=
t.
>
> However, if you suggest what specific problems related to QOS you want to=
 address in the P2PSIP application Layer for solving the performance proble=
ms, we can then look into those taking Navy's QOS requirements for MANET ne=
tworks.
>
> I appreciate for bringing the interesting real problems in the P2PSIP WG =
mailing list.
>
> Best regards,
> Radhika
>   =



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


From p2psip-bounces@ietf.org  Sat Apr  5 23:14:14 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 79A2A3A69D3;
	Sat,  5 Apr 2008 23:14:14 -0700 (PDT)
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 735483A6B52
	for <p2psip@core3.amsl.com>; Sat,  5 Apr 2008 23:14:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.968
X-Spam-Level: 
X-Spam-Status: No, score=0.968 tagged_above=-999 required=5
	tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001, SUBJ_ALL_CAPS=2.077]
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 fqROs95CoX0O for <p2psip@core3.amsl.com>;
	Sat,  5 Apr 2008 23:14:11 -0700 (PDT)
Received: from web54607.mail.re2.yahoo.com (web54607.mail.re2.yahoo.com
	[206.190.49.177])
	by core3.amsl.com (Postfix) with SMTP id 623743A695A
	for <p2psip@ietf.org>; Sat,  5 Apr 2008 23:14:11 -0700 (PDT)
Received: (qmail 7164 invoked by uid 60001); 6 Apr 2008 06:14:21 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=xWubFAPEQTbMwgCMcwMDM7Qw9/A5Yln9gvQvaF8e6M636zQBwl/zNJSswa65Xh51LsvxJTIo82LMD0SKk8odRsK74gmYjhcb/yvWcCZyfDXLVXVgfL0VwEfrj2sqWn+mOR4agf8pEHzbAQtj4t7+qS/lbCwnfW0O5EvtrSSmj+c=;
X-YMail-OSG: c50cj40VM1lofroXZEv8Q4vKIGeaEviHVfv1xhSOH9jIevxVR01jeC8qx54guwRpDSUGOfSNQbdt81Y5hntIbvB.4oDG3V9b6btYFLHoXaU5YfuWYx5MiquRbsWBqv89mIC4EwYfoMN408saX5cKqFw_
Received: from [212.138.113.8] by web54607.mail.re2.yahoo.com via HTTP;
	Sat, 05 Apr 2008 23:14:20 PDT
Date: Sat, 5 Apr 2008 23:14:20 -0700 (PDT)
From: Khaled Ragab <k_ragab2005@yahoo.com>
To: p2psip@ietf.org
MIME-Version: 1.0
Message-ID: <12638.6600.qm@web54607.mail.re2.yahoo.com>
Subject: [P2PSIP] CFP IEEE P2PWS
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1296073993=="
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

--===============1296073993==
Content-Type: multipart/alternative; boundary="0-581564740-1207462460=:6600"
Content-Transfer-Encoding: 8bit

--0-581564740-1207462460=:6600
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

We apologize in advance if you receive multiple copies of this CFP. 

  ======================================================================
    
                   CALL FOR CONTRIBUATIONS IEEE P2PWS 2008
                               The IEEE International Workshop On 
                                           Peer-to-Peer Web Services 
                                                  
                        http://faculty.kfupm.edu.sa/ICS/helmy/P2PWS08/index.htm
           In conjunction with the 10th International IEEE High Performance Computing and Communications 
  ======================================================================

  SCOPE
  Peer-to-peer (P2P) and Web Services (WS) technologies are currently attracting enormous media attention. 
In P2P systems a very large number of autonomous computing nodes (the peers) pool together their resources 
and rely on each other for data and services. We wish to organize a workshop to address the need for P2P 
technologies and platforms that support self-organization of WS, semantic WS, load balance, routing, etc.
The P2PWS workshop provides a forum for researchers and practitioners from academic, industrial, public 
and government sectors, to share their latest innovations on the P2P computing, Web services technologies 
and applications. The workshop will be advertised through mailing lists interested in P2P and WS fields in 
order to ensure that a wide range of authors will participate. 
 
Areas of interest include, but not limited to: 
  * Services composition in P2P Web services networks
  * Data placement and query answering in P2P systems
  * Transaction management for P2P Web services
  * Autonomous peers and semantic Web
  * Self-organization and emergent behavior in P2P systems
  * Resource allocation in P2P systems and Web services
  * Scalability, coordination, robustness and adaptability in P2P and Web services
  * Autonomic Web Services in P2P systems
  
Important Dates
   
  Papers Early Registration (abstract): April 20, 2008
  Papers Submission (No extend): May 20, 2008
  Author Notification: June 10, 2008
  Final Manuscript submission: July 1, 2008
  Workshop: September 25-27, 2008
   
  General Inquires Submission
   
  For more details and update information, please visit 
http://faculty.kfupm.edu.sa/ICS/helmy/P2PWS08/index.htm
  
Submit your paper through email to:
                    Khaled Ragab , General Chair
                    Tarek Helmy, Co-chair
  
Submission Guidelines
  Papers in P2P and Web Services related areas are solicited. Submissions must include an abstract, five to 
ten keywords, the e-mail address of the corresponding author and should not exceed 15 pages, including 
tables and figures. All paper submissions must represent original and unpublished work. Submission of a 
paper should be regarded as an undertaking that, should the paper be accepted, at least one of the authors 
will register for the conference and present the work. Submissions will be conducted electronically on the 
conference website
  ELECTRONIC SUBMISSION
  Prepare your paper with free styles not more than 15 pages in PDF file. Submit your paper(s) by email to 
workshop's General Chair Chair or Co-chair. 
Accepted papers will be published in the workshop proceedings by the IEEE Computer Society Press. 
In addition, there is a plan to invite authors to submit extended versions of their papers for a special issue 
of a respective journal. 
  General Chair
  Khaled Ragab (KFU, Saudi Arabia)
  Co-chair
  Tarek Helmy (KFUPM, Saudi Arabia)
  
International Program Committee 
  Aboul Ella Hassanien (Kuwait Univ.
  Asrar U. Haquie (KFU , Saudi Arabia)
  Farag Ezidin (KFUPM, Saudi Arabia)
  Jarallah Alghamdi (KFUPM, Saudi Arabia)
  Ibrahim Imam (AAST, Egypt)
  Iyad Rahwan (British Univ., UAE)
  Jeffery Bradshaw (IHMC, USA)
  Jianhua Ma  (Hosei Univ., Japan)
  Khaled Shaalan (British Univ., UAE)
  Laurence T. Yang (St. Francis Xavier Univ., Canada)
  M. Amamiya (Kyushu Univ., Japan)
  Moataz Ahmed (LEROS, USA)
  Mohamed Al-Naser (KFUPM, Saudi Arabia)
  M. Zahrani KFU, Saudi Arabia
  R. Kowalczyk (Swinburne Uni, Australia)
  Salaheldin Adam (KFUPM, Saudi Arabia)
  Sameh El-Ansary (Swedish Institute, Sweden)
  Satoshi Amamiya (Kyushu Univ., Japan)
  Yasser Kotb (Ain Shams Univ, Egypt


       
---------------------------------
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.
--0-581564740-1207462460=:6600
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<div>We apologize in advance if you receive multiple copies of this CFP. <BR></div>  <div>======================================================================<BR>&nbsp;&nbsp;&nbsp;&nbsp;</div>  <div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CALL FOR CONTRIBUATIONS IEEE P2PWS 2008</div>  <div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The IEEE International Workshop On <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Peer-to-Peer Web Services
 <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A href="http://faculty.kfupm.edu.sa/ICS/helmy/P2PWS08/index.htm">http://faculty.kfupm.edu.sa/ICS/helmy/P2PWS08/index.htm</A><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In conjunction with the 10th International IEEE High Performance Computing and Communications </div>  <div>======================================================================<BR></div>  <div>SCOPE</div>  <div>Peer-to-peer (P2P) and Web Services (WS) technologies are currently attracting enormous media attention. <BR>In P2P systems a very large number
 of autonomous computing nodes (the peers) pool together their resources <BR>and rely on each other for data and services. We wish to organize a workshop to address the need for P2P <BR>technologies and platforms that support self-organization of WS, semantic WS, load balance, routing, etc.<BR>The P2PWS workshop provides a forum for researchers and practitioners from academic, industrial, public <BR>and government sectors, to share their latest innovations on the P2P computing, Web services technologies <BR>and applications. The workshop will be advertised through mailing lists interested in P2P and WS fields in <BR>order to ensure that a wide range of authors will participate. <BR>&nbsp;<BR>Areas of interest include, but not limited to: </div>  <div>* Services composition in P2P Web services networks</div>  <div>* Data placement and query answering in P2P systems</div>  <div>* Transaction management for P2P Web services</div>  <div>* Autonomous peers and semantic Web</div>
  <div>* Self-organization and emergent behavior in P2P systems</div>  <div>* Resource allocation in P2P systems and Web services</div>  <div>* Scalability, coordination, robustness and adaptability in P2P and Web services</div>  <div>* Autonomic Web Services in P2P systems</div>  <div><BR>Important Dates</div>  <div>&nbsp;</div>  <div>Papers Early Registration (abstract): April 20, 2008</div>  <div>Papers Submission (No extend): May 20, 2008</div>  <div>Author Notification: June 10, 2008</div>  <div>Final Manuscript submission: July 1, 2008</div>  <div>Workshop: September 25-27, 2008</div>  <div>&nbsp;</div>  <div>General Inquires Submission</div>  <div>&nbsp;</div>  <div>For more details and update information, please visit <BR><A href="http://faculty.kfupm.edu.sa/ICS/helmy/P2PWS08/index.htm">http://faculty.kfupm.edu.sa/ICS/helmy/P2PWS08/index.htm</A></div>  <div><BR>Submit your paper through email
 to:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Khaled Ragab , General Chair<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Tarek Helmy, Co-chair</div>  <div><BR>Submission Guidelines</div>  <div>Papers in P2P and Web Services related areas are solicited. Submissions must include an abstract, five to <BR>ten keywords, the e-mail address of the corresponding author and should not exceed 15 pages, including <BR>tables and figures. All paper submissions must represent original and unpublished work. Submission of a <BR>paper should be regarded as an undertaking that, should the paper be accepted, at least one of the authors <BR>will register for the conference and present the work. Submissions will be conducted electronically on the <BR>conference website</div>  <div>ELECTRONIC SUBMISSION</div>  <div>Prepare your paper with free
 styles not more than 15 pages in PDF file. Submit your paper(s) by email to <BR>workshop's General Chair Chair or Co-chair. <BR>Accepted papers will be published in the workshop proceedings by the IEEE Computer Society Press. <BR>In addition, there is a plan to invite authors to submit extended versions of their papers for a special issue <BR>of a respective journal. </div>  <div>General Chair</div>  <div>Khaled Ragab (KFU, Saudi Arabia)</div>  <div>Co-chair</div>  <div>Tarek Helmy (KFUPM, Saudi Arabia)</div>  <div><BR>International Program Committee </div>  <div>Aboul Ella Hassanien (Kuwait Univ.</div>  <div>Asrar U. Haquie (KFU , Saudi Arabia)</div>  <div>Farag Ezidin (KFUPM, Saudi Arabia)</div>  <div>Jarallah Alghamdi (KFUPM, Saudi Arabia)</div>  <div>Ibrahim Imam (AAST, Egypt)</div>  <div>Iyad Rahwan (British Univ., UAE)</div>  <div>Jeffery Bradshaw (IHMC, USA)</div>  <div>Jianhua Ma&nbsp; (Hosei Univ., Japan)</div>  <div>Khaled Shaalan (British Univ., UAE)</div> 
 <div>Laurence T. Yang (St. Francis Xavier Univ., Canada)</div>  <div>M. Amamiya (Kyushu Univ., Japan)</div>  <div>Moataz Ahmed (LEROS, USA)</div>  <div>Mohamed Al-Naser (KFUPM, Saudi Arabia)</div>  <div>M. Zahrani KFU, Saudi Arabia</div>  <div>R. Kowalczyk (Swinburne Uni, Australia)</div>  <div>Salaheldin Adam (KFUPM, Saudi Arabia)</div>  <div>Sameh El-Ansary (Swedish Institute, Sweden)</div>  <div>Satoshi Amamiya (Kyushu Univ., Japan)</div>  <div>Yasser Kotb (Ain Shams Univ, Egypt<BR></div><p>&#32;

      <hr size=1>You rock. That's why Blockbuster's offering you <a href="http://us.rd.yahoo.com/evt=47523/*http://tc.deals.yahoo.com/tc/blockbuster/text5.com">one month of Blockbuster Total Access</a>, No Cost.
--0-581564740-1207462460=:6600--

--===============1296073993==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1296073993==--


From p2psip-bounces@ietf.org  Sun Apr  6 14:02:26 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7E6033A6C09;
	Sun,  6 Apr 2008 14:02:26 -0700 (PDT)
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 E65A33A6C09;
	Sun,  6 Apr 2008 14:02:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, 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 hmsa0ego3e0e; Sun,  6 Apr 2008 14:02:23 -0700 (PDT)
Received: from twilight.cs.hut.fi (twilight.cs.hut.fi [130.233.40.5])
	by core3.amsl.com (Postfix) with ESMTP id 170533A68E7;
	Sun,  6 Apr 2008 14:02:23 -0700 (PDT)
Received: by twilight.cs.hut.fi (Postfix, from userid 60001)
	id A88392FD5; Mon,  7 Apr 2008 00:02:33 +0300 (EEST)
X-Spam-Niksula: No
Received: from kekkonen (kekkonen.cs.hut.fi [130.233.41.50])
	by twilight.cs.hut.fi (Postfix) with ESMTP id 98B232EA6;
	Mon,  7 Apr 2008 00:02:31 +0300 (EEST)
Date: Mon, 7 Apr 2008 00:02:31 +0300 (EEST)
From: Miika Komu <miika@iki.fi>
X-X-Sender: mkomu@kekkonen.cs.hut.fi
To: Henry Sinnreich <hsinnrei@adobe.com>
In-Reply-To: <24CCCC428EFEA2469BF046DB3C7A8D22019E0954@namail5.corp.adobe.com>
Message-ID: <Pine.SOL.4.64.0804031059380.12341@kekkonen.cs.hut.fi>
References: <47F3642C.8050909@ericsson.com>
	<24CCCC428EFEA2469BF046DB3C7A8D22019E0954@namail5.corp.adobe.com>
MIME-Version: 1.0
Cc: rai-ads@tools.ietf.org, P2PSIP Mailing List <p2psip@ietf.org>,
	internet-ads@tools.ietf.org, mmusic-chairs@tools.ietf.org,
	David Ward <dward@cisco.com>, mmusic <mmusic@ietf.org>
Subject: Re: [P2PSIP] [MMUSIC] HIP NAT Traversal using NICE
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

On Wed, 2 Apr 2008, Henry Sinnreich wrote:

Hi Henry,

NAT traversal implementations are work in progress at least for the 
following projects:

http://www.hip4inter.net/
http://www.openhip.org/
http://www.infrahip.net/

> Gonzalo,
>
> I would be interested in an updated evaluation from you on the practical
> (near term) potential of using HIP NAT traversal for P2PSIP.
> There was even talk of running code.
>
> Can you (and anyone else) share a few key thoughts, references and links
> to running code?
>
> Henry
>
> -----Original Message-----
> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
> Of Gonzalo Camarillo
> Sent: Wednesday, April 02, 2008 5:47 AM
> To: mmusic
> Cc: internet-ads@tools.ietf.org; mmusic-chairs@tools.ietf.org;
> rai-ads@tools.ietf.org; David Ward
> Subject: [MMUSIC] HIP NAT Traversal using NICE
>
> Folks involved in the MMUSIC WG,
>
> the HIP WG is developing a NAT traversal solution that is based on NICE:
>
> http://www.ietf.org/internet-drafts/draft-ietf-hip-nat-traversal-03.txt
>
> http://www.ietf.org/internet-drafts/draft-rosenberg-mmusic-ice-nonsip-00
> .txt
>
> This means that we depend on the NICE draft to have a working NAT
> traversal solution for HIP. However, from the presentation of this draft
>
> in the last IETF, it is not clear to us whether or not the MMUSIC WG is
> going to work on this draft.
>
> The HIP WG would like to encourage the MMUSIC WG to work on this
> specification, since we need it. If the MMUSIC WG decides not to do so,
> the HIP WG will most likely copy/paste the contents of the NICE draft in
>
> our NAT traversal spec. However, we believe that having a stand-alone
> NICE specification can be useful for protocols other than HIP that will
> decide to use ICE for NAT traversal in the future.
>
> A clarification of the status of this work in the MMUSIC WG would be
> appreciated.
>
> Thanks,
>
> Gonzalo
> HIP WG co-chair
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www.ietf.org/mailman/listinfo/p2psip
>

-- 
Miika Komu                                       http://www.iki.fi/miika/
_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www.ietf.org/mailman/listinfo/p2psip


From p2psip-bounces@ietf.org  Mon Apr  7 00:08:21 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2A08328C2CC;
	Mon,  7 Apr 2008 00:08:21 -0700 (PDT)
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 E768B28C2BE;
	Mon,  7 Apr 2008 00:08:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 MsrR2su0IOzQ; Mon,  7 Apr 2008 00:08:18 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 7594928C2BB;
	Mon,  7 Apr 2008 00:08:18 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	8C59D2070A; Mon,  7 Apr 2008 09:08:29 +0200 (CEST)
X-AuditID: c1b4fb3c-ab896bb00000193b-14-47f9c86dfb6a
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	6B9BF20760; Mon,  7 Apr 2008 09:08:29 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 7 Apr 2008 09:08:29 +0200
Received: from [131.160.37.21] ([131.160.37.21]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 7 Apr 2008 09:08:28 +0200
Message-ID: <47F9C86C.6030106@ericsson.com>
Date: Mon, 07 Apr 2008 10:08:28 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Miika Komu <miika@iki.fi>
References: <47F3642C.8050909@ericsson.com>
	<24CCCC428EFEA2469BF046DB3C7A8D22019E0954@namail5.corp.adobe.com>
	<Pine.SOL.4.64.0804031059380.12341@kekkonen.cs.hut.fi>
In-Reply-To: <Pine.SOL.4.64.0804031059380.12341@kekkonen.cs.hut.fi>
X-OriginalArrivalTime: 07 Apr 2008 07:08:28.0978 (UTC)
	FILETIME=[2E473920:01C8987E]
X-Brightmail-Tracker: AAAAAA==
Cc: rai-ads@tools.ietf.org, mmusic <mmusic@ietf.org>,
	internet-ads@tools.ietf.org, mmusic-chairs@tools.ietf.org,
	Henry Sinnreich <hsinnrei@adobe.com>, David Ward <dward@cisco.com>,
	P2PSIP Mailing List <p2psip@ietf.org>
Subject: Re: [P2PSIP] [MMUSIC] HIP NAT Traversal using NICE
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

Hi,

yes, as Miika points out, there are several groups working on it. We 
should be doing the first interop tests between different 
implementations shortly.

Cheers,

Gonzalo


Miika Komu wrote:
> On Wed, 2 Apr 2008, Henry Sinnreich wrote:
> 
> Hi Henry,
> 
> NAT traversal implementations are work in progress at least for the 
> following projects:
> 
> http://www.hip4inter.net/
> http://www.openhip.org/
> http://www.infrahip.net/
> 
>> Gonzalo,
>>
>> I would be interested in an updated evaluation from you on the practical
>> (near term) potential of using HIP NAT traversal for P2PSIP.
>> There was even talk of running code.
>>
>> Can you (and anyone else) share a few key thoughts, references and links
>> to running code?
>>
>> Henry
>>
>> -----Original Message-----
>> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
>> Of Gonzalo Camarillo
>> Sent: Wednesday, April 02, 2008 5:47 AM
>> To: mmusic
>> Cc: internet-ads@tools.ietf.org; mmusic-chairs@tools.ietf.org;
>> rai-ads@tools.ietf.org; David Ward
>> Subject: [MMUSIC] HIP NAT Traversal using NICE
>>
>> Folks involved in the MMUSIC WG,
>>
>> the HIP WG is developing a NAT traversal solution that is based on NICE:
>>
>> http://www.ietf.org/internet-drafts/draft-ietf-hip-nat-traversal-03.txt
>>
>> http://www.ietf.org/internet-drafts/draft-rosenberg-mmusic-ice-nonsip-00
>> .txt
>>
>> This means that we depend on the NICE draft to have a working NAT
>> traversal solution for HIP. However, from the presentation of this draft
>>
>> in the last IETF, it is not clear to us whether or not the MMUSIC WG is
>> going to work on this draft.
>>
>> The HIP WG would like to encourage the MMUSIC WG to work on this
>> specification, since we need it. If the MMUSIC WG decides not to do so,
>> the HIP WG will most likely copy/paste the contents of the NICE draft in
>>
>> our NAT traversal spec. However, we believe that having a stand-alone
>> NICE specification can be useful for protocols other than HIP that will
>> decide to use ICE for NAT traversal in the future.
>>
>> A clarification of the status of this work in the MMUSIC WG would be
>> appreciated.
>>
>> Thanks,
>>
>> Gonzalo
>> HIP WG co-chair
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>> _______________________________________________
>> P2PSIP mailing list
>> P2PSIP@ietf.org
>> https://www.ietf.org/mailman/listinfo/p2psip
>>
> 

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


From p2psip-bounces@ietf.org  Mon Apr  7 06:18:19 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C905B3A6DC9;
	Mon,  7 Apr 2008 06:18:19 -0700 (PDT)
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 403063A6DC9;
	Mon,  7 Apr 2008 06:18:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.545
X-Spam-Level: 
X-Spam-Status: No, score=-4.545 tagged_above=-999 required=5 tests=[AWL=2.054, 
	BAYES_00=-2.599, 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 yo9HhpvNqMoQ; Mon,  7 Apr 2008 06:18:18 -0700 (PDT)
Received: from exprod6og102.obsmtp.com (exprod6og102.obsmtp.com [64.18.1.183])
	by core3.amsl.com (Postfix) with ESMTP id 76A523A6C5E;
	Mon,  7 Apr 2008 06:18:06 -0700 (PDT)
Received: from source ([192.150.11.134]) by exprod6ob102.postini.com
	([64.18.5.12]) with SMTP; Mon, 07 Apr 2008 06:18:19 PDT
Received: from inner-relay-3.eur.adobe.com ([192.150.8.236])
	by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	m37DFPG3003088; Mon, 7 Apr 2008 06:15:25 -0700 (PDT)
Received: from apacmail.pac.adobe.com (apacmail.pac.adobe.com [130.248.36.99])
	by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id
	m37DI9qJ019449; Mon, 7 Apr 2008 06:18:10 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by
	apacmail.pac.adobe.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 7 Apr 2008 22:18:08 +0900
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 7 Apr 2008 06:13:27 -0700
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D22019E0995@namail5.corp.adobe.com>
In-Reply-To: <47F9C86C.6030106@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] [MMUSIC] HIP NAT Traversal using NICE
Thread-Index: AciYfjDBCo4ZlKffR+OObnhzmpoqwwAMqW6w
References: <47F3642C.8050909@ericsson.com>
	<24CCCC428EFEA2469BF046DB3C7A8D22019E0954@namail5.corp.adobe.com>
	<Pine.SOL.4.64.0804031059380.12341@kekkonen.cs.hut.fi>
	<47F9C86C.6030106@ericsson.com>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>,
	"Miika Komu" <miika@iki.fi>
X-OriginalArrivalTime: 07 Apr 2008 13:18:08.0109 (UTC)
	FILETIME=[D21209D0:01C898B1]
Cc: rai-ads@tools.ietf.org, mmusic <mmusic@ietf.org>,
	internet-ads@tools.ietf.org, mmusic-chairs@tools.ietf.org,
	David Ward <dward@cisco.com>, P2PSIP Mailing List <p2psip@ietf.org>
Subject: Re: [P2PSIP] [MMUSIC] HIP NAT Traversal using NICE
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

Thanks Miika and Gonzalo!

Can you keep us advised of the interoperability work?
This will have IMO very beneficial effects for the whole industry.

Henry 

-----Original Message-----
From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com] 
Sent: Monday, April 07, 2008 2:08 AM
To: Miika Komu
Cc: Henry Sinnreich; mmusic; P2PSIP Mailing List;
internet-ads@tools.ietf.org; mmusic-chairs@tools.ietf.org;
rai-ads@tools.ietf.org; David Ward
Subject: Re: [P2PSIP] [MMUSIC] HIP NAT Traversal using NICE

Hi,

yes, as Miika points out, there are several groups working on it. We 
should be doing the first interop tests between different 
implementations shortly.

Cheers,

Gonzalo


Miika Komu wrote:
> On Wed, 2 Apr 2008, Henry Sinnreich wrote:
> 
> Hi Henry,
> 
> NAT traversal implementations are work in progress at least for the 
> following projects:
> 
> http://www.hip4inter.net/
> http://www.openhip.org/
> http://www.infrahip.net/
> 
>> Gonzalo,
>>
>> I would be interested in an updated evaluation from you on the
practical
>> (near term) potential of using HIP NAT traversal for P2PSIP.
>> There was even talk of running code.
>>
>> Can you (and anyone else) share a few key thoughts, references and
links
>> to running code?
>>
>> Henry
>>
>> -----Original Message-----
>> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On
Behalf
>> Of Gonzalo Camarillo
>> Sent: Wednesday, April 02, 2008 5:47 AM
>> To: mmusic
>> Cc: internet-ads@tools.ietf.org; mmusic-chairs@tools.ietf.org;
>> rai-ads@tools.ietf.org; David Ward
>> Subject: [MMUSIC] HIP NAT Traversal using NICE
>>
>> Folks involved in the MMUSIC WG,
>>
>> the HIP WG is developing a NAT traversal solution that is based on
NICE:
>>
>>
http://www.ietf.org/internet-drafts/draft-ietf-hip-nat-traversal-03.txt
>>
>>
http://www.ietf.org/internet-drafts/draft-rosenberg-mmusic-ice-nonsip-00
>> .txt
>>
>> This means that we depend on the NICE draft to have a working NAT
>> traversal solution for HIP. However, from the presentation of this
draft
>>
>> in the last IETF, it is not clear to us whether or not the MMUSIC WG
is
>> going to work on this draft.
>>
>> The HIP WG would like to encourage the MMUSIC WG to work on this
>> specification, since we need it. If the MMUSIC WG decides not to do
so,
>> the HIP WG will most likely copy/paste the contents of the NICE draft
in
>>
>> our NAT traversal spec. However, we believe that having a stand-alone
>> NICE specification can be useful for protocols other than HIP that
will
>> decide to use ICE for NAT traversal in the future.
>>
>> A clarification of the status of this work in the MMUSIC WG would be
>> appreciated.
>>
>> Thanks,
>>
>> Gonzalo
>> HIP WG co-chair
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>> _______________________________________________
>> P2PSIP mailing list
>> P2PSIP@ietf.org
>> https://www.ietf.org/mailman/listinfo/p2psip
>>
> 

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


From p2psip-bounces@ietf.org  Tue Apr  8 08:27:49 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5BF453A69F2;
	Tue,  8 Apr 2008 08:27:49 -0700 (PDT)
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 CDBB83A69F2
	for <p2psip@core3.amsl.com>; Tue,  8 Apr 2008 08:27:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.799
X-Spam-Level: 
X-Spam-Status: No, score=-5.799 tagged_above=-999 required=5 tests=[AWL=0.800, 
	BAYES_00=-2.599, 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 piLJQmLuaiam for <p2psip@core3.amsl.com>;
	Tue,  8 Apr 2008 08:27:46 -0700 (PDT)
Received: from mxoutps1.us.army.mil (mxoutps1.us.army.mil [143.69.250.38])
	by core3.amsl.com (Postfix) with ESMTP id 609433A68D7
	for <p2psip@ietf.org>; Tue,  8 Apr 2008 08:27:46 -0700 (PDT)
DomainKey-Signature: s=ako; d=us.army.mil; c=nofws; q=dns;
	h=From:X-AKO:X-IronPort-AV:Received:Received:To:Cc:
	Message-ID:Date:X-Mailer:MIME-Version:Content-Language:
	Subject:X-Accept-Language:Priority:In-Reply-To:References:
	Content-Type:Content-Disposition:
	Content-Transfer-Encoding;
	b=uVIYpq+XaF5N4r06Q8DVW3EXyuD/+SErxU07M6RhqpBQ/bnZ7N6GLggi
	TbvZAIV0IQLM3fZBhL1SdxT4DYBOFw==;
From: "Roy, Radhika R Dr CTR USA USAMC" <radhika.r.roy@us.army.mil>
X-AKO: 141237691:10.224.36.65:08 Apr 2008 15:27:58 +0000:$Webmail:None
X-IronPort-AV: E=Sophos;i="4.25,624,1199664000"; d="scan'208";a="141237691"
Received: from mail5.int.ps1.us.army.mil (HELO us.army.mil) ([10.224.36.65])
	by mxoutps1.us.army.mil with ESMTP; 08 Apr 2008 15:27:27 +0000
Received: from [10.240.32.176] (Forwarded-For: 134.80.13.193,
	[10.240.32.176]) by mail5.int.ps1.us.army.mil (mshttpd); Tue, 08 Apr
	2008 11:27:26 -0400
To: FORTAINE Guillaume <gui.fortaine@orange.fr>
Message-ID: <e17ffe9c32840.47fb569e@us.army.mil>
Date: Tue, 08 Apr 2008 11:27:26 -0400
X-Mailer: Sun Java(tm) System Messenger Express 6.2-9.04 (built Jun 11
 2007)
MIME-Version: 1.0
Content-Language: en
X-Accept-Language: en
Priority: normal
In-Reply-To: <47F7BE8E.7040100@orange.fr>
References: <47F00353.8090807@orange.fr>
	<ddb0a6cc2778f.47f0ad4f@us.army.mil> <47F7BE8E.7040100@orange.fr>
Content-Disposition: inline
Cc: p2psip@ietf.org, siwu@hrz.tu-chemnitz.de, dbryan@p2psip.org,
	axel@open-mesh.net, preston.marshall@darpa.mil,
	steve.stewart@navy.mil, lindner_marek@yahoo.de
Subject: Re: [P2PSIP] P2P SIP - Real-time Multimedia Services
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

Hi, Guillaume:

The technical points that you have made are being investigated since the inception of the MANET networking. Probably, nearly two decades have been passed in MANET research and some of the commercial prototypes of MANETs have been implemented and their results are being published in various literatures.

My personal understanding is the, encouraged by experiences of prototype implementations of MANETs, their large-scale implementations are being followed between now and 2015 especially for military networks. And you are right, standards also need to follow hand-by-hand to obtain the fruits of MANETs in the commercial large-scale networks. In fact, it is challenges of the day going forward.

The encouraging news is that MANET WG and AUTOCONFIG WG are developing the standards for MANETs in the network layer/IP layer. In directly, P2PSIP WG is also working for P2P SIP application that may be the first step which can be also be used for MANETs.

However, more standard works also need to be done as follows:

1. Implications of call signaling messages for call setup/teardown/re-establishment as mobile users will move with almost randomly unpredictable speed and direction with constantly variable topology and, thereby, the needs for extensions of P2PSIP standards.

2. In MANETs, there is no such "guaranteed QOS," and thereby, new QOS standards such as "soft" QOS has been to be created. For example, IETF research group is working on "delay tolerant networking" etc.

3. The congest ions/interferences in MANETs will be pushed back to the application layer (e.g., Navy's SBIR). It means that dynamic encoding of bandwidth-intensive application like video and others with a given session.

4. Items 1, 2, and 3 indicate that there may not anything that is called layer-agnostic. That is, cross-layer mechanisms will be a part of the usual MANET networking.

I do not want make the list long. The above items 1, 2, 3, and 4 reveal the fact that the days for the traditional networking are over for MANET networking. It also implies that an enormous amount of STANDARD works need to be done for full implementations of MANETs.

Now to do the standard works you may need to follow as explained in my earlier email:

* Wirte some drafts what works on standards need to be done related to MANETs

* Suggest for extensions of P2PSIP, MANET, AUTOCONFIG, and NSIS WG for may particular standards that may be applicable for MANETs

* If no existing WGs are suitable (e.g. X-layer) for any MANET topics, suggest to form new WGs writing some drafts explaining the needs and IETF management will be, I think, kind enough to provide chances for BOFs.

Best regards,
Radhika

----- Original Message -----
From: FORTAINE Guillaume 
Date: Saturday, April 5, 2008 14:01
Subject: Re: [P2PSIP] P2P SIP - Real-time Multimedia Services
To: "Roy, Radhika R Dr CTR USA USAMC" 
Cc: p2psip@ietf.org, dbryan@p2psip.org, preston.marshall@darpa.mil, lindner_marek@yahoo.de, axel@open-mesh.net, siwu@hrz.tu-chemnitz.de, steve.stewart@navy.mil

> Dear Mister Roy,
> 
> You are Excellence and it's definitely an honor for me to be in 
> contact 
> with You Today
> 
> There are various ways for P2P Networking :
> 
> -US Army :
> 
> DirecNet Portal 
> 
> 
> -DARPA :
> 
> Home - *Delay Tolerant Networking Research Group* 
> 
> 
> -Open Source :
> 
> 
> 
> 
> Layer-5 :
> 
> *Real*-*time Multimedia Services Using Hybrid P2P SIP* 
> 
> 
> *Real-time Multimedia Services Using Hybrid P2P SIP*
> Mo, Yijun; Wang, Fei; Huang, Benxiong; Luo, Fu
> Communications and Information Technologies, 2006. ISCIT apos;06. 
> International Symposium on
> Volume , Issue , Oct. 18 2006-Sept. 20 2006 Page(s):157 - 161
> Digital Object Identifier 10.1109/ISCIT.2006.339907
> *Summary:*SIP becomes one most poplar protocol in real-time 
> multimedia 
> services, but the central server becomes the single point of 
> failure, 
> While P2P becomes "killing level application" in Internet because 
> of its 
> robust and low cost. Combing P2P and SIP, we propose hybrid P2P 
> SIP 
> framework in the paper, and describe several important procedures, 
> such 
> as node registration, user registration and call procedure. But 
> current 
> P2P searching and routing arithmetic does not meet the requirement 
> for 
> low time delay in real-time multimedia applications. Then, we 
> present a 
> novel SOMCO arithmetic, which decreases the call delay and media 
> forwarding delay to some extend. Simulation verifies that SOMCO is 
> practical to support real-time multimedia services
> 
> 
> 
> 
> 
> 
> 
> I look forward to Your Answer,
> 
> Best Regards,
> 
> 
> 
> Roy, Radhika R Dr CTR USA USAMC wrote:
> > Hi, Fortain:
> >
> > I think that you can start working for all those QOS mechanisms 
> within the framework of P2PSIP. Let me explain as follows:
> >
> > 1. Mobile Ad Hoc networks need P2P networking. As result, the 
> applications also need to be P2P. P2PSIP WG is working for 
> facilitating in building of P2PSIP applications.
> >
> > 2. The ad hoc mobility part is primarily related to the topology 
> control of MANETs and MANET WG and AUTOCONFIG WG are working in 
> the layers 2-through 3/4. The QOS-mechanisms of the network layer 
> are being taken care of by those WGs.
> >
> > 3. The application layer QOS for SIP in peer-to-peer mode can 
> best be working within the framework of P2PSIP WG because, I 
> believe, you do not need to do anything explicitly related to 
> mobility assuming that the lower MAC and network layer of MANET 
> are being taken care of by those WGs (e.g. topology control, 
> routing, QOS) and we can plug those things from the application 
> layer to the lower network to work cooperatively.
> >
> > 4. It is true that we may have to do something in the P2P 
> application layer like P2PSIP for QOS as well as for taking care 
> of the ad hoc mobility, it is still not well understood by all of 
> us. Once the P2PSIP signaling protocol is taken care of, we will 
> gain more experiences what we have to do next.
> >
> > However, if you suggest what specific problems related to QOS 
> you want to address in the P2PSIP application Layer for solving 
> the performance problems, we can then look into those taking 
> Navy's QOS requirements for MANET networks.
> >
> > I appreciate for bringing the interesting real problems in the 
> P2PSIP WG mailing list.
> >
> > Best regards,
> > Radhika
> > 
> 
> 
> 
_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www.ietf.org/mailman/listinfo/p2psip


From p2psip-bounces@ietf.org  Fri Apr 11 07:52:02 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CD11F3A6E9B;
	Fri, 11 Apr 2008 07:52:02 -0700 (PDT)
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 98F793A6E0D
	for <p2psip@core3.amsl.com>; Fri, 11 Apr 2008 07:52:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.67
X-Spam-Level: ***
X-Spam-Status: No, score=3.67 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1,
	RELAY_IS_220=2.118]
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 eTuqoVF7yWqW for <p2psip@core3.amsl.com>;
	Fri, 11 Apr 2008 07:52:00 -0700 (PDT)
Received: from dcn.ssu.ac.kr (unknown [220.70.2.104])
	by core3.amsl.com (Postfix) with ESMTP id 920E03A6E7A
	for <p2psip@ietf.org>; Fri, 11 Apr 2008 07:52:00 -0700 (PDT)
Received: from softgear ([220.149.84.220])
	by dcn.ssu.ac.kr (8.12.8/8.12.8) with ESMTP id m3BEolVs016760
	for <p2psip@ietf.org>; Fri, 11 Apr 2008 23:50:47 +0900
From: "Softgear Ko" <softgear@dcn.ssu.ac.kr>
To: <p2psip@ietf.org>
References: <dce1a9600803270245w6d0a1ad1s1a18dd619ec25f36@mail.gmail.com>
Date: Fri, 11 Apr 2008 23:52:22 +0900
Message-ID: <000d01c89be3$a5f70550$dc5495dc@softgear>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
thread-index: AciP7xybLvF4DSlyR0O1RXT3hWf98AL8jZPQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <dce1a9600803270245w6d0a1ad1s1a18dd619ec25f36@mail.gmail.com>
Subject: Re: [P2PSIP] List of implementations
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

Hello all,
I suggest one very carefully.
I think reload is one of best candidate as WG peer protocol. But, before we
accept reload as WG peer protocol draft, can we push Mr. Bryan to open their
implementation?
If reload is opened, we can confirm the peer protocol and find more
practical issues. It can be also very helpful to deploy our protocols to
real world quickly.

- Softgear Ko
________________________________________
From: p2psip-bounces@ietf.org [mailto:p2psip-bounces@ietf.org] On Behalf Of
Simone Cirani
Sent: Thursday, March 27, 2008 6:45 PM
To: p2psip@ietf.org
Subject: Re: [P2PSIP] List of implementations

Hi everybody,
I would like to advertise an available open source implementation that came
along with the draft that Luca Veltri and I submitted
on October 25th, 2007 [draft-cirani-p2psip-dsip-dhtkademlia-00].
We have provided a dSIP implementation of both Chord and Kademlia, 
available from <http://www.mjsip.org/projects/p2psip/p2psip_dsip_071025.zip>
based on the MjSip SIP stack [http://www.mjsip.org].

Even though we understand that the WG is moving towards another direction
than dSIP, we thought that it would make sense to advertise it anyway.

Regards, 
Simone Cirani 

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


From p2psip-bounces@ietf.org  Fri Apr 11 08:36:45 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DF14A3A6E8F;
	Fri, 11 Apr 2008 08:36:45 -0700 (PDT)
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 B01053A6B1A
	for <p2psip@core3.amsl.com>; Fri, 11 Apr 2008 08:36:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level: 
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
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 HFkeeBo7DNY8 for <p2psip@core3.amsl.com>;
	Fri, 11 Apr 2008 08:36:44 -0700 (PDT)
Received: from maile.telecomitalia.it (maile.telecomitalia.it [156.54.233.31])
	by core3.amsl.com (Postfix) with ESMTP id 77FCF3A6C07
	for <p2psip@ietf.org>; Fri, 11 Apr 2008 08:36:43 -0700 (PDT)
Received: from ptpxch008ba020.idc.cww.telecomitalia.it ([156.54.240.51]) by
	maile.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 11 Apr 2008 17:37:05 +0200
Received: from ptpxch005ba020.idc.cww.telecomitalia.it ([156.54.240.44]) by
	ptpxch008ba020.idc.cww.telecomitalia.it with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 11 Apr 2008 17:37:04 +0200
Received: from [10.229.8.53] ([10.229.8.53]) by
	ptpxch005ba020.idc.cww.telecomitalia.it over TLS secured
	channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 11 Apr 2008 17:37:04 +0200
Message-ID: <47FF8598.60302@telecomitalia.it>
Date: Fri, 11 Apr 2008 17:36:56 +0200
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla-Thunderbird 2.0.0.12 (X11/20080406)
MIME-Version: 1.0
To: Softgear Ko <softgear@dcn.ssu.ac.kr>
References: <dce1a9600803270245w6d0a1ad1s1a18dd619ec25f36@mail.gmail.com>
	<000d01c89be3$a5f70550$dc5495dc@softgear>
In-Reply-To: <000d01c89be3$a5f70550$dc5495dc@softgear>
X-Enigmail-Version: 0.95.0
X-OriginalArrivalTime: 11 Apr 2008 15:37:04.0361 (UTC)
	FILETIME=[E4842590:01C89BE9]
Cc: p2psip@ietf.org
Subject: Re: [P2PSIP] List of implementations
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1710523845=="
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--===============1710523845==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms070203080404060403010000"

This is a cryptographically signed message in MIME format.

--------------ms070203080404060403010000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Softgear Ko wrote:
> I think reload is one of best candidate as WG peer protocol. But, before we
> accept reload as WG peer protocol draft, can we push Mr. Bryan to open their
> implementation?

No, we can't.  And we don't want in any way to make a choice based on a
company's business model.

> If reload is opened, we can confirm the peer protocol and find more
> practical issues. It can be also very helpful to deploy our protocols to
> real world quickly.

I agree.  But if people consider it the best candidate even without an
open implementation (I do consider it the best candidate, despite being
the author of an alternative proposal), there's nothing wrong with the
group adopting it.

-- 
Ciao,
Enrico

--------------ms070203080404060403010000
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJwTCC
AzswggKkoAMCAQICEB5MAA0NQwlT3ufR7UBbG7gwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA4MDMyOTEzMDExOVoX
DTA5MDMyOTEzMDExOVowejEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEuMCwG
CSqGSIb3DQEJARYfZW5yaWNvLm1hcm9jY29AdGVsZWNvbWl0YWxpYS5pdDEnMCUGCSqGSIb3
DQEJARYYZW5yaWNvLm1hcm9jY29AZ21haWwuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAscB8QkU/epro6Z59GpYTko0wKy8RkilXiec5xWsN2DuaGvHSz4IeWJlPiP7z
UnHHF5c/51wH6PzFyhq+OZjTP50NZLyh5VBfOuyjf6Hjh1LTYcF1WnggMZoaH/ktb6dMCHvO
oYCzR0J1ZtfBGmz7XuHUDiuTnbo0A16F685nBAkBh4HYLIQxqyORJ+snLSmiA7xLX1L5Gy+t
W950fMs9Z3SpSQM37AMSS2S2ooZB9cotvJAgmauWzclaS0SWzKMeHg3sjdI2tKxuf3eBb0v1
+XnOjz1YLyzmJjSrDwdwUarSjx8EhD9kBHdYSWxBCEY78X26J2y3N61DoZHYwYyNowIDAQAB
o1YwVDBEBgNVHREEPTA7gR9lbnJpY28ubWFyb2Njb0B0ZWxlY29taXRhbGlhLml0gRhlbnJp
Y28ubWFyb2Njb0BnbWFpbC5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOBgQCn
ZkvJXyvhUJf6wectMCJ83wWcBrWW6GbDZYzCwErd8X78ZIxGWKphMQ/iAAb0tuW+VdrAZpih
a7yRIE0DMkQiKNR9v1dszgIEVO+7ebe4l02T537gZAeDWCgiCKwRRemFHM1G7lWtKt6tHrfe
+BCmVslPGk2aphSk2KBAFbgCiTCCAzswggKkoAMCAQICEB5MAA0NQwlT3ufR7UBbG7gwDQYJ
KoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5n
IChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5n
IENBMB4XDTA4MDMyOTEzMDExOVoXDTA5MDMyOTEzMDExOVowejEfMB0GA1UEAxMWVGhhd3Rl
IEZyZWVtYWlsIE1lbWJlcjEuMCwGCSqGSIb3DQEJARYfZW5yaWNvLm1hcm9jY29AdGVsZWNv
bWl0YWxpYS5pdDEnMCUGCSqGSIb3DQEJARYYZW5yaWNvLm1hcm9jY29AZ21haWwuY29tMIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAscB8QkU/epro6Z59GpYTko0wKy8RkilX
iec5xWsN2DuaGvHSz4IeWJlPiP7zUnHHF5c/51wH6PzFyhq+OZjTP50NZLyh5VBfOuyjf6Hj
h1LTYcF1WnggMZoaH/ktb6dMCHvOoYCzR0J1ZtfBGmz7XuHUDiuTnbo0A16F685nBAkBh4HY
LIQxqyORJ+snLSmiA7xLX1L5Gy+tW950fMs9Z3SpSQM37AMSS2S2ooZB9cotvJAgmauWzcla
S0SWzKMeHg3sjdI2tKxuf3eBb0v1+XnOjz1YLyzmJjSrDwdwUarSjx8EhD9kBHdYSWxBCEY7
8X26J2y3N61DoZHYwYyNowIDAQABo1YwVDBEBgNVHREEPTA7gR9lbnJpY28ubWFyb2Njb0B0
ZWxlY29taXRhbGlhLml0gRhlbnJpY28ubWFyb2Njb0BnbWFpbC5jb20wDAYDVR0TAQH/BAIw
ADANBgkqhkiG9w0BAQUFAAOBgQCnZkvJXyvhUJf6wectMCJ83wWcBrWW6GbDZYzCwErd8X78
ZIxGWKphMQ/iAAb0tuW+VdrAZpiha7yRIE0DMkQiKNR9v1dszgIEVO+7ebe4l02T537gZAeD
WCgiCKwRRemFHM1G7lWtKt6tHrfe+BCmVslPGk2aphSk2KBAFbgCiTCCAz8wggKooAMCAQIC
AQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENh
cGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAm
BgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0
ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1h
aWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNV
BAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQD
EyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEF
AAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B
1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79A
gAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8E
CDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3
dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEa
MBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7M
DaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUa
C4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk1
3iSx0x1G/11fZU8xggNxMIIDbQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3
dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJl
ZW1haWwgSXNzdWluZyBDQQIQHkwADQ1DCVPe59HtQFsbuDAJBgUrDgMCGgUAoIIB0DAYBgkq
hkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wODA0MTExNTM2NTZaMCMG
CSqGSIb3DQEJBDEWBBQ8kr5FR7mS3XxvhjlE8khdPUti2jBfBgkqhkiG9w0BCQ8xUjBQMAsG
CWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAw
BwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMC
WkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1Ro
YXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhAeTAANDUMJU97n0e1AWxu4MIGH
BgsqhkiG9w0BCRACCzF4oHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25z
dWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJ
c3N1aW5nIENBAhAeTAANDUMJU97n0e1AWxu4MA0GCSqGSIb3DQEBAQUABIIBAAA+dtlFt1q8
MSWt16+ays7L4w8n11XO3mjyr5oLQsLGQDl6z1FG+QWwqGZMiq0pA59rS8Ep8vqPDCgIlhIo
Qsbp3V6j5r3CZ50Ic0qLUFK3RZZJ0AuqV8Q1l6KXcfi1gHZnOtsFWU7VUlBGpgxBMCHE6tbI
+l4WfGQCMY8+0eMmY1OdyAilOCh88ycu4f63CRtIUEFfnMZbEN7G8HYAnuo2uTNPRmrW5zfg
2yi9RfYToJK5Gaz2l36Jzbn/mtIrUxrmWfVlhAJA/YbEx7GNl5Ur/gkh1Aam9tPe+RlTiwjH
9hn/RoIvCkHr0IUywGrOBilqm0lpeFZMMicSjdXPAfwAAAAAAAA=
--------------ms070203080404060403010000--

--===============1710523845==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1710523845==--


From p2psip-bounces@ietf.org  Mon Apr 21 07:20:40 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6ADFB28C389;
	Mon, 21 Apr 2008 07:20:40 -0700 (PDT)
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 8B86928C251
	for <p2psip@core3.amsl.com>; Mon, 21 Apr 2008 07:20:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	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 gm5FKiBXfDK2 for <p2psip@core3.amsl.com>;
	Mon, 21 Apr 2008 07:20:35 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 50B8C28C23A
	for <p2psip@ietf.org>; Mon, 21 Apr 2008 07:20:35 -0700 (PDT)
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-3.cisco.com with ESMTP; 21 Apr 2008 07:20:42 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m3LEKgfe017672
	for <p2psip@ietf.org>; Mon, 21 Apr 2008 07:20:42 -0700
Received: from [192.168.4.2] (sjc-fluffy-vpn1.cisco.com [10.25.236.82])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with SMTP id m3LEKQ76016281
	for <p2psip@ietf.org>; Mon, 21 Apr 2008 14:20:41 GMT
Message-Id: <70D2F5C2-C908-4CB6-8352-DB6654FEC805@cisco.com>
From: Cullen Jennings <fluffy@cisco.com>
To: P2PSIP WG <p2psip@ietf.org>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Mon, 21 Apr 2008 07:24:30 -0700
References: <20080421120001.2682D3A6CE7@core3.amsl.com>
X-Mailer: Apple Mail (2.919.2)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=10553; t=1208787642;
	x=1209651642; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fluffy@cisco.com;
	z=From:=20Cullen=20Jennings=20<fluffy@cisco.com>
	|Subject:=20Fwd=3A=20P2P=20Infrastructure=20Workshop=20Anno
	uncement,=20May=2028,=202008=20 |Sender:=20;
	bh=tjPPvfGjFasDxWYKlthBTjK1w/hUNtSm0PiO+SCHxDc=;
	b=g6N8KZJigwfup+XqYGNMNY8D8Geo9oBTfrdlmZR5EVdVKQc9vJNhYbwvpr
	S3iSltFGOqqGS2NnKJPGlW7+bsuWvBlC1/J9+Wi/GXJVFvRbApm440BZJt1N
	dxRNGa78tzMpfYrRS4jNLgGcfVgqmsKzBpEha+neVJkaxdNmhw8zM=;
Authentication-Results: sj-dkim-1; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Subject: [P2PSIP] Fwd: P2P Infrastructure Workshop Announcement, May 28, 2008
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0315282662=="
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org


--===============0315282662==
Content-Type: multipart/alternative; boundary=Apple-Mail-2-699920600


--Apple-Mail-2-699920600
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit



Begin forwarded message:

> From: "IESG Secretary" <iesg-secretary@ietf.org>
> Date: April 21, 2008 5:00:01 AM PDT
> To: <ietf-announce@ietf.org>
> Cc: <iesg@ietf.org>
> Subject: P2P Infrastructure Workshop Announcement, May 28, 2008
>
> The Real-time Applications & Infrastructure (RAI) Area Directors, Jon
> Peterson and Cullen Jennings, would like to announce an IETF  
> workshop on
> P2P Infrastructure to be held on May 28, 2008 at 50 Vassar St, Room
> 34-101 on the MIT campus in Cambridge, MA USA.
>
> Several large ISPs have encountered issues with P2P traffic. The
> transfer of static, delay-tolerant data between nodes on the  
> Internet is
> a well-understood problem, but traditional management of fairness at  
> the
> transport level has largely been circumvented by applications designed
> to achieve the best end-user transfer rates. This results, at peak
> times, in networks running near absolute capacity, and in which all
> traffic incurs delays; the applications that bear the brunt of this
> additional latency are real-time applications like VoIP and Internet
> gaming. This has led to need for further discussion of the proper
> approaches to P2P application development, and infrastructure  
> management
> in environments where P2P is commonly used. This workshop intends to
> discover where additional IETF standards work is needed, or existing
> work might be reapplied, to alleviate these difficulties. In  
> particular,
> the workshop will draw on the experiences of Comcast and BitTorrent,
> representatives of both of whom will present their perspectives on the
> problem space.
>
> Example solution discussions might include, but are not limited to:
> deployment of application servers or caches to reduce network load;  
> new
> rendez-vous mechanisms to optimize P2P network topology; enabling
> applications to signal their bandwidth needs (and priority or lack
> thereof) to networks; enabling networks to signal bandwidth  
> constraints
> to elastic and inelastic applications; and, new approaches to fairness
> that are coupled with incentives for applications. Contributions from
> subject matter experts in the problem and solution space are
> welcome. The primary outcome should be a direction for one or more  
> IETF
> efforts exploring the best practices for addressing these challenges.
>
> The organizers would like to stress that this is a technical workshop
> exploring engineering issues and practices. The public policy
> implications of P2P applications are not in the scope of this  
> workshop.
>
> Position papers are requested from all attendees by May 9. Contact the
> RAI ADs for a waiver if it is inappropriate for you to submit a  
> position
> paper. These should constitute one to five pages on the problem or
> solution space of P2P architectures, with a particular emphasis on  
> areas
> that the IETF should address or revisit. Position papers will be made
> publicly available. On the basis of the position papers, a number of
> invited speakers will be asked to present at the workshop. A final
> agenda with timeslots will be published by May 16th. Potential  
> attendees
> for whom it is not appropriate to supply a position paper may contact
> the RAI ADs for a waiver.
>
> Evaluation of the position papers will be performed with the  
> assistance
> of a program committee consisting of the RAI ADs, Lars Eggert  
> (Transport
> AD), Danny Weitzner (MIT), John Morris (CDT), and Dave Clark (MIT).
>
> Further information about position paper submission procedures are
> forthcoming. Interested parties are advised to subscribe to the
> p2pi@ietf.org mailing list for discussion and announcements related to
> the workshop. Additional information will be available at
> http://www3.tools.ietf.org/area/rai/trac/wiki/ 
> PeerToPeerInfrastructure.
>
>


--Apple-Mail-2-699920600
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><br><div><br><div>Begin =
forwarded message:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"3" color=3D"#000000" =
style=3D"font: 12.0px Helvetica; color: #000000"><b>From: =
</b></font><font face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px =
Helvetica">"IESG Secretary" &lt;<a =
href=3D"mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>></font=
></div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><font face=3D"Helvetica" size=3D"3" =
color=3D"#000000" style=3D"font: 12.0px Helvetica; color: =
#000000"><b>Date: </b></font><font face=3D"Helvetica" size=3D"3" =
style=3D"font: 12.0px Helvetica">April 21, 2008 5:00:01 AM =
PDT</font></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><font face=3D"Helvetica" =
size=3D"3" color=3D"#000000" style=3D"font: 12.0px Helvetica; color: =
#000000"><b>To: </b></font><font face=3D"Helvetica" size=3D"3" =
style=3D"font: 12.0px Helvetica">&lt;<a =
href=3D"mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>></font><=
/div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><font face=3D"Helvetica" size=3D"3" =
color=3D"#000000" style=3D"font: 12.0px Helvetica; color: =
#000000"><b>Cc: </b></font><font face=3D"Helvetica" size=3D"3" =
style=3D"font: 12.0px Helvetica">&lt;<a =
href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>></font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"3" color=3D"#000000" =
style=3D"font: 12.0px Helvetica; color: #000000"><b>Subject: =
</b></font><font face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px =
Helvetica"><b>P2P Infrastructure Workshop Announcement, May 28, =
2008<span =
class=3D"Apple-converted-space">&nbsp;</span></b></font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div> </div> <div> <!-- =
Converted from text/plain format --><p><font size=3D"2">The Real-time =
Applications &amp; Infrastructure (RAI) Area Directors, Jon<br> Peterson =
and Cullen Jennings, would like to announce an IETF workshop on<br> P2P =
Infrastructure to be held on May 28, 2008 at 50 Vassar St, Room<br> =
34-101 on the MIT campus in Cambridge, MA USA.<br> <br> Several large =
ISPs have encountered issues with P2P traffic. The<br> transfer of =
static, delay-tolerant data between nodes on the Internet is<br> a =
well-understood problem, but traditional management of fairness at =
the<br> transport level has largely been circumvented by applications =
designed<br> to achieve the best end-user transfer rates. This results, =
at peak<br> times, in networks running near absolute capacity, and in =
which all<br> traffic incurs delays; the applications that bear the =
brunt of this<br> additional latency are real-time applications like =
VoIP and Internet<br> gaming. This has led to need for further =
discussion of the proper<br> approaches to P2P application development, =
and infrastructure management<br> in environments where P2P is commonly =
used. This workshop intends to<br> discover where additional IETF =
standards work is needed, or existing<br> work might be reapplied, to =
alleviate these difficulties. In particular,<br> the workshop will draw =
on the experiences of Comcast and BitTorrent,<br> representatives of =
both of whom will present their perspectives on the<br> problem =
space.<br> <br> Example solution discussions might include, but are not =
limited to:<br> deployment of application servers or caches to reduce =
network load; new<br> rendez-vous mechanisms to optimize P2P network =
topology; enabling<br> applications to signal their bandwidth needs (and =
priority or lack<br> thereof) to networks; enabling networks to signal =
bandwidth constraints<br> to elastic and inelastic applications; and, =
new approaches to fairness<br> that are coupled with incentives for =
applications. Contributions from<br> subject matter experts in the =
problem and solution space are<br> welcome. The primary outcome should =
be a direction for one or more IETF<br> efforts exploring the best =
practices for addressing these challenges.<br> <br> The organizers would =
like to stress that this is a technical workshop<br> exploring =
engineering issues and practices. The public policy<br> implications of =
P2P applications are not in the scope of this workshop.<br> <br> =
Position papers are requested from all attendees by May 9. Contact =
the<br> RAI ADs for a waiver if it is inappropriate for you to submit a =
position<br> paper. These should constitute one to five pages on the =
problem or<br> solution space of P2P architectures, with a particular =
emphasis on areas<br> that the IETF should address or revisit. Position =
papers will be made<br> publicly available. On the basis of the position =
papers, a number of<br> invited speakers will be asked to present at the =
workshop. A final<br> agenda with timeslots will be published by May =
16th. Potential attendees<br> for whom it is not appropriate to supply a =
position paper may contact<br> the RAI ADs for a waiver.<br> <br> =
Evaluation of the position papers will be performed with the =
assistance<br> of a program committee consisting of the RAI ADs, Lars =
Eggert (Transport<br> AD), Danny Weitzner (MIT), John Morris (CDT), and =
Dave Clark (MIT).<br> <br> Further information about position paper =
submission procedures are<br> forthcoming. Interested parties are =
advised to subscribe to the<br> <a =
href=3D"mailto:p2pi@ietf.org">p2pi@ietf.org</a> mailing list for =
discussion and announcements related to<br> the workshop. Additional =
information will be available at<br> <a =
href=3D"http://www3.tools.ietf.org/area/rai/trac/wiki/PeerToPeerInfrastruc=
ture">http://www3.tools.ietf.org/area/rai/trac/wiki/PeerToPeerInfrastructu=
re</a>.<br> <br> </font> </p> </div> =
</blockquote></div><br></body></html>=

--Apple-Mail-2-699920600--

--===============0315282662==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0315282662==--


From p2psip-bounces@ietf.org  Mon Apr 21 20:34:07 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AD87A28C1A8;
	Mon, 21 Apr 2008 20:34:07 -0700 (PDT)
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 0321928C29C
	for <p2psip@core3.amsl.com>; Mon, 21 Apr 2008 20:34:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.494
X-Spam-Level: 
X-Spam-Status: No, score=-0.494 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 
	HTML_MESSAGE=0.001, RDNS_NONE=0.1]
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 NCCaiXLG8ffO for <p2psip@core3.amsl.com>;
	Mon, 21 Apr 2008 20:33:58 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [61.144.161.55])
	by core3.amsl.com (Postfix) with ESMTP id A06423A6807
	for <p2psip@ietf.org>; Mon, 21 Apr 2008 20:33:53 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JZP00EHGJ8DAM@szxga03-in.huawei.com> for
	p2psip@ietf.org; Tue, 22 Apr 2008 11:33:49 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JZP003TLJ8CC2@szxga03-in.huawei.com> for
	p2psip@ietf.org; Tue, 22 Apr 2008 11:33:49 +0800 (CST)
Received: from s64081 ([10.164.9.76])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JZP00F7NJ88CY@szxml04-in.huawei.com> for
	p2psip@ietf.org; Tue, 22 Apr 2008 11:33:48 +0800 (CST)
Date: Tue, 22 Apr 2008 11:33:44 +0800
From: Song Haibin <melodysong@huawei.com>
In-reply-to: <70D2F5C2-C908-4CB6-8352-DB6654FEC805@cisco.com>
To: 'Cullen Jennings' <fluffy@cisco.com>, 'P2PSIP WG' <p2psip@ietf.org>
Message-id: <005601c8a429$ad037b00$4c09a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Office Outlook 11
Thread-index: Acijuut6XiaTNR7oQJaj68n45/8S1wAbfqtw
Subject: Re: [P2PSIP] Fwd: P2P Infrastructure Workshop Announcement, May 28,
 2008
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0425307798=="
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0425307798==
Content-type: multipart/alternative;
 boundary="Boundary_(ID_6QxB5XYIOFPxu5DUqBGozQ)"

This is a multi-part message in MIME format.

--Boundary_(ID_6QxB5XYIOFPxu5DUqBGozQ)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

I don't find any mail archives to P2PI mailing list. Is it a new created
one?

 

 

BTW: My name changed from Song Yongchao to Song Haibin. Greetings to every
guy with my new name.

Best Regards,
Song Haibin
Email: melodysong@huawei.com

  _____  

From: p2psip-bounces@ietf.org [mailto:p2psip-bounces@ietf.org] On Behalf Of
Cullen Jennings
Sent: Monday, April 21, 2008 10:25 PM
To: P2PSIP WG
Subject: [P2PSIP] Fwd: P2P Infrastructure Workshop Announcement, May 28,
2008

 

 

 

Begin forwarded message:





From: "IESG Secretary" <iesg-secretary@ietf.org>

Date: April 21, 2008 5:00:01 AM PDT

To: <ietf-announce@ietf.org>

Cc: <iesg@ietf.org>

Subject: P2P Infrastructure Workshop Announcement, May 28, 2008 

 

The Real-time Applications & Infrastructure (RAI) Area Directors, Jon
Peterson and Cullen Jennings, would like to announce an IETF workshop on
P2P Infrastructure to be held on May 28, 2008 at 50 Vassar St, Room
34-101 on the MIT campus in Cambridge, MA USA.

Several large ISPs have encountered issues with P2P traffic. The
transfer of static, delay-tolerant data between nodes on the Internet is
a well-understood problem, but traditional management of fairness at the
transport level has largely been circumvented by applications designed
to achieve the best end-user transfer rates. This results, at peak
times, in networks running near absolute capacity, and in which all
traffic incurs delays; the applications that bear the brunt of this
additional latency are real-time applications like VoIP and Internet
gaming. This has led to need for further discussion of the proper
approaches to P2P application development, and infrastructure management
in environments where P2P is commonly used. This workshop intends to
discover where additional IETF standards work is needed, or existing
work might be reapplied, to alleviate these difficulties. In particular,
the workshop will draw on the experiences of Comcast and BitTorrent,
representatives of both of whom will present their perspectives on the
problem space.

Example solution discussions might include, but are not limited to:
deployment of application servers or caches to reduce network load; new
rendez-vous mechanisms to optimize P2P network topology; enabling
applications to signal their bandwidth needs (and priority or lack
thereof) to networks; enabling networks to signal bandwidth constraints
to elastic and inelastic applications; and, new approaches to fairness
that are coupled with incentives for applications. Contributions from
subject matter experts in the problem and solution space are
welcome. The primary outcome should be a direction for one or more IETF
efforts exploring the best practices for addressing these challenges.

The organizers would like to stress that this is a technical workshop
exploring engineering issues and practices. The public policy
implications of P2P applications are not in the scope of this workshop.

Position papers are requested from all attendees by May 9. Contact the
RAI ADs for a waiver if it is inappropriate for you to submit a position
paper. These should constitute one to five pages on the problem or
solution space of P2P architectures, with a particular emphasis on areas
that the IETF should address or revisit. Position papers will be made
publicly available. On the basis of the position papers, a number of
invited speakers will be asked to present at the workshop. A final
agenda with timeslots will be published by May 16th. Potential attendees
for whom it is not appropriate to supply a position paper may contact
the RAI ADs for a waiver.

Evaluation of the position papers will be performed with the assistance
of a program committee consisting of the RAI ADs, Lars Eggert (Transport
AD), Danny Weitzner (MIT), John Morris (CDT), and Dave Clark (MIT).

Further information about position paper submission procedures are
forthcoming. Interested parties are advised to subscribe to the
p2pi@ietf.org mailing list for discussion and announcements related to
the workshop. Additional information will be available at
http://www3.tools.ietf.org/area/rai/trac/wiki/PeerToPeerInfrastructure.

 


--Boundary_(ID_6QxB5XYIOFPxu5DUqBGozQ)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="country-region"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
 name="State"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
 name="Street"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
 name="address"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
 name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
 name="place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Dotum;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:SimHei;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"MS UI Gothic";
	panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
	{font-family:DotumChe;
	panose-1:2 11 6 9 0 1 1 1 1 1;}
@font-face
	{font-family:KaiTi_GB2312;
	panose-1:2 1 6 9 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"\@Dotum";
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"\@MS UI Gothic";
	panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
	{font-family:"\@DotumChe";
	panose-1:2 11 6 9 0 1 1 1 1 1;}
@font-face
	{font-family:KaiTi_GB2312;
	panose-1:2 1 6 9 3 1 1 1 1 1;}
@font-face
	{font-family:SimHei;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
h1
	{margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:21.6pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-21.6pt;
	page-break-after:avoid;
	mso-list:l1 level1 lfo2;
	font-size:16.0pt;
	font-family:Arial;
	font-weight:bold;}
h2
	{margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:28.8pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-28.8pt;
	page-break-after:avoid;
	mso-list:l1 level2 lfo2;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:normal;}
h3
	{margin-top:13.0pt;
	margin-right:0cm;
	margin-bottom:13.0pt;
	margin-left:36.0pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-36.0pt;
	line-height:173%;
	page-break-after:avoid;
	mso-list:l1 level3 lfo2;
	font-size:12.0pt;
	font-family:"Times New Roman";
	layout-grid-mode:line;
	font-weight:normal;}
p.MsoHeader, li.MsoHeader, div.MsoHeader
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	layout-grid-mode:char;
	font-size:9.0pt;
	font-family:Arial;}
p.MsoFooter, li.MsoFooter, div.MsoFooter
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:Arial;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.a, li.a, div.a
	{margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:54.45pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:1.0gd;
	mso-para-margin-right:0cm;
	mso-para-margin-bottom:0cm;
	mso-para-margin-left:54.45pt;
	mso-para-margin-bottom:.0001pt;
	text-align:center;
	text-indent:-18.45pt;
	mso-list:l0 level9 lfo1;
	font-size:9.0pt;
	font-family:Arial;}
p.a0, li.a0, div.a0
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Arial;}
p.a1, li.a1, div.a1
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:center;
	font-size:10.5pt;
	font-family:Arial;
	font-weight:bold;}
p.a2, li.a2, div.a2
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:54.45pt;
	mso-para-margin-top:0cm;
	mso-para-margin-right:0cm;
	mso-para-margin-bottom:1.0gd;
	mso-para-margin-left:54.45pt;
	text-align:center;
	text-indent:-18.45pt;
	mso-list:l0 level8 lfo1;
	font-size:9.0pt;
	font-family:Arial;}
p.a3, li.a3, div.a3
	{margin-top:4.0pt;
	margin-right:0cm;
	margin-bottom:4.0pt;
	margin-left:0cm;
	text-align:center;
	line-height:150%;
	page-break-after:avoid;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";
	layout-grid-mode:line;}
p.a4, li.a4, div.a4
	{margin-top:15.0pt;
	margin-right:0cm;
	margin-bottom:15.0pt;
	margin-left:0cm;
	text-align:center;
	font-size:18.0pt;
	font-family:Arial;}
p.a5, li.a5, div.a5
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.a6, li.a6, div.a6
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	border:none;
	padding:0cm;
	font-size:9.0pt;
	font-family:Arial;}
p.a7, li.a7, div.a7
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:18.0pt;
	border:none;
	padding:0cm;
	font-size:9.0pt;
	font-family:Arial;}
p.a8, li.a8, div.a8
	{margin:0cm;
	margin-bottom:.0001pt;
	text-indent:21.0pt;
	font-size:12.0pt;
	font-family:Arial;
	color:blue;
	font-style:italic;}
span.a9
	{font-family:SimSun;
	color:black;
	font-weight:bold;}
span.aa
	{font-family:SimSun;
	color:black;
	font-weight:bold;}
span.EmailStyle35
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
 /* Page Definitions */
 @page
	{mso-endnote-separator:url("cid:header.htm\@01C8A46C.B8C6AAF0") es;
	mso-endnote-continuation-separator:url("cid:header.htm\@01C8A46C.B8C6AAF0") ecs;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:65.6pt 90.0pt 72.0pt 90.0pt;
	mso-footer:url("cid:header.htm\@01C8A46C.B8C6AAF0") f1;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1123964682;
	mso-list-template-ids:301907670;}
@list l0:level1
	{mso-level-suffix:none;
	mso-level-text:"%1  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:18.0pt;
	mso-bidi-font-size:18.0pt;
	font-family:Arial;
	mso-fareast-font-family:SimHei;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level2
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:15.0pt;
	mso-bidi-font-size:15.0pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level3
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:12.0pt;
	mso-bidi-font-size:12.0pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level4
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3\.%4  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level5
	{mso-level-tab-stop:2.0cm;
	mso-level-number-position:left;
	margin-left:2.0cm;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level6
	{mso-level-text:"%6\)";
	mso-level-tab-stop:2.0cm;
	mso-level-number-position:left;
	margin-left:2.0cm;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level7
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:2.0cm;
	mso-level-number-position:left;
	margin-left:2.0cm;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level8
	{mso-level-reset-level:level1;
	mso-level-style-link:\63D2\56FE\9898\6CE8;
	mso-level-suffix:space;
	mso-level-text:\56FE%8;
	mso-level-tab-stop:none;
	mso-level-number-position:center;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	font-family:Arial;
	mso-fareast-font-family:SimHei;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level9
	{mso-level-reset-level:level1;
	mso-level-style-link:\8868\683C\9898\6CE8;
	mso-level-suffix:space;
	mso-level-text:\8868%9;
	mso-level-tab-stop:none;
	mso-level-number-position:center;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	font-family:Arial;
	mso-fareast-font-family:SimHei;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l1
	{mso-list-id:1666475049;
	mso-list-template-ids:-28945502;}
@list l1:level1
	{mso-level-style-link:"Heading 1";
	mso-level-text:%1;
	mso-level-tab-stop:21.6pt;
	mso-level-number-position:left;
	margin-left:21.6pt;
	text-indent:-21.6pt;}
@list l1:level2
	{mso-level-style-link:"Heading 2";
	mso-level-text:"%1\.%2";
	mso-level-tab-stop:28.8pt;
	mso-level-number-position:left;
	margin-left:28.8pt;
	text-indent:-28.8pt;}
@list l1:level3
	{mso-level-style-link:"Heading 3";
	mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	margin-left:36.0pt;
	text-indent:-36.0pt;}
@list l1:level4
	{mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l1:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l1:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l1:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l1:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	margin-left:72.0pt;
	text-indent:-72.0pt;}
@list l1:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:79.2pt;
	mso-level-number-position:left;
	margin-left:79.2pt;
	text-indent:-79.2pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="2078" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="2" />
  <o:regrouptable v:ext="edit">
   <o:entry new="1" old="0" />
  </o:regrouptable>
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=ZH-CN link=blue vlink=blue style='word-wrap: break-word;-webkit-nbsp-mode: space;
-webkit-line-break: after-white-space'>

<div class=Section1>

<p class=MsoNormal><font size=1 color=navy face=Arial><span lang=EN-US
style='font-size:9.0pt;font-family:Arial;color:navy'>I don&#8217;t find any mail
archives to P2PI mailing list. Is it a new created one?<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=1 color=navy face=Arial><span lang=EN-US
style='font-size:9.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=1 color=navy face=Arial><span lang=EN-US
style='font-size:9.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=1 color=navy face=Arial><span lang=EN-US
style='font-size:9.0pt;font-family:Arial;color:navy'>BTW: My name changed from
Song Yongchao to Song Haibin. Greetings to every guy with my new name.<o:p></o:p></span></font></p>

<div>

<p><font size=2 color=navy face="Times New Roman"><span lang=EN-US
style='font-size:10.0pt;color:navy'>Best Regards,<br>
Song Haibin<br>
Email: melodysong@huawei.com</span></font><span lang=EN-US><o:p></o:p></span></p>

</div>

<div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'>

<div>

<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span lang=EN-US style='font-size:12.0pt'>

<hr size=2 width="100%" align=center tabindex=-1>

</span></font></div>

<p class=MsoNormal><b><font size=2 face=Tahoma><span lang=EN-US
style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=2 face=Tahoma><span lang=EN-US style='font-size:10.0pt;font-family:Tahoma'>
p2psip-bounces@ietf.org [mailto:p2psip-bounces@ietf.org] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Cullen Jennings<br>
<b><span style='font-weight:bold'>Sent:</span></b> Monday, April 21, 2008 10:25
PM<br>
<b><span style='font-weight:bold'>To:</span></b> P2PSIP WG<br>
<b><span style='font-weight:bold'>Subject:</span></b> [P2PSIP] Fwd: P2P Infrastructure
Workshop Announcement, May 28, 2008</span></font><span lang=EN-US><o:p></o:p></span></p>

</div>

<p class=MsoNormal><font size=3 face="Times New Roman"><span lang=EN-US
style='font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span lang=EN-US
style='font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=MsoNormal><font size=3 face="Times New Roman"><span lang=EN-US
style='font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=MsoNormal><font size=3 face="Times New Roman"><span lang=EN-US
style='font-size:12.0pt'>Begin forwarded message:<o:p></o:p></span></font></p>

</div>

<p class=MsoNormal><font size=3 face="Times New Roman"><span lang=EN-US
style='font-size:12.0pt'><br>
<br>
<o:p></o:p></span></font></p>

<div>

<div>

<p class=MsoNormal><b><font size=1 color=black face=Helvetica><span lang=EN-US
style='font-size:9.0pt;font-family:Helvetica;color:black;font-weight:bold'>From:
</span></font></b><font size=1 face=Helvetica><span lang=EN-US
style='font-size:9.0pt;font-family:Helvetica'>&quot;IESG Secretary&quot; &lt;<a
href="mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>&gt;</span></font><span
lang=EN-US><o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal><b><font size=1 color=black face=Helvetica><span lang=EN-US
style='font-size:9.0pt;font-family:Helvetica;color:black;font-weight:bold'>Date:
</span></font></b><font size=1 face=Helvetica><span lang=EN-US
style='font-size:9.0pt;font-family:Helvetica'>April 21, 2008 5:00:01 AM PDT</span></font><span
lang=EN-US><o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal><b><font size=1 color=black face=Helvetica><span lang=EN-US
style='font-size:9.0pt;font-family:Helvetica;color:black;font-weight:bold'>To: </span></font></b><font
size=1 face=Helvetica><span lang=EN-US style='font-size:9.0pt;font-family:Helvetica'>&lt;<a
href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>&gt;</span></font><span
lang=EN-US><o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal><b><font size=1 color=black face=Helvetica><span lang=EN-US
style='font-size:9.0pt;font-family:Helvetica;color:black;font-weight:bold'>Cc: </span></font></b><font
size=1 face=Helvetica><span lang=EN-US style='font-size:9.0pt;font-family:Helvetica'>&lt;<a
href="mailto:iesg@ietf.org">iesg@ietf.org</a>&gt;</span></font><span
lang=EN-US><o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal><b><font size=1 color=black face=Helvetica><span lang=EN-US
style='font-size:9.0pt;font-family:Helvetica;color:black;font-weight:bold'>Subject:
</span></font></b><b><font size=1 face=Helvetica><span lang=EN-US
style='font-size:9.0pt;font-family:Helvetica;font-weight:bold'>P2P
Infrastructure Workshop Announcement, May 28, 2008<span
class=apple-converted-space>&nbsp;</span></span></font></b><span lang=EN-US><o:p></o:p></span></p>

</div>

<div style='min-height: 14px'>

<p class=MsoNormal><font size=3 face="Times New Roman"><span lang=EN-US
style='font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</div>

<div><!-- Converted from text/plain format -->

<p style='margin-bottom:12.0pt'><font size=2 face="Times New Roman"><span
lang=EN-US style='font-size:10.0pt'>The Real-time Applications &amp;
Infrastructure (RAI) Area Directors, Jon<br>
Peterson and Cullen Jennings, would like to announce an IETF workshop on<br>
P2P Infrastructure to be held on May 28, 2008 at <st1:Street w:st="on"><st1:address
 w:st="on">50 Vassar St</st1:address></st1:Street>, Room<br>
34-101 on the MIT campus in <st1:place w:st="on"><st1:City w:st="on">Cambridge</st1:City>,
 <st1:State w:st="on">MA</st1:State> <st1:country-region w:st="on">USA</st1:country-region></st1:place>.<br>
<br>
Several large ISPs have encountered issues with P2P traffic. The<br>
transfer of static, delay-tolerant data between nodes on the Internet is<br>
a well-understood problem, but traditional management of fairness at the<br>
transport level has largely been circumvented by applications designed<br>
to achieve the best end-user transfer rates. This results, at peak<br>
times, in networks running near absolute capacity, and in which all<br>
traffic incurs delays; the applications that bear the brunt of this<br>
additional latency are real-time applications like VoIP and Internet<br>
gaming. This has led to need for further discussion of the proper<br>
approaches to P2P application development, and infrastructure management<br>
in environments where P2P is commonly used. This workshop intends to<br>
discover where additional IETF standards work is needed, or existing<br>
work might be reapplied, to alleviate these difficulties. In particular,<br>
the workshop will draw on the experiences of Comcast and BitTorrent,<br>
representatives of both of whom will present their perspectives on the<br>
problem space.<br>
<br>
Example solution discussions might include, but are not limited to:<br>
deployment of application servers or caches to reduce network load; new<br>
rendez-vous mechanisms to optimize P2P network topology; enabling<br>
applications to signal their bandwidth needs (and priority or lack<br>
thereof) to networks; enabling networks to signal bandwidth constraints<br>
to elastic and inelastic applications; and, new approaches to fairness<br>
that are coupled with incentives for applications. Contributions from<br>
subject matter experts in the problem and solution space are<br>
welcome. The primary outcome should be a direction for one or more IETF<br>
efforts exploring the best practices for addressing these challenges.<br>
<br>
The organizers would like to stress that this is a technical workshop<br>
exploring engineering issues and practices. The public policy<br>
implications of P2P applications are not in the scope of this workshop.<br>
<br>
Position papers are requested from all attendees by May 9. Contact the<br>
RAI ADs for a waiver if it is inappropriate for you to submit a position<br>
paper. These should constitute one to five pages on the problem or<br>
solution space of P2P architectures, with a particular emphasis on areas<br>
that the IETF should address or revisit. Position papers will be made<br>
publicly available. On the basis of the position papers, a number of<br>
invited speakers will be asked to present at the workshop. A final<br>
agenda with timeslots will be published by May 16th. Potential attendees<br>
for whom it is not appropriate to supply a position paper may contact<br>
the RAI ADs for a waiver.<br>
<br>
Evaluation of the position papers will be performed with the assistance<br>
of a program committee consisting of the RAI ADs, Lars Eggert (Transport<br>
AD), Danny Weitzner (MIT), John Morris (CDT), and Dave Clark (MIT).<br>
<br>
Further information about position paper submission procedures are<br>
forthcoming. Interested parties are advised to subscribe to the<br>
<a href="mailto:p2pi@ietf.org">p2pi@ietf.org</a> mailing list for discussion
and announcements related to<br>
the workshop. Additional information will be available at<br>
<a href="http://www3.tools.ietf.org/area/rai/trac/wiki/PeerToPeerInfrastructure">http://www3.tools.ietf.org/area/rai/trac/wiki/PeerToPeerInfrastructure</a>.</span></font><span
lang=EN-US><o:p></o:p></span></p>

</div>

</div>

<p class=MsoNormal><font size=3 face="Times New Roman"><span lang=EN-US
style='font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</div>

</body>

</html>

--Boundary_(ID_6QxB5XYIOFPxu5DUqBGozQ)--

--===============0425307798==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0425307798==--


From p2psip-bounces@ietf.org  Tue Apr 22 08:35:30 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 809013A6E0D;
	Tue, 22 Apr 2008 08:35:30 -0700 (PDT)
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 4D6B128C2C6
	for <p2psip@core3.amsl.com>; Tue, 22 Apr 2008 08:35:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Level: 
X-Spam-Status: No, score=-6.596 tagged_above=-999 required=5 tests=[AWL=0.003, 
	BAYES_00=-2.599, 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 MyhI2tqUBlJ9 for <p2psip@core3.amsl.com>;
	Tue, 22 Apr 2008 08:35:25 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 067603A6E2B
	for <p2psip@ietf.org>; Tue, 22 Apr 2008 08:35:25 -0700 (PDT)
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 22 Apr 2008 08:35:31 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m3MFZV5q026544; 
	Tue, 22 Apr 2008 08:35:31 -0700
Received: from [192.168.1.73] (sjc-vpn2-313.cisco.com [10.21.113.57])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m3MFZUKY008359;
	Tue, 22 Apr 2008 15:35:30 GMT
Message-Id: <17C0EB30-2EA1-4862-BE6E-4513FCED3737@cisco.com>
From: Cullen Jennings <fluffy@cisco.com>
To: Song Haibin <melodysong@huawei.com>
In-Reply-To: <005601c8a429$ad037b00$4c09a40a@china.huawei.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 22 Apr 2008 11:39:25 -0400
References: <005601c8a429$ad037b00$4c09a40a@china.huawei.com>
X-Mailer: Apple Mail (2.919.2)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4647; t=1208878531;
	x=1209742531; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fluffy@cisco.com;
	z=From:=20Cullen=20Jennings=20<fluffy@cisco.com>
	|Subject:=20Re=3A=20[P2PSIP]=20Fwd=3A=20P2P=20Infrastructur
	e=20Workshop=20Announcement,=20May=2028,=202008 |Sender:=20;
	bh=SB0EC9nXh4tUh/4GQsoReZRwPBspfTJOUipS57USURA=;
	b=mkiQqSFkrlpctQI1lcJzhv65kw78CYyTJVtu66lopZL1nt+fB5AXd/IoSj
	WihY7mSIiGhwd6l8leNI+L0AYjA9invPwTGPW2P2jRbKP8IxUrBscCH1XLIO
	ifT8zkrlCq;
Authentication-Results: sj-dkim-2; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: 'P2PSIP WG' <p2psip@ietf.org>
Subject: Re: [P2PSIP] Fwd: P2P Infrastructure Workshop Announcement, May 28,
	2008
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/pipermail/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>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org


Hmm - The list just got created but it should have an archive. I will   =

look into that. Thanks.


On Apr 21, 2008, at 11:33 PM, Song Haibin wrote:

> I don=92t find any mail archives to P2PI mailing list. Is it a new  =

> created one?
>
>
> BTW: My name changed from Song Yongchao to Song Haibin. Greetings to  =

> every guy with my new name.
> Best Regards,
> Song Haibin
> Email: melodysong@huawei.com
>
> From: p2psip-bounces@ietf.org [mailto:p2psip-bounces@ietf.org] On  =

> Behalf Of Cullen Jennings
> Sent: Monday, April 21, 2008 10:25 PM
> To: P2PSIP WG
> Subject: [P2PSIP] Fwd: P2P Infrastructure Workshop Announcement, May  =

> 28, 2008
>
>
>
> Begin forwarded message:
>
>
> From: "IESG Secretary" <iesg-secretary@ietf.org>
> Date: April 21, 2008 5:00:01 AM PDT
> To: <ietf-announce@ietf.org>
> Cc: <iesg@ietf.org>
> Subject: P2P Infrastructure Workshop Announcement, May 28, 2008
>
> The Real-time Applications & Infrastructure (RAI) Area Directors, Jon
> Peterson and Cullen Jennings, would like to announce an IETF  =

> workshop on
> P2P Infrastructure to be held on May 28, 2008 at 50 Vassar St, Room
> 34-101 on the MIT campus in Cambridge, MA USA.
>
> Several large ISPs have encountered issues with P2P traffic. The
> transfer of static, delay-tolerant data between nodes on the  =

> Internet is
> a well-understood problem, but traditional management of fairness at  =

> the
> transport level has largely been circumvented by applications designed
> to achieve the best end-user transfer rates. This results, at peak
> times, in networks running near absolute capacity, and in which all
> traffic incurs delays; the applications that bear the brunt of this
> additional latency are real-time applications like VoIP and Internet
> gaming. This has led to need for further discussion of the proper
> approaches to P2P application development, and infrastructure  =

> management
> in environments where P2P is commonly used. This workshop intends to
> discover where additional IETF standards work is needed, or existing
> work might be reapplied, to alleviate these difficulties. In  =

> particular,
> the workshop will draw on the experiences of Comcast and BitTorrent,
> representatives of both of whom will present their perspectives on the
> problem space.
>
> Example solution discussions might include, but are not limited to:
> deployment of application servers or caches to reduce network load;  =

> new
> rendez-vous mechanisms to optimize P2P network topology; enabling
> applications to signal their bandwidth needs (and priority or lack
> thereof) to networks; enabling networks to signal bandwidth  =

> constraints
> to elastic and inelastic applications; and, new approaches to fairness
> that are coupled with incentives for applications. Contributions from
> subject matter experts in the problem and solution space are
> welcome. The primary outcome should be a direction for one or more  =

> IETF
> efforts exploring the best practices for addressing these challenges.
>
> The organizers would like to stress that this is a technical workshop
> exploring engineering issues and practices. The public policy
> implications of P2P applications are not in the scope of this  =

> workshop.
>
> Position papers are requested from all attendees by May 9. Contact the
> RAI ADs for a waiver if it is inappropriate for you to submit a  =

> position
> paper. These should constitute one to five pages on the problem or
> solution space of P2P architectures, with a particular emphasis on  =

> areas
> that the IETF should address or revisit. Position papers will be made
> publicly available. On the basis of the position papers, a number of
> invited speakers will be asked to present at the workshop. A final
> agenda with timeslots will be published by May 16th. Potential  =

> attendees
> for whom it is not appropriate to supply a position paper may contact
> the RAI ADs for a waiver.
>
> Evaluation of the position papers will be performed with the  =

> assistance
> of a program committee consisting of the RAI ADs, Lars Eggert  =

> (Transport
> AD), Danny Weitzner (MIT), John Morris (CDT), and Dave Clark (MIT).
>
> Further information about position paper submission procedures are
> forthcoming. Interested parties are advised to subscribe to the
> p2pi@ietf.org mailing list for discussion and announcements related to
> the workshop. Additional information will be available at
> http://www3.tools.ietf.org/area/rai/trac/wiki/ =

> PeerToPeerInfrastructure.
>
>

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


From p2psip-bounces@ietf.org  Tue Apr 22 08:38:56 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E16513A6E23;
	Tue, 22 Apr 2008 08:38:56 -0700 (PDT)
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 12EE928C441
	for <p2psip@core3.amsl.com>; Tue, 22 Apr 2008 08:38:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.247
X-Spam-Level: **
X-Spam-Status: No, score=2.247 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2,
	HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SARE_SUB_ENC_GB2312=1.345]
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 i0LF9+rVKqka for <p2psip@core3.amsl.com>;
	Tue, 22 Apr 2008 08:38:47 -0700 (PDT)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211])
	by core3.amsl.com (Postfix) with ESMTP id DE1D928C1FC
	for <p2psip@ietf.org>; Tue, 22 Apr 2008 08:38:46 -0700 (PDT)
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JZQ00FRVGSSAV@usaga01-in.huawei.com> for
	p2psip@ietf.org; Tue, 22 Apr 2008 08:38:52 -0700 (PDT)
Received: from huawei.com ([172.17.1.31])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JZQ00HNVGSQ4K@usaga01-in.huawei.com> for
	p2psip@ietf.org; Tue, 22 Apr 2008 08:38:52 -0700 (PDT)
Received: from [172.24.1.6] (Forwarded-For: [70.23.122.87])
	by szxmc03-in.huawei.com (mshttpd); Tue, 22 Apr 2008 11:38:44 -0400
Date: Tue, 22 Apr 2008 11:38:44 -0400
From: jiangxingfeng 36340 <jiang.x.f@huawei.com>
In-reply-to: <70D2F5C2-C908-4CB6-8352-DB6654FEC805@cisco.com>
To: Spencer Dawkins <sdawkins@huawei.com>
Message-id: <fba5ab588c8ec.8c8ecfba5ab58@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.14 (built Aug  8 2006)
Content-type: multipart/mixed; boundary="Boundary_(ID_a/FwZRE8qIBjpojggKuEkQ)"
Content-language: zh-CN
X-Accept-Language: zh-CN
Priority: normal
References: <20080421120001.2682D3A6CE7@core3.amsl.com>
	<70D2F5C2-C908-4CB6-8352-DB6654FEC805@cisco.com>
Cc: P2PSIP WG <p2psip@ietf.org>
Subject: [P2PSIP] =?gb2312?b?u9i4tCA6IEZ3ZDogUDJQIEluZnJhc3RydWN0dXJlIFdv?=
 =?gb2312?b?cmtzaG9wIEFubm91bmNlbWVudCwgTWF5IDI4LCAyMDA4?=
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/pipermail/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>
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

This is a multi-part message in MIME format.

--Boundary_(ID_a/FwZRE8qIBjpojggKuEkQ)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline

Hi, Spencer:

How are you recently? You must notice the forwarded mail about a Workshop of P2P Infrastructure to be held on May 28th. Do you have a plan to attend the meeting? I think it is a important meeting in P2P area. It is great if you will be there. 


Regards

JiangXingFeng

--Boundary_(ID_a/FwZRE8qIBjpojggKuEkQ)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_GpM1lPhSIM5aVdm3vA3q7w)"


--Boundary_(ID_GpM1lPhSIM5aVdm3vA3q7w)
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-transfer-encoding: 7BIT



Begin forwarded message:

> From: "IESG Secretary" <iesg-secretary@ietf.org>
> Date: April 21, 2008 5:00:01 AM PDT
> To: <ietf-announce@ietf.org>
> Cc: <iesg@ietf.org>
> Subject: P2P Infrastructure Workshop Announcement, May 28, 2008
>
> The Real-time Applications & Infrastructure (RAI) Area Directors, Jon
> Peterson and Cullen Jennings, would like to announce an IETF  
> workshop on
> P2P Infrastructure to be held on May 28, 2008 at 50 Vassar St, Room
> 34-101 on the MIT campus in Cambridge, MA USA.
>
> Several large ISPs have encountered issues with P2P traffic. The
> transfer of static, delay-tolerant data between nodes on the  
> Internet is
> a well-understood problem, but traditional management of fairness at  
> the
> transport level has largely been circumvented by applications designed
> to achieve the best end-user transfer rates. This results, at peak
> times, in networks running near absolute capacity, and in which all
> traffic incurs delays; the applications that bear the brunt of this
> additional latency are real-time applications like VoIP and Internet
> gaming. This has led to need for further discussion of the proper
> approaches to P2P application development, and infrastructure  
> management
> in environments where P2P is commonly used. This workshop intends to
> discover where additional IETF standards work is needed, or existing
> work might be reapplied, to alleviate these difficulties. In  
> particular,
> the workshop will draw on the experiences of Comcast and BitTorrent,
> representatives of both of whom will present their perspectives on the
> problem space.
>
> Example solution discussions might include, but are not limited to:
> deployment of application servers or caches to reduce network load;  
> new
> rendez-vous mechanisms to optimize P2P network topology; enabling
> applications to signal their bandwidth needs (and priority or lack
> thereof) to networks; enabling networks to signal bandwidth  
> constraints
> to elastic and inelastic applications; and, new approaches to fairness
> that are coupled with incentives for applications. Contributions from
> subject matter experts in the problem and solution space are
> welcome. The primary outcome should be a direction for one or more  
> IETF
> efforts exploring the best practices for addressing these challenges.
>
> The organizers would like to stress that this is a technical workshop
> exploring engineering issues and practices. The public policy
> implications of P2P applications are not in the scope of this  
> workshop.
>
> Position papers are requested from all attendees by May 9. Contact the
> RAI ADs for a waiver if it is inappropriate for you to submit a  
> position
> paper. These should constitute one to five pages on the problem or
> solution space of P2P architectures, with a particular emphasis on  
> areas
> that the IETF should address or revisit. Position papers will be made
> publicly available. On the basis of the position papers, a number of
> invited speakers will be asked to present at the workshop. A final
> agenda with timeslots will be published by May 16th. Potential  
> attendees
> for whom it is not appropriate to supply a position paper may contact
> the RAI ADs for a waiver.
>
> Evaluation of the position papers will be performed with the  
> assistance
> of a program committee consisting of the RAI ADs, Lars Eggert  
> (Transport
> AD), Danny Weitzner (MIT), John Morris (CDT), and Dave Clark (MIT).
>
> Further information about position paper submission procedures are
> forthcoming. Interested parties are advised to subscribe to the
> p2pi@ietf.org mailing list for discussion and announcements related to
> the workshop. Additional information will be available at
> http://www3.tools.ietf.org/area/rai/trac/wiki/ 
> PeerToPeerInfrastructure.
>
>


--Boundary_(ID_GpM1lPhSIM5aVdm3vA3q7w)
Content-type: text/html; charset=US-ASCII
Content-transfer-encoding: 7BIT

<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><br><div>Begin forwarded message:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>From: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica">"IESG Secretary" &lt;<a href="mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>Date: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica">April 21, 2008 5:00:01 AM PDT</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><
 font fac
lor="#000000" style="font: 12.0px Helvetica; color: #000000"><b>To: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica">&lt;<a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>Cc: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica">&lt;<a href="mailto:iesg@ietf.org">iesg@ietf.org</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>Subject: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica"><b>P2P Infrastructure Workshop Announcement, May 28, 2008<span class="Apple-converted-space">&nbsp;</span></b></font></div><div style="margin-top: 0px; margin-right:
  0px; ma
left: 0px; min-height: 14px; "><br></div> </div> <div> <!-- Converted from text/plain format --><p><font size="2">The Real-time Applications &amp; Infrastructure (RAI) Area Directors, Jon<br> Peterson and Cullen Jennings, would like to announce an IETF workshop on<br> P2P Infrastructure to be held on May 28, 2008 at 50 Vassar St, Room<br> 34-101 on the MIT campus in Cambridge, MA USA.<br> <br> Several large ISPs have encountered issues with P2P traffic. The<br> transfer of static, delay-tolerant data between nodes on the Internet is<br> a well-understood problem, but traditional management of fairness at the<br> transport level has largely been circumvented by applications designed<br> to achieve the best end-user transfer rates. This results, at peak<br> times, in networks running near absolute capacity, and in which all<br> traffic incurs delays; the applications that bear the brunt of this<br> additional latency are real-time applications like VoIP and Internet<br> gaming.
  This ha
 discussion of the proper<br> approaches to P2P application development, and infrastructure management<br> in environments where P2P is commonly used. This workshop intends to<br> discover where additional IETF standards work is needed, or existing<br> work might be reapplied, to alleviate these difficulties. In particular,<br> the workshop will draw on the experiences of Comcast and BitTorrent,<br> representatives of both of whom will present their perspectives on the<br> problem space.<br> <br> Example solution discussions might include, but are not limited to:<br> deployment of application servers or caches to reduce network load; new<br> rendez-vous mechanisms to optimize P2P network topology; enabling<br> applications to signal their bandwidth needs (and priority or lack<br> thereof) to networks; enabling networks to signal bandwidth constraints<br> to elastic and inelastic applications; and, new approaches to fairness<br> that are coupled with incentives for application
 s. Contr
 matter experts in the problem and solution space are<br> welcome. The primary outcome should be a direction for one or more IETF<br> efforts exploring the best practices for addressing these challenges.<br> <br> The organizers would like to stress that this is a technical workshop<br> exploring engineering issues and practices. The public policy<br> implications of P2P applications are not in the scope of this workshop.<br> <br> Position papers are requested from all attendees by May 9. Contact the<br> RAI ADs for a waiver if it is inappropriate for you to submit a position<br> paper. These should constitute one to five pages on the problem or<br> solution space of P2P architectures, with a particular emphasis on areas<br> that the IETF should address or revisit. Position papers will be made<br> publicly available. On the basis of the position papers, a number of<br> invited speakers will be asked to present at the workshop. A final<br> agenda with timeslots will be publishe
 d by May
s<br> for whom it is not appropriate to supply a position paper may contact<br> the RAI ADs for a waiver.<br> <br> Evaluation of the position papers will be performed with the assistance<br> of a program committee consisting of the RAI ADs, Lars Eggert (Transport<br> AD), Danny Weitzner (MIT), John Morris (CDT), and Dave Clark (MIT).<br> <br> Further information about position paper submission procedures are<br> forthcoming. Interested parties are advised to subscribe to the<br> <a href="mailto:p2pi@ietf.org">p2pi@ietf.org</a> mailing list for discussion and announcements related to<br> the workshop. Additional information will be available at<br> <a href="http://www3.tools.ietf.org/area/rai/trac/wiki/PeerToPeerInfrastructure">http://www3.tools.ietf.org/area/rai/trac/wiki/PeerToPeerInfrastructure</a>.<br> <br> </font> </p> </div> </blockquote></div><br></body></html>

--Boundary_(ID_GpM1lPhSIM5aVdm3vA3q7w)--

--Boundary_(ID_a/FwZRE8qIBjpojggKuEkQ)
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline

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

--Boundary_(ID_a/FwZRE8qIBjpojggKuEkQ)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--Boundary_(ID_a/FwZRE8qIBjpojggKuEkQ)--


From p2psip-bounces@ietf.org  Tue Apr 22 08:44:29 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 03D323A6E4A;
	Tue, 22 Apr 2008 08:44:29 -0700 (PDT)
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 4C9C93A6A51
	for <p2psip@core3.amsl.com>; Tue, 22 Apr 2008 08:44:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.176
X-Spam-Level: 
X-Spam-Status: No, score=-0.176 tagged_above=-999 required=5 tests=[AWL=2.422, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 ucPSj6XlxkIl for <p2psip@core3.amsl.com>;
	Tue, 22 Apr 2008 08:44:27 -0700 (PDT)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211])
	by core3.amsl.com (Postfix) with ESMTP id F3CD528C14F
	for <p2psip@ietf.org>; Tue, 22 Apr 2008 08:44:26 -0700 (PDT)
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JZQ00FCAH28AV@usaga01-in.huawei.com> for
	p2psip@ietf.org; Tue, 22 Apr 2008 08:44:33 -0700 (PDT)
Received: from huawei.com ([172.17.1.31])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JZQ00HZJH264K@usaga01-in.huawei.com> for
	p2psip@ietf.org; Tue, 22 Apr 2008 08:44:31 -0700 (PDT)
Received: from [172.24.1.6] (Forwarded-For: [70.23.122.87])
	by szxmc03-in.huawei.com (mshttpd); Tue, 22 Apr 2008 11:44:23 -0400
Date: Tue, 22 Apr 2008 11:44:23 -0400
From: jiangxingfeng 36340 <jiang.x.f@huawei.com>
To: p2psip@ietf.org
Message-id: <f9d286db8a38c.8a38cf9d286db@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.14 (built Aug  8 2006)
Content-type: multipart/mixed; boundary="Boundary_(ID_+lbG6KadzL5p+qqzikwKPw)"
Content-language: zh-CN
X-Accept-Language: zh-CN
Priority: normal
Subject: [P2PSIP]  Fwd: P2P Infrastructure Workshop  Announcement, May 28,
	2008
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/pipermail/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>
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

This is a multi-part message in MIME format.

--Boundary_(ID_+lbG6KadzL5p+qqzikwKPw)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline

Hi, all:

Sorry for wrong post. Please ignore the previous mail. 

Regard

JiangXingFeng

--Boundary_(ID_+lbG6KadzL5p+qqzikwKPw)
Content-type: message/rfc822
Content-disposition: inline

Received: from [172.24.1.6] (Forwarded-For: [70.23.122.87])
 by szxmc03-in.huawei.com (mshttpd); Tue, 22 Apr 2008 11:38:44 -0400
Date: Tue, 22 Apr 2008 11:38:44 -0400
From: jiangxingfeng 36340 <jiang.x.f@huawei.com>
Subject: =?gb2312?B?u9i4tA==?=:[P2PSIP] Fwd: P2P Infrastructure Workshop
 Announcement, May 28, 2008
In-reply-to: <70D2F5C2-C908-4CB6-8352-DB6654FEC805@cisco.com>
To: Spencer Dawkins <sdawkins@huawei.com>
Cc: P2PSIP WG <p2psip@ietf.org>, Cullen Jennings <fluffy@cisco.com>
Message-id: <fba5ab588c8ec.8c8ecfba5ab58@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.14 (built Aug  8 2006)
Content-type: multipart/mixed; boundary="Boundary_(ID_LGkldI09jD4GeW47eL7JWw)"
Content-language: zh-CN
X-Accept-Language: zh-CN
Priority: normal
References: <20080421120001.2682D3A6CE7@core3.amsl.com>
 <70D2F5C2-C908-4CB6-8352-DB6654FEC805@cisco.com>

This is a multi-part message in MIME format.

--Boundary_(ID_LGkldI09jD4GeW47eL7JWw)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline

Hi, Spencer:

How are you recently? You must notice the forwarded mail about a Workshop of P2P Infrastructure to be held on May 28th. Do you have a plan to attend the meeting? I think it is a important meeting in P2P area. It is great if you will be there. 


Regards

JiangXingFeng

--Boundary_(ID_LGkldI09jD4GeW47eL7JWw)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_wsALObEWXtd7wpSfghZGrA)"


--Boundary_(ID_wsALObEWXtd7wpSfghZGrA)
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-transfer-encoding: 7BIT



Begin forwarded message:

> From: "IESG Secretary" <iesg-secretary@ietf.org>
> Date: April 21, 2008 5:00:01 AM PDT
> To: <ietf-announce@ietf.org>
> Cc: <iesg@ietf.org>
> Subject: P2P Infrastructure Workshop Announcement, May 28, 2008
>
> The Real-time Applications & Infrastructure (RAI) Area Directors, Jon
> Peterson and Cullen Jennings, would like to announce an IETF  
> workshop on
> P2P Infrastructure to be held on May 28, 2008 at 50 Vassar St, Room
> 34-101 on the MIT campus in Cambridge, MA USA.
>
> Several large ISPs have encountered issues with P2P traffic. The
> transfer of static, delay-tolerant data between nodes on the  
> Internet is
> a well-understood problem, but traditional management of fairness at  
> the
> transport level has largely been circumvented by applications designed
> to achieve the best end-user transfer rates. This results, at peak
> times, in networks running near absolute capacity, and in which all
> traffic incurs delays; the applications that bear the brunt of this
> additional latency are real-time applications like VoIP and Internet
> gaming. This has led to need for further discussion of the proper
> approaches to P2P application development, and infrastructure  
> management
> in environments where P2P is commonly used. This workshop intends to
> discover where additional IETF standards work is needed, or existing
> work might be reapplied, to alleviate these difficulties. In  
> particular,
> the workshop will draw on the experiences of Comcast and BitTorrent,
> representatives of both of whom will present their perspectives on the
> problem space.
>
> Example solution discussions might include, but are not limited to:
> deployment of application servers or caches to reduce network load;  
> new
> rendez-vous mechanisms to optimize P2P network topology; enabling
> applications to signal their bandwidth needs (and priority or lack
> thereof) to networks; enabling networks to signal bandwidth  
> constraints
> to elastic and inelastic applications; and, new approaches to fairness
> that are coupled with incentives for applications. Contributions from
> subject matter experts in the problem and solution space are
> welcome. The primary outcome should be a direction for one or more  
> IETF
> efforts exploring the best practices for addressing these challenges.
>
> The organizers would like to stress that this is a technical workshop
> exploring engineering issues and practices. The public policy
> implications of P2P applications are not in the scope of this  
> workshop.
>
> Position papers are requested from all attendees by May 9. Contact the
> RAI ADs for a waiver if it is inappropriate for you to submit a  
> position
> paper. These should constitute one to five pages on the problem or
> solution space of P2P architectures, with a particular emphasis on  
> areas
> that the IETF should address or revisit. Position papers will be made
> publicly available. On the basis of the position papers, a number of
> invited speakers will be asked to present at the workshop. A final
> agenda with timeslots will be published by May 16th. Potential  
> attendees
> for whom it is not appropriate to supply a position paper may contact
> the RAI ADs for a waiver.
>
> Evaluation of the position papers will be performed with the  
> assistance
> of a program committee consisting of the RAI ADs, Lars Eggert  
> (Transport
> AD), Danny Weitzner (MIT), John Morris (CDT), and Dave Clark (MIT).
>
> Further information about position paper submission procedures are
> forthcoming. Interested parties are advised to subscribe to the
> p2pi@ietf.org mailing list for discussion and announcements related to
> the workshop. Additional information will be available at
> http://www3.tools.ietf.org/area/rai/trac/wiki/ 
> PeerToPeerInfrastructure.
>
>


--Boundary_(ID_wsALObEWXtd7wpSfghZGrA)
Content-type: text/html; charset=US-ASCII
Content-transfer-encoding: 7BIT

<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><br><div>Begin forwarded message:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>From: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica">"IESG Secretary" &lt;<a href="mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>Date: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica">April 21, 2008 5:00:01 AM PDT</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><
 font fac
lor="#000000" style="font: 12.0px Helvetica; color: #000000"><b>To: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica">&lt;<a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>Cc: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica">&lt;<a href="mailto:iesg@ietf.org">iesg@ietf.org</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>Subject: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica"><b>P2P Infrastructure Workshop Announcement, May 28, 2008<span class="Apple-converted-space">&nbsp;</span></b></font></div><div style="margin-top: 0px; margin-right:
  0px; ma
left: 0px; min-height: 14px; "><br></div> </div> <div> <!-- Converted from text/plain format --><p><font size="2">The Real-time Applications &amp; Infrastructure (RAI) Area Directors, Jon<br> Peterson and Cullen Jennings, would like to announce an IETF workshop on<br> P2P Infrastructure to be held on May 28, 2008 at 50 Vassar St, Room<br> 34-101 on the MIT campus in Cambridge, MA USA.<br> <br> Several large ISPs have encountered issues with P2P traffic. The<br> transfer of static, delay-tolerant data between nodes on the Internet is<br> a well-understood problem, but traditional management of fairness at the<br> transport level has largely been circumvented by applications designed<br> to achieve the best end-user transfer rates. This results, at peak<br> times, in networks running near absolute capacity, and in which all<br> traffic incurs delays; the applications that bear the brunt of this<br> additional latency are real-time applications like VoIP and Internet<br> gaming.
  This ha
 discussion of the proper<br> approaches to P2P application development, and infrastructure management<br> in environments where P2P is commonly used. This workshop intends to<br> discover where additional IETF standards work is needed, or existing<br> work might be reapplied, to alleviate these difficulties. In particular,<br> the workshop will draw on the experiences of Comcast and BitTorrent,<br> representatives of both of whom will present their perspectives on the<br> problem space.<br> <br> Example solution discussions might include, but are not limited to:<br> deployment of application servers or caches to reduce network load; new<br> rendez-vous mechanisms to optimize P2P network topology; enabling<br> applications to signal their bandwidth needs (and priority or lack<br> thereof) to networks; enabling networks to signal bandwidth constraints<br> to elastic and inelastic applications; and, new approaches to fairness<br> that are coupled with incentives for application
 s. Contr
 matter experts in the problem and solution space are<br> welcome. The primary outcome should be a direction for one or more IETF<br> efforts exploring the best practices for addressing these challenges.<br> <br> The organizers would like to stress that this is a technical workshop<br> exploring engineering issues and practices. The public policy<br> implications of P2P applications are not in the scope of this workshop.<br> <br> Position papers are requested from all attendees by May 9. Contact the<br> RAI ADs for a waiver if it is inappropriate for you to submit a position<br> paper. These should constitute one to five pages on the problem or<br> solution space of P2P architectures, with a particular emphasis on areas<br> that the IETF should address or revisit. Position papers will be made<br> publicly available. On the basis of the position papers, a number of<br> invited speakers will be asked to present at the workshop. A final<br> agenda with timeslots will be publishe
 d by May
s<br> for whom it is not appropriate to supply a position paper may contact<br> the RAI ADs for a waiver.<br> <br> Evaluation of the position papers will be performed with the assistance<br> of a program committee consisting of the RAI ADs, Lars Eggert (Transport<br> AD), Danny Weitzner (MIT), John Morris (CDT), and Dave Clark (MIT).<br> <br> Further information about position paper submission procedures are<br> forthcoming. Interested parties are advised to subscribe to the<br> <a href="mailto:p2pi@ietf.org">p2pi@ietf.org</a> mailing list for discussion and announcements related to<br> the workshop. Additional information will be available at<br> <a href="http://www3.tools.ietf.org/area/rai/trac/wiki/PeerToPeerInfrastructure">http://www3.tools.ietf.org/area/rai/trac/wiki/PeerToPeerInfrastructure</a>.<br> <br> </font> </p> </div> </blockquote></div><br></body></html>

--Boundary_(ID_wsALObEWXtd7wpSfghZGrA)--

--Boundary_(ID_LGkldI09jD4GeW47eL7JWw)
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline

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

--Boundary_(ID_LGkldI09jD4GeW47eL7JWw)--

--Boundary_(ID_+lbG6KadzL5p+qqzikwKPw)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--Boundary_(ID_+lbG6KadzL5p+qqzikwKPw)--


From p2psip-bounces@ietf.org  Tue Apr 22 11:49:51 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C183F3A6A91;
	Tue, 22 Apr 2008 11:49:51 -0700 (PDT)
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 6F7823A6A91
	for <p2psip@core3.amsl.com>; Tue, 22 Apr 2008 11:49:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.202
X-Spam-Level: 
X-Spam-Status: No, score=-5.202 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396,
	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 JcBJ9SomTS2x for <p2psip@core3.amsl.com>;
	Tue, 22 Apr 2008 11:49:50 -0700 (PDT)
Received: from exprod6og102.obsmtp.com (exprod6og102.obsmtp.com [64.18.1.183])
	by core3.amsl.com (Postfix) with ESMTP id 791603A68BE
	for <p2psip@ietf.org>; Tue, 22 Apr 2008 11:49:49 -0700 (PDT)
Received: from source ([192.150.8.22]) by exprod6ob102.postini.com
	([64.18.5.12]) with SMTP; Tue, 22 Apr 2008 11:49:52 PDT
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
	m3MInoJV016007; Tue, 22 Apr 2008 11:49:51 -0700 (PDT)
Received: from fe1.corp.adobe.com (fe1.corp.adobe.com [10.8.192.70])
	by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id
	m3MInmqJ029646; Tue, 22 Apr 2008 11:49:49 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 Apr 2008 11:49:47 -0700
Received: from 10.7.241.3 ([10.7.241.3]) by namail5.corp.adobe.com
	([10.8.192.88]) with Microsoft Exchange Server HTTP-DAV ; 
	Tue, 22 Apr 2008 18:49:47 +0000
User-Agent: Microsoft-Entourage/12.1.0.080305
Date: Tue, 22 Apr 2008 13:49:45 -0500
From: Heinrich Sinnreich <hsinnrei@adobe.com>
To: Cullen Jennings <fluffy@cisco.com>, "'P2PSIP WG'" <p2psip@ietf.org>
Message-ID: <C4339D79.3843%hsinnrei@adobe.com>
Thread-Topic: [P2PSIP] Fwd: P2P Infrastructure Workshop Announcement, May 28, 
	2008
Thread-Index: Acijuut6XiaTNR7oQJaj68n45/8S1wAbfqtwACAu5TM=
In-Reply-To: <005601c8a429$ad037b00$4c09a40a@china.huawei.com>
Mime-version: 1.0
X-OriginalArrivalTime: 22 Apr 2008 18:49:47.0884 (UTC)
	FILETIME=[A374FAC0:01C8A4A9]
Subject: Re: [P2PSIP] Fwd: P2P Infrastructure Workshop Announcement, May 28,
 2008
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0615530009=="
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============0615530009==
Content-type: multipart/alternative;
	boundary="B_3291716986_4208257"

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3291716986_4208257
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

> See also the other meeting for balance:
> 
> http://www.dslreports.com/shownews/FCC-Net-Neutrality-Meeting-at-Stanford-Toda
> y-93665
> 
> Henry
> 
> 
> 
> From: "IESG Secretary" <iesg-secretary@ietf.org>
> 
> Date: April 21, 2008 5:00:01 AM PDT
> 
> To: <ietf-announce@ietf.org>
> 
> Cc: <iesg@ietf.org>
> 
> Subject: P2P Infrastructure Workshop Announcement, May 28, 2008
> 
>  
> 
> The Real-time Applications & Infrastructure (RAI) Area Directors, Jon
> Peterson and Cullen Jennings, would like to announce an IETF workshop on
> P2P Infrastructure to be held on May 28, 2008 at 50 Vassar St, Room
> 34-101 on the MIT campus in Cambridge, MA USA.
> 
> Several large ISPs have encountered issues with P2P traffic. The
> transfer of static, delay-tolerant data between nodes on the Internet is
> a well-understood problem, but traditional management of fairness at the
> transport level has largely been circumvented by applications designed
> to achieve the best end-user transfer rates. This results, at peak
> times, in networks running near absolute capacity, and in which all
> traffic incurs delays; the applications that bear the brunt of this
> additional latency are real-time applications like VoIP and Internet
> gaming. This has led to need for further discussion of the proper
> approaches to P2P application development, and infrastructure management
> in environments where P2P is commonly used. This workshop intends to
> discover where additional IETF standards work is needed, or existing
> work might be reapplied, to alleviate these difficulties. In particular,
> the workshop will draw on the experiences of Comcast and BitTorrent,
> representatives of both of whom will present their perspectives on the
> problem space.
> 
> Example solution discussions might include, but are not limited to:
> deployment of application servers or caches to reduce network load; new
> rendez-vous mechanisms to optimize P2P network topology; enabling
> applications to signal their bandwidth needs (and priority or lack
> thereof) to networks; enabling networks to signal bandwidth constraints
> to elastic and inelastic applications; and, new approaches to fairness
> that are coupled with incentives for applications. Contributions from
> subject matter experts in the problem and solution space are
> welcome. The primary outcome should be a direction for one or more IETF
> efforts exploring the best practices for addressing these challenges.
> 
> The organizers would like to stress that this is a technical workshop
> exploring engineering issues and practices. The public policy
> implications of P2P applications are not in the scope of this workshop.
> 
> Position papers are requested from all attendees by May 9. Contact the
> RAI ADs for a waiver if it is inappropriate for you to submit a position
> paper. These should constitute one to five pages on the problem or
> solution space of P2P architectures, with a particular emphasis on areas
> that the IETF should address or revisit. Position papers will be made
> publicly available. On the basis of the position papers, a number of
> invited speakers will be asked to present at the workshop. A final
> agenda with timeslots will be published by May 16th. Potential attendees
> for whom it is not appropriate to supply a position paper may contact
> the RAI ADs for a waiver.
> 
> Evaluation of the position papers will be performed with the assistance
> of a program committee consisting of the RAI ADs, Lars Eggert (Transport
> AD), Danny Weitzner (MIT), John Morris (CDT), and Dave Clark (MIT).
> 
> Further information about position paper submission procedures are
> forthcoming. Interested parties are advised to subscribe to the
> p2pi@ietf.org mailing list for discussion and announcements related to
> the workshop. Additional information will be available at
> http://www3.tools.ietf.org/area/rai/trac/wiki/PeerToPeerInfrastructure.
> 
>  
> 
> 
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www.ietf.org/mailman/listinfo/p2psip


--B_3291716986_4208257
Content-type: text/html;
	charset="US-ASCII"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [P2PSIP] Fwd: P2P Infrastructure Workshop Announcement, May 28, =
2008</TITLE>
</HEAD>
<BODY>
<BLOCKQUOTE><FONT SIZE=3D"4"><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial">=
<SPAN STYLE=3D'font-size:11pt'>See also the other meeting for balance:<BR>
<BR>
<a href=3D"http://www.dslreports.com/shownews/FCC-Net-Neutrality-Meeting-at-S=
tanford-Today-93665">http://www.dslreports.com/shownews/FCC-Net-Neutrality-M=
eeting-at-Stanford-Today-93665</a><BR>
<BR>
Henry<BR>
</SPAN></FONT></FONT><FONT SIZE=3D"5"><FONT FACE=3D"Times New Roman"><SPAN STYL=
E=3D'font-size:12pt'><BR>
<BR>
<BR>
</SPAN></FONT></FONT><FONT FACE=3D"Helvetica, Verdana, Arial"><SPAN STYLE=3D'fo=
nt-size:9pt'><B>From: </B>&quot;IESG Secretary&quot; &lt;iesg-secretary@ietf=
.org&gt;<BR>
</SPAN></FONT><FONT SIZE=3D"4"><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial=
"><SPAN STYLE=3D'font-size:11pt'><BR>
</SPAN></FONT></FONT><FONT FACE=3D"Helvetica, Verdana, Arial"><SPAN STYLE=3D'fo=
nt-size:9pt'><B>Date: </B>April 21, 2008 5:00:01 AM PDT<BR>
</SPAN></FONT><FONT SIZE=3D"4"><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial=
"><SPAN STYLE=3D'font-size:11pt'><BR>
</SPAN></FONT></FONT><FONT FACE=3D"Helvetica, Verdana, Arial"><SPAN STYLE=3D'fo=
nt-size:9pt'><B>To: </B>&lt;ietf-announce@ietf.org&gt;<BR>
</SPAN></FONT><FONT SIZE=3D"4"><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial=
"><SPAN STYLE=3D'font-size:11pt'><BR>
</SPAN></FONT></FONT><FONT FACE=3D"Helvetica, Verdana, Arial"><SPAN STYLE=3D'fo=
nt-size:9pt'><B>Cc: </B>&lt;iesg@ietf.org&gt;<BR>
</SPAN></FONT><FONT SIZE=3D"4"><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial=
"><SPAN STYLE=3D'font-size:11pt'><BR>
</SPAN></FONT></FONT><FONT FACE=3D"Helvetica, Verdana, Arial"><SPAN STYLE=3D'fo=
nt-size:9pt'><B>Subject: P2P Infrastructure Workshop Announcement, May 28, 2=
008 <BR>
</B></SPAN></FONT><FONT SIZE=3D"4"><FONT FACE=3D"Calibri, Verdana, Helvetica, A=
rial"><SPAN STYLE=3D'font-size:11pt'><BR>
</SPAN></FONT></FONT><FONT SIZE=3D"5"><FONT FACE=3D"Times New Roman"><SPAN STYL=
E=3D'font-size:12pt'> <BR>
</SPAN></FONT></FONT><FONT SIZE=3D"4"><FONT FACE=3D"Calibri, Verdana, Helvetica=
, Arial"><SPAN STYLE=3D'font-size:11pt'><BR>
</SPAN></FONT><FONT FACE=3D"Times New Roman"><SPAN STYLE=3D'font-size:10pt'>The=
 Real-time Applications &amp; Infrastructure (RAI) Area Directors, Jon<BR>
Peterson and Cullen Jennings, would like to announce an IETF workshop on<BR=
>
P2P Infrastructure to be held on May 28, 2008 at 50 Vassar St, Room<BR>
34-101 on the MIT campus in Cambridge, MA USA.<BR>
<BR>
Several large ISPs have encountered issues with P2P traffic. The<BR>
transfer of static, delay-tolerant data between nodes on the Internet is<BR=
>
a well-understood problem, but traditional management of fairness at the<BR=
>
transport level has largely been circumvented by applications designed<BR>
to achieve the best end-user transfer rates. This results, at peak<BR>
times, in networks running near absolute capacity, and in which all<BR>
traffic incurs delays; the applications that bear the brunt of this<BR>
additional latency are real-time applications like VoIP and Internet<BR>
gaming. This has led to need for further discussion of the proper<BR>
approaches to P2P application development, and infrastructure management<BR=
>
in environments where P2P is commonly used. This workshop intends to<BR>
discover where additional IETF standards work is needed, or existing<BR>
work might be reapplied, to alleviate these difficulties. In particular,<BR=
>
the workshop will draw on the experiences of Comcast and BitTorrent,<BR>
representatives of both of whom will present their perspectives on the<BR>
problem space.<BR>
<BR>
Example solution discussions might include, but are not limited to:<BR>
deployment of application servers or caches to reduce network load; new<BR>
rendez-vous mechanisms to optimize P2P network topology; enabling<BR>
applications to signal their bandwidth needs (and priority or lack<BR>
thereof) to networks; enabling networks to signal bandwidth constraints<BR>
to elastic and inelastic applications; and, new approaches to fairness<BR>
that are coupled with incentives for applications. Contributions from<BR>
subject matter experts in the problem and solution space are<BR>
welcome. The primary outcome should be a direction for one or more IETF<BR>
efforts exploring the best practices for addressing these challenges.<BR>
<BR>
The organizers would like to stress that this is a technical workshop<BR>
exploring engineering issues and practices. The public policy<BR>
implications of P2P applications are not in the scope of this workshop.<BR>
<BR>
Position papers are requested from all attendees by May 9. Contact the<BR>
RAI ADs for a waiver if it is inappropriate for you to submit a position<BR=
>
paper. These should constitute one to five pages on the problem or<BR>
solution space of P2P architectures, with a particular emphasis on areas<BR=
>
that the IETF should address or revisit. Position papers will be made<BR>
publicly available. On the basis of the position papers, a number of<BR>
invited speakers will be asked to present at the workshop. A final<BR>
agenda with timeslots will be published by May 16th. Potential attendees<BR=
>
for whom it is not appropriate to supply a position paper may contact<BR>
the RAI ADs for a waiver.<BR>
<BR>
Evaluation of the position papers will be performed with the assistance<BR>
of a program committee consisting of the RAI ADs, Lars Eggert (Transport<BR=
>
AD), Danny Weitzner (MIT), John Morris (CDT), and Dave Clark (MIT).<BR>
<BR>
Further information about position paper submission procedures are<BR>
forthcoming. Interested parties are advised to subscribe to the<BR>
p2pi@ietf.org mailing list for discussion and announcements related to<BR>
the workshop. Additional information will be available at<BR>
<a href=3D"http://www3.tools.ietf.org/area/rai/trac/wiki/PeerToPeerInfrastruc=
ture.">http://www3.tools.ietf.org/area/rai/trac/wiki/PeerToPeerInfrastructur=
e.</a><BR>
</SPAN></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'=
font-size:11pt'><BR>
</SPAN></FONT></FONT><FONT SIZE=3D"5"><FONT FACE=3D"Times New Roman"><SPAN STYL=
E=3D'font-size:12pt'> <BR>
</SPAN></FONT></FONT><FONT SIZE=3D"4"><FONT FACE=3D"Calibri, Verdana, Helvetica=
, Arial"><SPAN STYLE=3D'font-size:11pt'><BR>
<HR ALIGN=3DCENTER SIZE=3D"3" WIDTH=3D"95%"></SPAN></FONT><FONT FACE=3D"Consolas, C=
ourier New, Courier"><SPAN STYLE=3D'font-size:10pt'>__________________________=
_____________________<BR>
P2PSIP mailing list<BR>
P2PSIP@ietf.org<BR>
https://www.ietf.org/mailman/listinfo/p2psip<BR>
</SPAN></FONT></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--B_3291716986_4208257--


--===============0615530009==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0615530009==--



From p2psip-bounces@ietf.org  Wed Apr 23 12:33:42 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 419BC3A6D3F;
	Wed, 23 Apr 2008 12:33:42 -0700 (PDT)
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 165393A6E2D
	for <p2psip@core3.amsl.com>; Wed, 23 Apr 2008 12:33:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 Nh+uu2wGHdVe for <p2psip@core3.amsl.com>;
	Wed, 23 Apr 2008 12:33:35 -0700 (PDT)
Received: from jalapeno.cc.columbia.edu (jalapeno.cc.columbia.edu
	[128.59.29.5]) by core3.amsl.com (Postfix) with ESMTP id A39E13A6D3F
	for <p2psip@ietf.org>; Wed, 23 Apr 2008 12:33:35 -0700 (PDT)
Received: from ice.cs.columbia.edu (ice.cs.columbia.edu [128.59.18.177])
	(user=hgs10 mech=PLAIN bits=0)
	by jalapeno.cc.columbia.edu (8.14.1/8.14.1) with ESMTP id
	m3NJXc6O019889
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT)
	for <p2psip@ietf.org>; Wed, 23 Apr 2008 15:33:39 -0400 (EDT)
Message-Id: <4117A7E8-F0C3-44DB-A680-95960AEF9DD5@cs.columbia.edu>
From: Henning Schulzrinne <hgs@cs.columbia.edu>
To: P2PSIP Mailing List <p2psip@ietf.org>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 23 Apr 2008 15:33:38 -0400
X-Mailer: Apple Mail (2.919.2)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.63 on 128.59.29.5
Subject: [P2PSIP] Terminology - no WG names
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

In writing the revised draft, I took another look at the terminology  
document. In general, I think it's a really bad idea to label terms  
with the working group name. The name will be meaningless to non-IETF  
participants, i.e., 99% of developers, and will cease to have any  
meaning once the working group fades from memory. (I don't think  
P2PSIP wants to become another DHC or AVT WG...) In addition, the  
prefix doesn't really define anything, except recursively whatever the  
working group decided to work on. Thus, a P2PSIP overlay is the  
overlay defined by the P2PSIP working group, which is...

For example, I would suggest

resource discovery overlay

for our main work item.

On a related note, I would also suggest changing 'peer ID' to 'node  
ID', since we seem to have some agreement that clients, as future  
peers, would be identified by the same construct. But saying "a client  
has a peer ID, but isn't a peer" doesn't seem to further understanding.

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


From p2psip-bounces@ietf.org  Wed Apr 23 12:52:41 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9939728C2B4;
	Wed, 23 Apr 2008 12:52:41 -0700 (PDT)
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 70A2328C275
	for <p2psip@core3.amsl.com>; Wed, 23 Apr 2008 12:52:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 xSBMErQSWdmP for <p2psip@core3.amsl.com>;
	Wed, 23 Apr 2008 12:52:39 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.228])
	by core3.amsl.com (Postfix) with ESMTP id 1C55E28C2F4
	for <p2psip@ietf.org>; Wed, 23 Apr 2008 12:51:13 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so1386527rvf.49
	for <p2psip@ietf.org>; Wed, 23 Apr 2008 12:51:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
	bh=nd2eIjQY42Nw6KrMr0JmjvBGLrtGqF6hQCCM5Xy4+fQ=;
	b=E43HlY11rJBdyqwU48VMH1IsbzVM1uAZZkDibifAMwB3FER/qT6PUe6QzL2sgHtEm4gs7JP1IdQIgFPSpRn7uS82GWShn1iknmJZXo2eSo62z6gpSfNcM9a9FkVJecEvykVjmvc4DRAXpwXRBY/QjTIHEpDdNdrWiBnhgdcNZ6k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
	b=wFcKAlLhw40/5xm/62++KLwcGBDLZ4YgNZLKCDHqeS+pO5JT01wzR+J7aeUwChfsMpIrJuJcmk7Z1Vf4dvjgvtZhAqivwpwVXj0t9G+A3kAE1MnQGrhCiDv3WHiM7zZgY7F8HCUTxI/IOXb0lewxuZnuE1aJerFcObC0OOpJJgU=
Received: by 10.140.171.4 with SMTP id t4mr756586rve.187.1208980278025;
	Wed, 23 Apr 2008 12:51:18 -0700 (PDT)
Received: by 10.141.26.9 with HTTP; Wed, 23 Apr 2008 12:51:17 -0700 (PDT)
Message-ID: <4d4304a00804231251y686fe4dcr3ddad0af6f1e2bf6@mail.gmail.com>
Date: Wed, 23 Apr 2008 15:51:17 -0400
From: "David A. Bryan" <dbryan@sipeerior.com>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>
In-Reply-To: <4117A7E8-F0C3-44DB-A680-95960AEF9DD5@cs.columbia.edu>
MIME-Version: 1.0
Content-Disposition: inline
References: <4117A7E8-F0C3-44DB-A680-95960AEF9DD5@cs.columbia.edu>
X-Google-Sender-Auth: 3dbaa102b4b85ecc
Cc: P2PSIP Mailing List <p2psip@ietf.org>
Subject: Re: [P2PSIP] Terminology - no WG names
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

Inline

On Wed, Apr 23, 2008 at 3:33 PM, Henning Schulzrinne
<hgs@cs.columbia.edu> wrote:
> In writing the revised draft, I took another look at the terminology
>  document. In general, I think it's a really bad idea to label terms
>  with the working group name. The name will be meaningless to non-IETF
>  participants, i.e., 99% of developers, and will cease to have any
>  meaning once the working group fades from memory. (I don't think
>  P2PSIP wants to become another DHC or AVT WG...) In addition, the
>  prefix doesn't really define anything, except recursively whatever the
>  working group decided to work on. Thus, a P2PSIP overlay is the
>  overlay defined by the P2PSIP working group, which is...
>
>  For example, I would suggest
>
>  resource discovery overlay
>
>  for our main work item.

Not a bad idea, from my perspective. I think early on we did it to
distinguish what we talking about from the more general term, but
eliminating the P2PSIP labels sounds ok to me. Interested to see what
others think.

>  On a related note, I would also suggest changing 'peer ID' to 'node
>  ID', since we seem to have some agreement that clients, as future
>  peers, would be identified by the same construct. But saying "a client
>  has a peer ID, but isn't a peer" doesn't seem to further understanding.

There was a very long discussion about peer vs. node, and the
consensus was that the literature preferred peer to node. I know way
back, in the very first P2PSIP draft submitted, I used node
everywhere, and actually preferred it to peer. When we decided to
change it, I did so in all my drafts. I actually think this is one of
those where we could argue all day back and forth about it, and the
discussion would be "Full of sound and fury, signifying nothing". I
don't really care from a technical perspective, but I'd be willing to
bet $10 we could spend many more hours debating it, and someone would
still bring it up and propose to flip it again in 6 months (and
possibly with good, reasons too -- it's just there are good arguments
on both side).

I'd vote to just recognize language is an imperfect tool to express
ideas and leave it alone.

As an aside, I would think a client having a peer-id makes perfect
sense if the reason it has it is that it could conceivably be a peer
in some context. It is is "latent" peer-ID, in that case, ready to be
used if it becomes one. I don't really see the conflict.

David (as individual)

>  Henning
>  _______________________________________________
>  P2PSIP mailing list
>  P2PSIP@ietf.org
>  https://www.ietf.org/mailman/listinfo/p2psip
>



-- 
David A. Bryan
dbryan@SIPeerior.com
+1.757.565.0101 x101
+1.757.565.0088 (fax)
www.SIPeerior.com
_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www.ietf.org/mailman/listinfo/p2psip


From p2psip-bounces@ietf.org  Wed Apr 23 14:02:25 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 80F913A6E48;
	Wed, 23 Apr 2008 14:02:25 -0700 (PDT)
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 87FAB3A68E7
	for <p2psip@core3.amsl.com>; Wed, 23 Apr 2008 14:02:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 aJaR-t5ov2e5 for <p2psip@core3.amsl.com>;
	Wed, 23 Apr 2008 14:02:23 -0700 (PDT)
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168])
	by core3.amsl.com (Postfix) with ESMTP id 7DA493A6E5B
	for <p2psip@ietf.org>; Wed, 23 Apr 2008 14:01:10 -0700 (PDT)
Received: by ug-out-1314.google.com with SMTP id u2so553532uge.46
	for <p2psip@ietf.org>; Wed, 23 Apr 2008 14:01:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=ggHv5ZY4yzu6E5xMWFQYn3iUjSVICg8U7qkASM0TWuE=;
	b=sN0TuAKRRnhW03m7yDmhrj8+ggXwpG0AtdaO2wmE7nId2QMamx5J+aLgNx7Un37mCTQPepTGAjZwQ56X4WJrzNSgqQeSfy7+Q2GOMcOWRjqWIByX+G6Fyg66E7o2boK3UXeb9ISyo/I0w1uCTBbp13dbFEm4jyViyKEQxkEOJqk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=E2X0cDg43y+AtzstkbPvcbNg4URnCYYGiLh93k0z6e+PLFIHZRa+BTMBNYH5vmVChUSRX17AWSILjdBuNdogKFT/76UPIu3o36AUaNQLsx4k4EdKx1PW0hriben8d/INJwo1BkPISJUIJn1XB91ZYMo9BvOGp1qkCOPzNExiy30=
Received: by 10.67.24.18 with SMTP id b18mr8945816ugj.65.1208984474710;
	Wed, 23 Apr 2008 14:01:14 -0700 (PDT)
Received: by 10.67.15.11 with HTTP; Wed, 23 Apr 2008 14:01:14 -0700 (PDT)
Message-ID: <618e24240804231401k7332ca5eqf9ad4452cc2a223b@mail.gmail.com>
Date: Wed, 23 Apr 2008 23:01:14 +0200
From: "=?UTF-8?Q?Victor_Pascual_=C3=81vila?=" <victor.pascual.avila@gmail.com>
To: "David A. Bryan" <dbryan@sipeerior.com>
In-Reply-To: <4d4304a00804231251y686fe4dcr3ddad0af6f1e2bf6@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <4117A7E8-F0C3-44DB-A680-95960AEF9DD5@cs.columbia.edu>
	<4d4304a00804231251y686fe4dcr3ddad0af6f1e2bf6@mail.gmail.com>
Cc: P2PSIP Mailing List <p2psip@ietf.org>
Subject: Re: [P2PSIP] Terminology - no WG names
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/pipermail/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>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

SGksCgpPbiBXZWQsIEFwciAyMywgMjAwOCBhdCA5OjUxIFBNLCBEYXZpZCBBLiBCcnlhbiA8ZGJy
eWFuQHNpcGVlcmlvci5jb20+IHdyb3RlOgo+ICBOb3QgYSBiYWQgaWRlYSwgZnJvbSBteSBwZXJz
cGVjdGl2ZS4gSSB0aGluayBlYXJseSBvbiB3ZSBkaWQgaXQgdG8KPiAgZGlzdGluZ3Vpc2ggd2hh
dCB3ZSB0YWxraW5nIGFib3V0IGZyb20gdGhlIG1vcmUgZ2VuZXJhbCB0ZXJtLCBidXQKPiAgZWxp
bWluYXRpbmcgdGhlIFAyUFNJUCBsYWJlbHMgc291bmRzIG9rIHRvIG1lLiBJbnRlcmVzdGVkIHRv
IHNlZSB3aGF0Cj4gIG90aGVycyB0aGluay4KCkkgYWdyZWUgb24gdXNpbmcgbm8gUDJQU0lQIGxh
YmVscyBhbmQgc3VnZ2VzdCB0aGF0IHdlIHVzZSBQMlAKdGVybWlub2xvZ3kgY29tbW9uIGluIHRo
ZSB0ZWNobmljYWwgbGl0ZXJhdHVyZS4KClRoYW5rcywKLS0gClZpY3RvciBQYXNjdWFsIMOBdmls
YQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpQMlBTSVAg
bWFpbGluZyBsaXN0ClAyUFNJUEBpZXRmLm9yZwpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL3AycHNpcAo=


From p2psip-bounces@ietf.org  Wed Apr 23 14:16:36 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C207228C32B;
	Wed, 23 Apr 2008 14:16:36 -0700 (PDT)
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 8BC3828C32B
	for <p2psip@core3.amsl.com>; Wed, 23 Apr 2008 14:16:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.827
X-Spam-Level: 
X-Spam-Status: No, score=-1.827 tagged_above=-999 required=5
	tests=[AWL=-0.150, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622,
	MIME_8BIT_HEADER=0.3]
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 AbAoQfw5wJpC for <p2psip@core3.amsl.com>;
	Wed, 23 Apr 2008 14:16:34 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.228])
	by core3.amsl.com (Postfix) with ESMTP id C6C2328C2AF
	for <p2psip@ietf.org>; Wed, 23 Apr 2008 14:15:56 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so1403423rvf.49
	for <p2psip@ietf.org>; Wed, 23 Apr 2008 14:16:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
	bh=LzU0Kq9HvIfxa8Vj4QMgZ3Ql5QLGxqq6avuXO+XxiG0=;
	b=NS1uZZYNGyzT/6mncmh10xEKmrS6gb+KlcAhCppdg/7gNPmryo3CX2tWO4TRtsTZppWIF4nErS58U9ew4VgkQjKLjadlCOK7P1FxP6mu1Ra22xX5Y94SwUhW4todZZBV4GbexHeFOucThwkOY6z22JRkT+GIOSgV6aAI+2dvui8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
	b=hWoY+n0Fmos3D3ByscOyi5px3K7B7LxDdo/Dd2ra3UiyOTj0xRw2zPegQuQJNYeF78x1wIyczwAdYSdDjVxm8r1sInKaTE2lmh9z3VQQ5HhKtLavm/ToqBYd/s9esT8je45ZkWtNeV7FGy2wQpBccfLdNOfRjOA0mZ4bZuBXn5c=
Received: by 10.141.137.16 with SMTP id p16mr833510rvn.192.1208985362383;
	Wed, 23 Apr 2008 14:16:02 -0700 (PDT)
Received: by 10.141.26.9 with HTTP; Wed, 23 Apr 2008 14:16:02 -0700 (PDT)
Message-ID: <4d4304a00804231416p3d033ea8o5c39534252f83e53@mail.gmail.com>
Date: Wed, 23 Apr 2008 17:16:02 -0400
From: "David A. Bryan" <dbryan@sipeerior.com>
To: "=?ISO-8859-1?Q?Victor_Pascual_=C1vila?=" <victor.pascual.avila@gmail.com>
In-Reply-To: <618e24240804231401k7332ca5eqf9ad4452cc2a223b@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <4117A7E8-F0C3-44DB-A680-95960AEF9DD5@cs.columbia.edu>
	<4d4304a00804231251y686fe4dcr3ddad0af6f1e2bf6@mail.gmail.com>
	<618e24240804231401k7332ca5eqf9ad4452cc2a223b@mail.gmail.com>
X-Google-Sender-Auth: 8c598f5999e3b04f
Cc: P2PSIP Mailing List <p2psip@ietf.org>
Subject: Re: [P2PSIP] Terminology - no WG names
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/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

Most of the terms were very carefully picked to match the technical
literature as much as possible. That said, the literature sometimes is
not consistent between different papers...

I agree we should try to reflect the literature, and believe that we
for the most part do in the current draft (

David (as individual)

On Wed, Apr 23, 2008 at 5:01 PM, Victor Pascual =C1vila
<victor.pascual.avila@gmail.com> wrote:
> Hi,
>
>
>  On Wed, Apr 23, 2008 at 9:51 PM, David A. Bryan <dbryan@sipeerior.com> w=
rote:
>  >  Not a bad idea, from my perspective. I think early on we did it to
>  >  distinguish what we talking about from the more general term, but
>  >  eliminating the P2PSIP labels sounds ok to me. Interested to see what
>  >  others think.
>
>  I agree on using no P2PSIP labels and suggest that we use P2P
>  terminology common in the technical literature.
>
>  Thanks,
>  --
>  Victor Pascual =C1vila
>



-- =

David A. Bryan
dbryan@SIPeerior.com
+1.757.565.0101 x101
+1.757.565.0088 (fax)
www.SIPeerior.com
_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www.ietf.org/mailman/listinfo/p2psip


From p2psip-bounces@ietf.org  Wed Apr 23 15:59:09 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1D35428C231;
	Wed, 23 Apr 2008 15:59:09 -0700 (PDT)
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 EE1AF28C1F4
	for <p2psip@core3.amsl.com>; Wed, 23 Apr 2008 15:59:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.751
X-Spam-Level: 
X-Spam-Status: No, score=-5.751 tagged_above=-999 required=5 tests=[AWL=0.549, 
	BAYES_00=-2.599, 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 asm6mctKyUoE for <p2psip@core3.amsl.com>;
	Wed, 23 Apr 2008 15:59:06 -0700 (PDT)
Received: from exprod6og104.obsmtp.com (exprod6og104.obsmtp.com [64.18.1.187])
	by core3.amsl.com (Postfix) with ESMTP id 054E428C0E7
	for <p2psip@ietf.org>; Wed, 23 Apr 2008 15:59:03 -0700 (PDT)
Received: from source ([192.150.11.134]) by exprod6ob104.postini.com
	([64.18.5.12]) with SMTP; Wed, 23 Apr 2008 15:59:09 PDT
Received: from inner-relay-3.eur.adobe.com ([192.150.8.236])
	by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	m3NMu8G3020470; Wed, 23 Apr 2008 15:56:08 -0700 (PDT)
Received: from fe1.corp.adobe.com (fe1.corp.adobe.com [10.8.192.70])
	by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id
	m3NMx5qJ026006; Wed, 23 Apr 2008 15:59:06 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 23 Apr 2008 15:59:04 -0700
Received: from 10.7.242.3 ([10.7.242.3]) by namail5.corp.adobe.com
	([10.8.192.88]) with Microsoft Exchange Server HTTP-DAV ; 
	Wed, 23 Apr 2008 22:59:04 +0000
User-Agent: Microsoft-Entourage/12.1.0.080305
Date: Wed, 23 Apr 2008 17:59:02 -0500
From: Henry Sinnreich <hsinnrei@adobe.com>
To: "David A. Bryan" <dbryan@sipeerior.com>,
	Victor Pascual =?ISO-8859-1?B?wXZpbGE=?= <victor.pascual.avila@gmail.com>
Message-ID: <C4352966.3983%hsinnrei@adobe.com>
Thread-Topic: [P2PSIP] Terminology - no WG names
Thread-Index: AcillZ83mjfsNBkudEiMlloslNFf7Q==
In-Reply-To: <4d4304a00804231416p3d033ea8o5c39534252f83e53@mail.gmail.com>
Mime-version: 1.0
X-OriginalArrivalTime: 23 Apr 2008 22:59:04.0828 (UTC)
	FILETIME=[A0E743C0:01C8A595]
Cc: P2PSIP Mailing List <p2psip@ietf.org>
Subject: Re: [P2PSIP] Terminology - no WG names
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/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

I suppose a good start would be to agree on some reference sources on P2P,
for example:

* Wikipedia has an excellent P2P tutorial section with well known references

http://en.wikipedia.org/wiki/Peer-to-peer

* The openDHT publications

http://opendht.org/pubs.html

Just these two sources would be a good start, though folks on the list may
well have additional sources to suggest.

What this discussions proves however is that instead every I-D in the P2PSIP
WG having its own glossary, the WG should better invite someone to write a
glossary paper on its own that can be discussed and agreed on. This was not
in the charter, but may be a good option, given the work involved.

Another option is for the terminology paper by Dean Willis et al. to be
updated with an updated and comprehensive glossary for P2P.

What do you think?

Henry


On 4/23/08 4:16 PM, "David A. Bryan" <dbryan@sipeerior.com> wrote:

> Most of the terms were very carefully picked to match the technical
> literature as much as possible. That said, the literature sometimes is
> not consistent between different papers...
> =

> I agree we should try to reflect the literature, and believe that we
> for the most part do in the current draft (
> =

> David (as individual)
> =

> On Wed, Apr 23, 2008 at 5:01 PM, Victor Pascual =C1vila
> <victor.pascual.avila@gmail.com> wrote:
>> Hi,
>> =

>> =

>>  On Wed, Apr 23, 2008 at 9:51 PM, David A. Bryan <dbryan@sipeerior.com>
>> wrote:
>>>  Not a bad idea, from my perspective. I think early on we did it to
>>>  distinguish what we talking about from the more general term, but
>>>  eliminating the P2PSIP labels sounds ok to me. Interested to see what
>>>  others think.
>> =

>>  I agree on using no P2PSIP labels and suggest that we use P2P
>>  terminology common in the technical literature.
>> =

>>  Thanks,
>>  --
>>  Victor Pascual =C1vila
>> =

> =

> =


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


From p2psip-bounces@ietf.org  Wed Apr 23 16:22:10 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 382803A6C9F;
	Wed, 23 Apr 2008 16:22:10 -0700 (PDT)
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 CF5333A6BAF
	for <p2psip@core3.amsl.com>; Wed, 23 Apr 2008 16:22:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, 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 p4VKrP0Hdq+k for <p2psip@core3.amsl.com>;
	Wed, 23 Apr 2008 16:22:07 -0700 (PDT)
Received: from mail153.messagelabs.com (mail153.messagelabs.com
	[216.82.253.51]) by core3.amsl.com (Postfix) with SMTP id 36A4228C130
	for <p2psip@ietf.org>; Wed, 23 Apr 2008 16:21:36 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: mmontpetit@motorola.com
X-Msg-Ref: server-5.tower-153.messagelabs.com!1208992901!8822921!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.189.100.103]
Received: (qmail 4241 invoked from network); 23 Apr 2008 23:21:41 -0000
Received: from motgate3.mot.com (HELO motgate3.mot.com) (144.189.100.103)
	by server-5.tower-153.messagelabs.com with SMTP;
	23 Apr 2008 23:21:41 -0000
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate3.mot.com (8.12.11/Motorola) with ESMTP id m3NNLZGw009566
	for <p2psip@ietf.org>; Wed, 23 Apr 2008 16:21:40 -0700 (MST)
Received: from az10vts03 (az10vts03.mot.com [10.64.251.244])
	by az33exr04.mot.com (8.13.1/Vontu) with SMTP id m3NNLYst007439
	for <p2psip@ietf.org>; Wed, 23 Apr 2008 18:21:35 -0500 (CDT)
Received: from de01exm61.ds.mot.com (de01exm61.am.mot.com [10.176.8.106])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id m3NNLXf1007434
	for <p2psip@ietf.org>; Wed, 23 Apr 2008 18:21:34 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 23 Apr 2008 19:21:32 -0400
Message-ID: <768EE6AB7D56D54BB5000EC2DD113E7103E79E58@de01exm61.ds.mot.com>
In-Reply-To: <4117A7E8-F0C3-44DB-A680-95960AEF9DD5@cs.columbia.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] Terminology - no WG names
Thread-Index: AcilePbcrlgZ3uNdQYyAcZpNBPqmVwAH1+tw
References: <4117A7E8-F0C3-44DB-A680-95960AEF9DD5@cs.columbia.edu>
From: "Montpetit Marie-Jose-MGIF0300" <mmontpetit@motorola.com>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>,
	"P2PSIP Mailing List" <p2psip@ietf.org>
X-CFilter-Loop: Reflected
Subject: Re: [P2PSIP] Terminology - no WG names
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

I may be late but I agree with the proposal. The resource discovery is
essential as not all nodes are the same and some could be more
appropriate for certain task (storage vs computation vs rendering). I
also agree on node vs peer - actually some nodes could be involved in
P2P and non P2P relationships. Finally while I have no personal problem
with P2PSIP I know people who do.

/mjm 

-----Original Message-----
From: p2psip-bounces@ietf.org [mailto:p2psip-bounces@ietf.org] On Behalf
Of Henning Schulzrinne
Sent: Wednesday, April 23, 2008 3:34 PM
To: P2PSIP Mailing List
Subject: [P2PSIP] Terminology - no WG names

In writing the revised draft, I took another look at the terminology
document. In general, I think it's a really bad idea to label terms with
the working group name. The name will be meaningless to non-IETF
participants, i.e., 99% of developers, and will cease to have any
meaning once the working group fades from memory. (I don't think P2PSIP
wants to become another DHC or AVT WG...) In addition, the prefix
doesn't really define anything, except recursively whatever the working
group decided to work on. Thus, a P2PSIP overlay is the overlay defined
by the P2PSIP working group, which is...

For example, I would suggest

resource discovery overlay

for our main work item.

On a related note, I would also suggest changing 'peer ID' to 'node ID',
since we seem to have some agreement that clients, as future peers,
would be identified by the same construct. But saying "a client has a
peer ID, but isn't a peer" doesn't seem to further understanding.

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


From p2psip-bounces@ietf.org  Wed Apr 23 18:27:00 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF7213A699B;
	Wed, 23 Apr 2008 18:27:00 -0700 (PDT)
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 2C71B3A699B
	for <p2psip@core3.amsl.com>; Wed, 23 Apr 2008 18:27:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
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 Fml+GoKaRXve for <p2psip@core3.amsl.com>;
	Wed, 23 Apr 2008 18:26:59 -0700 (PDT)
Received: from voxeo.com (mmail.voxeo.com [66.193.54.208])
	by core3.amsl.com (Postfix) with ESMTP id D01D83A67EB
	for <p2psip@ietf.org>; Wed, 23 Apr 2008 18:26:58 -0700 (PDT)
Received: from pc-00144.lodestar2.dyndns.org (account dyork [75.68.245.43]
	verified) by voxeo.com (CommuniGate Pro SMTP 5.1.14)
	with ESMTPSA id 30274871; Thu, 24 Apr 2008 01:27:02 +0000
Message-Id: <97835A24-356F-4C0F-A515-C3EBF8236406@voxeo.com>
From: Dan York <dyork@voxeo.com>
To: David A. Bryan <dbryan@sipeerior.com>
In-Reply-To: <4d4304a00804231251y686fe4dcr3ddad0af6f1e2bf6@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 23 Apr 2008 21:27:01 -0400
References: <4117A7E8-F0C3-44DB-A680-95960AEF9DD5@cs.columbia.edu>
	<4d4304a00804231251y686fe4dcr3ddad0af6f1e2bf6@mail.gmail.com>
X-Mailer: Apple Mail (2.919.2)
Cc: P2PSIP Mailing List <p2psip@ietf.org>
Subject: Re: [P2PSIP] Terminology - no WG names
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org


On Apr 23, 2008, at 3:51 PM, David A. Bryan wrote:
>
> Not a bad idea, from my perspective. I think early on we did it to
> distinguish what we talking about from the more general term, but
> eliminating the P2PSIP labels sounds ok to me. Interested to see what
> others think.

DY> +1  Makes sense to not have the WG label in there.
>
>
>> On a related note, I would also suggest changing 'peer ID' to 'node
>> ID', since we seem to have some agreement that clients, as future
>> peers, would be identified by the same construct. But saying "a  
>> client
>> has a peer ID, but isn't a peer" doesn't seem to further  
>> understanding.
>
> There was a very long discussion about peer vs. node, and the
> consensus was that the literature preferred peer to node. I know way
> back, in the very first P2PSIP draft submitted, I used node
> everywhere, and actually preferred it to peer. When we decided to
> change it, I did so in all my drafts. I actually think this is one of
> those where we could argue all day back and forth about it, and the
> discussion would be "Full of sound and fury, signifying nothing". I
> don't really care from a technical perspective, but I'd be willing to
> bet $10 we could spend many more hours debating it, and someone would
> still bring it up and propose to flip it again in 6 months (and
> possibly with good, reasons too -- it's just there are good arguments
> on both side).

DY> With P2P in general getting more attention these days, has the  
literature changed at all in relation to 'peer' vs 'node'?

DY> I would be inclined to agree with your original usage. To me,  
"node" merely indicates that a device/program/whatever is a connection  
point on a network (or network overlay), while "peer" implies a  
"relationship" between the device/program/whatever and other similar  
objects.

DY> "Node" to me does not have the relationship baggage. It just "is".

DY> However, I can also see where this could very easily go down a  
semantic rathole and be one of those things that could consume  
zillions of electrons and hours of our time debating.

DY> I agree with Henry that a centralized glossary makes sense, but  
I'm a little bit confused - isn't that what the 'concepts' document is  
supposed to be? ( http://tools.ietf.org/html/draft-ietf-p2psip-concepts-01 
  ) While Henning did not explicitly state the draft he was referring  
to, I assumed it was this one.

Regards,
Dan
>

-- 
Dan York, CISSP, Director of Emerging Communication Technology
Office of the CTO    Voxeo Corporation     dyork@voxeo.com
Phone: +1-407-455-5859  Skype: danyork  http://www.voxeo.com
Blogs: http://blogs.voxeo.com  http://www.disruptivetelephony.com

Build voice applications based on open standards.
Find out how at http://www.voxeo.com/free





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


From p2psip-bounces@ietf.org  Wed Apr 23 19:26:21 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0FD753A69F4;
	Wed, 23 Apr 2008 19:26:21 -0700 (PDT)
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 057763A6846
	for <p2psip@core3.amsl.com>; Wed, 23 Apr 2008 19:26:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.494
X-Spam-Level: 
X-Spam-Status: No, score=-0.494 tagged_above=-999 required=5 tests=[AWL=0.001, 
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 
	RDNS_NONE=0.1]
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 QRH918PVBq8u for <p2psip@core3.amsl.com>;
	Wed, 23 Apr 2008 19:26:19 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [61.144.161.55])
	by core3.amsl.com (Postfix) with ESMTP id 2C00E3A6A4A
	for <p2psip@ietf.org>; Wed, 23 Apr 2008 19:26:10 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JZT00LCW5FH7E@szxga03-in.huawei.com> for
	p2psip@ietf.org; Thu, 24 Apr 2008 10:26:05 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JZT005JS5FHGA@szxga03-in.huawei.com> for
	p2psip@ietf.org; Thu, 24 Apr 2008 10:26:05 +0800 (CST)
Received: from s64081 ([10.164.9.76])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JZT000BC5FG90@szxml04-in.huawei.com> for
	p2psip@ietf.org; Thu, 24 Apr 2008 10:26:05 +0800 (CST)
Date: Thu, 24 Apr 2008 10:26:04 +0800
From: Song Haibin <melodysong@huawei.com>
In-reply-to: <97835A24-356F-4C0F-A515-C3EBF8236406@voxeo.com>
To: 'Dan York' <dyork@voxeo.com>, "'David A. Bryan'" <dbryan@sipeerior.com>
Message-id: <004201c8a5b2$8bc95b50$4c09a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Office Outlook 11
Thread-index: Acilqlpqzvhl46rPRESFWb9C9M2tcwABNdPA
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
Subject: Re: [P2PSIP] Terminology - no WG names
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

>-----Original Message-----
>From: p2psip-bounces@ietf.org [mailto:p2psip-bounces@ietf.org] On Behalf Of
>Dan York
>Sent: Thursday, April 24, 2008 9:27 AM
>To: David A. Bryan
>Cc: P2PSIP Mailing List
>Subject: Re: [P2PSIP] Terminology - no WG names
>
>
>On Apr 23, 2008, at 3:51 PM, David A. Bryan wrote:
>>
>> Not a bad idea, from my perspective. I think early on we did it to
>> distinguish what we talking about from the more general term, but
>> eliminating the P2PSIP labels sounds ok to me. Interested to see what
>> others think.
>
>DY> +1  Makes sense to not have the WG label in there.

[Song] +1 Agree, although I don't think "resource discovery overlay" is an
appropriate term for p2p overlay.

>>
>>> On a related note, I would also suggest changing 'peer ID' to 'node
>>> ID', since we seem to have some agreement that clients, as future
>>> peers, would be identified by the same construct. But saying "a
>>> client
>>> has a peer ID, but isn't a peer" doesn't seem to further
>>> understanding.
>>
>> There was a very long discussion about peer vs. node, and the
>> consensus was that the literature preferred peer to node. I know way
>> back, in the very first P2PSIP draft submitted, I used node
>> everywhere, and actually preferred it to peer. When we decided to
>> change it, I did so in all my drafts. I actually think this is one of
>> those where we could argue all day back and forth about it, and the
>> discussion would be "Full of sound and fury, signifying nothing". I
>> don't really care from a technical perspective, but I'd be willing to
>> bet $10 we could spend many more hours debating it, and someone would
>> still bring it up and propose to flip it again in 6 months (and
>> possibly with good, reasons too -- it's just there are good arguments
>> on both side).
>
>DY> With P2P in general getting more attention these days, has the
>literature changed at all in relation to 'peer' vs 'node'?
>
>DY> I would be inclined to agree with your original usage. To me,
>"node" merely indicates that a device/program/whatever is a connection
>point on a network (or network overlay), while "peer" implies a
>"relationship" between the device/program/whatever and other similar
>objects.
>
>DY> "Node" to me does not have the relationship baggage. It just "is".
>
>DY> However, I can also see where this could very easily go down a
>semantic rathole and be one of those things that could consume
>zillions of electrons and hours of our time debating.

[Song] Both "peer" and "node" are okay with me.

>DY> I agree with Henry that a centralized glossary makes sense, but
>I'm a little bit confused - isn't that what the 'concepts' document is
>supposed to be? ( http://tools.ietf.org/html/draft-ietf-p2psip-concepts-01
>  ) While Henning did not explicitly state the draft he was referring
>to, I assumed it was this one.

[Song] I think the concept and terminology draft is a centralized glossary
for the WG. If there are divergent opinions on the terminology, we should
discuss them in the mailing list or at the WG meeting, and the authors
should update the terminology draft according to the consensus.


>

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


From p2psip-bounces@ietf.org  Wed Apr 23 20:27:20 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C984A28C11A;
	Wed, 23 Apr 2008 20:27:20 -0700 (PDT)
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 473AA3A688E
	for <p2psip@core3.amsl.com>; Wed, 23 Apr 2008 20:27:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
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 ZjiWw8w-MzDX for <p2psip@core3.amsl.com>;
	Wed, 23 Apr 2008 20:27:18 -0700 (PDT)
Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.224])
	by core3.amsl.com (Postfix) with ESMTP id C92A13A6C02
	for <p2psip@ietf.org>; Wed, 23 Apr 2008 20:26:57 -0700 (PDT)
Received: by wr-out-0506.google.com with SMTP id 50so1767405wra.13
	for <p2psip@ietf.org>; Wed, 23 Apr 2008 20:27:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=uUa38I02ii/f0SPcuenNj4W7IHTsxnCiuJolJ8dKnLs=;
	b=Hlj3ld1XdWrcYLcOLsQFyM4Hid6W7Y2BmGt6nrzSao0OaQAHmXt88OpqS2LmE0BqYc2G/Bl3O6vO1yDCs/pPABvm7052So9bXIE2dfYTBVv3e4b0tZHN6s6bo6Y5Ir7wtVcy7iK8IVdz3EzQAE9gDUlzcAY3w8wucVVLHeAmV8c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=ChFsKnykT8Gcct3VQe7Q+KXUTocQ5ySa4/t7PGjiGY5upjVlUPGz+5vexKNABRg07BwqFJbp8VKO8izNsLgMZrpLYGmY4o3NuJACzTjNAbZ6HR37LmZgr1tKlX4EREbRz+OlkB4MWaKpg6GP/1VjHp1iZC0oGg98XHk9OOKEay0=
Received: by 10.141.141.3 with SMTP id t3mr991400rvn.72.1209007622232;
	Wed, 23 Apr 2008 20:27:02 -0700 (PDT)
Received: by 10.141.123.10 with HTTP; Wed, 23 Apr 2008 20:27:02 -0700 (PDT)
Message-ID: <7b683f3f0804232027x7ede29el22a7866fcf0285e7@mail.gmail.com>
Date: Wed, 23 Apr 2008 23:27:02 -0400
From: "Eunsoo Shim" <eunsooshim@gmail.com>
To: "Song Haibin" <melodysong@huawei.com>
In-Reply-To: <004201c8a5b2$8bc95b50$4c09a40a@china.huawei.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <97835A24-356F-4C0F-A515-C3EBF8236406@voxeo.com>
	<004201c8a5b2$8bc95b50$4c09a40a@china.huawei.com>
Cc: P2PSIP Mailing List <p2psip@ietf.org>
Subject: Re: [P2PSIP] Terminology - no WG names
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

I also agree to dropping the WG name from the names of the terms.
Since we distinguish Peers from Clients, changing 'Peer ID' to 'Node
ID' is a good idea since it makes sense to assign an ID to a Client
and there is no reason to distinguish Client IDs and Peer IDs.

Regarding P2P glossary, I don't think the intention of the concept and
terminology draft was to write a comprehensive P2P glossary document.
The initial objective was to do a ground work to help defining the
charter and thus the authors initially tried to focus on terms and
concepts relevant to defining the charter. Now the draft should
provide an overview of the key concepts and frequently used
terminology. It is probably not easy to say when the collected
terminology is comprehensive. Maybe we can try to extend the
terminology section in the current concept and terminology draft to
cover most terms frequently used in P2P literature and draft submitted
in the WG.

Thanks.

Eunsoo


On Wed, Apr 23, 2008 at 10:26 PM, Song Haibin <melodysong@huawei.com> wrote:
> >-----Original Message-----
>  >From: p2psip-bounces@ietf.org [mailto:p2psip-bounces@ietf.org] On Behalf Of
>
> >Dan York
>  >Sent: Thursday, April 24, 2008 9:27 AM
>  >To: David A. Bryan
>  >Cc: P2PSIP Mailing List
>  >Subject: Re: [P2PSIP] Terminology - no WG names
>  >
>  >
>  >On Apr 23, 2008, at 3:51 PM, David A. Bryan wrote:
>  >>
>  >> Not a bad idea, from my perspective. I think early on we did it to
>  >> distinguish what we talking about from the more general term, but
>  >> eliminating the P2PSIP labels sounds ok to me. Interested to see what
>  >> others think.
>  >
>  >DY> +1  Makes sense to not have the WG label in there.
>
>  [Song] +1 Agree, although I don't think "resource discovery overlay" is an
>  appropriate term for p2p overlay.
>
>
>
>  >>
>  >>> On a related note, I would also suggest changing 'peer ID' to 'node
>  >>> ID', since we seem to have some agreement that clients, as future
>  >>> peers, would be identified by the same construct. But saying "a
>  >>> client
>  >>> has a peer ID, but isn't a peer" doesn't seem to further
>  >>> understanding.
>  >>
>  >> There was a very long discussion about peer vs. node, and the
>  >> consensus was that the literature preferred peer to node. I know way
>  >> back, in the very first P2PSIP draft submitted, I used node
>  >> everywhere, and actually preferred it to peer. When we decided to
>  >> change it, I did so in all my drafts. I actually think this is one of
>  >> those where we could argue all day back and forth about it, and the
>  >> discussion would be "Full of sound and fury, signifying nothing". I
>  >> don't really care from a technical perspective, but I'd be willing to
>  >> bet $10 we could spend many more hours debating it, and someone would
>  >> still bring it up and propose to flip it again in 6 months (and
>  >> possibly with good, reasons too -- it's just there are good arguments
>  >> on both side).
>  >
>  >DY> With P2P in general getting more attention these days, has the
>  >literature changed at all in relation to 'peer' vs 'node'?
>  >
>  >DY> I would be inclined to agree with your original usage. To me,
>  >"node" merely indicates that a device/program/whatever is a connection
>  >point on a network (or network overlay), while "peer" implies a
>  >"relationship" between the device/program/whatever and other similar
>  >objects.
>  >
>  >DY> "Node" to me does not have the relationship baggage. It just "is".
>  >
>  >DY> However, I can also see where this could very easily go down a
>  >semantic rathole and be one of those things that could consume
>  >zillions of electrons and hours of our time debating.
>
>  [Song] Both "peer" and "node" are okay with me.
>
>
>  >DY> I agree with Henry that a centralized glossary makes sense, but
>  >I'm a little bit confused - isn't that what the 'concepts' document is
>  >supposed to be? ( http://tools.ietf.org/html/draft-ietf-p2psip-concepts-01
>  >  ) While Henning did not explicitly state the draft he was referring
>  >to, I assumed it was this one.
>
>  [Song] I think the concept and terminology draft is a centralized glossary
>  for the WG. If there are divergent opinions on the terminology, we should
>  discuss them in the mailing list or at the WG meeting, and the authors
>  should update the terminology draft according to the consensus.
>
>
>
>
>  >
>
>  _______________________________________________
>  P2PSIP mailing list
>  P2PSIP@ietf.org
>  https://www.ietf.org/mailman/listinfo/p2psip
>



-- 
Eunsoo
_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www.ietf.org/mailman/listinfo/p2psip


From p2psip-bounces@ietf.org  Thu Apr 24 02:15:16 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5E24F3A6949;
	Thu, 24 Apr 2008 02:15:16 -0700 (PDT)
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 1CDC73A692A
	for <p2psip@core3.amsl.com>; Thu, 24 Apr 2008 02:15:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 IkJKuDSYAyxV for <p2psip@core3.amsl.com>;
	Thu, 24 Apr 2008 02:15:12 -0700 (PDT)
Received: from jalapeno.cc.columbia.edu (jalapeno.cc.columbia.edu
	[128.59.29.5]) by core3.amsl.com (Postfix) with ESMTP id 9D8783A68D3
	for <p2psip@ietf.org>; Thu, 24 Apr 2008 02:15:12 -0700 (PDT)
Received: from [10.34.1.94] (80-254-78-2.dynamic.monzoon.net [80.254.78.2])
	(user=hgs10 mech=PLAIN bits=0)
	by jalapeno.cc.columbia.edu (8.14.1/8.14.1) with ESMTP id
	m3O9F1xe005152
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 24 Apr 2008 05:15:04 -0400 (EDT)
Message-Id: <8364343B-9E10-43A4-AC38-156241BB83F7@cs.columbia.edu>
From: Henning Schulzrinne <hgs@cs.columbia.edu>
To: Song Haibin <melodysong@huawei.com>
In-Reply-To: <004201c8a5b2$8bc95b50$4c09a40a@china.huawei.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Thu, 24 Apr 2008 05:15:01 -0400
References: <004201c8a5b2$8bc95b50$4c09a40a@china.huawei.com>
X-Mailer: Apple Mail (2.919.2)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.63 on 128.59.29.5
Cc: P2PSIP Mailing List <p2psip@ietf.org>
Subject: Re: [P2PSIP] Terminology - no WG names
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

> [Song] +1 Agree, although I don't think "resource discovery overlay"  
> is an
> appropriate term for p2p overlay.
>

Why not? If not, please suggest a better alternative.

>
> [Song] I think the concept and terminology draft is a centralized  
> glossary
> for the WG. If there are divergent opinions on the terminology, we  
> should
> discuss them in the mailing list or at the WG meeting, and the authors
> should update the terminology draft according to the consensus.
>

That's the point of my email :-)


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


From p2psip-bounces@ietf.org  Thu Apr 24 02:18:15 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BFBCB28C11C;
	Thu, 24 Apr 2008 02:18:15 -0700 (PDT)
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 B5EBE28C110
	for <p2psip@core3.amsl.com>; Thu, 24 Apr 2008 02:18:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 WnRXX29E0eaL for <p2psip@core3.amsl.com>;
	Thu, 24 Apr 2008 02:18:13 -0700 (PDT)
Received: from brinza.cc.columbia.edu (brinza.cc.columbia.edu [128.59.29.8])
	by core3.amsl.com (Postfix) with ESMTP id 54A6B28C0E4
	for <p2psip@ietf.org>; Thu, 24 Apr 2008 02:18:13 -0700 (PDT)
Received: from [10.34.1.94] (80-254-78-2.dynamic.monzoon.net [80.254.78.2])
	(user=hgs10 mech=PLAIN bits=0)
	by brinza.cc.columbia.edu (8.14.1/8.14.1) with ESMTP id m3O9IDTH000015
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 24 Apr 2008 05:18:14 -0400 (EDT)
Message-Id: <BDBAAEE1-CA2A-4673-A455-F4DD9E4F0697@cs.columbia.edu>
From: Henning Schulzrinne <hgs@cs.columbia.edu>
To: Henry Sinnreich <hsinnrei@adobe.com>
In-Reply-To: <C4352966.3983%hsinnrei@adobe.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Thu, 24 Apr 2008 05:18:12 -0400
References: <C4352966.3983%hsinnrei@adobe.com>
X-Mailer: Apple Mail (2.919.2)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.63 on 128.59.29.8
Cc: P2PSIP Mailing List <p2psip@ietf.org>
Subject: Re: [P2PSIP] Terminology - no WG names
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/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

Henry,

I appreciate the pointers, but there is no agreement for many of these  =

terms in the literature or the terms are very specific to either a  =

particular class of resource discovery systems (such as structured/DHT  =

ones) or an algorithm. I think everyone would like to use existing  =

terminology as much as possible.

Henning

On Apr 23, 2008, at 6:59 PM, Henry Sinnreich wrote:

> I suppose a good start would be to agree on some reference sources  =

> on P2P,
> for example:
>
> * Wikipedia has an excellent P2P tutorial section with well known  =

> references
>
> http://en.wikipedia.org/wiki/Peer-to-peer
>
> * The openDHT publications
>
> http://opendht.org/pubs.html
>
> Just these two sources would be a good start, though folks on the  =

> list may
> well have additional sources to suggest.
>
> What this discussions proves however is that instead every I-D in  =

> the P2PSIP
> WG having its own glossary, the WG should better invite someone to  =

> write a
> glossary paper on its own that can be discussed and agreed on. This  =

> was not
> in the charter, but may be a good option, given the work involved.
>
> Another option is for the terminology paper by Dean Willis et al. to  =

> be
> updated with an updated and comprehensive glossary for P2P.
>
> What do you think?
>
> Henry
>
>
> On 4/23/08 4:16 PM, "David A. Bryan" <dbryan@sipeerior.com> wrote:
>
>> Most of the terms were very carefully picked to match the technical
>> literature as much as possible. That said, the literature sometimes  =

>> is
>> not consistent between different papers...
>>
>> I agree we should try to reflect the literature, and believe that we
>> for the most part do in the current draft (
>>
>> David (as individual)
>>
>> On Wed, Apr 23, 2008 at 5:01 PM, Victor Pascual =C1vila
>> <victor.pascual.avila@gmail.com> wrote:
>>> Hi,
>>>
>>>
>>> On Wed, Apr 23, 2008 at 9:51 PM, David A. Bryan <dbryan@sipeerior.com =

>>> >
>>> wrote:
>>>> Not a bad idea, from my perspective. I think early on we did it to
>>>> distinguish what we talking about from the more general term, but
>>>> eliminating the P2PSIP labels sounds ok to me. Interested to see  =

>>>> what
>>>> others think.
>>>
>>> I agree on using no P2PSIP labels and suggest that we use P2P
>>> terminology common in the technical literature.
>>>
>>> Thanks,
>>> --
>>> Victor Pascual =C1vila
>>>
>>
>>
>
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www.ietf.org/mailman/listinfo/p2psip

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


From p2psip-bounces@ietf.org  Thu Apr 24 03:11:53 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 50B5C3A6913;
	Thu, 24 Apr 2008 03:11:53 -0700 (PDT)
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 612743A6BAC
	for <p2psip@core3.amsl.com>; Thu, 24 Apr 2008 03:11:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 
	RDNS_NONE=0.1]
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 nDYiS6RvdlJu for <p2psip@core3.amsl.com>;
	Thu, 24 Apr 2008 03:11:49 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [61.144.161.53])
	by core3.amsl.com (Postfix) with ESMTP id 7367C3A67E1
	for <p2psip@ietf.org>; Thu, 24 Apr 2008 03:11:11 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JZT00EI1QPTCW@szxga01-in.huawei.com> for
	p2psip@ietf.org; Thu, 24 Apr 2008 18:05:53 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JZT0074AQPTJN@szxga01-in.huawei.com> for
	p2psip@ietf.org; Thu, 24 Apr 2008 18:05:53 +0800 (CST)
Received: from s64081 ([10.164.9.76])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JZT00LRPQPSFM@szxml04-in.huawei.com> for
	p2psip@ietf.org; Thu, 24 Apr 2008 18:05:53 +0800 (CST)
Date: Thu, 24 Apr 2008 18:05:52 +0800
From: Song Haibin <melodysong@huawei.com>
In-reply-to: <8364343B-9E10-43A4-AC38-156241BB83F7@cs.columbia.edu>
To: 'Henning Schulzrinne' <hgs@cs.columbia.edu>
Message-id: <005601c8a5f2$c7badcc0$4c09a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Office Outlook 11
Thread-index: Acil67mcEvfYeVeZR2GfKIU6PkTYFAABDLtQ
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
Subject: Re: [P2PSIP] Terminology - no WG names
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

>-----Original Message-----
>From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]
>Sent: Thursday, April 24, 2008 5:15 PM
>To: Song Haibin
>Cc: P2PSIP Mailing List
>Subject: Re: [P2PSIP] Terminology - no WG names
>
>> [Song] +1 Agree, although I don't think "resource discovery overlay"
>> is an
>> appropriate term for p2p overlay.
>>
>
>Why not? If not, please suggest a better alternative.
>
[Song] I think most p2p overlays, no matter structured or unstructured, are
used for resource discovery, e.g. file sharing, p2p VoIP and etc. I feel
that if we use the term "resource discovery overlay" for now used "P2PSIP
Overlay", we do not distinguish the application "SIP" from other
applications. I don't know if we need the term "P2PSIP Overlay", or we just
need a "P2P Overlay". For P2PSIP, we may just call it "SIP Over P2P".
>>
>> [Song] I think the concept and terminology draft is a centralized
>> glossary
>> for the WG. If there are divergent opinions on the terminology, we
>> should
>> discuss them in the mailing list or at the WG meeting, and the authors
>> should update the terminology draft according to the consensus.
>>
>
>That's the point of my email :-)


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


From p2psip-bounces@ietf.org  Thu Apr 24 10:08:25 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 12C5F28C1A0;
	Thu, 24 Apr 2008 10:08:25 -0700 (PDT)
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 5072F3A6C6E
	for <p2psip@core3.amsl.com>; Thu, 24 Apr 2008 10:08:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, 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 7fycNMWTKw3K for <p2psip@core3.amsl.com>;
	Thu, 24 Apr 2008 10:08:22 -0700 (PDT)
Received: from exprod6og101.obsmtp.com (exprod6og101.obsmtp.com [64.18.1.181])
	by core3.amsl.com (Postfix) with ESMTP id EE1043A6CBD
	for <p2psip@ietf.org>; Thu, 24 Apr 2008 10:08:15 -0700 (PDT)
Received: from source ([192.150.8.22]) by exprod6ob101.postini.com
	([64.18.5.12]) with SMTP; Thu, 24 Apr 2008 10:08:20 PDT
Received: from inner-relay-1.corp.adobe.com ([153.32.1.51])
	by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	m3OH8IJV024456; Thu, 24 Apr 2008 10:08:18 -0700 (PDT)
Received: from fe1.corp.adobe.com (fe1.corp.adobe.com [10.8.192.70])
	by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	m3OH8GI2028761; Thu, 24 Apr 2008 10:08:16 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 24 Apr 2008 10:08:16 -0700
Received: from 10.7.242.167 ([10.7.242.167]) by namail5.corp.adobe.com
	([10.8.192.88]) with Microsoft Exchange Server HTTP-DAV ; 
	Thu, 24 Apr 2008 17:08:16 +0000
User-Agent: Microsoft-Entourage/12.1.0.080305
Date: Thu, 24 Apr 2008 12:08:15 -0500
From: Henry Sinnreich <hsinnrei@adobe.com>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Message-ID: <C43628AF.39FC%hsinnrei@adobe.com>
Thread-Topic: [P2PSIP] Terminology - no WG names
Thread-Index: AcimLcikYnrU21ZplUmENtyNQf7Tsg==
In-Reply-To: <BDBAAEE1-CA2A-4673-A455-F4DD9E4F0697@cs.columbia.edu>
Mime-version: 1.0
X-OriginalArrivalTime: 24 Apr 2008 17:08:16.0508 (UTC)
	FILETIME=[C98A43C0:01C8A62D]
Cc: P2PSIP Mailing List <p2psip@ietf.org>
Subject: Re: [P2PSIP] Terminology - no WG names
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/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

Henning,

>I think everyone would like to use existing
> terminology as much as possible.

Can you point us to some?

Thanks, Henry


On 4/24/08 4:18 AM, "Henning Schulzrinne" <hgs@cs.columbia.edu> wrote:

> Henry,
> =

> I appreciate the pointers, but there is no agreement for many of these
> terms in the literature or the terms are very specific to either a
> particular class of resource discovery systems (such as structured/DHT
> ones) or an algorithm. I think everyone would like to use existing
> terminology as much as possible.
> =

> Henning
> =

> On Apr 23, 2008, at 6:59 PM, Henry Sinnreich wrote:
> =

>> I suppose a good start would be to agree on some reference sources
>> on P2P,
>> for example:
>> =

>> * Wikipedia has an excellent P2P tutorial section with well known
>> references
>> =

>> http://en.wikipedia.org/wiki/Peer-to-peer
>> =

>> * The openDHT publications
>> =

>> http://opendht.org/pubs.html
>> =

>> Just these two sources would be a good start, though folks on the
>> list may
>> well have additional sources to suggest.
>> =

>> What this discussions proves however is that instead every I-D in
>> the P2PSIP
>> WG having its own glossary, the WG should better invite someone to
>> write a
>> glossary paper on its own that can be discussed and agreed on. This
>> was not
>> in the charter, but may be a good option, given the work involved.
>> =

>> Another option is for the terminology paper by Dean Willis et al. to
>> be
>> updated with an updated and comprehensive glossary for P2P.
>> =

>> What do you think?
>> =

>> Henry
>> =

>> =

>> On 4/23/08 4:16 PM, "David A. Bryan" <dbryan@sipeerior.com> wrote:
>> =

>>> Most of the terms were very carefully picked to match the technical
>>> literature as much as possible. That said, the literature sometimes
>>> is
>>> not consistent between different papers...
>>> =

>>> I agree we should try to reflect the literature, and believe that we
>>> for the most part do in the current draft (
>>> =

>>> David (as individual)
>>> =

>>> On Wed, Apr 23, 2008 at 5:01 PM, Victor Pascual =C1vila
>>> <victor.pascual.avila@gmail.com> wrote:
>>>> Hi,
>>>> =

>>>> =

>>>> On Wed, Apr 23, 2008 at 9:51 PM, David A. Bryan <dbryan@sipeerior.com
>>>>> =

>>>> wrote:
>>>>> Not a bad idea, from my perspective. I think early on we did it to
>>>>> distinguish what we talking about from the more general term, but
>>>>> eliminating the P2PSIP labels sounds ok to me. Interested to see
>>>>> what
>>>>> others think.
>>>> =

>>>> I agree on using no P2PSIP labels and suggest that we use P2P
>>>> terminology common in the technical literature.
>>>> =

>>>> Thanks,
>>>> --
>>>> Victor Pascual =C1vila
>>>> =

>>> =

>>> =

>> =

>> _______________________________________________
>> P2PSIP mailing list
>> P2PSIP@ietf.org
>> https://www.ietf.org/mailman/listinfo/p2psip
> =


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


From p2psip-bounces@ietf.org  Thu Apr 24 10:29:48 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8914228C26B;
	Thu, 24 Apr 2008 10:29:48 -0700 (PDT)
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 194E73A6B7E
	for <p2psip@core3.amsl.com>; Thu, 24 Apr 2008 10:29:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.452
X-Spam-Level: 
X-Spam-Status: No, score=-2.452 tagged_above=-999 required=5 tests=[AWL=0.147, 
	BAYES_00=-2.599]
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 zM2ScUQyLbQA for <p2psip@core3.amsl.com>;
	Thu, 24 Apr 2008 10:29:46 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 3E8583A68B7
	for <p2psip@ietf.org>; Thu, 24 Apr 2008 10:29:46 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m3OHTZPf028785
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 24 Apr 2008 12:29:36 -0500
Message-Id: <CCF9DC70-0717-4432-89B3-CCEFA084D517@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Henry Sinnreich <hsinnrei@adobe.com>
In-Reply-To: <C4352966.3983%hsinnrei@adobe.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Thu, 24 Apr 2008 12:29:29 -0500
References: <C4352966.3983%hsinnrei@adobe.com>
X-Mailer: Apple Mail (2.919.2)
Cc: P2PSIP Mailing List <p2psip@ietf.org>
Subject: Re: [P2PSIP] Terminology - no WG names
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org


On Apr 23, 2008, at 5:59 PM, Henry Sinnreich wrote:
> Another option is for the terminology paper by Dean Willis et al. to  
> be
> updated with an updated and comprehensive glossary for P2P.

Sure -- bring vocabulary words to the list, and once we have agreement  
on what they mean, we'll stick 'em into the draft.

That might not be as easy as we think, and it's part of why everything  
currently has a "p2psip" label in front of it.

A P2PSIP overlay is not a BitTorrent overlay. For example, there's no  
concept of discretely bounded namespaces in BitTorrent.  And as far as  
I know, BitTorrent has no concept of "resource discovery" -- we use  
web sites to distribute the resource keys. But we still think of  
BitTorrent as P2P and an overlay . . .

So some of our terms are going to have names that are used in other  
literature to mean something that's not quite exactly the same thing.  
As long as we have them prefixed with "p2psip", it's clear that we're  
referring to "our" definition.

Presumably, we understand this and can drop the "p2psip" part from the  
names, but still know it is there.

But eventually some joker is going to pop up and say "You can't call  
this thing a Node, because a Node is another name for a Peer, and it's  
not a Peer, it's a Client" or some such, and I'm going to have to hit  
him with a blunt object. That's more-or-less already happened, and the  
blunt object we used was the concepts draft, with its mind-numbing  
repetition of the "p2psip" modifier.

--
Dean

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


From p2psip-bounces@ietf.org  Thu Apr 24 12:59:42 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C621F3A6B6C;
	Thu, 24 Apr 2008 12:59:42 -0700 (PDT)
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 B74FF3A6D4E
	for <p2psip@core3.amsl.com>; Thu, 24 Apr 2008 12:59:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 pEMJEEN1NFFS for <p2psip@core3.amsl.com>;
	Thu, 24 Apr 2008 12:59:39 -0700 (PDT)
Received: from jalapeno.cc.columbia.edu (jalapeno.cc.columbia.edu
	[128.59.29.5]) by core3.amsl.com (Postfix) with ESMTP id 3936E3A6D0A
	for <p2psip@ietf.org>; Thu, 24 Apr 2008 12:59:39 -0700 (PDT)
Received: from [10.5.0.65] ([62.168.58.2]) (user=hgs10 mech=PLAIN bits=0)
	by jalapeno.cc.columbia.edu (8.14.1/8.14.1) with ESMTP id
	m3OJxc46018876
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 24 Apr 2008 15:59:40 -0400 (EDT)
Message-Id: <F279044E-4A96-4440-B1A7-1A38A602CAF3@cs.columbia.edu>
From: Henning Schulzrinne <hgs@cs.columbia.edu>
To: Song Haibin <melodysong@huawei.com>
In-Reply-To: <005601c8a5f2$c7badcc0$4c09a40a@china.huawei.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Thu, 24 Apr 2008 15:59:32 -0400
References: <005601c8a5f2$c7badcc0$4c09a40a@china.huawei.com>
X-Mailer: Apple Mail (2.919.2)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.63 on 128.59.29.5
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
Subject: Re: [P2PSIP] Terminology - no WG names
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

>

That's a feature, not a bug :-) The core P2P protocol being designed  
does not depend on SIP, even though it naturally supports that  
application.

> [Song] I think most p2p overlays, no matter structured or  
> unstructured, are
> used for resource discovery, e.g. file sharing, p2p VoIP and etc. I  
> feel
> that if we use the term "resource discovery overlay" for now used  
> "P2PSIP
> Overlay", we do not distinguish the application "SIP" from other
> applications. I don't know if we need the term "P2PSIP Overlay", or  
> we just
> need a "P2P Overlay". For P2PSIP, we may just call it "SIP Over P2P".
>>>
_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www.ietf.org/mailman/listinfo/p2psip


From p2psip-bounces@ietf.org  Thu Apr 24 21:39:34 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 78FA13A6C67;
	Thu, 24 Apr 2008 21:39:34 -0700 (PDT)
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 2D82A3A6AC3
	for <p2psip@core3.amsl.com>; Thu, 24 Apr 2008 21:39:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.387
X-Spam-Level: 
X-Spam-Status: No, score=-1.387 tagged_above=-999 required=5 tests=[AWL=1.212, 
	BAYES_00=-2.599]
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 SKebsrrdBj3k for <p2psip@core3.amsl.com>;
	Thu, 24 Apr 2008 21:39:31 -0700 (PDT)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211])
	by core3.amsl.com (Postfix) with ESMTP id 801483A6BF4
	for <p2psip@ietf.org>; Thu, 24 Apr 2008 21:39:31 -0700 (PDT)
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JZV00HEZ69ZAK@usaga01-in.huawei.com> for
	p2psip@ietf.org; Thu, 24 Apr 2008 21:39:35 -0700 (PDT)
Received: from huawei.com ([172.17.1.31])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JZV00KHA69WLS@usaga01-in.huawei.com> for
	p2psip@ietf.org; Thu, 24 Apr 2008 21:39:34 -0700 (PDT)
Received: from [172.24.1.6] (Forwarded-For: [70.23.122.87])
	by szxmc03-in.huawei.com (mshttpd); Fri, 25 Apr 2008 00:39:24 -0400
Date: Fri, 25 Apr 2008 00:39:24 -0400
From: jiangxingfeng 36340 <jiang.x.f@huawei.com>
In-reply-to: <7b683f3f0804232027x7ede29el22a7866fcf0285e7@mail.gmail.com>
To: Eunsoo Shim <eunsooshim@gmail.com>
Message-id: <fafeaa058d985.8d985fafeaa05@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.14 (built Aug  8 2006)
Content-language: zh-CN
Content-disposition: inline
X-Accept-Language: zh-CN
Priority: normal
References: <97835A24-356F-4C0F-A515-C3EBF8236406@voxeo.com>
	<004201c8a5b2$8bc95b50$4c09a40a@china.huawei.com>
	<7b683f3f0804232027x7ede29el22a7866fcf0285e7@mail.gmail.com>
Cc: P2PSIP Mailing List <p2psip@ietf.org>
Subject: Re: [P2PSIP] Terminology - no WG names
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

Hi, all:

IMO, another important work is to make clear the assumptions of the future work, such as:
1. Which kinds of data will be stored in the overlay? what's the reasonable size of the data?

2. How much churn of the overlay where the peer protocol will be applied? The pratical way is to use the experimental data from the real existing system. I am not sure the resulting peer protcol could work in all cases. 

3. How much percent of the public nodes in the overlay is reasonable? 

IMHO, if we don't work it out before we come up with the protocol, I think, it's hard to get consensus on the proposal, because we have no common assumptions. 

Comments?

Regards
JiangXingFeng




> I also agree to dropping the WG name from the names of the terms.
> Since we distinguish Peers from Clients, changing 'Peer ID' to 'Node
> ID' is a good idea since it makes sense to assign an ID to a Client
> and there is no reason to distinguish Client IDs and Peer IDs.
> 
> Regarding P2P glossary, I don't think the intention of the concept and
> terminology draft was to write a comprehensive P2P glossary document.
> The initial objective was to do a ground work to help defining the
> charter and thus the authors initially tried to focus on terms and
> concepts relevant to defining the charter. Now the draft should
> provide an overview of the key concepts and frequently used
> terminology. It is probably not easy to say when the collected
> terminology is comprehensive. Maybe we can try to extend the
> terminology section in the current concept and terminology draft to
> cover most terms frequently used in P2P literature and draft submitted
> in the WG.
> 
> Thanks.
> 
> Eunsoo
> 
> 
> On Wed, Apr 23, 2008 at 10:26 PM, Song Haibin 
> <melodysong@huawei.com> wrote:
> > >-----Original Message-----
> >  >From: p2psip-bounces@ietf.org [mailto:p2psip-bounces@ietf.org] 
> On Behalf Of
> >
> > >Dan York
> >  >Sent: Thursday, April 24, 2008 9:27 AM
> >  >To: David A. Bryan
> >  >Cc: P2PSIP Mailing List
> >  >Subject: Re: [P2PSIP] Terminology - no WG names
> >  >
> >  >
> >  >On Apr 23, 2008, at 3:51 PM, David A. Bryan wrote:
> >  >>
> >  >> Not a bad idea, from my perspective. I think early on we did 
> it to
> >  >> distinguish what we talking about from the more general 
> term, but
> >  >> eliminating the P2PSIP labels sounds ok to me. Interested to 
> see what
> >  >> others think.
> >  >
> >  >DY> +1  Makes sense to not have the WG label in there.
> >
> >  [Song] +1 Agree, although I don't think "resource discovery 
> overlay" is an
> >  appropriate term for p2p overlay.
> >
> >
> >
> >  >>
> >  >>> On a related note, I would also suggest changing 'peer ID' 
> to 'node
> >  >>> ID', since we seem to have some agreement that clients, as 
> future>  >>> peers, would be identified by the same construct. But 
> saying "a
> >  >>> client
> >  >>> has a peer ID, but isn't a peer" doesn't seem to further
> >  >>> understanding.
> >  >>
> >  >> There was a very long discussion about peer vs. node, and the
> >  >> consensus was that the literature preferred peer to node. I 
> know way
> >  >> back, in the very first P2PSIP draft submitted, I used node
> >  >> everywhere, and actually preferred it to peer. When we 
> decided to
> >  >> change it, I did so in all my drafts. I actually think this 
> is one of
> >  >> those where we could argue all day back and forth about it, 
> and the
> >  >> discussion would be "Full of sound and fury, signifying 
> nothing". I
> >  >> don't really care from a technical perspective, but I'd be 
> willing to
> >  >> bet $10 we could spend many more hours debating it, and 
> someone would
> >  >> still bring it up and propose to flip it again in 6 months (and
> >  >> possibly with good, reasons too -- it's just there are good 
> arguments>  >> on both side).
> >  >
> >  >DY> With P2P in general getting more attention these days, has the
> >  >literature changed at all in relation to 'peer' vs 'node'?
> >  >
> >  >DY> I would be inclined to agree with your original usage. To me,
> >  >"node" merely indicates that a device/program/whatever is a 
> connection>  >point on a network (or network overlay), while 
> "peer" implies a
> >  >"relationship" between the device/program/whatever and other 
> similar>  >objects.
> >  >
> >  >DY> "Node" to me does not have the relationship baggage. It 
> just "is".
> >  >
> >  >DY> However, I can also see where this could very easily go 
> down a
> >  >semantic rathole and be one of those things that could consume
> >  >zillions of electrons and hours of our time debating.
> >
> >  [Song] Both "peer" and "node" are okay with me.
> >
> >
> >  >DY> I agree with Henry that a centralized glossary makes 
> sense, but
> >  >I'm a little bit confused - isn't that what the 'concepts' 
> document is
> >  >supposed to be? ( http://tools.ietf.org/html/draft-ietf-p2psip-
> concepts-01
> >  >  ) While Henning did not explicitly state the draft he was 
> referring>  >to, I assumed it was this one.
> >
> >  [Song] I think the concept and terminology draft is a 
> centralized glossary
> >  for the WG. If there are divergent opinions on the terminology, 
> we should
> >  discuss them in the mailing list or at the WG meeting, and the 
> authors>  should update the terminology draft according to the 
> consensus.>
> >
> >
> >
> >  >
> >
> >  _______________________________________________
> >  P2PSIP mailing list
> >  P2PSIP@ietf.org
> >  https://www.ietf.org/mailman/listinfo/p2psip
> >
> 
> 
> 
> -- 
> Eunsoo
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www.ietf.org/mailman/listinfo/p2psip
> 
_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www.ietf.org/mailman/listinfo/p2psip


From p2psip-bounces@ietf.org  Fri Apr 25 00:10:42 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 26EDD28C201;
	Fri, 25 Apr 2008 00:10:42 -0700 (PDT)
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 15C5628C201
	for <p2psip@core3.amsl.com>; Fri, 25 Apr 2008 00:10:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 sv8YUpIaBlOL for <p2psip@core3.amsl.com>;
	Fri, 25 Apr 2008 00:10:40 -0700 (PDT)
Received: from jalapeno.cc.columbia.edu (jalapeno.cc.columbia.edu
	[128.59.29.5]) by core3.amsl.com (Postfix) with ESMTP id 1902928C100
	for <p2psip@ietf.org>; Fri, 25 Apr 2008 00:10:40 -0700 (PDT)
Received: from [10.5.0.65] ([62.168.58.2]) (user=hgs10 mech=PLAIN bits=0)
	by jalapeno.cc.columbia.edu (8.14.1/8.14.1) with ESMTP id
	m3P7APGd010063
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 25 Apr 2008 03:10:34 -0400 (EDT)
Message-Id: <4D33217C-213A-4704-AA32-DAA0156D281B@cs.columbia.edu>
From: Henning Schulzrinne <hgs@cs.columbia.edu>
To: jiangxingfeng 36340 <jiang.x.f@huawei.com>
In-Reply-To: <fafeaa058d985.8d985fafeaa05@huawei.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Fri, 25 Apr 2008 03:10:21 -0400
References: <97835A24-356F-4C0F-A515-C3EBF8236406@voxeo.com>
	<004201c8a5b2$8bc95b50$4c09a40a@china.huawei.com>
	<7b683f3f0804232027x7ede29el22a7866fcf0285e7@mail.gmail.com>
	<fafeaa058d985.8d985fafeaa05@huawei.com>
X-Mailer: Apple Mail (2.919.2)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.63 on 128.59.29.5
Cc: P2PSIP Mailing List <p2psip@ietf.org>
Subject: Re: [P2PSIP] Terminology - no WG names
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org


On Apr 25, 2008, at 12:39 AM, jiangxingfeng 36340 wrote:

> Hi, all:
>
> IMO, another important work is to make clear the assumptions of the  
> future work, such as:
> 1. Which kinds of data will be stored in the overlay? what's the  
> reasonable size of the data?

The only reasonable answers are: For the protocol: any and any. For a  
particular instance: whatever policy allows.


>
>
> 2. How much churn of the overlay where the peer protocol will be  
> applied? The pratical way is to use the experimental data from the  
> real existing system. I am not sure the resulting peer protcol could  
> work in all cases.

I don't think that is productive. We can't predict what churn is  
realistic, given that I can create networks with close to zero churn  
and networks with node lifetimes measured in seconds. As usual,  
performance and data availability will degrade as churn increases.


>
>
> 3. How much percent of the public nodes in the overlay is reasonable?

Anywhere from 0 to 100%. Again, a protocol design needs to be robust  
in these parameters; we're not designing a specific instance, but  
rather something that works across the Internet, present and future.  
Clearly, there will be configurations where nothing will work and  
things will work faster in 'nice' configurations, but that's about all  
we can say. Hopefully, our design will work as well as it can in any  
given circumstance.


>
>
> IMHO, if we don't work it out before we come up with the protocol, I  
> think, it's hard to get consensus on the proposal, because we have  
> no common assumptions.

I'm sorry to say that if this is required, we may as well fold now.

>
>
> Comments?
>
> Regards
> JiangXingFeng
>
>

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


From p2psip-bounces@ietf.org  Sat Apr 26 06:46:26 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 48F843A6C86;
	Sat, 26 Apr 2008 06:46:26 -0700 (PDT)
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 1CFD93A68A4
	for <p2psip@core3.amsl.com>; Sat, 26 Apr 2008 06:46:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.351
X-Spam-Level: 
X-Spam-Status: No, score=0.351 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HELO_EQ_FR=0.35]
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 IgOdaFcIckoW for <p2psip@core3.amsl.com>;
	Sat, 26 Apr 2008 06:46:21 -0700 (PDT)
Received: from smtp2b.orange.fr (smtp2b.orange.fr [80.12.242.146])
	by core3.amsl.com (Postfix) with ESMTP id 608DB3A6C1E
	for <p2psip@ietf.org>; Sat, 26 Apr 2008 06:46:20 -0700 (PDT)
Received: from me-wanadoo.net (localhost [127.0.0.1])
	by mwinf2b21.orange.fr (SMTP Server) with ESMTP id 003DB20007A8
	for <p2psip@ietf.org>; Sat, 26 Apr 2008 15:46:24 +0200 (CEST)
Received: from puffy.lan (LPuteaux-151-41-30-75.w217-128.abo.wanadoo.fr
	[217.128.82.75])
	by mwinf2b21.orange.fr (SMTP Server) with ESMTP id CB9AC20007A6
	for <p2psip@ietf.org>; Sat, 26 Apr 2008 15:46:23 +0200 (CEST)
X-ME-UUID: 20080426134623834.CB9AC20007A6@mwinf2b21.orange.fr
Message-ID: <4813322F.4090203@orange.fr>
Date: Sat, 26 Apr 2008 15:46:23 +0200
From: FORTAINE Guillaume <gui.fortaine@orange.fr>
User-Agent: Thunderbird 2.0.0.6 (X11/20071225)
MIME-Version: 1.0
To: p2psip@ietf.org
Subject: [P2PSIP] P2P
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

Hello all,

Best Regards,

Guillaume FORTAINE

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


From p2psip-bounces@ietf.org  Mon Apr 28 18:34:21 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: p2psip-archive@optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 31C133A6D33;
	Mon, 28 Apr 2008 18:34:21 -0700 (PDT)
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 339533A6D26
	for <p2psip@core3.amsl.com>; Mon, 28 Apr 2008 18:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.256
X-Spam-Level: 
X-Spam-Status: No, score=-0.256 tagged_above=-999 required=5
	tests=[AWL=-0.239, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, WHOIS_DMNBYPROXY=0.478]
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 PV5gpfBF30p8 for <p2psip@core3.amsl.com>;
	Mon, 28 Apr 2008 18:34:18 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [61.144.161.54])
	by core3.amsl.com (Postfix) with ESMTP id ADE433A6CEB
	for <p2psip@ietf.org>; Mon, 28 Apr 2008 18:34:18 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K0200IDZCCZKV@szxga02-in.huawei.com> for
	p2psip@ietf.org; Tue, 29 Apr 2008 09:34:11 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K02007CVCCZGM@szxga02-in.huawei.com> for
	p2psip@ietf.org; Tue, 29 Apr 2008 09:34:11 +0800 (CST)
Received: from s64081 ([10.164.9.76])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0K0200KH9CCZBC@szxml03-in.huawei.com> for
	p2psip@ietf.org; Tue, 29 Apr 2008 09:34:11 +0800 (CST)
Date: Tue, 29 Apr 2008 09:34:12 +0800
From: Song Haibin <melodysong@huawei.com>
To: 'P2PSIP Mailing List' <p2psip@ietf.org>
Message-id: <003601c8a999$21036460$4c09a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Office Outlook 11
Thread-index: AcipNZd9QscyTwZqSfSv5NvsiSiG4gAY3K1g
Subject: [P2PSIP] FW: The implementation code for SEP
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org


Best Regards,
Song Haibin
Email: melodysong@huawei.com
>-----Original Message-----
>From: amelampus@gmail.com [mailto:amelampus@gmail.com] On Behalf Of David
A.
>Bryan
>Sent: Monday, April 28, 2008 9:42 PM
>To: Song Haibin
>Subject: Re: The implementation code for SEP
>
>Thanks,
>
>I'll get it posted soon on P2PSIP.org.
>
>David
>
>On Sun, Apr 27, 2008 at 10:12 PM, Song Haibin <melodysong@huawei.com>
wrote:
>> Hi David,
>>
>>  Sorry for the late notification. The following is the link for Huawei's
>>  implementation of SEP peer
>>  (http://tools.ietf.org/wg/p2psip/draft-jiang-p2psip-sep-01.txt) and
>client
>>
>(http://tools.ietf.org/wg/p2psip/draft-zheng-p2psip-client-protocol-01.txt)
>>  protocol. We implement two DHT algorithms (Chord and Pastry) and the
simple
>>  NAT traversal in it. We provide the SEP code at present, and the
>>  installation guide will be provided soon.
>>
>>  The code for SEP project can be found at:
>>  http://www.savefile.com/projects/808633433
>>
>>  Please add this information to the webpage for p2psip implementations
and
>>  forward this message to P2PSIP workgroup.
>>
>>  Thanks!
>>
>>  Best Regards,
>>  Song Haibin
>>  Email: melodysong@huawei.com
>>
>>
>
>
>
>--
>David A. Bryan
>dbryan@SIPeerior.com
>+1.757.565.0101 x101
>+1.757.565.0088 (fax)
>www.SIPeerior.com

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


