From p2psip-bounces@ietf.org Mon Jan 07 08:44:22 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JBsH3-0006nK-9J; Mon, 07 Jan 2008 08:44:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JBsH1-0006iJ-3v; Mon, 07 Jan 2008 08:44:15 -0500
Received: from exprod6og105.obsmtp.com ([64.18.1.189])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1JBsH0-0006Dt-KP; Mon, 07 Jan 2008 08:44:15 -0500
Received: from source ([192.150.11.134]) by exprod6ob105.postini.com
	([64.18.5.12]) with SMTP; Mon, 07 Jan 2008 05:44:13 PST
Received: from inner-relay-3.eur.adobe.com (inner-relay-3.adobe.com
	[192.150.20.198] (may be forged))
	by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	m07Dfnin026227; Mon, 7 Jan 2008 05:41:50 -0800 (PST)
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
	m07Di6FZ003221; Mon, 7 Jan 2008 05:44:11 -0800 (PST)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by
	apacmail.pac.adobe.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 7 Jan 2008 22:44:07 +0900
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 7 Jan 2008 05:44:00 -0800
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D223AE4A7@namail5.corp.adobe.com>
In-Reply-To: <0C549DAFE1A8004D8EB57ACDD108646D070BA682@XCH-NW-2V2.nw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Discussion items for the Tuesday teleconference
Thread-Index: AchEH96vkLdr2CwpRny3bB+oZLdYwQNEMNOw
References: <0C549DAFE1A8004D8EB57ACDD108646D070BA682@XCH-NW-2V2.nw.nos.boeing.com>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Paine, Richard H" <richard.h.paine@boeing.com>, <p2psip@ietf.org>,
	<hipsec@ietf.org>
X-OriginalArrivalTime: 07 Jan 2008 13:44:07.0539 (UTC)
	FILETIME=[5FF8EC30:01C85133]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: 
Subject: [P2PSIP] Discussion items for the Tuesday teleconference
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

The paper on the Boeing HIP implementation along with the I-D:
draft-camarillo-hip-bone-00.txt is very helpful to SIP oriented people
like me who are new to HIP. Quite frankly I am close to becoming a
believer, if only some questions could be addressed and where more
details would be helpful:

1. TCP/IP stack use and implementation

If and how can the existing PCP/IP stack in Windows, OSX, Symbian and
LINUX be used or does it have to be rewritten? Is there a workaround and
if yes, can anyone share what it may look like?

Product managers would see the rewriting of the TCP/IP stack to insert
HIP as a major problem to avoid at any cost. Waiting for these OS to
support HIP does not seem a good alternative.

2. NAT traversal

VPN implementations have had problems with NAT and as a result most NAT
vendors have addressed VPN support. What is the experience with HIP
support in NAT, or how much of a problem is NAT traversal for HIP?
Are there any measurements or deployment data that can be shared?

Thanks, Henry

-----Original Message-----
From: Paine, Richard H [mailto:richard.h.paine@boeing.com]=20
Sent: Friday, December 21, 2007 4:22 PM
To: p2psip@ietf.org; hipsec@ietf.org
Subject: [P2PSIP] Boeing HIP Implementation of SIP (which is
point-to-pointsecure SIP)

At the Vancouver meeting, there was a joint meeting of the HIP and
P2PSIP groups on Friday morning.  At this meeting, Boeing committed to
sent the P2PSIP group a releasable white paper on the Boeing HIP
implementation that is, in effect, point-to-point secure SIP. =20

 <<NGI_SMA_Boeing_VoWLAN_Demo_White_Paper_12-8-07.doc>>=20
The next step beyond this is to hold a teleconference in the first or
second week of the new year to discuss this paper.  Please note that
although the identity in this example is an IPv6 address, any
cryptographic identity can be used as a name in the HIP namespace.  The
Boeing intent is to use PKI crytographic identities in the HIP
namespace.

Richard H. Paine
Success is getting what you want, happiness is liking what you get!
Cell:  206-854-8199
IPPhone:  425-373-8296
Email:  richard.h.paine@boeing.com=20


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



From p2psip-bounces@ietf.org Mon Jan 07 10:42:45 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JBu7g-0002MB-9L; Mon, 07 Jan 2008 10:42:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JBu7f-0002M2-3k; Mon, 07 Jan 2008 10:42:43 -0500
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1JBu7e-0008HI-L5; Mon, 07 Jan 2008 10:42:43 -0500
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id m07FbXe5027188
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Mon, 7 Jan 2008 07:37:34 -0800 (PST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	m07FbXcj027779; Mon, 7 Jan 2008 07:37:33 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	m07FbXCK027773; Mon, 7 Jan 2008 07:37:33 -0800 (PST)
Received: from XCH-NW-2V2.nw.nos.boeing.com ([130.247.55.18]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 7 Jan 2008 07:37:32 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:calendarmessage
MIME-Version: 1.0
Date: Mon, 7 Jan 2008 07:37:31 -0800
Message-ID: <0C549DAFE1A8004D8EB57ACDD108646D06520831@XCH-NW-2V2.nw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: P2PSIP and HIP Joint Meeting on the Boeing VOIP HIPImplementation
Thread-Index: AchEJF7WXDz4rIgVQHuS1XYc5gSeRANHthmw
From: "Paine, Richard H" <richard.h.paine@boeing.com>
To: "Venema, Steve A" <Steve.A.Venema@boeing.com>,
	"Mattes, David" <david.mattes@boeing.com>,
	"Brewer, Orlie T" <brewer@thumper.rt.cs.boeing.com>, <p2psip@ietf.org>, 
	<hipsec@ietf.org>
X-OriginalArrivalTime: 07 Jan 2008 15:37:32.0081 (UTC)
	FILETIME=[37CBA210:01C85143]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985
Cc: "Wang, Sherry" <Sherry.Wang@jhuapl.edu>,
	Henry Sinnreich <hsinnrei@adobe.com>, "Venema,
	Steven C" <steven.c.venema@boeing.com>,
	"David Ward \(wardd\)" <wardd@cisco.com>
Subject: [P2PSIP] Updated: P2PSIP and HIP Joint Meeting on the Boeing VOIP
	HIPImplementation
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0874268116=="
Errors-To: p2psip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0874268116==
Content-class: urn:content-classes:calendarmessage
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C85143.3751A3A1"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C85143.3751A3A1
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

When: Tuesday, January 08, 2008 8:00 AM-9:30 AM (GMT-08:00) Pacific Time =
(US & Canada).
Where: Virtual (866-752-6974 Passcode: 9710856#

*~*~*~*~*~*~*~*~*~*

Just so everyone is clear - the teleconference is at 8am Pacific Time on =
Tuesday, Jan 8, 2008 at the following teleconference and Webex numbers.

The teleconference is per a meeting at the Vancouver IETF on Friday, Dec =
7, 2007 that was a joint meeting of the HIP and P2PSIP Working Groups.  =
The joint meeting determined the need to look at the Boeing =
demonstration of SIP over HIP.  The demonstration used an =
IEEE802.11-WPA-wireless connection to the Boeing Intranet and the SIP =
call traversed both the wireless and wired network securely to get to a =
wired laptop.  The call occurred in a HIP namespace using a =
cryptographic identity as an SPI value in the ESP field.

This teleconference is being held to discuss the white paper on the =
demonstration and the use of HIP for secure point-to-point SIP.

Teleconference Details:

Date: Tuesday, January 8, 2008 Starting time: 8:00 am, Pacific Standard =
Time (GMT -08:00, San Francisco) Duration: 1 hour 30 minutes Meeting =
number: 896 132 416 Meeting password: hipmeeting Teleconference: =
Dial-in:1-866-752-6974 (US)
Leader passcode:9710856
Participant passcode:9710856 Host: Richard Paine Host's email address: =
richard.h.paine@boeing.com=20

Richard H. Paine
Success is getting what you want, happiness is liking what you get!
Cell:  206-854-8199
IPPhone:  425-373-8296
Email:  richard.h.paine@boeing.com=20

------_=_NextPart_001_01C85143.3751A3A1
Content-class: urn:content-classes:calendarmessage
Content-Type: text/calendar;
	method=REQUEST;
	name="meeting.ics"
Content-Transfer-Encoding: 8bit

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft CDO for Microsoft Exchange
VERSION:2.0
BEGIN:VTIMEZONE
TZID:(GMT-08.00) Pacific Time (US & Canada)
X-MICROSOFT-CDO-TZID:13
BEGIN:STANDARD
DTSTART:16010101T020000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=11;BYDAY=1SU
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T020000
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20080107T153731Z
DTSTART;TZID="(GMT-08.00) Pacific Time (US & Canada)":20080108T080000
SUMMARY:Updated: P2PSIP and HIP Joint Meeting on the Boeing VOIP HIPImpleme
 ntation
UID:040000008200E00074C5B7101A82E0080000000080ACA250E143C801000000000000000
 01000000020FE7606F6D5FC42BF9DE36E7AF87CFA
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Venema, S
 teve A":MAILTO:Steve.A.Venema@boeing.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Mattes, D
 avid":MAILTO:david.mattes@boeing.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Brewer, 
 Orlie T'":MAILTO:brewer@thumper.rt.cs.boeing.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'p2psip@i
 etf.org'":MAILTO:p2psip@ietf.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'hipsec@i
 etf.org'":MAILTO:hipsec@ietf.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;X-REPLYTIME=89071205T18
 4200Z;RSVP=TRUE;CN="'dwing@cisco.com'":MAILTO:dwing@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'ndlgroup
 1@gmail.com'":MAILTO:ndlgroup1@gmail.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;X-REPLYTIME=20071226T18
 3836Z;RSVP=TRUE;CN="'David Ward (wardd)'":MAILTO:wardd@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;X-REPLYTIME=20080102T16
 2106Z;RSVP=TRUE;CN="'Wang, Sherry'":MAILTO:Sherry.Wang@jhuapl.edu
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;X-REPLYTIME=20080103T21
 0543Z;RSVP=TRUE;CN="'Henry Sinnreich'":MAILTO:hsinnrei@adobe.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;X-REPLYTIME=20080104T11
 1500Z;RSVP=TRUE;CN="'Matuszewski Marcin (Nokia-OCTO/Helsinki)'":MAILTO:mar
 cin.matuszewski@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;X-REPLYTIME=20080107T01
 4720Z;RSVP=TRUE;CN="Venema, Steven C":MAILTO:steven.c.venema@boeing.com
ORGANIZER;CN="Paine, Richard H":MAILTO:richard.h.paine@boeing.com
LOCATION:Virtual (866-752-6974 Passcode: 9710856#
DTEND;TZID="(GMT-08.00) Pacific Time (US & Canada)":20080108T093000
DESCRIPTION:Just so everyone is clear - the teleconference is at 8am Pacifi
 c Time on Tuesday\, Jan 8\, 2008 at the following teleconference and Webex
  numbers.\N\NThe teleconference is per a meeting at the Vancouver IETF on 
 Friday\, Dec 7\, 2007 that was a joint meeting of the HIP and P2PSIP Worki
 ng Groups.  The joint meeting determined the need to look at the Boeing de
 monstration of SIP over HIP.  The demonstration used an IEEE802.11-WPA-wir
 eless connection to the Boeing Intranet and the SIP call traversed both th
 e wireless and wired network securely to get to a wired laptop.  The call 
 occurred in a HIP namespace using a cryptographic identity as an SPI value
  in the ESP field.\N\NThis teleconference is being held to discuss the whi
 te paper on the demonstration and the use of HIP for secure point-to-point
  SIP.\N\NTeleconference Details:\N\NDate: Tuesday\, January 8\, 2008 Start
 ing time: 8:00 am\, Pacific Standard Time (GMT -08:00\, San Francisco) Dur
 ation: 1 hour 30 minutes Meeting number: 896 132 416 Meeting password: hip
 meeting Teleconference: Dial-in:1-866-752-6974 (US)\NLeader passcode:97108
 56\NParticipant passcode:9710856 Host: Richard Paine Host's email address:
  richard.h.paine@boeing.com \N\NRichard H. Paine\NSuccess is getting what 
 you want\, happiness is liking what you get!\NCell:  206-854-8199\NIPPhone
 :  425-373-8296\NEmail:  richard.h.paine@boeing.com \N
SEQUENCE:0
PRIORITY:5
CLASS:
CREATED:20080107T153731Z
LAST-MODIFIED:20080107T153731Z
STATUS:CONFIRMED
TRANSP:OPAQUE
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-OWNERAPPTID:1471530967
X-MICROSOFT-CDO-APPT-SEQUENCE:1
X-MICROSOFT-CDO-ATTENDEE-CRITICAL-CHANGE:20080107T153731Z
X-MICROSOFT-CDO-OWNER-CRITICAL-CHANGE:20080107T153731Z
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT00H15M00S
END:VALARM
END:VEVENT
END:VCALENDAR

------_=_NextPart_001_01C85143.3751A3A1--


--===============0874268116==
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://www1.ietf.org/mailman/listinfo/p2psip

--===============0874268116==--




From p2psip-bounces@ietf.org Mon Jan 07 14:58:28 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JBy76-0007Mc-MS; Mon, 07 Jan 2008 14:58:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JBy76-0007MU-8k; Mon, 07 Jan 2008 14:58:24 -0500
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1JBy73-0007eJ-VU; Mon, 07 Jan 2008 14:58:24 -0500
Received: from [192.168.2.100] (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
	m07Jw8aE024092
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Mon, 7 Jan 2008 13:58:10 -0600
In-Reply-To: <0C549DAFE1A8004D8EB57ACDD108646D06520831@XCH-NW-2V2.nw.nos.boeing.com>
References: <0C549DAFE1A8004D8EB57ACDD108646D06520831@XCH-NW-2V2.nw.nos.boeing.com>
Mime-Version: 1.0 (Apple Message framework v753)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <ABEC1524-458C-413C-97A1-31D0E088B90A@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [P2PSIP] Updated: P2PSIP and HIP Joint Meeting on the Boeing VOIP
	HIPImplementation
Date: Mon, 7 Jan 2008 13:57:48 -0600
To: "Paine, Richard H" <richard.h.paine@boeing.com>
X-Mailer: Apple Mail (2.753)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: "Brewer, Orlie T" <brewer@thumper.rt.cs.boeing.com>, "Wang,
	Sherry" <Sherry.Wang@jhuapl.edu>, p2psip@ietf.org,
	hipsec@ietf.org, Henry Sinnreich <hsinnrei@adobe.com>, "Venema,
	Steve A" <Steve.A.Venema@boeing.com>, "Mattes,
	David" <david.mattes@boeing.com>,
	"David Ward \(wardd\)" <wardd@cisco.com>, "Venema,
	Steven C" <steven.c.venema@boeing.com>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org


On Jan 7, 2008, at 9:37 AM, Paine, Richard H wrote:

> <meeting.ics>

I'll parse that for those whose software breaks on the attachment:

------

Just so everyone is clear - the teleconference is at 8am Pacific Time  
on Tuesday, Jan 8, 2008 at the following teleconference and Webex  
numbers.

The teleconference is per a meeting at the Vancouver IETF on  Friday,  
Dec 7, 2007 that was a joint meeting of the HIP and P2PSIP Working  
Groups.  The joint meeting determined the need to look at the Boeing  
demonstration of SIP over HIP.  The demonstration used an IEEE802.11- 
WPA-wireless connection to the Boeing Intranet and the SIP call  
traversed both the wireless and wired network securely to get to a  
wired laptop.  The call occurred in a HIP namespace using a  
cryptographic identity as an SPI value in the ESP field.

This teleconference is being held to discuss the white paper on the  
demonstration and the use of HIP for secure point-to-point SIP.

Teleconference Details:

Date: Tuesday, January 8, 2008
Starting time: 8:00 am, Pacific Standard Time (GMT -08:00, San  
Francisco) Duration: 1 hour 30 minutes Meeting number: 896 132 416
Meeting password: hip meeting
Teleconference: Dial-in: 1-866-752-6974 (US)
Participant passcode:9710856
Host: Richard Paine
Host's email address: richard.h.paine@boeing.com

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



From p2psip-bounces@ietf.org Mon Jan 07 15:36:09 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JByhW-0002Q6-C4; Mon, 07 Jan 2008 15:36:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JByhU-0002Pw-Hc; Mon, 07 Jan 2008 15:36:00 -0500
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1JByhU-0008Ib-1O; Mon, 07 Jan 2008 15:36:00 -0500
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id m07KVrjt029437
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Mon, 7 Jan 2008 14:31:53 -0600 (CST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	m07KVq2j000235; Mon, 7 Jan 2008 14:31:52 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	m07KVjHb029945; Mon, 7 Jan 2008 14:31:52 -0600 (CST)
Received: from XCH-NW-2V2.nw.nos.boeing.com ([130.247.55.18]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 7 Jan 2008 12:31:51 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [P2PSIP] Updated: P2PSIP and HIP Joint Meeting on the Boeing VOIP
	HIPImplementation
Date: Mon, 7 Jan 2008 12:31:50 -0800
Message-ID: <0C549DAFE1A8004D8EB57ACDD108646D0652083A@XCH-NW-2V2.nw.nos.boeing.com>
In-Reply-To: <8390D7C9-7EA5-49D2-B4DE-917FFDD89A71@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] Updated: P2PSIP and HIP Joint Meeting on the Boeing
	VOIP HIPImplementation
Thread-Index: AchRZ9ElDuPiOhZ1TwOU6LpptF4qNgABDsjw
References: <0C549DAFE1A8004D8EB57ACDD108646D06520831@XCH-NW-2V2.nw.nos.boeing.com>
	<8390D7C9-7EA5-49D2-B4DE-917FFDD89A71@softarmor.com>
From: "Paine, Richard H" <richard.h.paine@boeing.com>
To: "Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 07 Jan 2008 20:31:51.0397 (UTC)
	FILETIME=[55916950:01C8516C]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: "Brewer, Orlie T" <brewer@thumper.rt.cs.boeing.com>, "Wang,
	Sherry" <Sherry.Wang@jhuapl.edu>, p2psip@ietf.org,
	hipsec@ietf.org, "Venema, Steve A" <Steve.A.Venema@boeing.com>,
	"Mattes, David" <david.mattes@boeing.com>,
	Henry Sinnreich <hsinnrei@adobe.com>,
	Roy Kuntz <roykuntz@exchange.microsoft.com>, "Venema,
	Steven C" <steven.c.venema@boeing.com>,
	"David Ward \(wardd\)" <wardd@cisco.com>,
	Sean Olson <Sean.Olson@microsoft.com>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Non-toll-free number for the P2PSIP and HIP teleconference:

203-310-8979
Participant passcode: 9710856

Richard H. Paine
Success is getting what you want, happiness is liking what you get!
Cell:  206-854-8199
IPPhone:  425-373-8296
Email:  richard.h.paine@boeing.com=20
=20

-----Original Message-----
From: Dean Willis [mailto:dean.willis@softarmor.com]=20
Sent: Monday, January 07, 2008 11:59 AM
To: Paine, Richard H
Subject: Re: [P2PSIP] Updated: P2PSIP and HIP Joint Meeting on the
Boeing VOIP HIPImplementation


On Jan 7, 2008, at 9:37 AM, Paine, Richard H wrote:

> <meeting.ics>

It occurs to me that you may have some folks calling in from outside the
US, and US toll-free numbers are notoriously difficult to reach from
some countries. Do you have a non-toll-free number? Or did I just miss
it in that Microsoft-mangled calendar invitation?

--
Dean


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



From p2psip-bounces@ietf.org Tue Jan 08 09:11:30 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCFAb-0006cW-B5; Tue, 08 Jan 2008 09:11:09 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JCFAa-0006ZW-2g
	for p2psip@ietf.org; Tue, 08 Jan 2008 09:11:08 -0500
Received: from py-out-1112.google.com ([64.233.166.183])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JCFAZ-0004Yb-M9
	for p2psip@ietf.org; Tue, 08 Jan 2008 09:11:07 -0500
Received: by py-out-1112.google.com with SMTP id x19so4411979pyg.24
	for <p2psip@ietf.org>; Tue, 08 Jan 2008 06:11:07 -0800 (PST)
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=hARonup28FvRboe4PbDG124f6W1QCtzxxjnIIRc66+4=;
	b=jA1GBJjsh7jp2dibFrCLJHdt07uAv8twA+EywG85gOXo+FIkKlSNuI+FDczizPW3as3weH4JkcYaRE6TpA8AxrhX95cP0TBaD8tbfaNu+YRe56+Bnb+mXI+IwzI4lNt2eCHAJn27FZV31D6wbtER5+NXgXzf0VsUj2ZFHEu8Es8=
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=m0rNq7LBFEzS/YK6xYP5wsim32FeqtBWoP01q7BLAr+wWg/dS3ICJLSl4vJAsrbWHRzIoz5T5tfe2I4eJUYIYlshWOUapCEmyPGQkic/5qx843iG8i5zAdu532Evc1h0BBl1dfNb1Jo/AyhVqiHr3wv5QfkzV45Mq8h2m4TsU8Q=
Received: by 10.65.224.11 with SMTP id b11mr45072847qbr.93.1199801466949;
	Tue, 08 Jan 2008 06:11:06 -0800 (PST)
Received: by 10.65.180.16 with HTTP; Tue, 8 Jan 2008 06:11:06 -0800 (PST)
Message-ID: <4d4304a00801080611q49033d81pa3368beb93f9928f@mail.gmail.com>
Date: Tue, 8 Jan 2008 09:11:06 -0500
From: "David A. Bryan" <dbryan@sipeerior.com>
To: "Paine, Richard H" <richard.h.paine@boeing.com>
Subject: Re: [P2PSIP] Updated: P2PSIP and HIP Joint Meeting on the Boeing VOIP
	HIPImplementation
In-Reply-To: <0C549DAFE1A8004D8EB57ACDD108646D0652083A@XCH-NW-2V2.nw.nos.boeing.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <0C549DAFE1A8004D8EB57ACDD108646D06520831@XCH-NW-2V2.nw.nos.boeing.com>
	<8390D7C9-7EA5-49D2-B4DE-917FFDD89A71@softarmor.com>
	<0C549DAFE1A8004D8EB57ACDD108646D0652083A@XCH-NW-2V2.nw.nos.boeing.com>
X-Google-Sender-Auth: 2c4f6086dd855a4f
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: "Venema, Steve A" <Steve.A.Venema@boeing.com>, "Wang,
	Sherry" <Sherry.Wang@jhuapl.edu>, p2psip@ietf.org,
	hipsec@ietf.org, Henry Sinnreich <hsinnrei@adobe.com>, "Brewer,
	Orlie T" <brewer@thumper.rt.cs.boeing.com>, "Mattes,
	David" <david.mattes@boeing.com>, "David Ward \(wardd\)" <wardd@cisco.com>,
	Roy Kuntz <roykuntz@exchange.microsoft.com>, "Venema,
	Steven C" <steven.c.venema@boeing.com>,
	Sean Olson <Sean.Olson@microsoft.com>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Some folks asked if the IETF note well statement applied here.

Since this is being discussed on list, published on list, etc., I
believe it does. So, the note well policy applies. If you aren't
familiar with the IETF IPR / Note Well policy, it is here; please read
it before the call:

http://www.ietf.org/NOTEWELL.html

Thanks,

David (as chair on P2PSIP)

On Jan 7, 2008 3:31 PM, Paine, Richard H <richard.h.paine@boeing.com> wrote:
> Non-toll-free number for the P2PSIP and HIP teleconference:
>
> 203-310-8979
> Participant passcode: 9710856
>
> Richard H. Paine
> Success is getting what you want, happiness is liking what you get!
> Cell:  206-854-8199
> IPPhone:  425-373-8296
> Email:  richard.h.paine@boeing.com
>
>
> -----Original Message-----
> From: Dean Willis [mailto:dean.willis@softarmor.com]
> Sent: Monday, January 07, 2008 11:59 AM
> To: Paine, Richard H
> Subject: Re: [P2PSIP] Updated: P2PSIP and HIP Joint Meeting on the
> Boeing VOIP HIPImplementation
>
>
> On Jan 7, 2008, at 9:37 AM, Paine, Richard H wrote:
>
> > <meeting.ics>
>
> It occurs to me that you may have some folks calling in from outside the
> US, and US toll-free numbers are notoriously difficult to reach from
> some countries. Do you have a non-toll-free number? Or did I just miss
> it in that Microsoft-mangled calendar invitation?
>
> --
> Dean
>
>
>
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.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://www1.ietf.org/mailman/listinfo/p2psip



From p2psip-bounces@ietf.org Tue Jan 08 11:10:13 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCH1i-0002gZ-3c; Tue, 08 Jan 2008 11:10:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JCH1f-0002gP-Tj
	for p2psip@ietf.org; Tue, 08 Jan 2008 11:10:03 -0500
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JCH1d-0002rv-M4
	for p2psip@ietf.org; Tue, 08 Jan 2008 11:10:03 -0500
Received: from [206.176.144.213] (206-176-144-213.waymark.net
	[206.176.144.213]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m08G9xAV030403
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <p2psip@ietf.org>; Tue, 8 Jan 2008 10:10:01 -0600
Message-ID: <4783A058.2070904@softarmor.com>
Date: Tue, 08 Jan 2008 10:10:00 -0600
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20071022)
MIME-Version: 1.0
To: p2psip@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d62ab47271805379d7172ee693a45db
Subject: [P2PSIP] info on webex for meeting with HIP
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

http://boeing.webex.com
number: 896 132 416
Meeting password: hipmeeting
Teleconference: Dial-in: 1-866-752-6974 (US)
Participant passcode:9710856

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



From p2psip-bounces@ietf.org Tue Jan 08 11:35:32 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCHQE-0008D8-OA; Tue, 08 Jan 2008 11:35:26 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JCHQD-0008D2-Vx
	for p2psip@ietf.org; Tue, 08 Jan 2008 11:35:26 -0500
Received: from nylon.softarmor.com ([66.135.38.164])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JCHQD-0007t6-LV
	for p2psip@ietf.org; Tue, 08 Jan 2008 11:35:25 -0500
Received: from [192.168.2.100] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113] (may be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m08GZN9a030614
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT)
	for <p2psip@ietf.org>; Tue, 8 Jan 2008 10:35:25 -0600
Mime-Version: 1.0 (Apple Message framework v753)
Content-Transfer-Encoding: 7bit
Message-Id: <7983C400-54D1-49EA-877A-A0118F55F1A6@softarmor.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: P2PSIP Mailing List <p2psip@ietf.org>
From: Dean Willis <dean.willis@softarmor.com>
Date: Tue, 8 Jan 2008 10:34:55 -0600
X-Mailer: Apple Mail (2.753)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Subject: [P2PSIP] HIP link for Nokia 770 sip-hip demo
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org


I believe this is the HIP stack used for the Nokia 770 on some  
projects including the hip-sip demo we've been talking about.

See:
http://infrahip.hiit.fi/

--
Dean

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



From p2psip-bounces@ietf.org Tue Jan 08 11:49:47 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCHe6-0001w8-LY; Tue, 08 Jan 2008 11:49:46 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JCHe5-0001uJ-BZ
	for p2psip@ietf.org; Tue, 08 Jan 2008 11:49:45 -0500
Received: from nylon.softarmor.com ([66.135.38.164])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JCHe5-00088p-1H
	for p2psip@ietf.org; Tue, 08 Jan 2008 11:49:45 -0500
Received: from [192.168.2.100] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113] (may be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m08GnhfT030733
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT)
	for <p2psip@ietf.org>; Tue, 8 Jan 2008 10:49:44 -0600
Mime-Version: 1.0 (Apple Message framework v753)
Content-Transfer-Encoding: 7bit
Message-Id: <56BBA2F3-7F96-4FAB-B070-C43EF20002DE@softarmor.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: P2PSIP Mailing List <p2psip@ietf.org>
From: Dean Willis <dean.willis@softarmor.com>
Date: Tue, 8 Jan 2008 10:49:14 -0600
X-Mailer: Apple Mail (2.753)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Subject: [P2PSIP] Link to Voice over IP Security Alliance
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org


This came up in today's conference call about HIP-SIP

http://www.voipsa.org/

Apparently they have a mailing list that carries some related traffic.

--
Dean

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



From p2psip-bounces@ietf.org Tue Jan 08 11:57:16 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCHlK-0004yo-5W; Tue, 08 Jan 2008 11:57:14 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JCHlI-0004yc-96
	for p2psip@ietf.org; Tue, 08 Jan 2008 11:57:12 -0500
Received: from mmail.voxeo.com ([66.193.54.208] helo=voxeo.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JCHlH-0008HB-Ky
	for p2psip@ietf.org; Tue, 08 Jan 2008 11:57:12 -0500
Received: from [75.68.245.43] (account dyork HELO [172.20.12.144])
	by voxeo.com (CommuniGate Pro SMTP 5.1.12)
	with ESMTPSA id 26340500; Tue, 08 Jan 2008 16:57:10 +0000
In-Reply-To: <56BBA2F3-7F96-4FAB-B070-C43EF20002DE@softarmor.com>
References: <56BBA2F3-7F96-4FAB-B070-C43EF20002DE@softarmor.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <2A4E1F8B-3226-4468-A8E4-C3AE2C3A3CC6@voxeo.com>
From: Dan York <dyork@voxeo.com>
Subject: Re: [P2PSIP] Link to Voice over IP Security Alliance
Date: Tue, 8 Jan 2008 11:56:21 -0500
To: Dean Willis <dean.willis@softarmor.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 42e3ed3f10a1d8bef690f09da16f507a
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0460811413=="
Errors-To: p2psip-bounces@ietf.org


--===============0460811413==
Content-Type: multipart/alternative; boundary=Apple-Mail-304-313366070


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

FYI, Richard Paine was referring to our VOIPSEC mailing list at:

   http://www.voipsa.org/VOIPSEC  (and yes, it's case-sensitive)

Traffic level goes up and down (and currently is light) and is  
related to VoIP security concerns.  Some time back... as Richard  
said, probably a year ago, we did have a brief discussion about his  
experiment at Boeing.  I had, quite frankly, forgotten about that  
until he mentioned it.

Regards,
Dan

On Jan 8, 2008, at 11:49 AM, Dean Willis wrote:

>
> This came up in today's conference call about HIP-SIP
>
> http://www.voipsa.org/
>
> Apparently they have a mailing list that carries some related traffic.
>
> --
> Dean
>
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.ietf.org/mailman/listinfo/p2psip

-- 
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

Bring your web applications to the phone.
Find out how at http://evolution.voxeo.com





--Apple-Mail-304-313366070
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">FYI, Richard Paine was referring =
to our VOIPSEC mailing list at:<DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>=A0 <A =
href=3D"http://www.voipsa.org/VOIPSEC">http://www.voipsa.org/VOIPSEC</A>=A0=
 (and yes, it's case-sensitive)</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Traffic level goes up and =
down (and currently is light) and is related to VoIP security concerns.=A0=
 Some time back... as Richard said, probably a year ago, we did have a =
brief discussion about his experiment at Boeing.=A0 I had, quite =
frankly, forgotten about that until he mentioned it.</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Regards,</DIV><DIV>Dan</DIV><=
DIV><BR><DIV><DIV>On Jan 8, 2008, at 11:49 AM, Dean Willis =
wrote:</DIV><BR class=3D"Apple-interchange-newline"><BLOCKQUOTE =
type=3D"cite"><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">This came up in today's conference call about =
HIP-SIP</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"http://www.voipsa.org">http://www.voipsa.org</A>/</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">Apparently they have a mailing list that carries some related =
traffic.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">--</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; ">Dean</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">_______________________________________________</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">P2PSIP mailing list</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A =
href=3D"mailto:P2PSIP@ietf.org">P2PSIP@ietf.org</A></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"https://www1.ietf.org/mailman/listinfo/p2psip">https://www1.ietf.o=
rg/mailman/listinfo/p2psip</A></DIV> </BLOCKQUOTE></DIV><BR><DIV> <SPAN =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; text-align: auto; =
-khtml-text-decorations-in-effect: none; text-indent: 0px; =
-apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">--=A0</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Dan York, =
CISSP, Director of Emerging Communication Technology</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Office of the CTO=A0 =A0<SPAN =
class=3D"Apple-converted-space">=A0</SPAN>Voxeo Corporation<SPAN =
class=3D"Apple-converted-space">=A0</SPAN>=A0 =A0<SPAN =
class=3D"Apple-converted-space">=A0</SPAN><A =
href=3D"mailto:dyork@voxeo.com">dyork@voxeo.com</A></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Phone: +1-407-455-5859=A0<SPAN =
class=3D"Apple-converted-space">=A0</SPAN>Skype: danyork=A0<SPAN =
class=3D"Apple-converted-space">=A0</SPAN><A =
href=3D"http://www.voxeo.com">http://www.voxeo.com</A></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Blogs: <A =
href=3D"http://blogs.voxeo.com">http://blogs.voxeo.com</A>=A0<SPAN =
class=3D"Apple-converted-space">=A0</SPAN><A =
href=3D"http://www.disruptivetelephony.com">http://www.disruptivetelephony=
.com</A></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
12px/normal Helvetica; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Bring your web applications to the phone.</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Find out how at <A =
href=3D"http://evolution.voxeo.com">http://evolution.voxeo.com</A></DIV><D=
IV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 12px/normal Helvetica; min-height: 14px; "><BR =
class=3D"khtml-block-placeholder"></DIV><BR =
class=3D"Apple-interchange-newline"></SPAN> =
</DIV><BR></DIV></BODY></HTML>=

--Apple-Mail-304-313366070--


--===============0460811413==
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://www1.ietf.org/mailman/listinfo/p2psip

--===============0460811413==--




From p2psip-bounces@ietf.org Tue Jan 08 12:42:04 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCISc-0000D7-N1; Tue, 08 Jan 2008 12:41:58 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCISb-0000Cm-Aa; Tue, 08 Jan 2008 12:41:57 -0500
Received: from usaga01-in.huawei.com ([206.16.17.211])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1JCISa-0000rO-61; Tue, 08 Jan 2008 12:41:57 -0500
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 <0JUC000SA6HUPX@usaga01-in.huawei.com>; Tue,
	08 Jan 2008 09:41:55 -0800 (PST)
Received: from s73602 (cpe-72-190-0-23.tx.res.rr.com [72.190.0.23])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006))
	with ESMTPA id <0JUC00H4E6HQ40@usaga01-in.huawei.com>; Tue,
	08 Jan 2008 09:41:54 -0800 (PST)
Date: Tue, 08 Jan 2008 11:41:23 -0600
From: Spencer Dawkins <spencer@mcsr-labs.org>
Subject: Re: [P2PSIP] P2PSIP and HIP Joint Meeting on the Boeing
	VOIPHIPImplementation
To: "Paine, Richard H" <richard.h.paine@boeing.com>
Message-id: <042701c8521d$b01b2f80$6601a8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
Content-type: text/plain; format=flowed; charset=iso-8859-1;
	reply-type=original
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <0C549DAFE1A8004D8EB57ACDD108646D070BA68B@XCH-NW-2V2.nw.nos.boeing.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1e467ff145ef391eb7b594ef62b8301f
Cc: "Venema, Steve A" <Steve.A.Venema@boeing.com>, "Brewer,
	Orlie T" <brewer@thumper.rt.cs.boeing.com>, "Mattes,
	David" <david.mattes@boeing.com>, p2psip@ietf.org, hipsec@ietf.org
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Richard,

These are the notes I took during the telechat - I hope you find them 
helpful.

It would be really good for people to see how badly they were misquoted - 
please send corrections to me privately, and I can provide a bulk update to 
Richard. I'm almost sure I attributed several Dan York statements randomly 
to other people...

Thanks again for setting up this call - very helpful.

Spencer
We started with a review of "Note Well" (we're under IETF IPR rules for this 
meeting).

- Agenda bashing...

Planned agenda is to review the VoWLAN paper and then do Q&A. No bashing to 
this agenda.

- Paper review...

This paper was distributed to P2PSIP mailing list on December 21 (also 
downloadable from http://www.opengroup.org/bookstore/catalog/e041.htm).

Using Open Group's Secure Mobile Architecture for both wireless and wireline 
secure communication, including voice, for factory operations.

Mechanism described is currently in production on the Boeing 777 assembly 
line robots, but is much more broadly applicable.

Overlay network, using HIP ("SCADANET Plane" in the paper). Tunnel looks 
like IPsec, with a cryptographic identifier.

Wireless devices are Nokia 770s with Linux and LinPhone. SIP provides call 
management services, while HIP provides security associations.

Some infrastructure is involved - "virtual directory" (identity, IP address, 
location of a device), DNS proxy for directory, certificate 
download-to-device management, location service.

Need to know who someone is, and where they are, to do security well.

Using HIP UPDATE packets for subnet mobility.

Provide crytographic security for every packet (also protects 
infrastructure).

Does rely on enterprise PKI in this demonstration.

- Questions and answers ...

Did this require mods to Linux IP stack? Used HIP from Helsinki, did have 
some kernel patches that added a new transform.

Does this use Orchid? Tom said all HIP implementations use Orchids (Orchids 
are a particular form of IPv6 addresses, allocated experimentally).

Would this also require changes to a Windows TCP/IP stack? Tom said that 
Boeing uses an OpenVPN "shim" with all modifications in user space, so no 
kernel mods are required.

There's no way for an application to know that it's talking to an overlay - 
how does the application know it's using a secure overlay? This is security 
by configuration - the application "just knows" the interface is magically 
secure.

Do we want applications to know about these security characteristics? Big 
design question (using ORCHIDs with legacy APIs tells you nothing about 
these characteristics).

What about a secure SIP security indicator? Applications don't get any 
indication of security from IPsec, this is no different from any other IPsec 
operation.

Dean said that there are mechanisms to make applications aware of HIP-IP 
mapping, if you build an application to be aware - this demo is using 
opportunistic mode, which does not, but there are 5 other modes.

Lots of discussions about HIP security on VOIP-SEC/VOIP-SA mailing list 
(voipsec@voipsa.org), but not in about a year.

The question here is whether we can use modified applications with 
unmodified stacks. Ted thinks the real question is whether you get something 
easy for the application writer to use without awareness of an underlying 
overlay or not. Anything - OpenVPN, kernel mod, etc. are just creating 
another interface that is exposed to anything that uses normal mechanisms 
for discovery - applications would not know the difference between IDs and 
LOCs. Ted thinks we need to know this difference - need to have a design 
discussion about this.

This is a tradeoff between easy deployment and application awareness of 
unique characteristics - we need to talk.

Spencer- There are a lot of other reasons to dork with an API - multihoming, 
route selection. Is API enhancement bounded?

Dean - we went with TLS 10 years ago because we could do it without dorking 
with stacks. We might make a different decision now, if we were 
reconsidering.

Henry - the IPsec mechanism secures all applications, not just SIP.

Ted - but applications that don't know IPsec is there will run TLS over 
IPsec happily if they care about security. Maybe we could know that we're 
using an ORCHID that must be HIP-ergo-IPsec. There are questions about the 
layering model we need to talk about.

Steve - not sure what approach we want - transparency for legacy 
applications or application awareness.

Ted - we're using P2P anyway, HIP or not. If applications understand 
characteristics, you want to have the same answer for P2P and HIP awareness.

Steve - both mechanisms available? and application writer chooses?

Dave Bryan - transparency isn't going to make SIP phones P2P, right? 
built-in free resource location, etc. doesn't happen by magic. Still work to 
do on both SIP and P2P to make this work.

Question (sorry, missed name) - if HIP is providing overlay routing, there 
is also a coupling with resource location, etc.

Dave Bryan - but think about service, voice mail, etc. We still have work to 
do before we can remove all the servers.

Spencer - seeing people talking about HIP over P2P and P2P over HIP - need 
to nail down an architecture early in this discussion.

Tom - HIP is doing security for media streams, and there is separate work 
about extending the architecture to do routing. Could be different ways to 
go here (media streams only, or entire overlay on architecture).

Gonzalo - WithHIP proposal started discussion using HIP in naive way, but 
this was too simple an approach to use. We would modify the architecture, 
use ORCHIDs (or derivation) as identifiers, etc.

Sherry - has anyone done competitive analysis about performance, operational 
scenarios, etc.

Richard - not an alternative that met our requirements (in the broader 
context). We did what we did to meet our requirements. We're going through a 
competitive analysis now, for another reason (and it's not obvious we would 
release that analysis externally).

- Next Steps? ...

Ted would like to resolve design decision about application awareness - 
write this up early in the process. If HIP is only transport-mode security, 
it's low-handing but not very valuable fruit. P2PSIP needs to be clear about 
API expectations about underlying overlay. If we don't get that right, we'll 
be headed in the wrong direction.

David Bryan - consensus on that issue would help a lot. A lot of people in 
P2PSIP don't understand how this would work and would benefit from one clear 
statement.

Henry - a lot of confusion about protocol stack, what's on top. Could Boeing 
team identify architectural choices in a separate paper, perhaps working 
with Gonzalo? It would help the P2PSIP folks a lot. Should come from 
authoritative source, right now that looks like Boeing and Finland.

Gonzalo - three proposals, but thought HIP-HOP was abandoned and no one is 
working on WithHIP, we're working on HIP-BONE. We need to communicate better 
with P2PSIP working group. We've been having conversations within HIP, with 
P2PSIP guys, clearer than before IETF 70.

Tom - still needs to be discussion. Eric Cooper is still interested in 
HIP-HOP, Philip is interested in IP-LOC. Thought we agreed to talk on HIP-RG 
mailing list and then HIP-BONE came out and things got quiet.

Gonzalo - don't see HIP-HOP and HIP-BONE as different proposals - saying 
similar things. Published new draft because I didn't think there was 
interest in revising HIP-HOP.

Henry - new draft with tutorial and framework?

Gonzalo - has some tutorial but did draft in a few hours. Need to add 
historical statements, etc.

Henry - how to represent Boeing contribution to IETF? don't have to decide 
now, but would like to see Boeing work better understood in IETF. Extremely 
interesting for entire HIP community.

Gonzalo - choices have to be explained further.

Richard - Sherry was talking about "competitive analysis" beyond 
architecture - MEXT, MIP, etc?

Sherry - think more practical to decide architecture and educate people. 
Start with this. Eventually have to give analysis answer - P2PSIP and 
conventional SIP.

Dave Bryan - need to focus on HIP and non-HIP discussion.

Is there an interest in HIP within industry? This is what Richard hopes to 
finish by February.

Henry - believe working working group is not proper place for economic 
analysis, but need to think about wquestions like balkanized security for 
different applications, etc.

Dan York - if we're going to do a comparison, I'd like to understand how 
widely HIP might be endorsed.

Spencer - need to ask about interest in architecture, not interest in 
specific protocols.

Henry - dialup IP is a good model - a way to get started, and then 
applications that manage connectivity can move into OS code.

ANOTHER TELECHAT?

Gonzalo - yes, but everyone prepare. Don't discuss on abstract level because 
we won't make progress.

Richard - have to deliver comparison between technologies in February. If I 
can get that approved for release, it could be a basis for top-down 
discussion, then talk about protocol stack, architecture, etc. If Gonzalo 
adds tutorial material that would also help.

Gonzalo - sure, what tutorial do people need? Trying to do tutorial in three 
pages so people will it read it.

Henry - had to read 10 references anyway...

Having read through HIP-BONE, Gonzalo and team did this well and unfortunate 
we truncated discussion during the holidays. Let's not keep starting out 
"what would this architecture look like" - keep going from where we are.

Richard - want me to set up another joint meeting?

(No objections!)

Stopping at 1:35 minutes... will go from there.

Much gratitude to Boeing for throwing these ideas out for thought!



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



From p2psip-bounces@ietf.org Tue Jan 08 14:16:18 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCJu0-00065t-Sq; Tue, 08 Jan 2008 14:14:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JCJtz-0005ra-2Y
	for p2psip@ietf.org; Tue, 08 Jan 2008 14:14:19 -0500
Received: from twilight.cs.hut.fi ([130.233.40.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JCJtn-0006ag-EM
	for p2psip@ietf.org; Tue, 08 Jan 2008 14:14:19 -0500
Received: by twilight.cs.hut.fi (Postfix, from userid 60001)
	id B7B062E0B; Tue,  8 Jan 2008 21:13:56 +0200 (EET)
X-Spam-Checker-Version: SpamAssassin 3.2.3-niksula20070810 (2007-08-08) on
	twilight.cs.hut.fi
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled
	version=3.2.3-niksula20070810
X-Spam-Niksula: No
Received: from kekkonen (kekkonen.cs.hut.fi [130.233.41.50])
	by twilight.cs.hut.fi (Postfix) with ESMTP id 37C442D6F;
	Tue,  8 Jan 2008 21:13:48 +0200 (EET)
Date: Tue, 8 Jan 2008 21:13:48 +0200 (EET)
From: Miika Komu <miika@iki.fi>
X-X-Sender: mkomu@kekkonen.cs.hut.fi
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [P2PSIP] Re: a modular approach for integrating HIP for P2PSIP
In-Reply-To: <4778C88A.20201@ericsson.com>
Message-ID: <Pine.SOL.4.64.0801082024001.21865@kekkonen.cs.hut.fi>
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com> <47724ED2.7060508@uni-tuebingen.de>
	<47725398.4000309@ericsson.com> <477268E1.4050509@uni-tuebingen.de>
	<4778C88A.20201@ericsson.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

On Mon, 31 Dec 2007, Gonzalo Camarillo wrote:

Hi Ali and Gonzalo,

sorry for catching up late.

> Hi Ali,
>
> HIP includes an ICE-based NAT traversal mechanism. If two nodes use HIP, 
> they will perform ICE at the HIP level, not at the application level. 
> Using application-level ICE to negotiate the use of HIP between nodes, 
> per your email below, is cumbersome. The use of HIP can be negotiated in 
> simpler ways.
>

Basically I agree with Gonzalo here, but to be more specific...

In a "normal" (no overlay, no extra mods to ICE or HIP) HIP scenario, 
sending some data to a HIT would trigger an I1. Either with or without UDP 
encapsulation, depending on local policies. When I1 is sent without UDP, 
the hipd could speed up the connection set-up in the case there are no 
NATs between the two machines. However, the ICE module would not know 
when to stop the connectivity tests, because it wasn't HIP-aware in this 
case. Also, this "optimization" would be unnecessary in the case there are 
NATs between the two hosts because the HIP messages would be just dropped.

In another non-overlay scenario, where ICE is HIP-aware, we could define 
that ICE and HIP module can interact with each other. Sending STUN 
messages to a HIT would trigger a I1 packet without UDP encapsulation and 
upon success the HIP module could abort the ICE connectivity tests 
gracefully. One benefit of this would be that we would skip the UDP 
encapsulation altogether, but the benefit is neglectible.

As indicated by the other discussion thread, applying HIP-aware ICE in 
HIP-enabled overlays may have some caveats related to handling of multiple 
overlays. Anyway, there should be a distinction between getting a direct 
connection to the peer (using ICE) vs. routing through the overlay. I 
think this could be implemented e.g. using a socket option.

> With regards to the use of HIP in overlays, the simplest way would be to 
> deploy overlays where all nodes use HIP and overlays where none of the 
> nodes use HIP. However, some people have expressed interest in having 
> mixed overlays where some nodes use HIP while others don't. If people 
> are interested in doing this, we will have to look into ways to 
> negotiate its use within the overlay.
>
> With regards to the use of HIP in overlays, the simplest way would be to 
> deploy overlays where all nodes use HIP and overlays where none of the 
> nodes use HIP. However, some people have expressed interest in having 
> mixed overlays where some nodes use HIP while others don't. If people 
> are interested in doing this, we will have to look into ways to 
> negotiate its use within the overlay.

Regarding to Ali's original suggestion on detecting localhost and peer 
support, I think localhost support would be easy. Connecting to a HIT is 
one way detect it, but it may include a timeout. Other ways are to go 
through the addresses of host using e.g. getaddrinfo() and check if there 
are any ORCHIDs there. Perhaps the quickest way is to create a socket with 
PF_HIP family and check for errors in the return value.

-- 
Miika Komu                                       http://www.iki.fi/miika/

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



From p2psip-bounces@ietf.org Tue Jan 08 14:31:06 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCKAB-0007Ai-8g; Tue, 08 Jan 2008 14:31:03 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCKA9-000798-DM; Tue, 08 Jan 2008 14:31:01 -0500
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1JCKA8-0004ie-Tq; Tue, 08 Jan 2008 14:31:01 -0500
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id m08JUuHR006390
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Tue, 8 Jan 2008 13:30:56 -0600 (CST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	m08JUu9J013260; Tue, 8 Jan 2008 13:30:56 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	m08JUpR6013049; Tue, 8 Jan 2008 13:30:56 -0600 (CST)
Received: from XCH-NW-5V1.nw.nos.boeing.com ([130.247.55.44]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 8 Jan 2008 11:30:56 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [P2PSIP] Discussion items for the Tuesday teleconference
Date: Tue, 8 Jan 2008 11:30:55 -0800
Message-ID: <77F357662F8BFA4CA7074B0410171B6D04049B0F@XCH-NW-5V1.nw.nos.boeing.com>
In-Reply-To: <24CCCC428EFEA2469BF046DB3C7A8D223AE4A7@namail5.corp.adobe.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] Discussion items for the Tuesday teleconference
Thread-Index: AchEH96vkLdr2CwpRny3bB+oZLdYwQNEMNOwADlowyA=
References: <0C549DAFE1A8004D8EB57ACDD108646D070BA682@XCH-NW-2V2.nw.nos.boeing.com>
	<24CCCC428EFEA2469BF046DB3C7A8D223AE4A7@namail5.corp.adobe.com>
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "Henry Sinnreich" <hsinnrei@adobe.com>,
	"Paine, Richard H" <richard.h.paine@boeing.com>, <p2psip@ietf.org>,
	<hipsec@ietf.org>
X-OriginalArrivalTime: 08 Jan 2008 19:30:56.0016 (UTC)
	FILETIME=[FD344900:01C8522C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: 
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Henry,
A few responses below.=20

> -----Original Message-----
> From: Henry Sinnreich [mailto:hsinnrei@adobe.com]=20
> Sent: Monday, January 07, 2008 5:44 AM
> To: Paine, Richard H; p2psip@ietf.org; hipsec@ietf.org
> Subject: [P2PSIP] Discussion items for the Tuesday teleconference
>=20
> The paper on the Boeing HIP implementation along with the I-D:
> draft-camarillo-hip-bone-00.txt is very helpful to SIP oriented people
> like me who are new to HIP. Quite frankly I am close to becoming a
> believer, if only some questions could be addressed and where more
> details would be helpful:
>=20
> 1. TCP/IP stack use and implementation
>=20
> If and how can the existing PCP/IP stack in Windows, OSX, Symbian and
> LINUX be used or does it have to be rewritten? Is there a=20
> workaround and
> if yes, can anyone share what it may look like?

There are HIP implementations that modify the kernel TCP/IP
implementation, and those that do not.  Those that do not use various
techniques to intercept packets and copy them to user-space where they
are further processed and re-injected to the stack.  OpenVPN
(http://openvpn.net) is one such example.

What it may look like in this approach is to create a virtual interface
and assign one or more HIP identifiers (that look like addresses to the
operating system) to that interface.  Packets sent to identifiers in
that identifier space are internally routed to that virtual interface.
This interface is a tap interface (http://en.wikipedia.org/wiki/TUN/TAP)
that directs packets to userspace, where they can be processed further
and written back to the interface or to a raw socket.

Note that this technique is recommended as a deployment crutch for
applications that cannot be easily modified; the eventual goal is that
stacks are upgraded to include HIP and that applications use more
explicit HIP-aware APIs such as:
https://datatracker.ietf.org/drafts/draft-ietf-hip-native-api/

Also note that I do not know about the applicability of the above to
Symbian, only that it has worked for Windows XP, OS X, and Linux.

>=20
> Product managers would see the rewriting of the TCP/IP stack to insert
> HIP as a major problem to avoid at any cost. Waiting for these OS to
> support HIP does not seem a good alternative.
>=20
> 2. NAT traversal
>=20
> VPN implementations have had problems with NAT and as a=20
> result most NAT
> vendors have addressed VPN support. What is the experience with HIP
> support in NAT, or how much of a problem is NAT traversal for HIP?
> Are there any measurements or deployment data that can be shared?

To my knowledge, there has been no inbound NAT traversal mechanism
integrated with any of the HIP implementations.  There have been
implementations of UDP encapsulation for outbound NAT traversal for a
few years, according to an expired Internet draft:
http://tools.ietf.org/html/draft-schmitt-hip-nat-traversal-02.  I don't
know how much testing they have undergone; not as much as the non-NAT
variants, I would say.

The HIP WG has a design team working on NAT traversal, and STUN/ICE is
the basic design framework.

Tom

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



From p2psip-bounces@ietf.org Tue Jan 08 17:16:40 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCMkG-0004gD-47; Tue, 08 Jan 2008 17:16:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JCMkF-0004fw-3q
	for p2psip@ietf.org; Tue, 08 Jan 2008 17:16:27 -0500
Received: from wa-out-1112.google.com ([209.85.146.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JCMkA-0001Rx-Is
	for p2psip@ietf.org; Tue, 08 Jan 2008 17:16:27 -0500
Received: by wa-out-1112.google.com with SMTP id k40so16337216wah.25
	for <p2psip@ietf.org>; Tue, 08 Jan 2008 14:16:20 -0800 (PST)
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=YRkn9VeuB3mz2ppMBM99VrlZ5FyMYv0zD+uUM8VQHJs=;
	b=hDDoiLdW3H4kCEVfh4M1rPeHEZTbjZ5bVdu+OKSBRAnrwF4ZgHQ1i2fAGGtNfAgJyZhW/w6VwHZNN9Fu08X9XhIrnQZBnmcP0ufdJ36BwQe0aQOy45ocW0E87iHx5PCFVZZvbKVfQrg3tx5NZZUVVW41zT26klU0qBoiwaOi/vc=
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=M+EBbFhJ0MjnzuVt+zfAuMj9Osq2r2wdrN+22pGxB8CbcJIZ8TmWhBk8I2AvqgxLsJ2Mc0b5Ldkyv/sEWiWkr3LleEXoett5DqVqCz5qHioVSFHvNpV2fv+pm/34xPVLWtIAVgj64NFeKXT68g7tKZk0osxX0zXaDfPrPcTOX7Y=
Received: by 10.114.157.1 with SMTP id f1mr7992064wae.13.1199830580500;
	Tue, 08 Jan 2008 14:16:20 -0800 (PST)
Received: by 10.114.209.13 with HTTP; Tue, 8 Jan 2008 14:16:20 -0800 (PST)
Message-ID: <20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
Date: Tue, 8 Jan 2008 17:16:20 -0500
From: "Bruce Lowekamp" <lowekamp@sipeerior.com>
To: "Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [P2PSIP] New draft: HIP BONE
In-Reply-To: <476E2B7C.9070601@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
X-Google-Sender-Auth: 54a7386c4a8b0eff
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
Cc: Pekka Nikander <pekka.nikander@nomadiclab.com>,
	P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

On Dec 23, 2007 4:33 AM, Gonzalo Camarillo
<Gonzalo.Camarillo@ericsson.com> wrote:
> Hi Bruce,
>
> thanks for your comments.
>
> Regarding your question about Sections 3.2 and 3.3 when RELOAD is the
> peer protocol and HIP BONE is used for connection management, the idea
> is to use HIP, instead of RELOAD, to perform connection management. All
> the other functions RELOAD typically performs are still performed by RELOAD.
>
> RELOAD defines the CONNECT primitive and the TUNNEL primitive. If HIP is
> being used, you would use the CONNECT primitive of HIP (i.e., an I1
> packet) *instead* of the CONNECT primitive of RELOAD. The same way, you
> would use the TUNNEL primitive of HIP (i.e., a HIP message) *instead* of
> the TUNNEL primitive of RELOAD.

This is where I still get confused, and I think this is a pretty big
architectural issue.  The combination of 3.2, 3.3, and 6 still leave
some questions in my mind as to exactly what is being proposed, so let
me try to form up an example for discussion purposes.


Suppose I have an overlay with the following connections between peers
(labeled with their peerid):

1 ------ 5 ------ 10

So 1 has 5 in its routing table (and thus a direct connection) but not
10.  5 has direct connections to 1 and 10.  I'm assuming recursive
routing and am not being precise with a DHT algorithm for the purposes
of this example.

10 is responsible for a resource, 9, that 1 wants to query for.  In a
non-HIP DHT implementation, 1 sends a query "to" 9.  It looks up for
the closest match in its routing table and discovers it is 5, then it
sends the message to 5.  5 performs a similar lookup and discovers
that its closest match is 10, so it forwards the query to 10.

Going with the HIP-BONE, approach, as I understand the "HIP is IP and
the peer protocol is OSPF" idea, I see two approaches that would meet
that requirement:
- the peer protocol loads enough information into the HIP layer that
the HIP layer on peer 1 knows that the next hop for a message bound
for "9" is 5.  I will refer to this as the hip routing table approach.
- the peer protocol sets the next-hop for the query to "5" based on
its own routing table, and lets the HIP layer forward it.  I will
refer to this as the hip link layer approach.

The hip routing table approach looks great from a layering
perspective, but implementation looks to be very hard.  Since there
are multiple DHT (and unstructured overlay) algorithms with different
routing rules, there would have to be a pluggable routing algorithm
loaded into the HIP layer by the DHT algorithm or there  needs to be
an upcall from the HIP layer into the peer protocol layer to query for
the next-hop for messages.

In the hip link layer approach, the peer protocol layer knows that the
current set of next-hop candidates are, and it runs the DHT routing
algorithm in the conventional sense, telling the HIP layer what the
next hop for a message is.  This seems like a much simpler approach to
implement, but limits the usefulness of HIP.

So the first question is whether HIP-BONE is intended to specify one
of these approaches, and if so, which one?  I believe it's the hip
routing table approach.


Next, let's take the case of 3.3, "lightweight message exchange."  As
I understand 3.3,   it should work fine in the hip routing table
approach for both application and peer protocol message exchanges.  In
the hip link layer approach, peer protocol messages can be delivered
this way, but application messages cannot (they would require a direct
connection).


Next, how about CONNECT messages.  Suppose that now peer 1 wants to
establish a direct connection to peer 10 for some reason.  Your email
indicates that there will be no CONNECT messages as in RELOAD, but
instead there will only be I1 etc messages.  Let's just assume that
the peer protocol has some way of indicating that it wants to be able
to send messages directly to another peer rather than over the
overlay.  So in the hip routing table approach, the I1 etc messages
are routed via 5 using HIP to 10 and eventually a new direct
connection is established.  In the hip link layer approach, the peer
protocol would have to insert the I1 into a peer message and forward
it itself.  That would work, but it's a bit cumbersome.


What continues to confuse me, and what I think is the hardest
architectural question here, is how the issue I mentioned above:
"there would have to be a pluggable routing algorithm loaded into the
HIP layer by the DHT algorithm or there  needs to be an upcall from
the HIP layer into the peer protocol layer to query for the next-hop
for messages"
is solved.  Section 6 has quite a few block diagrams, but none of them
seem to help me resolve this issue.  I don't think I see any other
alternatives, but it would be nice to see this specific issue
addressed, because it would make the layering more concrete.



>
> Regarding when to use these primitives, you would use them in the same
> way as defined by RELOAD. That is, when RELOADs tells you to use a
> CONNECT primitive today, you would send an I1 message. When RELOAD tells
> you to use the TUNNEL primitive today, you would use a HIP message as
> well. That is, RELOAD (not HIP BONE) tells you what to do  (i.e., which
> primitive to use) and when to do it.
>
> As you can see, the only modifications to RELOAD in this context is the
> substitution of these two primitives by the HIP equivalent ones.

So I'm not quite sure that this is completely true.  If we let the HIP
layer handle the routing, then RELOAD wouldn't have to handle the
hop-by-hop nature of the recursive forwarding like it does now.  It
doesn't change anything about the majority of the peer protocol
issues, but it does change a bit in how the peer protocol's forwarding
layer (in RELOAD-02's arch diagram) would work.

Bruce

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



From p2psip-bounces@ietf.org Wed Jan 09 12:59:56 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCfDQ-00067y-AV; Wed, 09 Jan 2008 12:59:48 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JCfDO-00066C-Gg
	for p2psip@ietf.org; Wed, 09 Jan 2008 12:59:46 -0500
Received: from slb-smtpout-01.boeing.com ([130.76.64.48])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JCfDO-0004xt-2D
	for p2psip@ietf.org; Wed, 09 Jan 2008 12:59:46 -0500
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id m09HxGnQ005318
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Wed, 9 Jan 2008 09:59:24 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	m09HxFZj000393; Wed, 9 Jan 2008 11:59:15 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	m09HxAAV000158; Wed, 9 Jan 2008 11:59:15 -0600 (CST)
Received: from XCH-NW-5V1.nw.nos.boeing.com ([130.247.55.44]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 9 Jan 2008 09:59:13 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [P2PSIP] New draft: HIP BONE
Date: Wed, 9 Jan 2008 09:59:13 -0800
Message-ID: <77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
In-Reply-To: <20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] New draft: HIP BONE
Thread-Index: AchSRCq9gUIFqz+2S8SGyiUtxRen+QAn1O8w
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "Bruce Lowekamp" <lowekamp@sipeerior.com>,
	"Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>
X-OriginalArrivalTime: 09 Jan 2008 17:59:13.0860 (UTC)
	FILETIME=[5813A840:01C852E9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: Pekka Nikander <pekka.nikander@nomadiclab.com>,
	P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

=20

> -----Original Message-----
> From: Bruce Lowekamp [mailto:lowekamp@sipeerior.com]=20
> Sent: Tuesday, January 08, 2008 2:16 PM
> To: Gonzalo Camarillo
> Cc: Pekka Nikander; P2PSIP Mailing List
> Subject: Re: [P2PSIP] New draft: HIP BONE
>=20

>=20
> Going with the HIP-BONE, approach, as I understand the "HIP is IP and
> the peer protocol is OSPF" idea...

I think this analogy has some weaknesses, as you have pointed out, in
the "peer protocol is OSPF" part.  My reading of HIP BONE is that the
overall goal is to allow the peer protocol and other applications to
deal with HIP identifiers instead of IP addresses.  That is a worthy
goal IMO which might free RELOAD and other applications from having to
do ICE and handle recursive routing issues or host mobility and
multihoming.

However, the problem with this approach is that HIP needs a naming
service or routing service to resolve identifiers to either locators or
route lists.  This does not exist yet in HIP.  There have been proposals
to use DHTs to provide this service, but they do not presently
accommodate the possibility of multiple DHTs, which is pretty much a
requirement to handle, from my perspective.  HIP BONE seems to be
suggesting that the peer protocol can fill this gap but there appear to
be some issues that need to be worked out, or maybe HIP BONE needs its
own resolution/routing service separate from the application overlay.

Let's presume, for the sake of discussion, that HIP BONE could be made
to work (perhaps not exactly how it is written in the draft, but
somehow), and that it provided an abstraction to the peer protocol layer
and other applications that every node was reachable within a single
Internet; i.e., that each node had a single, globally scoped, unchanging
IP address, that there was a routing service that made each IP address
reachable from any other, and that there were no NATs.  Let's also
presume that HIP BONE was co-deployed with the peer protocol deployment;
that HIP was guaranteed to be available wherever the peer protocol was
deployed.

Question (for P2PSIP):  Is that a useful goal, for HIP to try to provide
the above abstraction, and to try to work out the rest of the details to
realize that service?  Or would there be other considerations that still
make this an unattractive abstraction to P2PSIP?  For instance, are
there reasons that nodes would want to know more details about the
underlying IP addresses associated with peer nodes, and wouldn't want
those details hidden?

Question:  How would RELOAD or other proposals change if that were the
case?  Would the benefits greatly outweigh any drawbacks to this
abstraction?

Tom

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



From p2psip-bounces@ietf.org Wed Jan 09 16:28:35 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCiTJ-00085K-6c; Wed, 09 Jan 2008 16:28:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JCiTI-00085E-IQ
	for p2psip@ietf.org; Wed, 09 Jan 2008 16:28:24 -0500
Received: from wa-out-1112.google.com ([209.85.146.176])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JCiTH-0002MI-N8
	for p2psip@ietf.org; Wed, 09 Jan 2008 16:28:24 -0500
Received: by wa-out-1112.google.com with SMTP id k40so847720wah.25
	for <p2psip@ietf.org>; Wed, 09 Jan 2008 13:28:22 -0800 (PST)
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=83yCv3Iprs0whAGxF4p8b5sop1kufOg2ZZlr1DxPTss=;
	b=jqpqjRmqpiqt+y7tugK0PTNHYOUCDEI5GRUNFQw5bpyymBrEDfou74VZIZO4Gyu7dNMiuwjHpoPMhSWZ28aG30zudkZadxWCPURmgKsBh+lF85GPGlznbZ5hiZPNW47mF4rmt3b6BD/dzF2h6KBwXoQjZAYzFYeqiKdYv6kbivo=
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=apN39JY621kJzJ240qJFsZcaGjZqrqS8Y4wQOhNEEHYFyBfp/UqjB0J88UIgY4aiVNv+uNnPlniTqU/7wqRjVZRRzipAauyLc+cBZPehrH5t47KF12FGHeLIuLEuME9HyjBKS8PvVU76zzeoyyBs4RtrWxkpNy+Lt2e8V52VhLU=
Received: by 10.114.61.1 with SMTP id j1mr1354501waa.62.1199914102723;
	Wed, 09 Jan 2008 13:28:22 -0800 (PST)
Received: by 10.114.209.13 with HTTP; Wed, 9 Jan 2008 13:28:22 -0800 (PST)
Message-ID: <20d2bdfb0801091328l7ecb881y903dac47b13d5b71@mail.gmail.com>
Date: Wed, 9 Jan 2008 16:28:22 -0500
From: "Bruce Lowekamp" <lowekamp@sipeerior.com>
To: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
Subject: Re: [P2PSIP] New draft: HIP BONE
In-Reply-To: <77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
X-Google-Sender-Auth: 8e72a6f389e70733
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: Pekka Nikander <pekka.nikander@nomadiclab.com>,
	P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

On 1/9/08, Henderson, Thomas R <thomas.r.henderson@boeing.com> wrote:
>
>
> > -----Original Message-----
> > From: Bruce Lowekamp [mailto:lowekamp@sipeerior.com]
> > Sent: Tuesday, January 08, 2008 2:16 PM
> > To: Gonzalo Camarillo
> > Cc: Pekka Nikander; P2PSIP Mailing List
> > Subject: Re: [P2PSIP] New draft: HIP BONE
> >
>
> >
> > Going with the HIP-BONE, approach, as I understand the "HIP is IP and
> > the peer protocol is OSPF" idea...
>
> I think this analogy has some weaknesses, as you have pointed out, in
> the "peer protocol is OSPF" part.  My reading of HIP BONE is that the
> overall goal is to allow the peer protocol and other applications to
> deal with HIP identifiers instead of IP addresses.  That is a worthy
> goal IMO which might free RELOAD and other applications from having to
> do ICE and handle recursive routing issues or host mobility and
> multihoming.
>
> However, the problem with this approach is that HIP needs a naming
> service or routing service to resolve identifiers to either locators or
> route lists.  This does not exist yet in HIP.  There have been proposals
> to use DHTs to provide this service, but they do not presently
> accommodate the possibility of multiple DHTs, which is pretty much a
> requirement to handle, from my perspective.  HIP BONE seems to be
> suggesting that the peer protocol can fill this gap but there appear to
> be some issues that need to be worked out, or maybe HIP BONE needs its
> own resolution/routing service separate from the application overlay.
>

I think this is hitting on the key issue.  A p2p overlay is
fundamentally about routing.  It already has its own ID/locator
mechanism.  Trying to separate the routing and resource querying
aspects is going to be difficult.  Rather than try, I think it's best
to take advantage of the connections.  The peer protocol provides a
component that can answer routing questions for the HIP layer.  The
HIP layer provides the traversal/connection opening functionality, a
link layer capability, and delivers to applications the ability to
transparently use end-to-end connections while being unaware of the
details.

I don't think that having HIP BONE have a separate resolution/routing
service from the application overlay would help.  I'm not even sure
what that would mean, given the relationship between overlay routing
and resource storage.

> Question:  How would RELOAD or other proposals change if that were the
> case?  Would the benefits greatly outweigh any drawbacks to this
> abstraction?

In the RELOAD-02 architecture, what you would presumably do would be
to replace the bottom two layers (Forwarding Layer and Transport
Layer) with HIP.  The routing queries are merely an upcall between
layers.

This is just one possibility, but it is reasonably clean, and it
should be easy to clarify what functions the HIP layers are providing
when they're used, compared to when non-HIP forwarding and transport
layers are used.

Bruce

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



From p2psip-bounces@ietf.org Wed Jan 09 16:46:34 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCikp-0004Gm-2l; Wed, 09 Jan 2008 16:46:31 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JCikn-0004Gg-To
	for p2psip@ietf.org; Wed, 09 Jan 2008 16:46:29 -0500
Received: from exprod6og107.obsmtp.com ([64.18.1.208])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JCikn-0001vn-8K
	for p2psip@ietf.org; Wed, 09 Jan 2008 16:46:29 -0500
Received: from source ([192.150.11.134]) by exprod6ob107.postini.com
	([64.18.5.12]) with SMTP; Wed, 09 Jan 2008 13:46:22 PST
Received: from inner-relay-3.eur.adobe.com (inner-relay-3.adobe.com
	[192.150.20.198] (may be forged))
	by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	m09Lhiin000692; Wed, 9 Jan 2008 13:43:48 -0800 (PST)
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
	m09LjsFX027054; Wed, 9 Jan 2008 13:46:06 -0800 (PST)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 9 Jan 2008 13:46:00 -0800
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [P2PSIP] New draft: HIP BONE
Date: Wed, 9 Jan 2008 13:45:48 -0800
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D223AE4D2@namail5.corp.adobe.com>
In-Reply-To: <20d2bdfb0801091328l7ecb881y903dac47b13d5b71@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] New draft: HIP BONE
Thread-Index: AchTBraRkJm69sr0RFiUJpCnlk+Y8wAAZIWA
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com><20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com><77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<20d2bdfb0801091328l7ecb881y903dac47b13d5b71@mail.gmail.com>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Bruce Lowekamp" <lowekamp@sipeerior.com>,
	"Henderson, Thomas R" <thomas.r.henderson@boeing.com>
X-OriginalArrivalTime: 09 Jan 2008 21:46:00.0078 (UTC)
	FILETIME=[0603C2E0:01C85309]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: Pekka Nikander <pekka.nikander@nomadiclab.com>,
	P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Bruce,

>In the RELOAD-02 architecture, what you would presumably do would be
>to replace the bottom two layers (Forwarding Layer and Transport
>Layer) with HIP.  The routing queries are merely an upcall between
>layers.

What you describe seems very solid and may be applicable to other P2PSIP
proposals as well.

Would you have time to elaborate in a little write-up and add a diagram
for the RELOAD case?
It could but need not be an I-D at this point.

Henry

-----Original Message-----
From: Bruce Lowekamp [mailto:lowekamp@sipeerior.com]=20
Sent: Wednesday, January 09, 2008 3:28 PM
To: Henderson, Thomas R
Cc: Pekka Nikander; P2PSIP Mailing List
Subject: Re: [P2PSIP] New draft: HIP BONE

On 1/9/08, Henderson, Thomas R <thomas.r.henderson@boeing.com> wrote:
>
>
> > -----Original Message-----
> > From: Bruce Lowekamp [mailto:lowekamp@sipeerior.com]
> > Sent: Tuesday, January 08, 2008 2:16 PM
> > To: Gonzalo Camarillo
> > Cc: Pekka Nikander; P2PSIP Mailing List
> > Subject: Re: [P2PSIP] New draft: HIP BONE
> >
>
> >
> > Going with the HIP-BONE, approach, as I understand the "HIP is IP
and
> > the peer protocol is OSPF" idea...
>
> I think this analogy has some weaknesses, as you have pointed out, in
> the "peer protocol is OSPF" part.  My reading of HIP BONE is that the
> overall goal is to allow the peer protocol and other applications to
> deal with HIP identifiers instead of IP addresses.  That is a worthy
> goal IMO which might free RELOAD and other applications from having to
> do ICE and handle recursive routing issues or host mobility and
> multihoming.
>
> However, the problem with this approach is that HIP needs a naming
> service or routing service to resolve identifiers to either locators
or
> route lists.  This does not exist yet in HIP.  There have been
proposals
> to use DHTs to provide this service, but they do not presently
> accommodate the possibility of multiple DHTs, which is pretty much a
> requirement to handle, from my perspective.  HIP BONE seems to be
> suggesting that the peer protocol can fill this gap but there appear
to
> be some issues that need to be worked out, or maybe HIP BONE needs its
> own resolution/routing service separate from the application overlay.
>

I think this is hitting on the key issue.  A p2p overlay is
fundamentally about routing.  It already has its own ID/locator
mechanism.  Trying to separate the routing and resource querying
aspects is going to be difficult.  Rather than try, I think it's best
to take advantage of the connections.  The peer protocol provides a
component that can answer routing questions for the HIP layer.  The
HIP layer provides the traversal/connection opening functionality, a
link layer capability, and delivers to applications the ability to
transparently use end-to-end connections while being unaware of the
details.

I don't think that having HIP BONE have a separate resolution/routing
service from the application overlay would help.  I'm not even sure
what that would mean, given the relationship between overlay routing
and resource storage.

> Question:  How would RELOAD or other proposals change if that were the
> case?  Would the benefits greatly outweigh any drawbacks to this
> abstraction?

In the RELOAD-02 architecture, what you would presumably do would be
to replace the bottom two layers (Forwarding Layer and Transport
Layer) with HIP.  The routing queries are merely an upcall between
layers.

This is just one possibility, but it is reasonably clean, and it
should be easy to clarify what functions the HIP layers are providing
when they're used, compared to when non-HIP forwarding and transport
layers are used.

Bruce

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

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



From p2psip-bounces@ietf.org Wed Jan 09 17:25:11 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCjM4-0002hc-Er; Wed, 09 Jan 2008 17:25:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JCjM3-0002hC-JF
	for p2psip@ietf.org; Wed, 09 Jan 2008 17:24:59 -0500
Received: from usaga01-in.huawei.com ([206.16.17.211])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JCjM1-0003VW-LI
	for p2psip@ietf.org; Wed, 09 Jan 2008 17:24:59 -0500
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 <0JUE008HBE9KPO@usaga01-in.huawei.com> for
	p2psip@ietf.org; Wed, 09 Jan 2008 14:24:57 -0800 (PST)
Received: from s73602 (cpe-72-190-0-23.tx.res.rr.com [72.190.0.23])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006))
	with ESMTPA id <0JUE004G4E9IRJ@usaga01-in.huawei.com> for
	p2psip@ietf.org; Wed, 09 Jan 2008 14:24:56 -0800 (PST)
Date: Wed, 09 Jan 2008 16:24:19 -0600
From: Spencer Dawkins <spencer@mcsr-labs.org>
Subject: Re: [P2PSIP] New draft: HIP BONE
To: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
Message-id: <086801c8530e$611d8030$6601a8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
Content-type: text/plain; format=flowed; charset=iso-8859-1;
	reply-type=original
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: Pekka Nikander <pekka.nikander@nomadiclab.com>,
	P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hi, Thomas,

I'm not sure I'm entirely in sync with the conversation, but when I was
speed-reading HIP BONE over the Christmas break, I saw the following text, 
which seems to say that P2P comes first, because the overlay is used to 
route I1 packets. ("HIP over P2P")

My understanding of HIPHOP was that HIP came first, because it was used to 
forward P2P packets without "popping up" to a P2P protocol engine at every 
hop. ("P2P over HIP")

If I am misrepresenting either of these proposals, I apologize.

If I am not, I am confused, and think that this is one of the key design 
decisions we need to discuss before moving forward with a P2P/HIP proposal, 
which I hope we do, by the way.

Thanks,

Spencer

>From draft-camarillo-hip-bone-00.txt:

3.2.  Connection Establishment

   Nodes in an overlay need to establish connection with other nodes in
   different cases.  For example, a node typically has connections to
   the nodes in its finger table.  Nodes also need to establish
   connections with other nodes in order to exchange application-layer
   messages.

   As discussed earlier, HIP uses the base exchange to establish
   connections.  Therefore, a node uses an I1 packet to establish a
   connection with another node in the overlay.  Nodes in the overlay
   forward I1 packets in a hop-by-hop fashion according to the overlay's
   routing table towards its destination.  If the overlay nodes have
   active connections with other nodes in their finger tables and if
   those connections are protected (typically with IPsec ESP), I1
   packets may be sent over protected connections between nodes.
   Alternatively, if there no such an active connection but the sending
   peer node has a valid locator for the next hop, the I1 packets may be
   forwarded directly, in a similar fashion to how I1 packets are today
   forwarded by the HIP RVS service.

   Since HIP supports NAT traversal, a HIP base exchange over the
   overlay will perform an ICE offer/answer exchange between the nodes
   that are establishing the connection.  In order to perform this
   exchange, the nodes need to first gather candidate addresses.  Which
   nodes can be used to obtain reflexive address candidates and which
   ones can be used to obtain relayed candidates is defined by the peer
   protocol.

3.3.  Lightweight Message Exchanges

   In some cases, nodes need to perform a lightweight query to another
   node.  In this situation, establishing a connection using the
   mechanisms in Section 3.2 for a simple query would be an overkill.  A
   better solution is to forward a HIP message through the overlay with
   the query and another one with the response to the query.  The
   payload of such HIP packet is integrity protected.  Nodes in the
   overlay forward this HIP packet in a hop-by-hop fashion according to
   the overlay's routing table towards its destination, typically
   through the protected connections established between them.



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



From p2psip-bounces@ietf.org Wed Jan 09 18:20:05 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCkDD-0002Tj-PZ; Wed, 09 Jan 2008 18:19:55 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JCkDB-0002P0-JG
	for p2psip@ietf.org; Wed, 09 Jan 2008 18:19:53 -0500
Received: from u-173-c156.cs.uni-tuebingen.de ([134.2.173.156]
	helo=smtp.cs.uni-tuebingen.de)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JCkDA-00041w-RN
	for p2psip@ietf.org; Wed, 09 Jan 2008 18:19:53 -0500
Received: from p54a01ec1.dip0.t-ipconnect.de ([84.160.30.193]
	helo=[192.168.178.20])
	by smtp.cs.uni-tuebingen.de with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.60) (envelope-from <ali.fessi@uni-tuebingen.de>)
	id 1JCkCX-0002wA-Bg; Thu, 10 Jan 2008 00:19:13 +0100
Message-ID: <4785566F.7000700@uni-tuebingen.de>
Date: Thu, 10 Jan 2008 00:19:11 +0100
From: Ali Fessi <ali.fessi@uni-tuebingen.de>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Spencer Dawkins <spencer@mcsr-labs.org>
Subject: Re: [P2PSIP] New draft: HIP BONE
References: <476BA8D9.4010203@ericsson.com>	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>	<476E2B7C.9070601@ericsson.com>	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<086801c8530e$611d8030$6601a8c0@china.huawei.com>
In-Reply-To: <086801c8530e$611d8030$6601a8c0@china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Cc: Pekka Nikander <pekka.nikander@nomadiclab.com>,
	P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

maybe the best way to understand the inter-working between HIP and P2P 
is to compare it with the inter-working between SIP and P2P.

HIP has the Identifier/Locator separation and SIP has also the 
SIP-URI/Contact-URI seperation.

In both cases, the P2P protocol is used for the overlay maintenance 
(e.g. join and leave).

and usually it is also the P2P protocol that will resolve lookups and be 
responsible for storing data, (i.e. get and put)

So you can use the P2P protocol to resolve a SIP-URI to a Contact-URI 
and perform B2B SIP signaling afterwards.

Simlarly, you can use the P2P protocol to resolve a HIP ORCHID to a 
Locator, and then when you get the Locator start the HIP handshake.

And in fact, this is maybe something confusing in the HIP BONE draft

(many thanks BTW to the authors here. IMHO, the draft clarified many 
things about HIP and its potential use for P2PSIP),

because HIP BONE says that a I1 message is transported hop-by-hop in the 
overlay. I would let the P2P protocol resolve the HIP Identifier to a 
Locator first, and then send the I1 message directly to the HIP Responder.

Cheers,
  Ali


Spencer Dawkins wrote:
> Hi, Thomas,
> 
> I'm not sure I'm entirely in sync with the conversation, but when I was
> speed-reading HIP BONE over the Christmas break, I saw the following 
> text, which seems to say that P2P comes first, because the overlay is 
> used to route I1 packets. ("HIP over P2P")
> 
> My understanding of HIPHOP was that HIP came first, because it was used 
> to forward P2P packets without "popping up" to a P2P protocol engine at 
> every hop. ("P2P over HIP")
> 
> If I am misrepresenting either of these proposals, I apologize.
> 
> If I am not, I am confused, and think that this is one of the key design 
> decisions we need to discuss before moving forward with a P2P/HIP 
> proposal, which I hope we do, by the way.
> 
> Thanks,
> 
> Spencer
> 
>> From draft-camarillo-hip-bone-00.txt:
> 
> 3.2.  Connection Establishment
> 
>   Nodes in an overlay need to establish connection with other nodes in
>   different cases.  For example, a node typically has connections to
>   the nodes in its finger table.  Nodes also need to establish
>   connections with other nodes in order to exchange application-layer
>   messages.
> 
>   As discussed earlier, HIP uses the base exchange to establish
>   connections.  Therefore, a node uses an I1 packet to establish a
>   connection with another node in the overlay.  Nodes in the overlay
>   forward I1 packets in a hop-by-hop fashion according to the overlay's
>   routing table towards its destination.  If the overlay nodes have
>   active connections with other nodes in their finger tables and if
>   those connections are protected (typically with IPsec ESP), I1
>   packets may be sent over protected connections between nodes.
>   Alternatively, if there no such an active connection but the sending
>   peer node has a valid locator for the next hop, the I1 packets may be
>   forwarded directly, in a similar fashion to how I1 packets are today
>   forwarded by the HIP RVS service.
> 
>   Since HIP supports NAT traversal, a HIP base exchange over the
>   overlay will perform an ICE offer/answer exchange between the nodes
>   that are establishing the connection.  In order to perform this
>   exchange, the nodes need to first gather candidate addresses.  Which
>   nodes can be used to obtain reflexive address candidates and which
>   ones can be used to obtain relayed candidates is defined by the peer
>   protocol.
> 
> 3.3.  Lightweight Message Exchanges
> 
>   In some cases, nodes need to perform a lightweight query to another
>   node.  In this situation, establishing a connection using the
>   mechanisms in Section 3.2 for a simple query would be an overkill.  A
>   better solution is to forward a HIP message through the overlay with
>   the query and another one with the response to the query.  The
>   payload of such HIP packet is integrity protected.  Nodes in the
>   overlay forward this HIP packet in a hop-by-hop fashion according to
>   the overlay's routing table towards its destination, typically
>   through the protected connections established between them.
> 
> 
> 
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.ietf.org/mailman/listinfo/p2psip
> 


-- 
Ali Fessi
Computer Networks and Internet
University of Tuebingen, Germany
Phone: +49 7071 29-70576 / Fax: +49 7071 29-5220
EMail: ali.fessi@uni-tuebingen.de
Web: http://net.informatik.uni-tuebingen.de/~fessi/

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



From p2psip-bounces@ietf.org Wed Jan 09 19:37:49 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JClQW-00015l-Ne; Wed, 09 Jan 2008 19:37:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JClQV-0000yY-6P
	for p2psip@ietf.org; Wed, 09 Jan 2008 19:37:43 -0500
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JClQU-00050x-QM
	for p2psip@ietf.org; Wed, 09 Jan 2008 19:37:43 -0500
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id m0A0bLF8022284
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Wed, 9 Jan 2008 18:37:32 -0600 (CST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	m0A0bKEx000764; Wed, 9 Jan 2008 16:37:21 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	m0A0bKuc000761; Wed, 9 Jan 2008 16:37:20 -0800 (PST)
Received: from XCH-NW-5V1.nw.nos.boeing.com ([130.247.55.44]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 9 Jan 2008 16:37:20 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [P2PSIP] New draft: HIP BONE
Date: Wed, 9 Jan 2008 16:37:20 -0800
Message-ID: <77F357662F8BFA4CA7074B0410171B6D04049B28@XCH-NW-5V1.nw.nos.boeing.com>
In-Reply-To: <086801c8530e$611d8030$6601a8c0@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] New draft: HIP BONE
Thread-Index: AchTDng/ZbI8OmEvSRucmO/8lF7iIgAET++w
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com><20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com><77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<086801c8530e$611d8030$6601a8c0@china.huawei.com>
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "Spencer Dawkins" <spencer@mcsr-labs.org>
X-OriginalArrivalTime: 10 Jan 2008 00:37:20.0751 (UTC)
	FILETIME=[F5C5F7F0:01C85320]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: Pekka Nikander <pekka.nikander@nomadiclab.com>,
	P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

=20

> -----Original Message-----
> From: Spencer Dawkins [mailto:spencer@mcsr-labs.org]=20
> Sent: Wednesday, January 09, 2008 2:24 PM
> To: Henderson, Thomas R
> Cc: Pekka Nikander; P2PSIP Mailing List
> Subject: Re: [P2PSIP] New draft: HIP BONE
>=20
> Hi, Thomas,
>=20
> I'm not sure I'm entirely in sync with the conversation, but=20
> when I was
> speed-reading HIP BONE over the Christmas break, I saw the=20
> following text,=20
> which seems to say that P2P comes first, because the overlay=20
> is used to=20
> route I1 packets. ("HIP over P2P")
>=20
> My understanding of HIPHOP was that HIP came first, because=20
> it was used to=20
> forward P2P packets without "popping up" to a P2P protocol=20
> engine at every=20
> hop. ("P2P over HIP")
>=20
> If I am misrepresenting either of these proposals, I apologize.
>=20
> If I am not, I am confused, and think that this is one of the=20
> key design=20
> decisions we need to discuss before moving forward with a=20
> P2P/HIP proposal,=20
> which I hope we do, by the way.

Spencer,

Maybe the authors can clarify.  I agree that the text you quote suggests
that difference.  OTOH, there is Figure 5 that suggests that it is
mainly peer protocols over HIP (although I don't know whether the fact
that peer protocols "overhang" the data transport has any significance
in that diagram), and I thought that Gonzalo remarked during the Boeing
call that HIP BONE and HIP HOP were basically the same. =20

quoting from the draft:


   The HIP BONE allows quite a lot of flexibility how to arrange the
   different protocols in detail.  Figure 5 shows one potential stack
   structure.


      +-----------------------+--------------+
      | peer protocols        |     media    |
      +------------------+----+--------------+
      | HIP signalling   |   data transport  |
      |                                      |
      +------------------+-------------------+
      | NAT    | non-NAT |                   |
      |                  |                   |
      |      IPv4        |       IPv6        |
      +------------------+-------------------+

                Figure 5: Example HIP BONE stack structure

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



From p2psip-bounces@ietf.org Thu Jan 10 06:11:36 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCvJt-0008Nb-LZ; Thu, 10 Jan 2008 06:11:33 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JCvJs-0008L9-5r
	for p2psip@ietf.org; Thu, 10 Jan 2008 06:11:32 -0500
Received: from n2.nomadiclab.com ([193.234.219.2])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JCvJq-00072w-T2
	for p2psip@ietf.org; Thu, 10 Jan 2008 06:11:32 -0500
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 52ED61EF105;
	Thu, 10 Jan 2008 13:10:59 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id DF18B1EF104;
	Thu, 10 Jan 2008 13:10:58 +0200 (EET)
In-Reply-To: <20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v753)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <57B24871-D72C-4043-A9F4-B2E5AFA8CC52@nomadiclab.com>
Content-Transfer-Encoding: 7bit
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: Re: [P2PSIP] New draft: HIP BONE
Date: Thu, 10 Jan 2008 10:17:37 +0200
To: Bruce Lowekamp <lowekamp@sipeerior.com>
X-Mailer: Apple Mail (2.753)
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8c5db863102a3ada84e0cd52a81a79e
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hi Bruce,

On Dec 23, 2007 4:33 AM, Gonzalo Camarillo  
<Gonzalo.Camarillo@ericsson.com> wrote:
>> Regarding your question about Sections 3.2 and 3.3 when RELOAD is  
>> the peer protocol and HIP BONE is used for connection management,  
>> the idea is to use HIP, instead of RELOAD, to perform connection  
>> management. All the other functions RELOAD typically performs are  
>> still performed by RELOAD.
>>
>> RELOAD defines the CONNECT primitive and the TUNNEL primitive. If  
>> HIP is being used, you would use the CONNECT primitive of HIP  
>> (i.e., an I1 packet) *instead* of the CONNECT primitive of RELOAD.  
>> The same way, you would use the TUNNEL primitive of HIP (i.e., a  
>> HIP message) *instead* of the TUNNEL primitive of RELOAD.

On 9 Jan 2008, at 00:16, Bruce Lowekamp wrote:
>
> This is where I still get confused, and I think this is a pretty  
> big architectural issue.  The combination of 3.2, 3.3, and 6 still  
> leave some questions in my mind as to exactly what is being  
> proposed, so let me try to form up an example for discussion purposes.

Briefly, what I had in mind when writing the HIP BONE draft was your  
"HIP routing table" approach below.  While I agree with you that at  
the architectural level the question is relatively big, I think that  
when you go to the implementation level the actual difference between  
the "HIP routing table" and "HIP link layer" approaches will be quite  
small.  The key issue here is whether it is possible to divide the  
work between a "routing table" and a "forwarding table".  I don't  
know the proposed peer protocols well enough to be able to answer  
that question.  If it indeed is possible to make such a division,  
then I think the difference between "HIP routing table" and "HIP link  
layer" almost disappears.  Otherwise the situation gets hairier, as  
you apparently suggest below.

But let's have a look at your example:
> Suppose I have an overlay with the following connections between  
> peers (labeled with their peerid):
>
> 1 ------ 5 ------ 10
>
> So 1 has 5 in its routing table (and thus a direct connection) but  
> not 10.  5 has direct connections to 1 and 10.  I'm assuming  
> recursive routing and am not being precise with a DHT algorithm for  
> the purposes of this example.
>
> 10 is responsible for a resource, 9, that 1 wants to query for.  In  
> a non-HIP DHT implementation, 1 sends a query "to" 9.  It looks up  
> for the closest match in its routing table and discovers it is 5,  
> then it sends the message to 5.  5 performs a similar lookup and  
> discovers that its closest match is 10, so it forwards the query to  
> 10.
>
> Going with the HIP-BONE, approach, as I understand the "HIP is IP  
> and the peer protocol is OSPF" idea, I see two approaches that  
> would meet that requirement:
>
> - the peer protocol loads enough information into the HIP layer  
> that the HIP layer on peer 1 knows that the next hop for a message  
> bound for "9" is 5.  I will refer to this as the hip routing table  
> approach.

In this approach I would call the "information loaded into the HIP  
layer" as the forwarding table.

> - the peer protocol sets the next-hop for the query to "5" based on  
> its own routing table, and lets the HIP layer forward it.  I will  
> refer to this as the hip link layer approach.

The only difference that I can see between the previous one and this  
one is that here there are no explicit routing table.  Hence, instead  
of doing the typical thing routers do, i.e., to compute a forwarding  
table from the routing table as a "batch job" the forwarding decision  
is performed "lazily" on demand.

> The hip routing table approach looks great from a layering  
> perspective, but implementation looks to be very hard.

Why?  Do you allude that the various overlay routing protocols are  
sufficiently different from the IP routing protocols so that one  
cannot compute a forwarding table?  Or is there some other  
implementation problem that you are thinking about?

> Since there are multiple DHT (and unstructured overlay) algorithms  
> with different routing rules, there would have to be a pluggable  
> routing algorithm loaded into the HIP layer by the DHT algorithm or  
> there  needs to be
> an upcall from the HIP layer into the peer protocol layer to query  
> for the next-hop for messages.

So, you do seem to be saying that it is impossible to process the DHT- 
layer routing information into a consistent forwarding table format  
that can be used by a single look-up algorithm.  Now, I have to  
confess that I don't understand this argument at all.  Given that for  
each packet the forwarding decision has to eventually be made, the  
time complexity of computing a forwarding decision must be manageable  
(sub-linear w.r.t the number of nodes in the overlay).  Hence, are  
you saying that there is no reasonable representation of the  
forwarding table, i.e., that the space complexity will be  
overwhelming?  But then I don't understand either, as my  
understanding is that with e.g. Bloom filters you can represent an  
random collection of sets with in a relatively small space.  [In the  
case of Bloom filters we of course have the question of false  
positives, but I cannot see a big problem if some packets get briefly  
duplicated on the overlay.  Intuitively, That doesn't seem to add  
much to the already pretty high inefficiency of the overlay.]

> In the hip link layer approach, the peer protocol layer knows that  
> the current set of next-hop candidates are, and it runs the DHT  
> routing algorithm in the conventional sense, telling the HIP layer  
> what the next hop for a message is.  This seems like a much simpler  
> approach to implement, but limits the usefulness of HIP.

I agree with you that this would limit the usefulness of HIP.   
However, if there is a forwarding table, then the practical level  
difference between the "HIP routing table" and "HIP link layer" boils  
down to on which layer you store the forwarding table.

> So the first question is whether HIP-BONE is intended to specify  
> one of these approaches, and if so, which one?  I believe it's the  
> hip routing table approach.


Well, at the time of writing I couldn't see such a difference.   
Hence, perhaps the "right" answer to this question is "neither".   
Instead, while HIP BONE in its current form doesn't specify either of  
the approaches, it alludes towards a "third" approach, i.e., towards  
separating the routing and forwarding tables, which makes the  
implementation-level difference very small.  Hence, from that point  
of view, HIP BONE would allow either architectural choice.

> Next, let's take the case of 3.3, "lightweight message exchange."   
> As I understand 3.3, it should work fine in the hip routing table  
> approach for both application and peer protocol message exchanges.   
> In the hip link layer approach, peer protocol messages can be  
> delivered this way, but application messages cannot (they would  
> require a direct connection).

I don't quite understand what you are saying.  Would you please clarify?

> Next, how about CONNECT messages.  Suppose that now peer 1 wants to  
> establish a direct connection to peer 10 for some reason.  Your  
> email indicates that there will be no CONNECT messages as in  
> RELOAD, but instead there will only be I1 etc messages.  Let's just  
> assume that the peer protocol has some way of indicating that it  
> wants to be able to send messages directly to another peer rather  
> than over the overlay.

I'm following so far.

> So in the hip routing table approach, the I1 etc messages are  
> routed via 5 using HIP to 10 and eventually a new direct connection  
> is established.

Well, depending on many factors, it may be only a subset of the HIP  
base exchange messages that would be routed over the overlay (through  
node 5); some of them (like perhaps R2) could perhaps be sent  
directly, at least in some cases.  So, there is some flexibility  
here, but at least I don't quite understand the situation in cases  
where both 1 and 10 are behind NATs.

> In the hip link layer approach, the peer protocol would have to  
> insert the I1 into a peer message and forward
> it itself.  That would work, but it's a bit cumbersome.

Again, I don't understand.  Why would the peer protocol need to  
insert I1 into a peer message?

> What continues to confuse me, and what I think is the hardest  
> architectural question here, is how the issue I mentioned above:  
> "there would have to be a pluggable routing algorithm loaded into  
> the HIP layer by the DHT algorithm or there  needs to be an upcall  
> from the HIP layer into the peer protocol layer to query for the  
> next-hopfor messages" is solved.

As I indicated above, my idea was to separate the routing table and  
forwarding table.  Right now I cannot see why it would not work, but  
maybe I'm just ignorant about the various overlay routing protocols.

<snipping the rest>

--Pekka Nikander


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



From p2psip-bounces@ietf.org Thu Jan 10 07:40:50 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCwiG-0006rl-GI; Thu, 10 Jan 2008 07:40:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JCwiF-0006rf-CA
	for p2psip@ietf.org; Thu, 10 Jan 2008 07:40:47 -0500
Received: from n2.nomadiclab.com ([193.234.219.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JCwiD-0005wt-1L
	for p2psip@ietf.org; Thu, 10 Jan 2008 07:40:47 -0500
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id C73AB1EF105;
	Thu, 10 Jan 2008 14:40:11 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 8F05A1EF104;
	Thu, 10 Jan 2008 14:40:11 +0200 (EET)
In-Reply-To: <77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
Mime-Version: 1.0 (Apple Message framework v753)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
Content-Transfer-Encoding: 7bit
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: Re: [P2PSIP] New draft: HIP BONE
Date: Thu, 10 Jan 2008 14:40:09 +0200
To: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
X-Mailer: Apple Mail (2.753)
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Tom,

>> Going with the HIP-BONE, approach, as I understand the "HIP is IP  
>> and the peer protocol is OSPF" idea...
>
> I think this analogy has some weaknesses, as you have pointed out,  
> in the "peer protocol is OSPF" part.  My reading of HIP BONE is  
> that the overall goal is to allow the peer protocol and other  
> applications to deal with HIP identifiers instead of IP addresses.

Yes and no.  The goal certainly is that there may be some (or even  
most) applications that use the HIP identifiers directly.  However,  
for the peer protocols and maybe also some applications it may make  
more sense to use other kinds of identifiers.  That's why we made the  
distinction between Peer IDs and HIP identities in Section 3.1.

> That is a worthy goal IMO which might free RELOAD and other  
> applications from having to do ICE and handle recursive routing  
> issues or host mobility and multihoming.

That is certainly part of our goal.

> However, the problem with this approach is that HIP needs a naming  
> service or routing service to resolve identifiers to either  
> locators or route lists.  This does not exist yet in HIP.

Right.  I agree.

> There have been proposals to use DHTs to provide this service, but  
> they do not presently accommodate the possibility of multiple DHTs,  
> which is pretty much a requirement to handle, from my perspective.

That issue Gonzalo and I have discussed extensively.  On my part I  
still don't quite understand the requirement (as is probably visible  
from the previous exchange of message between you Tom and me).   
However, for example, one possibility here would be that the routing  
tables could contain PeerIDs (distinct from HIP identifiers) while  
the forwarding tables would contain HIP identifiers.  However, of  
course, whether that would work in a scalable manner depends on many  
details that haven't really been figure out yet.  For example, in  
such an approach it might be necessary to define a new HIP parameter  
(or reuse the existing HOST_ID parameter) to carry the PeerID when  
routing HIP packets through the overlay.

> HIP BONE seems to be suggesting that the peer protocol can fill  
> this gap ...

Exactly.

> ... but there appear to be some issues that need to be worked out,  
> or maybe HIP BONE needs its own resolution/routing service separate  
> from the application overlay.

There are certainly many things that need to be worked out in order  
to make HIP BONE practical.  The present draft was more meant to  
provide an overall map of some territory rather than providing detail  
instructions on how to get to the goal.  But, from the HIP BONE point  
of view, it would not make sense to make the peer protocol and a  
resolution or routing service separate.  Ideally, HIP BONE would  
support both P2PSIP based peer protocols and other, unrelated overlay  
or identity routing protocols, perhaps something similar to Berkeley  
DONA.

<snip>

> Question (for P2PSIP):  ...

I think your questions are very good, but since I am not really a  
member of the P2PSIP community, I don't feel myself able to answer to  
those.

--Pekka


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



From p2psip-bounces@ietf.org Thu Jan 10 07:45:49 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCwn7-000652-FK; Thu, 10 Jan 2008 07:45:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JCwn6-00064u-NX
	for p2psip@ietf.org; Thu, 10 Jan 2008 07:45:48 -0500
Received: from n2.nomadiclab.com ([193.234.219.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JCwn6-00069h-9b
	for p2psip@ietf.org; Thu, 10 Jan 2008 07:45:48 -0500
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 8C9A11EF105;
	Thu, 10 Jan 2008 14:45:17 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 22BE21EF104;
	Thu, 10 Jan 2008 14:45:17 +0200 (EET)
In-Reply-To: <4785566F.7000700@uni-tuebingen.de>
References: <476BA8D9.4010203@ericsson.com>	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>	<476E2B7C.9070601@ericsson.com>	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<086801c8530e$611d8030$6601a8c0@china.huawei.com>
	<4785566F.7000700@uni-tuebingen.de>
Mime-Version: 1.0 (Apple Message framework v753)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <833EB4F9-41EE-41E5-A951-DE2AF0FE9FF8@nomadiclab.com>
Content-Transfer-Encoding: 7bit
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: Re: [P2PSIP] New draft: HIP BONE
Date: Thu, 10 Jan 2008 14:45:15 +0200
To: Ali Fessi <ali.fessi@uni-tuebingen.de>
X-Mailer: Apple Mail (2.753)
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hi Ali,

On 10 Jan 2008, at 01:19, Ali Fessi wrote:
<snip>
> Simlarly, you can use the P2P protocol to resolve a HIP ORCHID to a  
> Locator, and then when you get the Locator start the HIP handshake.
>
> And in fact, this is maybe something confusing in the HIP BONE  
> draft [...] because HIP BONE says that a I1 message is transported  
> hop-by-hop in the overlay. I would let the P2P protocol resolve the  
> HIP Identifier to a Locator first, and then send the I1 message  
> directly to the HIP Responder.

That has been tried and there is even a prototype working on  
PlanetLab using OpenDHT, but unfortunately there appears to be two  
problems.  First, OpenDHT latencies appear to be too long and  
unpredictable, sometimes minutes and often exceeding 10 seconds.  But  
that may be an implementation problem that can be fixed.  The second,  
bigger problem is that if both the initiator and the responder are  
behind NATs, the you just cannot send the I1 message directly to the  
HIP responder.

The latter is the reason why we chose to use a Berkeley i3 -like  
system in both Hi3 and in HIP BONE, i.e., to forward HIP messages  
through the overlay instead of using it in a typical DHT put/get manner.

--Pekka Nikander


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



From p2psip-bounces@ietf.org Thu Jan 10 07:49:55 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCwr5-00030R-1J; Thu, 10 Jan 2008 07:49:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JCwr3-00030F-VR
	for p2psip@ietf.org; Thu, 10 Jan 2008 07:49:53 -0500
Received: from n2.nomadiclab.com ([193.234.219.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JCwr3-0006F3-H8
	for p2psip@ietf.org; Thu, 10 Jan 2008 07:49:53 -0500
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 8985B1EF105;
	Thu, 10 Jan 2008 14:49:22 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 21DD91EF104;
	Thu, 10 Jan 2008 14:49:22 +0200 (EET)
In-Reply-To: <77F357662F8BFA4CA7074B0410171B6D04049B28@XCH-NW-5V1.nw.nos.boeing.com>
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com><20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com><77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<086801c8530e$611d8030$6601a8c0@china.huawei.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B28@XCH-NW-5V1.nw.nos.boeing.com>
Mime-Version: 1.0 (Apple Message framework v753)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <6384D11E-5D7D-48E4-B86A-816269EC864C@nomadiclab.com>
Content-Transfer-Encoding: 7bit
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: Re: [P2PSIP] New draft: HIP BONE
Date: Thu, 10 Jan 2008 14:49:20 +0200
To: Spencer Dawkins <spencer@mcsr-labs.org>,
	Thomas R Henderson <thomas.r.henderson@boeing.com>
X-Mailer: Apple Mail (2.753)
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Spencer and Tom,

>> I'm not sure I'm entirely in sync with the conversation, but when  
>> I was speed-reading HIP BONE over the Christmas break, I saw the  
>> following text, which seems to say that P2P comes first, because  
>> the overlay is used to route I1 packets. ("HIP over P2P")

I think your confusion here is mixing the "overlay" and the "peer  
protocol".  In HIP BONE case the overlay is formed by combining HIP  
and the peer protocol.  Hence, while HIP packets can be routed over  
the overlay, that does not mean that they are routed over the peer  
protocol.

>> My understanding of HIPHOP was that HIP came first, because it was  
>> used to forward P2P packets without "popping up" to a P2P protocol  
>> engine at every hop. ("P2P over HIP")

Perhaps a key issue in understanding this is the separation of the  
routing table and the forwarding table; see my previous message  
earlier today.

> Maybe the authors can clarify.  I agree that the text you quote  
> suggests that difference.  OTOH, there is Figure 5 that suggests  
> that it is mainly peer protocols over HIP

Yes.

> (although I don't know whether the fact that peer protocols  
> "overhang" the data transport has any significance in that diagram),

Yes it does.  It means that you can use either existing HIP  
associations (data transport) for transporting peer protocol packets  
between nodes (Section 3.2), or you may piggyback them in HIP  
signalling messages (Section 3.3).

<snip>

--Pekka Nikander


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



From p2psip-bounces@ietf.org Thu Jan 10 11:19:51 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JD08B-0007Hs-DP; Thu, 10 Jan 2008 11:19:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JD08A-0007HU-Fb
	for p2psip@ietf.org; Thu, 10 Jan 2008 11:19:46 -0500
Received: from wa-out-1112.google.com ([209.85.146.180])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JD086-0002FI-Sb
	for p2psip@ietf.org; Thu, 10 Jan 2008 11:19:46 -0500
Received: by wa-out-1112.google.com with SMTP id k40so1566528wah.25
	for <p2psip@ietf.org>; Thu, 10 Jan 2008 08:19:40 -0800 (PST)
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=XD2FlHP/qbrunyMZXK7GcPe56hIPW+kRtjzLHrAbZJE=;
	b=dH8FZUWIdasZH2HsLG2eCiMwJfjRBsjU5Q3eiukOfEq0TDcXa2W3+eBteoqS78SLvhyYiMxvvV6+bfLN5NgIfn/I5SgvhthaJDrug/OvGzkQ/k9oUF13i6hCzYshUappBR9E8lgmKBQxwisuxYyHcFyI8y1Hgh9l/udYtXE+NJA=
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=jcVs8zgVARcO0XrtdqNznBwSh7GJMfyh6SkO73SXxyrSz+z3u7LZ1YPpvPXP/WOZSWVuCsLI0+mVpGwRoDyTZpts1k4VJ9vVq8TxVIIzzhkvtAoUsu9QgEH1bbm8PTB+z47X4IZkGfl1PcTquSC5/FsXndev2Eyj4lIsDW7lo2c=
Received: by 10.114.13.1 with SMTP id 1mr2418403wam.106.1199981979855;
	Thu, 10 Jan 2008 08:19:39 -0800 (PST)
Received: by 10.114.209.13 with HTTP; Thu, 10 Jan 2008 08:19:39 -0800 (PST)
Message-ID: <20d2bdfb0801100819g64d64a2bpaaa0a9ac6a535c4d@mail.gmail.com>
Date: Thu, 10 Jan 2008 11:19:39 -0500
From: "Bruce Lowekamp" <lowekamp@sipeerior.com>
To: "Pekka Nikander" <pekka.nikander@nomadiclab.com>
Subject: Re: [P2PSIP] New draft: HIP BONE
In-Reply-To: <57B24871-D72C-4043-A9F4-B2E5AFA8CC52@nomadiclab.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<57B24871-D72C-4043-A9F4-B2E5AFA8CC52@nomadiclab.com>
X-Google-Sender-Auth: 0e2f269697c36763
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

On Jan 10, 2008 3:17 AM, Pekka Nikander <pekka.nikander@nomadiclab.com> wrote:
> Hi Bruce,
>
> > - the peer protocol sets the next-hop for the query to "5" based on
> > its own routing table, and lets the HIP layer forward it.  I will
> > refer to this as the hip link layer approach.
>
> The only difference that I can see between the previous one and this
> one is that here there are no explicit routing table.  Hence, instead
> of doing the typical thing routers do, i.e., to compute a forwarding
> table from the routing table as a "batch job" the forwarding decision
> is performed "lazily" on demand.
>
> > The hip routing table approach looks great from a layering
> > perspective, but implementation looks to be very hard.
>
> Why?  Do you allude that the various overlay routing protocols are
> sufficiently different from the IP routing protocols so that one
> cannot compute a forwarding table?  Or is there some other
> implementation problem that you are thinking about?
>

The issue I'm concerned about here is that different DHTs use
completely different routing algorithms.  For example, for Chord you
forward the message to the peer with the closest ID that is < the
target, but with Kademlia, you do a prefix match and calculate
distances with xor.  I'm sure it's possible to come up with a safe
language or something that could be used to describe how to make
routing decisions, but it's certainly non-trivial.  I think in a later
message I sent yesterday, I looked a bit more at the layering and
believe that it's not a layering violation, but an interface that is
needed between the two adjacent layers.


>
> > Next, let's take the case of 3.3, "lightweight message exchange."
> > As I understand 3.3, it should work fine in the hip routing table
> > approach for both application and peer protocol message exchanges.
> > In the hip link layer approach, peer protocol messages can be
> > delivered this way, but application messages cannot (they would
> > require a direct connection).
>
> I don't quite understand what you are saying.  Would you please clarify?
>

As I thought of the "hip link layer" approach, it was somewhat limited
in what it could do independently without the request of the peer
protocol.


> > So in the hip routing table approach, the I1 etc messages are
> > routed via 5 using HIP to 10 and eventually a new direct connection
> > is established.
>
> Well, depending on many factors, it may be only a subset of the HIP
> base exchange messages that would be routed over the overlay (through
> node 5); some of them (like perhaps R2) could perhaps be sent
> directly, at least in some cases.  So, there is some flexibility
> here, but at least I don't quite understand the situation in cases
> where both 1 and 10 are behind NATs.
>

As long as they are both reachable in the overlay, both peers behind
nats isn't a problem as long as the ice message exchanges are carried
over the overlay.

Bruce

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



From p2psip-bounces@ietf.org Thu Jan 10 16:26:37 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JD4u9-0002qt-Rm; Thu, 10 Jan 2008 16:25:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JD4u8-0002qo-VO
	for p2psip@ietf.org; Thu, 10 Jan 2008 16:25:36 -0500
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JD4u7-000828-0r
	for p2psip@ietf.org; Thu, 10 Jan 2008 16:25:36 -0500
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id m0ALPFcb011671
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Thu, 10 Jan 2008 13:25:20 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	m0ALPEcp013419; Thu, 10 Jan 2008 15:25:14 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	m0ALP66t012919; Thu, 10 Jan 2008 15:25:14 -0600 (CST)
Received: from XCH-NW-5V1.nw.nos.boeing.com ([130.247.55.44]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 10 Jan 2008 13:25:07 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [P2PSIP] New draft: HIP BONE
Date: Thu, 10 Jan 2008 13:25:06 -0800
Message-ID: <77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
In-Reply-To: <7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] New draft: HIP BONE
Thread-Index: AchThfMUSurhc6NHRsaFuWHV/qfdvwAQVAxQ
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "Pekka Nikander" <pekka.nikander@nomadiclab.com>
X-OriginalArrivalTime: 10 Jan 2008 21:25:07.0403 (UTC)
	FILETIME=[45C679B0:01C853CF]
X-Spam-Score: -2.0 (--)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Pekka, thanks for your responses (some more discussion inline below)=20

> -----Original Message-----
> From: Pekka Nikander [mailto:pekka.nikander@nomadiclab.com]=20
> Sent: Thursday, January 10, 2008 4:40 AM
> To: Henderson, Thomas R
> Cc: Bruce Lowekamp; Gonzalo Camarillo; P2PSIP Mailing List
> Subject: Re: [P2PSIP] New draft: HIP BONE
>=20
> Tom,
>=20
> >> Going with the HIP-BONE, approach, as I understand the "HIP is IP =20
> >> and the peer protocol is OSPF" idea...
> >
> > I think this analogy has some weaknesses, as you have pointed out, =20
> > in the "peer protocol is OSPF" part.  My reading of HIP BONE is =20
> > that the overall goal is to allow the peer protocol and other =20
> > applications to deal with HIP identifiers instead of IP addresses.
>=20
> Yes and no.  The goal certainly is that there may be some (or even =20
> most) applications that use the HIP identifiers directly.  However, =20
> for the peer protocols and maybe also some applications it may make =20
> more sense to use other kinds of identifiers.  That's why we=20
> made the =20
> distinction between Peer IDs and HIP identities in Section 3.1.

Yes, but I believe that you are saying in section 3.1 that those other
identifiers are turned into ORCHIDs for use in HIP.  That was the point
I was trying to make.

>=20
> > That is a worthy goal IMO which might free RELOAD and other =20
> > applications from having to do ICE and handle recursive routing =20
> > issues or host mobility and multihoming.
>=20
> That is certainly part of our goal.
>=20
> > However, the problem with this approach is that HIP needs a naming =20
> > service or routing service to resolve identifiers to either =20
> > locators or route lists.  This does not exist yet in HIP.
>=20
> Right.  I agree.
>=20
> > There have been proposals to use DHTs to provide this service, but =20
> > they do not presently accommodate the possibility of=20
> multiple DHTs, =20
> > which is pretty much a requirement to handle, from my perspective.
>=20
> That issue Gonzalo and I have discussed extensively.  On my part I =20
> still don't quite understand the requirement (as is probably visible =20
> from the previous exchange of message between you Tom and me).=20

For a given system provided by a provider (example.com), only one
overlay is necessary.  But what happens when the user concurrently gets
a second provider (example2.com)?  The problem is that the layer trying
to resolve the flat identifier doesn't know where to try to resolve it,
unless there is metadata about the system that holds bindings for that
identifier.  What happens when the user wants to enforce policy on what
applications use which overlay, at any given time, to resolve the
identifiers?

The Balakrishan et. al paper in Sigcomm 2004 (Section 4.1) elaborated on
why multiple name service providers will proliferate in an architecture
based on flat names:
http://nms.lcs.mit.edu/papers/layerednames-sigcomm04.pdf

I do not think it is a show stopper issue, but one that HIP hasn't
addressed yet. =20
 =20
> However, for example, one possibility here would be that the routing =20
> tables could contain PeerIDs (distinct from HIP identifiers) while =20
> the forwarding tables would contain HIP identifiers.  However, of =20
> course, whether that would work in a scalable manner depends on many =20
> details that haven't really been figure out yet.  For example, in =20
> such an approach it might be necessary to define a new HIP parameter =20
> (or reuse the existing HOST_ID parameter) to carry the PeerID when =20
> routing HIP packets through the overlay.
>=20
> > HIP BONE seems to be suggesting that the peer protocol can fill =20
> > this gap ...
>=20
> Exactly.
>=20
> > ... but there appear to be some issues that need to be worked out, =20
> > or maybe HIP BONE needs its own resolution/routing service=20
> separate =20
> > from the application overlay.
>=20
> There are certainly many things that need to be worked out in order =20
> to make HIP BONE practical.  The present draft was more meant to =20
> provide an overall map of some territory rather than=20
> providing detail =20
> instructions on how to get to the goal.  But, from the HIP=20
> BONE point =20
> of view, it would not make sense to make the peer protocol and a =20
> resolution or routing service separate.  Ideally, HIP BONE would =20
> support both P2PSIP based peer protocols and other, unrelated=20
> overlay =20
> or identity routing protocols, perhaps something similar to Berkeley =20
> DONA.

The difficulty I have (also with the OSPF analogy) is that it seems
necessary to avoid circular dependencies.  OSPF and IS-IS build IP
forwarding tables but, in so doing, they do not use those IP forwarding
tables, because that would be a circular dependency.  If you say that
peer protocol and resolution and routing service are combined, then it
seems to me that you are saying in HIP BONE that the peer protocol is
both a user of HIP (in some contexts) and an enabler of HIP (such as
overlay-routing the HIP messages).=20

If HIP provides connection managment, and the peer protocol provides
data storage and retrieval, and peer protocol uses HIP for its
connections, and HIP uses the peer protocol for data storage, there seem
to be some circular dependencies.  Or does HIP only apply to the media
stream connections?

I'm led to assume that, in the model you're describing, the peer
protocol has to operate in the absence of HIP (and must implement ICE);
i.e., data storage and retrieval is necessary to bootstrap HIP, and
therefore the connections used to implement data storage and retrieval
do not run over HIP.  Is that correct, or am I missing something?=20

- Tom

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



From p2psip-bounces@ietf.org Thu Jan 10 17:15:53 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JD5fv-0001AC-UC; Thu, 10 Jan 2008 17:14:59 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JD5fu-0001A7-DE
	for p2psip@ietf.org; Thu, 10 Jan 2008 17:14:58 -0500
Received: from serrano.cc.columbia.edu ([128.59.29.6])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JD5ft-0006Md-R5
	for p2psip@ietf.org; Thu, 10 Jan 2008 17:14:58 -0500
Received: from dhcp71.cs.columbia.edu (dhcp71.cs.columbia.edu [128.59.17.221])
	(user=hgs10 mech=PLAIN bits=0)
	by serrano.cc.columbia.edu (8.14.1/8.14.1) with ESMTP id m0AMEuOX022947
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT)
	for <p2psip@ietf.org>; Thu, 10 Jan 2008 17:14:57 -0500 (EST)
Message-Id: <10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
From: Henning Schulzrinne <hgs@cs.columbia.edu>
To: P2PSIP Mailing List <p2psip@ietf.org>
In-Reply-To: <77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Subject: Re: [P2PSIP] HIP: optional, mandatory?
Date: Thu, 10 Jan 2008 17:14:56 -0500
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
X-Mailer: Apple Mail (2.915)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.6
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

One of the issues I don't understand about this discussion is whether  
all instances of P2PSIP would be expected to be running HIP or just  
some. There seem to be at least three options:

(1) Mandatory to implement and run

The only non-recursive-dependency model seems to be that peer nodes  
would store the HIT-IP bindings in their routing tables. (This largely  
negates any mobility advantages, but that's a separate discussion.)

(2) Mandatory to implement, but there can be instances of an overlay  
(or maybe even part of an overlay) that don't use HIP

This would require providing ICE functionality at both the HIP level  
and directly to the P2P protocol.

(3) Optional to implement and run

This only works if you can have mixed HIP-non-HIP nodes. Also requires  
implementations of ICE in both layers and the ability to mix-and-match  
HIP and non-HIP nodes within an overlay, unless each overlay has a  
"HIP flag".

I admit that I'm rather worried about the complexity of this whole  
edifice. I think it would be helpful if the proponents of a HIP-based  
approach stated clearly which of these they have in mind.

Henning

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



From p2psip-bounces@ietf.org Thu Jan 10 17:43:10 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JD66L-0005IB-QI; Thu, 10 Jan 2008 17:42:17 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JD66K-0005I5-IU
	for p2psip@ietf.org; Thu, 10 Jan 2008 17:42:16 -0500
Received: from usaga01-in.huawei.com ([206.16.17.211])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JD66K-0006tI-6J
	for p2psip@ietf.org; Thu, 10 Jan 2008 17:42:16 -0500
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 <0JUG0099D9QFJJ@usaga01-in.huawei.com> for
	p2psip@ietf.org; Thu, 10 Jan 2008 14:42:15 -0800 (PST)
Received: from s73602 (cpe-72-190-0-23.tx.res.rr.com [72.190.0.23])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006))
	with ESMTPA id <0JUG00JQX9QAL4@usaga01-in.huawei.com> for
	p2psip@ietf.org; Thu, 10 Jan 2008 14:42:15 -0800 (PST)
Date: Thu, 10 Jan 2008 16:41:28 -0600
From: Spencer Dawkins <spencer@mcsr-labs.org>
Subject: Re: [P2PSIP] New draft: HIP BONE
To: P2PSIP Mailing List <p2psip@ietf.org>
Message-id: <0ba601c853d9$f0cdffe0$6601a8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
Content-type: text/plain; format=flowed; charset=iso-8859-1;
	reply-type=original
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<57B24871-D72C-4043-A9F4-B2E5AFA8CC52@nomadiclab.com>
	<20d2bdfb0801100819g64d64a2bpaaa0a9ac6a535c4d@mail.gmail.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hi, Bruce,

From: "Bruce Lowekamp" <lowekamp@sipeerior.com>

> On Jan 10, 2008 3:17 AM, Pekka Nikander <pekka.nikander@nomadiclab.com> 
> wrote:
>> Hi Bruce,
>>
>> > The hip routing table approach looks great from a layering
>> > perspective, but implementation looks to be very hard.
>>
>> Why?  Do you allude that the various overlay routing protocols are
>> sufficiently different from the IP routing protocols so that one
>> cannot compute a forwarding table?  Or is there some other
>> implementation problem that you are thinking about?
>
> The issue I'm concerned about here is that different DHTs use
> completely different routing algorithms.  For example, for Chord you
> forward the message to the peer with the closest ID that is < the
> target, but with Kademlia, you do a prefix match and calculate
> distances with xor.  I'm sure it's possible to come up with a safe
> language or something that could be used to describe how to make
> routing decisions, but it's certainly non-trivial.

This is my concern also, FWIW. I also think it's possible, and I also think 
it's non-trivial.

>> > So in the hip routing table approach, the I1 etc messages are
>> > routed via 5 using HIP to 10 and eventually a new direct connection
>> > is established.
>>
>> Well, depending on many factors, it may be only a subset of the HIP
>> base exchange messages that would be routed over the overlay (through
>> node 5); some of them (like perhaps R2) could perhaps be sent
>> directly, at least in some cases.  So, there is some flexibility
>> here, but at least I don't quite understand the situation in cases
>> where both 1 and 10 are behind NATs.
>
> As long as they are both reachable in the overlay, both peers behind
> nats isn't a problem as long as the ice message exchanges are carried
> over the overlay.

I'm not saying there is a chicken-and-egg problem, but I'm not sure that 
there isn't (yet).

Thanks,

Spencer 



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



From p2psip-bounces@ietf.org Thu Jan 10 17:56:17 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JD6J3-0006xa-7q; Thu, 10 Jan 2008 17:55:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JD6J2-0006xV-2V
	for p2psip@ietf.org; Thu, 10 Jan 2008 17:55:24 -0500
Received: from usaga01-in.huawei.com ([206.16.17.211])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JD6J0-0000mY-B2
	for p2psip@ietf.org; Thu, 10 Jan 2008 17:55:24 -0500
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 <0JUG00897AC9FF@usaga01-in.huawei.com> for
	p2psip@ietf.org; Thu, 10 Jan 2008 14:55:21 -0800 (PST)
Received: from s73602 (cpe-72-190-0-23.tx.res.rr.com [72.190.0.23])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006))
	with ESMTPA id <0JUG00J2YAC7L4@usaga01-in.huawei.com> for
	p2psip@ietf.org; Thu, 10 Jan 2008 14:55:21 -0800 (PST)
Date: Thu, 10 Jan 2008 16:54:37 -0600
From: Spencer Dawkins <spencer@mcsr-labs.org>
Subject: Re: [P2PSIP] New draft: HIP BONE
To: Pekka Nikander <pekka.nikander@nomadiclab.com>,
	Thomas R Henderson <thomas.r.henderson@boeing.com>
Message-id: <0bf701c853db$c711e0c0$6601a8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
Content-type: text/plain; format=flowed; charset=iso-8859-1;
	reply-type=response
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<086801c8530e$611d8030$6601a8c0@china.huawei.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B28@XCH-NW-5V1.nw.nos.boeing.com>
	<6384D11E-5D7D-48E4-B86A-816269EC864C@nomadiclab.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hi, Pekka,

I wanted to thank you for this explanation. It's helpful in understanding 
what other people mean by what they're saying.

Spencer

From: "Pekka Nikander" <pekka.nikander@nomadiclab.com>


> Spencer and Tom,
>
>>> I'm not sure I'm entirely in sync with the conversation, but when  I was 
>>> speed-reading HIP BONE over the Christmas break, I saw the  following 
>>> text, which seems to say that P2P comes first, because  the overlay is 
>>> used to route I1 packets. ("HIP over P2P")
>
> I think your confusion here is mixing the "overlay" and the "peer 
> protocol".  In HIP BONE case the overlay is formed by combining HIP  and 
> the peer protocol.  Hence, while HIP packets can be routed over  the 
> overlay, that does not mean that they are routed over the peer  protocol.
>
>>> My understanding of HIPHOP was that HIP came first, because it was  used 
>>> to forward P2P packets without "popping up" to a P2P protocol  engine at 
>>> every hop. ("P2P over HIP")
>
> Perhaps a key issue in understanding this is the separation of the 
> routing table and the forwarding table; see my previous message  earlier 
> today. 



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



From p2psip-bounces@ietf.org Thu Jan 10 17:57:49 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JD6KX-0003j9-9K; Thu, 10 Jan 2008 17:56:57 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JD6KV-0003j4-Vl
	for p2psip@ietf.org; Thu, 10 Jan 2008 17:56:56 -0500
Received: from usaga01-in.huawei.com ([206.16.17.211])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JD6KV-00077Q-KF
	for p2psip@ietf.org; Thu, 10 Jan 2008 17:56:55 -0500
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 <0JUG008ABAETFF@usaga01-in.huawei.com> for
	p2psip@ietf.org; Thu, 10 Jan 2008 14:56:53 -0800 (PST)
Received: from s73602 (cpe-72-190-0-23.tx.res.rr.com [72.190.0.23])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006))
	with ESMTPA id <0JUG00J3UAESL4@usaga01-in.huawei.com> for
	p2psip@ietf.org; Thu, 10 Jan 2008 14:56:53 -0800 (PST)
Date: Thu, 10 Jan 2008 16:56:10 -0600
From: Spencer Dawkins <spencer@mcsr-labs.org>
Subject: Re: [P2PSIP] New draft: HIP BONE
To: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>,
	Pekka Nikander <pekka.nikander@nomadiclab.com>
Message-id: <0bf801c853db$fe101830$6601a8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
Content-type: text/plain; format=flowed; charset=iso-8859-1;
	reply-type=original
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

[Spencer] Yes, exactly. I'm not sure that we DON'T have circular 
dependencies yet. I'm still trying to understand whether the peer protocol 
is a user of HIP or an enabler of HIP.

Thanks,

Spencer

From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>

The difficulty I have (also with the OSPF analogy) is that it seems
necessary to avoid circular dependencies.  OSPF and IS-IS build IP
forwarding tables but, in so doing, they do not use those IP forwarding
tables, because that would be a circular dependency.  If you say that
peer protocol and resolution and routing service are combined, then it
seems to me that you are saying in HIP BONE that the peer protocol is
both a user of HIP (in some contexts) and an enabler of HIP (such as
overlay-routing the HIP messages).

If HIP provides connection managment, and the peer protocol provides
data storage and retrieval, and peer protocol uses HIP for its
connections, and HIP uses the peer protocol for data storage, there seem
to be some circular dependencies.  Or does HIP only apply to the media
stream connections?

I'm led to assume that, in the model you're describing, the peer
protocol has to operate in the absence of HIP (and must implement ICE);
i.e., data storage and retrieval is necessary to bootstrap HIP, and
therefore the connections used to implement data storage and retrieval
do not run over HIP.  Is that correct, or am I missing something?

- Tom

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



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



From p2psip-bounces@ietf.org Thu Jan 10 18:06:32 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JD6Sx-00043y-QG; Thu, 10 Jan 2008 18:05:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JD6Sv-000438-1z
	for p2psip@ietf.org; Thu, 10 Jan 2008 18:05:37 -0500
Received: from nz-out-0506.google.com ([64.233.162.229])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JD6St-00011d-2c
	for p2psip@ietf.org; Thu, 10 Jan 2008 18:05:37 -0500
Received: by nz-out-0506.google.com with SMTP id n1so507128nzf.4
	for <p2psip@ietf.org>; Thu, 10 Jan 2008 15:05:34 -0800 (PST)
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=AIfEpu5V6MNE0NA88LkOBSoxiCVupeMomzDHq56/hCY=;
	b=n8C4y5hNDt45Rm5g4cJtyzQCnjNXz+QTRzWYC5zzKOEHCgbm87VL2iHd/BJs/CydaW1J1fVZ0iQXk4zotzvBWA9+90q7Y3D2JuzJ8Cn4sY4w8YzNZ4hfm8nGdRVsGa9xSuk44npYbTe4mwJ81Fo3cvGzBsqmH3UJUO92jRQ2UyI=
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=lY4JHTgYcwQWjGHW3aIWk977iRBkh0q8by4AiBeiXe3SKKOiKCCGFmlrQUd8Z/1eVp62jXBinFNmYjBlpuu0SQ5wLf2M8d0MZUoAj0/K8FUUo4bo8SYgiyKzbk1TgJn++R1CAFX5XfJ4Eeoq/qnujA52He/JS91bj4r9eGfrmG4=
Received: by 10.114.124.1 with SMTP id w1mr2872060wac.114.1200006334097;
	Thu, 10 Jan 2008 15:05:34 -0800 (PST)
Received: by 10.114.209.13 with HTTP; Thu, 10 Jan 2008 15:05:34 -0800 (PST)
Message-ID: <20d2bdfb0801101505n71da2740y7cbfa56f6e846643@mail.gmail.com>
Date: Thu, 10 Jan 2008 18:05:34 -0500
From: "Bruce Lowekamp" <lowekamp@sipeerior.com>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>
Subject: Re: [P2PSIP] HIP: optional, mandatory?
In-Reply-To: <10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
X-Google-Sender-Auth: 9bae5bb5fbbba84c
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Henning,

I think it can done in a modular way that will make it possible for it
to be optional to implement and run.  Then vendors and deployments can
decide whether they want to use it or not.

I'm not entirely convinced that HIP is the right solution, but I'm
interested enough in it that I think it will be cool to play with and
see how well it works.  That to me says it should be an optional
component. If it's successful, obviously it will be more widely
adopted.

Bruce


On Jan 10, 2008 5:14 PM, Henning Schulzrinne <hgs@cs.columbia.edu> wrote:
> One of the issues I don't understand about this discussion is whether
> all instances of P2PSIP would be expected to be running HIP or just
> some. There seem to be at least three options:
>
> (1) Mandatory to implement and run
>
> The only non-recursive-dependency model seems to be that peer nodes
> would store the HIT-IP bindings in their routing tables. (This largely
> negates any mobility advantages, but that's a separate discussion.)
>
> (2) Mandatory to implement, but there can be instances of an overlay
> (or maybe even part of an overlay) that don't use HIP
>
> This would require providing ICE functionality at both the HIP level
> and directly to the P2P protocol.
>
> (3) Optional to implement and run
>
> This only works if you can have mixed HIP-non-HIP nodes. Also requires
> implementations of ICE in both layers and the ability to mix-and-match
> HIP and non-HIP nodes within an overlay, unless each overlay has a
> "HIP flag".
>
> I admit that I'm rather worried about the complexity of this whole
> edifice. I think it would be helpful if the proponents of a HIP-based
> approach stated clearly which of these they have in mind.
>
> Henning
>
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.ietf.org/mailman/listinfo/p2psip
>
>

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



From p2psip-bounces@ietf.org Thu Jan 10 18:16:36 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JD6ch-0006zE-Sn; Thu, 10 Jan 2008 18:15:43 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JD6cg-0006z8-4K
	for p2psip@ietf.org; Thu, 10 Jan 2008 18:15:42 -0500
Received: from jalapeno.cc.columbia.edu ([128.59.29.5])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JD6cf-0007ZO-IG
	for p2psip@ietf.org; Thu, 10 Jan 2008 18:15:41 -0500
Received: from dhcp71.cs.columbia.edu (dhcp71.cs.columbia.edu [128.59.17.221])
	(user=hgs10 mech=PLAIN bits=0)
	by jalapeno.cc.columbia.edu (8.14.1/8.14.1) with ESMTP id
	m0ANFa5i019074
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 10 Jan 2008 18:15:36 -0500 (EST)
Message-Id: <4BE2B95B-B5F6-4FBF-AB03-F38A6004E11E@cs.columbia.edu>
From: Henning Schulzrinne <hgs@cs.columbia.edu>
To: Bruce Lowekamp <lowekamp@sipeerior.com>
In-Reply-To: <20d2bdfb0801101505n71da2740y7cbfa56f6e846643@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Subject: Re: [P2PSIP] HIP: optional, mandatory?
Date: Thu, 10 Jan 2008 18:15:35 -0500
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<20d2bdfb0801101505n71da2740y7cbfa56f6e846643@mail.gmail.com>
X-Mailer: Apple Mail (2.915)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.5
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

If it's optional, would it mean that the upper layer has to be aware  
of its existence, possibly re-running ICE on ORCHIDs?

Can we envision hybrid HIP-non HIP overlays?

Again, I'm rather worried about the complexity of this whole effort. I  
think one reasonable criterion of going forward is that those who are  
*not* interested in using HIP shouldn't have to pay for it, in terms  
of implementation costs, interoperability or performance.

On Jan 10, 2008, at 6:05 PM, Bruce Lowekamp wrote:

> Henning,
>
> I think it can done in a modular way that will make it possible for it
> to be optional to implement and run.  Then vendors and deployments can
> decide whether they want to use it or not.
>
> I'm not entirely convinced that HIP is the right solution, but I'm
> interested enough in it that I think it will be cool to play with and
> see how well it works.  That to me says it should be an optional
> component. If it's successful, obviously it will be more widely
> adopted.
>
> Bruce
>
>>
>>
>>


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



From p2psip-bounces@ietf.org Thu Jan 10 18:19:26 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JD6fS-0000Y1-Jk; Thu, 10 Jan 2008 18:18:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JD6fQ-0000Wr-RN
	for p2psip@ietf.org; Thu, 10 Jan 2008 18:18:32 -0500
Received: from wa-out-1112.google.com ([209.85.146.183])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JD6fO-0001EQ-2t
	for p2psip@ietf.org; Thu, 10 Jan 2008 18:18:32 -0500
Received: by wa-out-1112.google.com with SMTP id k40so1796642wah.25
	for <p2psip@ietf.org>; Thu, 10 Jan 2008 15:18:29 -0800 (PST)
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=kl9tBwH9QggeypVsaFV1Aa+ZEHguERfOx+W39wyUtTI=;
	b=SxoUTwRfEuQeQh/HVlgBjjsBE65W3g5YV9hnX35JIBXsNB9Own6uDq4xMb3/GTqZlDYzJgF54YUrzGdWTxa+C9joxKU1u8fzHN8yHGIOJHkNi9m1GkWsrQnz7HD8PZXa/vlwrt1cRx81mjHO7/CqzaE6vw8went/BBuedg962DA=
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=bmI5LGMJmR7z9+waZQjU1j3tR0HEw+KMYAX/S55WzRfouIKENwcS0UDIbqgo5tMuUyi6dwg+ziKiNudq4m5ksjfam12HTeCad22j4ouDmgmIm4u9Yv8TA+Tt+3L9PCA65ztIc5A/SWbQYKXjgzGGFcXYRHxyNXlTbmLhvT0VcNA=
Received: by 10.115.74.1 with SMTP id b1mr2890861wal.93.1200007108958;
	Thu, 10 Jan 2008 15:18:28 -0800 (PST)
Received: by 10.114.209.13 with HTTP; Thu, 10 Jan 2008 15:18:28 -0800 (PST)
Message-ID: <20d2bdfb0801101518v5dccb062u421633da5fb7d34c@mail.gmail.com>
Date: Thu, 10 Jan 2008 18:18:28 -0500
From: "Bruce Lowekamp" <lowekamp@sipeerior.com>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>
Subject: Re: [P2PSIP] HIP: optional, mandatory?
In-Reply-To: <4BE2B95B-B5F6-4FBF-AB03-F38A6004E11E@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<20d2bdfb0801101505n71da2740y7cbfa56f6e846643@mail.gmail.com>
	<4BE2B95B-B5F6-4FBF-AB03-F38A6004E11E@cs.columbia.edu>
X-Google-Sender-Auth: b3903a677c23303d
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

On Jan 10, 2008 6:15 PM, Henning Schulzrinne <hgs@cs.columbia.edu> wrote:
> If it's optional, would it mean that the upper layer has to be aware
> of its existence, possibly re-running ICE on ORCHIDs?
>

I think it may mean that the upper layer (other applications) need to
be aware they don't have to run ICE, at least for efficiency (they
could do it).


> Can we envision hybrid HIP-non HIP overlays?
>
> Again, I'm rather worried about the complexity of this whole effort. I
> think one reasonable criterion of going forward is that those who are
> *not* interested in using HIP shouldn't have to pay for it, in terms
> of implementation costs, interoperability or performance.
>

I fully agree.  It only makes sense if it's actually a separable module.

Bruce

>
> On Jan 10, 2008, at 6:05 PM, Bruce Lowekamp wrote:
>
> > Henning,
> >
> > I think it can done in a modular way that will make it possible for it
> > to be optional to implement and run.  Then vendors and deployments can
> > decide whether they want to use it or not.
> >
> > I'm not entirely convinced that HIP is the right solution, but I'm
> > interested enough in it that I think it will be cool to play with and
> > see how well it works.  That to me says it should be an optional
> > component. If it's successful, obviously it will be more widely
> > adopted.
> >
> > Bruce
> >
> >>
> >>
> >>
>
>

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



From p2psip-bounces@ietf.org Thu Jan 10 21:04:36 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JD9G0-0005PN-NH; Thu, 10 Jan 2008 21:04:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JD9Fz-0005O3-AE
	for p2psip@ietf.org; Thu, 10 Jan 2008 21:04:27 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JD9Fy-0003Qz-SP
	for p2psip@ietf.org; Thu, 10 Jan 2008 21:04:27 -0500
X-IronPort-AV: E=Sophos;i="4.24,269,1196668800"; d="scan'208";a="33950462"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 10 Jan 2008 18:04:26 -0800
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m0B24QO9005207; 
	Thu, 10 Jan 2008 18:04:26 -0800
Received: from [192.168.4.177] (sjc-fluffy-vpn1.cisco.com [10.25.236.82])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with SMTP id m0B24OcW001671;
	Fri, 11 Jan 2008 02:04:24 GMT
In-Reply-To: <10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
Impp: xmpp:cullenfluffyjennings@jabber.org
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [P2PSIP] HIP: optional, mandatory?
Date: Thu, 10 Jan 2008 18:03:14 -0800
To: Henning Schulzrinne <hgs@cs.columbia.edu>
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1825; t=1200017066;
	x=1200881066; c=relaxed/simple; s=sjdkim3002;
	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]=20HIP=3A=20optional,=20mandato ry?
	|Sender:=20; bh=GGfChrmz8a8uTA/PkcPmIrfeWvduoXUPCJAGayBg11U=;
	b=O08/AUylme9Q+K63HyHxu87jNGdtgNNcFLngrXxf0x8o3AOb6AmQw4LnOu
	aKQFOKhkLYdUwVN8OWfpFuUaSvJe7V03LXp1t45YRo/RKQ0QIw3wpeAOzF65
	yeTHK4VgM1;
Authentication-Results: sj-dkim-3; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org


On Jan 10, 2008, at 2:14 PM, Henning Schulzrinne wrote:

> One of the issues I don't understand about this discussion is  
> whether all instances of P2PSIP would be expected to be running HIP  
> or just some. There seem to be at least three options:
>
> (1) Mandatory to implement and run
>
> The only non-recursive-dependency model seems to be that peer nodes  
> would store the HIT-IP bindings in their routing tables. (This  
> largely negates any mobility advantages, but that's a separate  
> discussion.)
>
> (2) Mandatory to implement, but there can be instances of an  
> overlay (or maybe even part of an overlay) that don't use HIP
>
> This would require providing ICE functionality at both the HIP  
> level and directly to the P2P protocol.
>
> (3) Optional to implement and run
>
> This only works if you can have mixed HIP-non-HIP nodes. Also  
> requires implementations of ICE in both layers and the ability to  
> mix-and-match HIP and non-HIP nodes within an overlay, unless each  
> overlay has a "HIP flag".
>
> I admit that I'm rather worried about the complexity of this whole  
> edifice. I think it would be helpful if the proponents of a HIP- 
> based approach stated clearly which of these they have in mind.
>
> Henning
>
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.ietf.org/mailman/listinfo/p2psip

I was assuming most folks were talking about (3) given that much of  
HIP is still being designed and it will be awhile to get things build  
and deployed. I know lots of parts of HIP have been done but when we  
are talking about mobility, nat traversal, no DNS, and easy end user  
installations, there is still work. Anyway, I am in the 3 category.

Cullen <with my individual hat on>


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



From p2psip-bounces@ietf.org Thu Jan 10 22:30:16 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDAb1-0003uB-7B; Thu, 10 Jan 2008 22:30:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDAaz-0003u5-Pk
	for p2psip@ietf.org; Thu, 10 Jan 2008 22:30:13 -0500
Received: from usaga01-in.huawei.com ([206.16.17.211])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JDAax-0004QA-VP
	for p2psip@ietf.org; Thu, 10 Jan 2008 22:30:13 -0500
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 <0JUG008JIN2AFF@usaga01-in.huawei.com> for
	p2psip@ietf.org; Thu, 10 Jan 2008 19:30:11 -0800 (PST)
Received: from s73602 (cpe-72-190-0-23.tx.res.rr.com [72.190.0.23])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006))
	with ESMTPA id <0JUG00EI0N25DD@usaga01-in.huawei.com> for
	p2psip@ietf.org; Thu, 10 Jan 2008 19:30:10 -0800 (PST)
Date: Thu, 10 Jan 2008 21:29:22 -0600
From: Spencer Dawkins <spencer@mcsr-labs.org>
Subject: Re: [P2PSIP] HIP: optional, mandatory?
To: P2PSIP Mailing List <p2psip@ietf.org>
Message-id: <0c3a01c85402$28d821e0$6601a8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
Content-type: text/plain; format=flowed; charset=iso-8859-1;
	reply-type=response
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hi, Cullen and Henning,

I guess today is a good day for me to be confused.

I thought I understood "optional to implement, optional to run", and I 
understood Cullen's reasons stated below, but I'm very confused about why 
"this only works if you can have mixed HIP-non-HIP" ...

... and that's probably because I'm not quite sure what "mixed HIP-non-HIP" 
means.

Are you talking about

a - mixed within P2PSIP technology, so that some overlays use HIP and others 
do not?

b - mixed within the same endpoint, that can join a HIP overlay and a 
non-HIP overlay?

c - mixed within the same overlay, so some peers use HIP and others do not?

I'll stop talking now ...

Spencer

From: "Cullen Jennings" <fluffy@cisco.com>

> On Jan 10, 2008, at 2:14 PM, Henning Schulzrinne wrote:
>
>> One of the issues I don't understand about this discussion is  whether 
>> all instances of P2PSIP would be expected to be running HIP  or just 
>> some. There seem to be at least three options:
>>
>> (1) Mandatory to implement and run
>>
>> The only non-recursive-dependency model seems to be that peer nodes 
>> would store the HIT-IP bindings in their routing tables. (This  largely 
>> negates any mobility advantages, but that's a separate  discussion.)
>>
>> (2) Mandatory to implement, but there can be instances of an  overlay (or 
>> maybe even part of an overlay) that don't use HIP
>>
>> This would require providing ICE functionality at both the HIP  level and 
>> directly to the P2P protocol.
>>
>> (3) Optional to implement and run
>>
>> This only works if you can have mixed HIP-non-HIP nodes. Also  requires 
>> implementations of ICE in both layers and the ability to  mix-and-match 
>> HIP and non-HIP nodes within an overlay, unless each  overlay has a "HIP 
>> flag".
>>
>> I admit that I'm rather worried about the complexity of this whole 
>> edifice. I think it would be helpful if the proponents of a HIP- based 
>> approach stated clearly which of these they have in mind.
>>
>> Henning
>
> I was assuming most folks were talking about (3) given that much of  HIP 
> is still being designed and it will be awhile to get things build  and 
> deployed. I know lots of parts of HIP have been done but when we  are 
> talking about mobility, nat traversal, no DNS, and easy end user 
> installations, there is still work. Anyway, I am in the 3 category.
>
> Cullen <with my individual hat on> 



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



From p2psip-bounces@ietf.org Thu Jan 10 22:52:50 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDAwr-00085B-Bm; Thu, 10 Jan 2008 22:52:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDAwp-00084w-CW
	for p2psip@ietf.org; Thu, 10 Jan 2008 22:52:47 -0500
Received: from serrano.cc.columbia.edu ([128.59.29.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JDAwp-0004gR-28
	for p2psip@ietf.org; Thu, 10 Jan 2008 22:52:47 -0500
Received: from Upstairs-Mac (pool-71-250-50-170.nwrknj.east.verizon.net
	[71.250.50.170]) (user=hgs10 mech=PLAIN bits=0)
	by serrano.cc.columbia.edu (8.14.1/8.14.1) with ESMTP id m0B3qjKD006640
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 10 Jan 2008 22:52:46 -0500 (EST)
From: Henning Schulzrinne <hgs@cs.columbia.edu>
To: Spencer Dawkins <spencer@mcsr-labs.org>
In-Reply-To: <0c3a01c85402$28d821e0$6601a8c0@china.huawei.com>
Subject: Re: [P2PSIP] HIP: optional, mandatory?
X-Priority: 3
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
	<0c3a01c85402$28d821e0$6601a8c0@china.huawei.com>
Message-Id: <CBAEA83C-A2BB-47E7-AE49-A3E901DDB50C@cs.columbia.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Date: Thu, 10 Jan 2008 22:52:38 -0500
X-Mailer: Apple Mail (2.915)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.6
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

I'm assuming that the goal is that a P2PSIP-compliant application will  
be able to participate in any P2PSIP-compliant overlay, subject to  
having code for the DHT  the overlay is running. Thus, this means that  
non-HIP peers must be able to be full peers. Unless the arrival of a  
single non-HIP peer converts the whole overlay to non-HIP usage, this  
also implies that all nodes must be able to deal with non-HIP peers,  
even if they prefer to speak HIP. Among other things, they'll probably  
have to implement ICE and TLS.

Thus, it's something like (b) and (c).

Henning

On Jan 10, 2008, at 10:29 PM, Spencer Dawkins wrote:

> Hi, Cullen and Henning,
>
> I guess today is a good day for me to be confused.
>
> I thought I understood "optional to implement, optional to run", and  
> I understood Cullen's reasons stated below, but I'm very confused  
> about why "this only works if you can have mixed HIP-non-HIP" ...
>
> ... and that's probably because I'm not quite sure what "mixed HIP- 
> non-HIP" means.
>
> Are you talking about
>
> a - mixed within P2PSIP technology, so that some overlays use HIP  
> and others do not?
>
> b - mixed within the same endpoint, that can join a HIP overlay and  
> a non-HIP overlay?
>
> c - mixed within the same overlay, so some peers use HIP and others  
> do not?
>
> I'll stop talking now ...


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



From p2psip-bounces@ietf.org Thu Jan 10 23:24:15 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDBRE-0006cQ-O7; Thu, 10 Jan 2008 23:24:12 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDBRC-0006cL-J3
	for p2psip@ietf.org; Thu, 10 Jan 2008 23:24:12 -0500
Received: from quinthar.com ([72.52.120.178])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1JDBRB-0004cY-UC
	for p2psip@ietf.org; Thu, 10 Jan 2008 23:24:10 -0500
Received: from 116.68.71.147 ([116.68.71.147]) by quinthar.com for
	<p2psip@ietf.org>; Thu, 10 Jan 2008 20:24:04 -0800
Message-Id: <465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com>
From: David Barrett <dbarrett@quinthar.com>
To: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Subject: Re: [P2PSIP] HIP: optional, mandatory?
Date: Fri, 11 Jan 2008 09:53:59 +0530
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
X-Mailer: Apple Mail (2.915)
X-Spam-Score: 2.6 (++)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

We don't need more options for what we CAN do, we need decisions on  
what we WILL do.  If we're not considering making HIP mandatory, then  
let's stop talking about it and start focusing on those things that  
*will* be mandatory.

That said, I think this HIP discussion is the best thing to happen in  
P2PSIP for years.  It seems like the most practical and powerful  
solution, the best layering of functionality, and the most feasible  
design that I've yet to hear.  Moving the hard P2P code into a  
reusable HIP layer makes a lot of sense, not only for P2PSIP, but for  
the internet as a whole.  It seems like a wagon that we should  
voluntarily and enthusiastically hitch ourselves to, rather than try  
to reproduce or compete with it, or toss it in the overflowing bucket  
of optional extensions.

It seems sensible to have a base HIP layer that either comes pre- 
installed with the OS or redistributed by the application (similar to  
WinPCap).  (I could even see making a sort of "HIP-lite" self- 
contained library that can be linked straight into the application for  
when installing a   Then P2PSIP can be one of many HIP-using  
applications that are vastly simplified by being insulated from the  
gnarly realities of NAT and firewall penetration, mobility, etc.

This makes a lot more sense than continually reproducing this really  
hard functionality in every application.

-david

On Jan 11, 2008, at 7:33 AM, Cullen Jennings wrote:

>
> I was assuming most folks were talking about (3) given that much of  
> HIP is still being designed and it will be awhile to get things  
> build and deployed. I know lots of parts of HIP have been done but  
> when we are talking about mobility, nat traversal, no DNS, and easy  
> end user installations, there is still work. Anyway, I am in the 3  
> category.
>
> Cullen <with my individual hat on>
> On Jan 10, 2008, at 2:14 PM, Henning Schulzrinne wrote:
>
>> One of the issues I don't understand about this discussion is  
>> whether all instances of P2PSIP would be expected to be running HIP  
>> or just some. There seem to be at least three options:
>>
>> (1) Mandatory to implement and run
>>
>> The only non-recursive-dependency model seems to be that peer nodes  
>> would store the HIT-IP bindings in their routing tables. (This  
>> largely negates any mobility advantages, but that's a separate  
>> discussion.)
>>
>> (2) Mandatory to implement, but there can be instances of an  
>> overlay (or maybe even part of an overlay) that don't use HIP
>>
>> This would require providing ICE functionality at both the HIP  
>> level and directly to the P2P protocol.
>>
>> (3) Optional to implement and run
>>
>> This only works if you can have mixed HIP-non-HIP nodes. Also  
>> requires implementations of ICE in both layers and the ability to  
>> mix-and-match HIP and non-HIP nodes within an overlay, unless each  
>> overlay has a "HIP flag".
>>
>> I admit that I'm rather worried about the complexity of this whole  
>> edifice. I think it would be helpful if the proponents of a HIP- 
>> based approach stated clearly which of these they have in mind.
>>
>> Henning
>>
>> _______________________________________________
>> P2PSIP mailing list
>> P2PSIP@ietf.org
>> https://www1.ietf.org/mailman/listinfo/p2psip
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.ietf.org/mailman/listinfo/p2psip
>


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



From p2psip-bounces@ietf.org Fri Jan 11 02:45:29 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDEZx-0000qd-FE; Fri, 11 Jan 2008 02:45:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDEZv-0000qC-SF
	for p2psip@ietf.org; Fri, 11 Jan 2008 02:45:23 -0500
Received: from n2.nomadiclab.com ([2001:14b8:400:101::2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JDEZv-00084z-BL
	for p2psip@ietf.org; Fri, 11 Jan 2008 02:45:23 -0500
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id C10BD1EF105;
	Fri, 11 Jan 2008 09:45:21 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 5AE2E1EF104;
	Fri, 11 Jan 2008 09:45:20 +0200 (EET)
In-Reply-To: <0bf801c853db$fe101830$6601a8c0@china.huawei.com>
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<0bf801c853db$fe101830$6601a8c0@china.huawei.com>
Mime-Version: 1.0 (Apple Message framework v753)
X-Priority: 3
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <B5C4134C-1856-4150-BC88-1D43A45C66F3@nomadiclab.com>
Content-Transfer-Encoding: 7bit
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: Re: [P2PSIP] New draft: HIP BONE
Date: Fri, 11 Jan 2008 09:45:18 +0200
To: Spencer Dawkins <spencer@mcsr-labs.org>
X-Mailer: Apple Mail (2.753)
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: -1.4 (-)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

In the case of HIP BONE, the peer (or routing) protocol is both a  
user of HIP and an enable of HIP.  But so are the routing protocols  
for IP, and in certain sense DNS for IP, too.

Such a circular dependency in itself is not bad, as long as it is  
designed (i.e. not accidental) and we have a clear understanding how  
to manage the bootstrap problem.

In this case, the bootstrap may take place, for example, in the form  
of direct HIP connections (no overlay routing).  That is, if that  
approach is taken, when a node joins to an overlay, it looks up the  
HIT and IP address of some host within the overlay (e.g. using DNS,  
local service discovery, or manual configuration), creates an HIP  
association, and runs the peer protocol join over the HIP association.

--Pekka


On 11 Jan 2008, at 00:56, Spencer Dawkins wrote:

> [Spencer] Yes, exactly. I'm not sure that we DON'T have circular  
> dependencies yet. I'm still trying to understand whether the peer  
> protocol is a user of HIP or an enabler of HIP.
>
> Thanks,
>
> Spencer
>
> From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
>>
>> The difficulty I have (also with the OSPF analogy) is that it seems
>> necessary to avoid circular dependencies.  OSPF and IS-IS build IP
>> forwarding tables but, in so doing, they do not use those IP  
>> forwarding
>> tables, because that would be a circular dependency.  If you say that
>> peer protocol and resolution and routing service are combined,  
>> then it
>> seems to me that you are saying in HIP BONE that the peer protocol is
>> both a user of HIP (in some contexts) and an enabler of HIP (such as
>> overlay-routing the HIP messages).
>>
>> If HIP provides connection managment, and the peer protocol provides
>> data storage and retrieval, and peer protocol uses HIP for its
>> connections, and HIP uses the peer protocol for data storage,  
>> there seem
>> to be some circular dependencies.  Or does HIP only apply to the  
>> media
>> stream connections?
>>
>> I'm led to assume that, in the model you're describing, the peer
>> protocol has to operate in the absence of HIP (and must implement  
>> ICE);
>> i.e., data storage and retrieval is necessary to bootstrap HIP, and
>> therefore the connections used to implement data storage and  
>> retrieval
>> do not run over HIP.  Is that correct, or am I missing something?
>
>

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



From p2psip-bounces@ietf.org Fri Jan 11 05:04:25 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDGkR-0005GT-13; Fri, 11 Jan 2008 05:04:23 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDGkQ-0005GO-4i
	for p2psip@ietf.org; Fri, 11 Jan 2008 05:04:22 -0500
Received: from mail.gmx.net ([213.165.64.20])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1JDGkP-0002vi-Bj
	for p2psip@ietf.org; Fri, 11 Jan 2008 05:04:21 -0500
Received: (qmail invoked by alias); 11 Jan 2008 10:04:14 -0000
Received: from proxy3-nsn.nsn-inter.net (EHLO [217.115.75.231])
	[217.115.75.231]
	by mail.gmx.net (mp019) with SMTP; 11 Jan 2008 11:04:14 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+jJV0QFdCjXeSyzh7FBuKvRQhO9QlY1XX3Y9mfix
	Fa6XnqpCu8ChFJ
Message-ID: <47873F1A.9060702@gmx.net>
Date: Fri, 11 Jan 2008 12:04:10 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: "Paine, Richard H" <richard.h.paine@boeing.com>
References: <0C549DAFE1A8004D8EB57ACDD108646D06520831@XCH-NW-2V2.nw.nos.boeing.com>
In-Reply-To: <0C549DAFE1A8004D8EB57ACDD108646D06520831@XCH-NW-2V2.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: p2psip@ietf.org
Subject: [P2PSIP] Slides? -- Re: [Hipsec] Updated: P2PSIP and HIP Joint
 Meeting on the Boeing VOIP	HIPImplementation
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hi Richard,
Hi all,

I wasn't able to attend the meeting but I was wondering whether some 
slides are available.

Ciao
Hannes

Paine, Richard H wrote:
> When: Tuesday, January 08, 2008 8:00 AM-9:30 AM (GMT-08:00) Pacific Time (US & Canada).
> Where: Virtual (866-752-6974 Passcode: 9710856#
>
> *~*~*~*~*~*~*~*~*~*
>
> Just so everyone is clear - the teleconference is at 8am Pacific Time on Tuesday, Jan 8, 2008 at the following teleconference and Webex numbers.
>
> The teleconference is per a meeting at the Vancouver IETF on Friday, Dec 7, 2007 that was a joint meeting of the HIP and P2PSIP Working Groups.  The joint meeting determined the need to look at the Boeing demonstration of SIP over HIP.  The demonstration used an IEEE802.11-WPA-wireless connection to the Boeing Intranet and the SIP call traversed both the wireless and wired network securely to get to a wired laptop.  The call occurred in a HIP namespace using a cryptographic identity as an SPI value in the ESP field.
>
> This teleconference is being held to discuss the white paper on the demonstration and the use of HIP for secure point-to-point SIP.
>
> Teleconference Details:
>
> Date: Tuesday, January 8, 2008 Starting time: 8:00 am, Pacific Standard Time (GMT -08:00, San Francisco) Duration: 1 hour 30 minutes Meeting number: 896 132 416 Meeting password: hipmeeting Teleconference: Dial-in:1-866-752-6974 (US)
> Leader passcode:9710856
> Participant passcode:9710856 Host: Richard Paine Host's email address: richard.h.paine@boeing.com 
>
> Richard H. Paine
> Success is getting what you want, happiness is liking what you get!
> Cell:  206-854-8199
> IPPhone:  425-373-8296
> Email:  richard.h.paine@boeing.com 
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Hipsec mailing list
> Hipsec@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/hipsec
>   


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



From p2psip-bounces@ietf.org Fri Jan 11 09:21:32 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDKlD-0005Iy-W9; Fri, 11 Jan 2008 09:21:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDKlC-0005IJ-Rd
	for p2psip@ietf.org; Fri, 11 Jan 2008 09:21:26 -0500
Received: from usaga01-in.huawei.com ([206.16.17.211])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JDKlB-0005p7-35
	for p2psip@ietf.org; Fri, 11 Jan 2008 09:21:26 -0500
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 <0JUH00ETBH7N8C@usaga01-in.huawei.com> for
	p2psip@ietf.org; Fri, 11 Jan 2008 06:21:24 -0800 (PST)
Received: from s73602 (cpe-72-190-0-23.tx.res.rr.com [72.190.0.23])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006))
	with ESMTPA id <0JUH00KHIH7KYC@usaga01-in.huawei.com> for
	p2psip@ietf.org; Fri, 11 Jan 2008 06:21:23 -0800 (PST)
Date: Fri, 11 Jan 2008 08:20:33 -0600
From: Spencer Dawkins <spencer@mcsr-labs.org>
Subject: Re: [P2PSIP] New draft: HIP BONE
To: Pekka Nikander <pekka.nikander@nomadiclab.com>
Message-id: <0cdd01c8545d$2107a520$6601a8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
Content-type: text/plain; format=flowed; charset=iso-8859-1;
	reply-type=response
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<0bf801c853db$fe101830$6601a8c0@china.huawei.com>
	<B5C4134C-1856-4150-BC88-1D43A45C66F3@nomadiclab.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

OK, I'm not the architecture monitor, but I disagree with some of this, and 
agree with the rest...


> In the case of HIP BONE, the peer (or routing) protocol is both a  user of 
> HIP and an enable of HIP.  But so are the routing protocols  for IP, and 
> in certain sense DNS for IP, too.

OSPF does use IP *encapsulation*, *fragmentation/reassembly*, etc. but OSPF 
conversations happen with direct adjacencies. Using IP *encapsulation* is 
very different from using *IP*.

IS-IS runs directly over link-layer protocols ("same level as CLNS").

DNS looks like a IP enabler to applications that are trying to use DNS 
names, but it's not - IP ran for years before there was a naming system at 
all (see HOSTS.TXT).

> Such a circular dependency in itself is not bad, as long as it is 
> designed (i.e. not accidental) and we have a clear understanding how  to 
> manage the bootstrap problem.

I would agree with both points here - design and understanding are what's 
needed, and being able to bootstrap would be the first test that we have a 
design and understanding.

Thanks,

Spencer 



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



From p2psip-bounces@ietf.org Fri Jan 11 10:10:32 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDLWh-00005q-Hf; Fri, 11 Jan 2008 10:10:31 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDLWg-00005l-6m
	for p2psip@ietf.org; Fri, 11 Jan 2008 10:10:30 -0500
Received: from py-out-1112.google.com ([64.233.166.180])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JDLWf-0000wq-Gu
	for p2psip@ietf.org; Fri, 11 Jan 2008 10:10:29 -0500
Received: by py-out-1112.google.com with SMTP id x19so1431987pyg.24
	for <p2psip@ietf.org>; Fri, 11 Jan 2008 07:10:29 -0800 (PST)
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=7HeXjHox3+x41wGoJSoe1XruGvGevC0Kyb4rfMBEmck=;
	b=FNyBdEMPowaVJ+bAvdUfMn7Um9wRdjsqWDiCe7e+3DIphvCFNOsNXli7hr21OUWD+1W8vkt87Iz03W6E3LFi6ELncSQqGSMB2znlCU8s2W4LxXeNP0/9l5ziBQ/uaixVtCCtCHKupToS+1DyARPGl0RQQY2kQXiWhTRXYjQjbJs=
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=qdQXxqyxxzyngXlLcY3BUD+LQ8j1jR0UNMBavGxnnI4gZcEws4wfn2nKghSklsU/k/FKgEic9xmuSDnO5NPueIJwhLPSucOauInfjRV8tjntXRX0xAMsHzShQOEAMGx3Vl62ypE7oQ8NIVvSqOJWtSw2nMfHdQ9UHpF/H/4y3Ok=
Received: by 10.65.15.19 with SMTP id s19mr7209151qbi.17.1200064228305;
	Fri, 11 Jan 2008 07:10:28 -0800 (PST)
Received: by 10.65.180.16 with HTTP; Fri, 11 Jan 2008 07:10:28 -0800 (PST)
Message-ID: <4d4304a00801110710x1b7f04b4lcbcbb9eb8702ba1e@mail.gmail.com>
Date: Fri, 11 Jan 2008 10:10:28 -0500
From: "David A. Bryan" <dbryan@sipeerior.com>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>
Subject: Re: [P2PSIP] HIP: optional, mandatory?
In-Reply-To: <CBAEA83C-A2BB-47E7-AE49-A3E901DDB50C@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <476BA8D9.4010203@ericsson.com> <476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
	<0c3a01c85402$28d821e0$6601a8c0@china.huawei.com>
	<CBAEA83C-A2BB-47E7-AE49-A3E901DDB50C@cs.columbia.edu>
X-Google-Sender-Auth: 04b815dd1f2f88d4
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hmmm...(b) and (c) doesn't make sense to me, unless I'm missing
something. After reading Spencer's email, (a) and (b) make more sense
to me.

I agree with Cullen that HIP should me optional both to implement and
run. That means that many overlays may simply not support it all, and
others may use it exclusively, giving us the (a) scenario. A
particular endpoint may choose to implement both, allowing it join
both types of overlays, which is (b).

(c) makes little sense to me operationally, although I guess I can see
how it could be done technically if there are some (b) type peers that
are effectively relays. It would make for some really odd DHTs,
however, since you might have to route calls via the adaptors, and I'm
not sure it really gains you anything.

In my mind, this would be a capabilities negotiation issue. Although
the mechanics of how you do it might differ a good bit, logically it
might be good to think about it like offer-answer in SIP. If I start
an overlay, I'm free to choose the DHT and if it is SIP or not. If, on
the other hand a few peers were negotiating among themselves, they
could compare capabilities (DHTs, HIP or not, security model, etc.)
and choose the best. I don't think we have a "One ring to rule them
all..." thing going on where every single peer is in a global overlay,
although there could be some (very) large and essentially public
rings. There will be rings with different choices on DHT/transport,
and that decision may limit who can join that particular ring.

So I guess since we are all picking numbers here, I am the (3)(a and
b) camp. I might just not have my head around (c), however...anyone
care to take a stab at explaining how it actually works?

David (as individual)

On Jan 10, 2008 10:52 PM, Henning Schulzrinne <hgs@cs.columbia.edu> wrote:
> I'm assuming that the goal is that a P2PSIP-compliant application will
> be able to participate in any P2PSIP-compliant overlay, subject to
> having code for the DHT  the overlay is running. Thus, this means that
> non-HIP peers must be able to be full peers. Unless the arrival of a
> single non-HIP peer converts the whole overlay to non-HIP usage, this
> also implies that all nodes must be able to deal with non-HIP peers,
> even if they prefer to speak HIP. Among other things, they'll probably
> have to implement ICE and TLS.
>
> Thus, it's something like (b) and (c).
>
> Henning
>
> On Jan 10, 2008, at 10:29 PM, Spencer Dawkins wrote:
>
> > Hi, Cullen and Henning,
> >
> > I guess today is a good day for me to be confused.
> >
> > I thought I understood "optional to implement, optional to run", and
> > I understood Cullen's reasons stated below, but I'm very confused
> > about why "this only works if you can have mixed HIP-non-HIP" ...
> >
> > ... and that's probably because I'm not quite sure what "mixed HIP-
> > non-HIP" means.
> >
> > Are you talking about
> >
> > a - mixed within P2PSIP technology, so that some overlays use HIP
> > and others do not?
> >
> > b - mixed within the same endpoint, that can join a HIP overlay and
> > a non-HIP overlay?
> >
> > c - mixed within the same overlay, so some peers use HIP and others
> > do not?
> >
> > I'll stop talking now ...
>
>
>
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.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://www1.ietf.org/mailman/listinfo/p2psip



From p2psip-bounces@ietf.org Fri Jan 11 10:16:28 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDLcR-00044l-0l; Fri, 11 Jan 2008 10:16:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDLcO-00040T-QB
	for p2psip@ietf.org; Fri, 11 Jan 2008 10:16:25 -0500
Received: from an-out-0708.google.com ([209.85.132.245])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JDLcO-0006hm-7p
	for p2psip@ietf.org; Fri, 11 Jan 2008 10:16:24 -0500
Received: by an-out-0708.google.com with SMTP id d11so286937and.122
	for <p2psip@ietf.org>; Fri, 11 Jan 2008 07:16:23 -0800 (PST)
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:mime-version:content-type:content-transfer-encoding:content-disposition;
	bh=seL34ylWiK5m8jLsQhKtynoBQay2OrQ8QqKNXEPftT0=;
	b=iTGJYGlJfCpPMJqw8krBsO4BhacsxfuGMgR4BwC/91TV2/lFOzGVPJjj+G8t+5QuWwTjSdLb25buhdTOEH9mk8bLK/Ho+ai4RNNXDhr6WpzHr7FB7Varai7QIQAMg7MtJWxJm7mEu1kwm3bD06rOxP2PXoDfVgS2QNEiHnH2HlY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=TTlIhHF1MdDwbfttt1g5BjT5rAyHOgpQoXgmRUXBzcdcrW8gbyZ25gHZy4ViOTpcVz4pR5x/QG+efh9iJtNNLP8FP5UlkbqAwm4DXL6Vbc8mbPh8H//vsVqeYil8MhXrMGP1drxr9knCmSQsy+4pl/mckJU/wNSIbanx0vApj68=
Received: by 10.100.34.16 with SMTP id h16mr6973176anh.114.1200064583426;
	Fri, 11 Jan 2008 07:16:23 -0800 (PST)
Received: by 10.100.8.5 with HTTP; Fri, 11 Jan 2008 07:16:23 -0800 (PST)
Message-ID: <e92712b70801110716t20d86f0bn22b783e7f68844a6@mail.gmail.com>
Date: Fri, 11 Jan 2008 17:16:23 +0200
From: "Andrey Lukyanenko" <laser.ru@gmail.com>
To: "Bruce Lowekamp" <lowekamp@sipeerior.com>
Subject: FW: [P2PSIP] Re: HIP pros and cons
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: p2psip@ietf.org
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1947361070=="
Errors-To: p2psip-bounces@ietf.org

--===============1947361070==
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64
Content-Disposition: inline

SGVsbG8sCgo+IEknZCBiZSBpbnRlcmVzdGVkIGluIGhvdyB0aGF0J3MgaW1wbGVtZW50ZWQuICBG
cm9tIHdoYXQgSSBjYW4gc2VlLCB0aGUgb3JpZ2luYWwKPiBwYXBlcnMgc2ltcGx5IGFzc3VtZSB0
aGUgZXhpc3RlbmNlIG9mIFNlY3VyZS1pMyBmb3IgIHJlbmRlenZvdXMsIGFuZCBJIGRvbid0Cj4g
c2VlIGRldGFpbGVkIGVub3VnaCBkb2NzIGZyb20gT3BlbkhJUCBvciBISVBMIGZvciBtZSB0byB0
ZWxsIGhvdyB0aGV5J3ZlIGltcGxlbWVudGVkIGl0LgoKCkhpMyBpcyBiYXNlZCBvbiBpMyBuZXR3
b3JrIChyZWFsaXphdGlvbiBodHRwOi8vaTMuY3MuYmVya2VsZXkuZWR1LykuCk9wZW5ISVAgYW5k
IEhJUEwgYm90aCB1c2UgdGhlIHNhbWUgc2ltcGxlIG1vZGVsIHRvIGRlYWwgd2l0aCBoaTMuCkZp
cnN0IG9mIGFsbCwgaXQgaXMgYW4gaW5pdGlhbGl6YXRpb24sIHdoZXJlIHdlIHN0YXJ0IHRoZQpp
bml0aWFsaXphdGlvbiBmdW5jdGlvbnMgZnJvbSBpMyBsaWJyYXJ5LCBwdXQgdHJpZ2dlcnMgKG9u
ZSBwdWJsaWMKdHJpZ2dlciB3aXRoIElkMT1ISVQgYW5kIG9uZSBwcml2YXRlIHdpdGggSWQyPSdS
YW5kb20gbnVtYmVyJykgaW50bwpleGlzdGluZyBpMy1uZXR3b3JrIChvbiBwbGFuZXRsYWIpLiBJ
biB0aGUgaW5pdGlhbGl6YXRpb24gcGhhc2Ugd2UKYWxzbyBzZXQgdGhhdCB0aGUgY29udHJvbCBw
YWNrZXRzIHNob3VsZCBnbyB0aHJvdWdoIGkzIG5ldHdvcmsgKHNlbmR0bwpmdW5jdGlvbiBmcm9t
IGxpYnJhcnkpLiBTZWNvbmRseSwgdG8gZGVhbCB3aXRoIGhpMyB3ZSBoYXZlICJzZW5kaW5nCnBo
YXNlIi4gRHVyaW5nIHRoaXMgcGhhc2Ugd2Ugc2VuZCBhbGwgY29udHJvbCB0cmFmZmljIHRocm91
Z2ggaTMKbmV0d29yayAobm90IHRocm91Z2ggcmF3IHNvY2tldHMpLiBXZSBzZXBhcmF0ZSBpbml0
aWF0b3IgYW5kIHJlc3BvbmRlcgpzaWRlLiBJbiBISVBMLCB0aGUgaW5pdGlhdG9yIGlzIHJlc3Bv
bnNpYmxlIGZvciBzZW5kaW5nIHRyYWZmaWMKdGhyb3VnaCBpMzsgd2hpbGUgdGhlIHJlc3BvbmRl
ciBzaG91bGQgYW5zd2VyIHRoZSBzYW1lIG5ldHdvcmsKKG92ZXJsYXkpIGl0IHJlY2VpdmVkIHBh
Y2tldC4KClVzZSBjYXNlcyAoZm9yIEhJUEwpOgoKSSwgUiDigJMgaW5pdGlhdG9yIGFuZCByZXNw
b25kZXIuCklQX0ksIElQX1Ig4oCTIElQcyBvZiBpbml0aWF0b3IgYW5kIHJlc3BvbmRlci4KUl9J
LCBSX1Ig4oCTIHJhbmRvbSBudW1iZXJzLgpISVRfSSwgSElUX3IgIC0gSElUcy4KCjEuIEluaXRp
YWxpemF0aW9uLgoKYSkgSSBhbmQgUiBzdGFydCBoaXBsIHdpdGggaGkzIG9wdGlvbi4KYikgaGlw
bCBvbiBib3RoIG1hY2hpbmVzIGNoZWNrcwpyb3NlLmNzLmJlcmtlbGV5LmVkdTo4MDgwL2kzX3N0
YXR1cy50eHQgbGlzdCBvZiBleGlzdGluZyBpMyBzZXJ2ZXJzLAphbmQgdHJpZXMgdG8gY29ubmVj
dCB0aGVtLgpjKSBJIHNlbmRzIHRyaWdnZXJzIChISVRfSSxSX0kpIGFuZCAoUl9JLCBJUF9JKSAg
aW5zZXJ0aW9uIGNvbW1hbmQgdG8KaGlzIGJlc3QgbG9va2luZyBpMyBzZXJ2ZXIuIFIgaW5zZXJ0
cyAoSElUX1IsUl9SKSBhbmQgKFJfUixJUF9SKS4KZCkgSSBhbmQgUiByZWRlZmluZXMgdGhlcmUg
c2VuZCBjb21tYW5kIHRvIHNlbmQgY29udHJvbCBwYWNrZXRzIHRocm91Z2ggaTMuCgoyLiBCYXNl
IGV4Y2hhbmdlCgphKSBJIHNlbmRzIEkxIHBhY2tldCB0byB0cmlnZ2VyIEhJVF9SIHRocm91Z2gg
aTMuIChJIGRvIG5vdCBzZW5kIElQX0kKYW5kIGRvIG5vdCBrbm93IElQX1IpLgpiKSBSIHJlY2Vp
dmVzIEkxIHBhY2tldCBhbmQgcmVwbGF5cyB3aXRoIFIxIHRvIEhJVF9JIGluIGkzLgpjKSBJIHJl
Y2VpdmVzIFIxIHBhY2tldCBhbmQgc2VuZHMgSTIgcGFja2V0IHdpdGggbG9jYXRvcnMgKHNldCBv
Zgpwb3NzaWJsZSBJUCBhZGRyZXNzZXMgb2YgSSkuCmQpIFIgcmVjZWl2ZXMgSTIgcGFja2V0LCBj
aG9vc2Ugb25lIElQIGFkZHJlc3MgZnJvbSBsb2NhdG9ycyBpbiBJMiBhbmQKc2V0cyBpdCB0byBT
QS4gQW5kIHJlcGxheXMgd2l0aCBSMiBwYWNrZXQgd2l0aCBsaXN0IG9mIFIgbG9jYXRvcnMuCmUp
IEkgcmVjZWl2ZXMgUjIgd2l0aCBsb2NhdG9ycywgY2hvb3NlIElQIGFkZHJlc3MgZm9yIFIsIGFu
ZCBzZXQgdXAgU0EuCgpCb3RoIHJlYWR5IGZvciBkaXJlY3Qgc2VjdXJlIGNvbW11bmljYXRpb25z
LiBDdXJyZW50bHksIGFzIEkga25vdywKbG9jYXRvcnMgYXJlIGluIFIxIGFuZCBJMiBwYWNrZXRz
IGluIGhpcGwsIGxhdGVyIHRoZXkgc2hvdWxkIGJlIG1vdmVkCnRvIFIyLCBJMi4KCk9wZW5ISVAg
ZG8gbm90IHVzZSBsb2NhdG9ycyB0byBzZW5kIElQIGFkZHJlc3Nlcywgc28gSSBhbmQgUiBkbyBu
b3QKaGlkZSB0aGVyZSBJUCBhZGRyZXNzZXMgZnJvbSB0aGUgYmVnaW5uaW5nLgoKQmVzdCBSZWdh
cmRzLApBbmRyZXkgTHVreWFuZW5rby4K


--===============1947361070==
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://www1.ietf.org/mailman/listinfo/p2psip

--===============1947361070==--



From p2psip-bounces@ietf.org Fri Jan 11 10:39:20 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDLya-0001RS-4a; Fri, 11 Jan 2008 10:39:20 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDLyY-0001OF-TG
	for p2psip@ietf.org; Fri, 11 Jan 2008 10:39:18 -0500
Received: from usaga01-in.huawei.com ([206.16.17.211])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JDLyY-0001bA-3u
	for p2psip@ietf.org; Fri, 11 Jan 2008 10:39:18 -0500
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 <0JUH00E6BKTG8C@usaga01-in.huawei.com> for
	p2psip@ietf.org; Fri, 11 Jan 2008 07:39:17 -0800 (PST)
Received: from s73602 (cpe-72-190-0-23.tx.res.rr.com [72.190.0.23])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006))
	with ESMTPA id <0JUH00I1LKTF6G@usaga01-in.huawei.com> for
	p2psip@ietf.org; Fri, 11 Jan 2008 07:39:16 -0800 (PST)
Date: Fri, 11 Jan 2008 09:38:28 -0600
From: Spencer Dawkins <spencer@mcsr-labs.org>
Subject: Re: [P2PSIP] HIP: optional, mandatory?
To: P2PSIP Mailing List <p2psip@ietf.org>
Message-id: <0d2101c85468$034c4080$6601a8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
Content-type: text/plain; format=flowed; charset=iso-8859-1;
	reply-type=original
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <476BA8D9.4010203@ericsson.com> <476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
	<0c3a01c85402$28d821e0$6601a8c0@china.huawei.com>
	<CBAEA83C-A2BB-47E7-AE49-A3E901DDB50C@cs.columbia.edu>
	<4d4304a00801110710x1b7f04b4lcbcbb9eb8702ba1e@mail.gmail.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hi, David,

I think you're right about the !("one ring to rule them all") part.

After re-reading Henning's email down to the part that said

> On Jan 10, 2008 10:52 PM, Henning Schulzrinne <hgs@cs.columbia.edu> wrote:
>> Unless the arrival of a
>> single non-HIP peer converts the whole overlay to non-HIP usage, this
>> also implies that all nodes must be able to deal with non-HIP peers,
>> even if they prefer to speak HIP. Among other things, they'll probably
>> have to implement ICE and TLS.

I think we're discussing an application scenarios question.

If you can bridge two overlays, you don't need to convert to non-HIP when a 
non-HIP peer tries to join - just bootstrap a non-HIP overlay and bridge.

If that's not possible, then you need to figure out what to do when a 
non-HIP peer joins.

If the expected application is amateur video sharing, you can probably fail 
the join request and tell someone to upgrade (this is what happens when I 
try to connect to AIM with an old client, right?). That's a lot simpler than 
anything else.

If the expected application is first-responder ad-hoc, you probably 
shouldn't fail the request...

Thanks,

Spencer


> Hmmm...(b) and (c) doesn't make sense to me, unless I'm missing
> something. After reading Spencer's email, (a) and (b) make more sense
> to me.
>
> I agree with Cullen that HIP should me optional both to implement and
> run. That means that many overlays may simply not support it all, and
> others may use it exclusively, giving us the (a) scenario. A
> particular endpoint may choose to implement both, allowing it join
> both types of overlays, which is (b).
>
> (c) makes little sense to me operationally, although I guess I can see
> how it could be done technically if there are some (b) type peers that
> are effectively relays. It would make for some really odd DHTs,
> however, since you might have to route calls via the adaptors, and I'm
> not sure it really gains you anything.
>
> In my mind, this would be a capabilities negotiation issue. Although
> the mechanics of how you do it might differ a good bit, logically it
> might be good to think about it like offer-answer in SIP. If I start
> an overlay, I'm free to choose the DHT and if it is SIP or not. If, on
> the other hand a few peers were negotiating among themselves, they
> could compare capabilities (DHTs, HIP or not, security model, etc.)
> and choose the best. I don't think we have a "One ring to rule them
> all..." thing going on where every single peer is in a global overlay,
> although there could be some (very) large and essentially public
> rings. There will be rings with different choices on DHT/transport,
> and that decision may limit who can join that particular ring.
>
> So I guess since we are all picking numbers here, I am the (3)(a and
> b) camp. I might just not have my head around (c), however...anyone
> care to take a stab at explaining how it actually works?
>
> David (as individual) 



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



From p2psip-bounces@ietf.org Fri Jan 11 10:50:42 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDM9Z-00037z-Ci; Fri, 11 Jan 2008 10:50:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDM9Y-00037t-8V
	for p2psip@ietf.org; Fri, 11 Jan 2008 10:50:40 -0500
Received: from rv-out-0910.google.com ([209.85.198.187])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JDM9X-0007HV-FN
	for p2psip@ietf.org; Fri, 11 Jan 2008 10:50:40 -0500
Received: by rv-out-0910.google.com with SMTP id l15so1011924rvb.49
	for <p2psip@ietf.org>; Fri, 11 Jan 2008 07:50:38 -0800 (PST)
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=VxRmZ0zqeQg0iyNDuAlkqGvXaQrWILxJmoOiLnBH5iI=;
	b=SvI/KUpGmkqWbbj1JjKipzP2PNCh4g6ZBtJDSYISZpWWgtFTUb4LgSqgBqEL8bG2iqcNQ/ld6mWnF1btJMNh5ixpEzwY1tPK/5Zjx7L/4wo2Ks4yqlgDL0w7hvKN6m6N6UEIVuvjCZF/YVQBX7dYgbRlyMFqHuT8zb6jr9LZUDs=
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=OOaARwfELjc7CQjGXljQPIFvvpPbDqc/mNp5JHmYYAcEj/DpVPJwhRcrEEi2X/dyq8rxPEYUD7S4t0f3h/+bBGc2tqIelglTLYK9cLhvsv7Ob5lxh21rGezfCTEOLUBdWurFwU7zGR+9qDD+03oBKFmSIVDNLJvQ8KYgxDrFa74=
Received: by 10.140.134.15 with SMTP id h15mr2102769rvd.51.1200066638671;
	Fri, 11 Jan 2008 07:50:38 -0800 (PST)
Received: by 10.65.180.16 with HTTP; Fri, 11 Jan 2008 07:50:38 -0800 (PST)
Message-ID: <4d4304a00801110750g22ac7ab6s56fdf0bb98e3bcfd@mail.gmail.com>
Date: Fri, 11 Jan 2008 10:50:38 -0500
From: "David A. Bryan" <dbryan@sipeerior.com>
To: "Spencer Dawkins" <spencer@mcsr-labs.org>
Subject: Re: [P2PSIP] HIP: optional, mandatory?
In-Reply-To: <0d2101c85468$034c4080$6601a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <476BA8D9.4010203@ericsson.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
	<0c3a01c85402$28d821e0$6601a8c0@china.huawei.com>
	<CBAEA83C-A2BB-47E7-AE49-A3E901DDB50C@cs.columbia.edu>
	<4d4304a00801110710x1b7f04b4lcbcbb9eb8702ba1e@mail.gmail.com>
	<0d2101c85468$034c4080$6601a8c0@china.huawei.com>
X-Google-Sender-Auth: 9dab149a94b374ba
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

I think I pretty much agree with you hear. If (c) is implemented as
two overlays bridged together, I'm much more comfortable with that,
but one overlay where messages between some peers are HIP and some are
not seems a bit more architecturally brittle to me, especially if some
peers can only speak one or the other. (then again, we can have mixed
TCP/UDP hops in SIP, but I am not sure that is a good thing) If (c) is
bridging, it can effectively work the same as bridging two overlays
with different DHTs (although the open question is if HIP is used for
the bridge then ;) )

David (as individual)

On Jan 11, 2008 10:38 AM, Spencer Dawkins <spencer@mcsr-labs.org> wrote:
> Hi, David,
>
> I think you're right about the !("one ring to rule them all") part.
>
> After re-reading Henning's email down to the part that said
>
> > On Jan 10, 2008 10:52 PM, Henning Schulzrinne <hgs@cs.columbia.edu> wrote:
> >> Unless the arrival of a
> >> single non-HIP peer converts the whole overlay to non-HIP usage, this
> >> also implies that all nodes must be able to deal with non-HIP peers,
> >> even if they prefer to speak HIP. Among other things, they'll probably
> >> have to implement ICE and TLS.
>
> I think we're discussing an application scenarios question.
>
> If you can bridge two overlays, you don't need to convert to non-HIP when a
> non-HIP peer tries to join - just bootstrap a non-HIP overlay and bridge.
>
> If that's not possible, then you need to figure out what to do when a
> non-HIP peer joins.
>
> If the expected application is amateur video sharing, you can probably fail
> the join request and tell someone to upgrade (this is what happens when I
> try to connect to AIM with an old client, right?). That's a lot simpler than
> anything else.
>
> If the expected application is first-responder ad-hoc, you probably
> shouldn't fail the request...
>
> Thanks,
>
> Spencer
>
>
>
> > Hmmm...(b) and (c) doesn't make sense to me, unless I'm missing
> > something. After reading Spencer's email, (a) and (b) make more sense
> > to me.
> >
> > I agree with Cullen that HIP should me optional both to implement and
> > run. That means that many overlays may simply not support it all, and
> > others may use it exclusively, giving us the (a) scenario. A
> > particular endpoint may choose to implement both, allowing it join
> > both types of overlays, which is (b).
> >
> > (c) makes little sense to me operationally, although I guess I can see
> > how it could be done technically if there are some (b) type peers that
> > are effectively relays. It would make for some really odd DHTs,
> > however, since you might have to route calls via the adaptors, and I'm
> > not sure it really gains you anything.
> >
> > In my mind, this would be a capabilities negotiation issue. Although
> > the mechanics of how you do it might differ a good bit, logically it
> > might be good to think about it like offer-answer in SIP. If I start
> > an overlay, I'm free to choose the DHT and if it is SIP or not. If, on
> > the other hand a few peers were negotiating among themselves, they
> > could compare capabilities (DHTs, HIP or not, security model, etc.)
> > and choose the best. I don't think we have a "One ring to rule them
> > all..." thing going on where every single peer is in a global overlay,
> > although there could be some (very) large and essentially public
> > rings. There will be rings with different choices on DHT/transport,
> > and that decision may limit who can join that particular ring.
> >
> > So I guess since we are all picking numbers here, I am the (3)(a and
> > b) camp. I might just not have my head around (c), however...anyone
> > care to take a stab at explaining how it actually works?
> >
> > David (as individual)
>
>
>
>
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.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://www1.ietf.org/mailman/listinfo/p2psip



From p2psip-bounces@ietf.org Fri Jan 11 10:51:13 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDMA5-0003Gx-8s; Fri, 11 Jan 2008 10:51:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDMA4-0003Gr-Gh
	for p2psip@ietf.org; Fri, 11 Jan 2008 10:51:12 -0500
Received: from rv-out-0910.google.com ([209.85.198.187])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JDM9z-0007HV-9C
	for p2psip@ietf.org; Fri, 11 Jan 2008 10:51:12 -0500
Received: by rv-out-0910.google.com with SMTP id l15so1011924rvb.49
	for <p2psip@ietf.org>; Fri, 11 Jan 2008 07:51:06 -0800 (PST)
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=6vZsj2CWTVrUepQHH56CiM+Gdx3qLKL7685G0ovQ4Z4=;
	b=EHJ/ezp3DWGZo0f7PdBWVPDCsE72t5KSTwRGsnihhxn6qDOB8jFerGNo57xCbH3s3+Box/cujHolyDJj1+W6V1kE3knqpggeObHUJujpQX5VqwZxmnNJIU2f6X8+49MDj194kWYzXTsS1zUSkJwfahePo3PqSqi0XhQznF0u5A0=
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=vvJsW852oDSGeOGE0CLPeLgi7GenDHy2i4VVIjxXxotMqTO0Q4vHv5Li4vX3qiQPZk8PglQRz52x8j3A2/GpLNmai3SOyCmRWwtCH7MZOIe9Y5s3SATf2AaU9wj2HBjHheEcwjwycCdowhEZoXEZj9o1HAUoDzV1R8YrX+vbKRg=
Received: by 10.141.99.4 with SMTP id b4mr2081930rvm.196.1200066666908;
	Fri, 11 Jan 2008 07:51:06 -0800 (PST)
Received: by 10.65.180.16 with HTTP; Fri, 11 Jan 2008 07:51:06 -0800 (PST)
Message-ID: <4d4304a00801110751s18507eecv51041ba2999d8e8e@mail.gmail.com>
Date: Fri, 11 Jan 2008 10:51:06 -0500
From: "David A. Bryan" <dbryan@sipeerior.com>
To: "Spencer Dawkins" <spencer@mcsr-labs.org>
Subject: Re: [P2PSIP] HIP: optional, mandatory?
In-Reply-To: <4d4304a00801110750g22ac7ab6s56fdf0bb98e3bcfd@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <476BA8D9.4010203@ericsson.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
	<0c3a01c85402$28d821e0$6601a8c0@china.huawei.com>
	<CBAEA83C-A2BB-47E7-AE49-A3E901DDB50C@cs.columbia.edu>
	<4d4304a00801110710x1b7f04b4lcbcbb9eb8702ba1e@mail.gmail.com>
	<0d2101c85468$034c4080$6601a8c0@china.huawei.com>
	<4d4304a00801110750g22ac7ab6s56fdf0bb98e3bcfd@mail.gmail.com>
X-Google-Sender-Auth: d9e69b9d33efff63
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Er, I guess I *hear* you and agree with you *here* ;)

On Jan 11, 2008 10:50 AM, David A. Bryan <dbryan@sipeerior.com> wrote:
> I think I pretty much agree with you hear. If (c) is implemented as
> two overlays bridged together, I'm much more comfortable with that,
> but one overlay where messages between some peers are HIP and some are
> not seems a bit more architecturally brittle to me, especially if some
> peers can only speak one or the other. (then again, we can have mixed
> TCP/UDP hops in SIP, but I am not sure that is a good thing) If (c) is
> bridging, it can effectively work the same as bridging two overlays
> with different DHTs (although the open question is if HIP is used for
> the bridge then ;) )
>
> David (as individual)
>
>
> On Jan 11, 2008 10:38 AM, Spencer Dawkins <spencer@mcsr-labs.org> wrote:
> > Hi, David,
> >
> > I think you're right about the !("one ring to rule them all") part.
> >
> > After re-reading Henning's email down to the part that said
> >
> > > On Jan 10, 2008 10:52 PM, Henning Schulzrinne <hgs@cs.columbia.edu> wrote:
> > >> Unless the arrival of a
> > >> single non-HIP peer converts the whole overlay to non-HIP usage, this
> > >> also implies that all nodes must be able to deal with non-HIP peers,
> > >> even if they prefer to speak HIP. Among other things, they'll probably
> > >> have to implement ICE and TLS.
> >
> > I think we're discussing an application scenarios question.
> >
> > If you can bridge two overlays, you don't need to convert to non-HIP when a
> > non-HIP peer tries to join - just bootstrap a non-HIP overlay and bridge.
> >
> > If that's not possible, then you need to figure out what to do when a
> > non-HIP peer joins.
> >
> > If the expected application is amateur video sharing, you can probably fail
> > the join request and tell someone to upgrade (this is what happens when I
> > try to connect to AIM with an old client, right?). That's a lot simpler than
> > anything else.
> >
> > If the expected application is first-responder ad-hoc, you probably
> > shouldn't fail the request...
> >
> > Thanks,
> >
> > Spencer
> >
> >
> >
> > > Hmmm...(b) and (c) doesn't make sense to me, unless I'm missing
> > > something. After reading Spencer's email, (a) and (b) make more sense
> > > to me.
> > >
> > > I agree with Cullen that HIP should me optional both to implement and
> > > run. That means that many overlays may simply not support it all, and
> > > others may use it exclusively, giving us the (a) scenario. A
> > > particular endpoint may choose to implement both, allowing it join
> > > both types of overlays, which is (b).
> > >
> > > (c) makes little sense to me operationally, although I guess I can see
> > > how it could be done technically if there are some (b) type peers that
> > > are effectively relays. It would make for some really odd DHTs,
> > > however, since you might have to route calls via the adaptors, and I'm
> > > not sure it really gains you anything.
> > >
> > > In my mind, this would be a capabilities negotiation issue. Although
> > > the mechanics of how you do it might differ a good bit, logically it
> > > might be good to think about it like offer-answer in SIP. If I start
> > > an overlay, I'm free to choose the DHT and if it is SIP or not. If, on
> > > the other hand a few peers were negotiating among themselves, they
> > > could compare capabilities (DHTs, HIP or not, security model, etc.)
> > > and choose the best. I don't think we have a "One ring to rule them
> > > all..." thing going on where every single peer is in a global overlay,
> > > although there could be some (very) large and essentially public
> > > rings. There will be rings with different choices on DHT/transport,
> > > and that decision may limit who can join that particular ring.
> > >
> > > So I guess since we are all picking numbers here, I am the (3)(a and
> > > b) camp. I might just not have my head around (c), however...anyone
> > > care to take a stab at explaining how it actually works?
> > >
> > > David (as individual)
> >
> >
> >
> >
> > _______________________________________________
> > P2PSIP mailing list
> > P2PSIP@ietf.org
> > https://www1.ietf.org/mailman/listinfo/p2psip
> >
>
>
>
>
> --
> David A. Bryan
> dbryan@SIPeerior.com
> +1.757.565.0101 x101
> +1.757.565.0088 (fax)
> www.SIPeerior.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://www1.ietf.org/mailman/listinfo/p2psip



From p2psip-bounces@ietf.org Fri Jan 11 10:53:45 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDMCW-00058O-Mx; Fri, 11 Jan 2008 10:53:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDMCV-00058J-Jl
	for p2psip@ietf.org; Fri, 11 Jan 2008 10:53:43 -0500
Received: from u-173-c156.cs.uni-tuebingen.de ([134.2.173.156]
	helo=smtp.cs.uni-tuebingen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JDMCT-0007KJ-JZ
	for p2psip@ietf.org; Fri, 11 Jan 2008 10:53:43 -0500
Received: from u-172-c174.cs.uni-tuebingen.de ([134.2.172.174])
	by smtp.cs.uni-tuebingen.de with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.60) (envelope-from <iinfe01@ri.uni-tuebingen.de>)
	id 1JDMC8-0004A4-1A; Fri, 11 Jan 2008 16:53:20 +0100
Message-ID: <478790EE.4050301@uni-tuebingen.de>
Date: Fri, 11 Jan 2008 16:53:18 +0100
From: Ali Fessi <ali.fessi@uni-tuebingen.de>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: Re: [P2PSIP] New draft: HIP BONE
References: <476BA8D9.4010203@ericsson.com>	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>	<476E2B7C.9070601@ericsson.com>	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<086801c8530e$611d8030$6601a8c0@china.huawei.com>
	<4785566F.7000700@uni-tuebingen.de>
	<833EB4F9-41EE-41E5-A951-DE2AF0FE9FF8@nomadiclab.com>
In-Reply-To: <833EB4F9-41EE-41E5-A951-DE2AF0FE9FF8@nomadiclab.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hi Pekka,

On 10 Jan 2008, at 13:45 Pekka Nikander wrote:
> Hi Ali,
> 
> On 10 Jan 2008, at 01:19, Ali Fessi wrote:
> <snip>
>> Simlarly, you can use the P2P protocol to resolve a HIP ORCHID to a 
>> Locator, and then when you get the Locator start the HIP handshake.
>>
>> And in fact, this is maybe something confusing in the HIP BONE draft 
>> [...] because HIP BONE says that a I1 message is transported 
>> hop-by-hop in the overlay. I would let the P2P protocol resolve the 
>> HIP Identifier to a Locator first, and then send the I1 message 
>> directly to the HIP Responder.
> 
> That has been tried and there is even a prototype working on PlanetLab 
> using OpenDHT, but unfortunately there appears to be two problems.  
> First, OpenDHT latencies appear to be too long and unpredictable, 
> sometimes minutes and often exceeding 10 seconds.  But that may be an 
> implementation problem that can be fixed.  

yes indeed, this is a OpenDHT specific problem. (we also had similar 
performance problems when experimenting with P2PSIP on OpenDHT)

> The second, bigger problem is 
> that if both the initiator and the responder are behind NATs, the you 
> just cannot send the I1 message directly to the HIP responder.
> 
> The latter is the reason why we chose to use a Berkeley i3 -like system 
> in both Hi3 and in HIP BONE, i.e., to forward HIP messages through the 
> overlay instead of using it in a typical DHT put/get manner.

i3, Secure-i3 and Hi3 have however an assumption that does not hold 
here. The overlay consitutes of i3 servers which are considered to be 
trustworthy, have public addresses and can converge as rendez-vous 
points for "clients" behind NATs. This assumption does not hold for 
P2PSIP, since there is not such an overlay.

So, when the I1 message is forwarded on the overlay, the NAT traversal 
problem needs to solved for each link on the path between the Initiator 
and the Responder. And this is not solved by HIP, unless you run HIP for 
each link on the overlay (including the HIP handshake and ICE for NAT 
traversal) which would be proably too much overhead.

Moreover, the peer protocol needs to cope with NAT traversal for other 
type of messages for the overlay maintenance, e.g. joins and leaves, 
anyway. and again this is not solved by HIP, unless you do HIP hop-by-hop.

My conslusions from these facts here (please feel free to heavily 
disagree and let me know if i am wrong) would be that:

- *HIP actually does not solve the NAT traversal problem for P2PSIP*, as 
it has been assumed.
- The peer protocol needs to cope with the NAT traversal by itself.

Cheers,
  Ali


> 
> --Pekka Nikander
> 


-- 
Ali Fessi
Computer Networks and Internet
University of Tuebingen, Germany
Phone: +49 7071 29-70576 / Fax: +49 7071 29-5220
EMail: ali.fessi@uni-tuebingen.de
Web: http://net.informatik.uni-tuebingen.de/~fessi/

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



From p2psip-bounces@ietf.org Fri Jan 11 10:53:54 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDMCg-0005JB-25; Fri, 11 Jan 2008 10:53:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDMCf-0005HL-2j
	for p2psip@ietf.org; Fri, 11 Jan 2008 10:53:53 -0500
Received: from jalapeno.cc.columbia.edu ([128.59.29.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JDMCe-0007KS-FT
	for p2psip@ietf.org; Fri, 11 Jan 2008 10:53:53 -0500
Received: from dhcp71.cs.columbia.edu (dhcp71.cs.columbia.edu [128.59.17.221])
	(user=hgs10 mech=PLAIN bits=0)
	by jalapeno.cc.columbia.edu (8.14.1/8.14.1) with ESMTP id
	m0BFrpgl013015
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT)
	for <p2psip@ietf.org>; Fri, 11 Jan 2008 10:53:52 -0500 (EST)
Message-Id: <1B79D7E7-A67B-42D9-9F00-66E69080C358@cs.columbia.edu>
From: Henning Schulzrinne <hgs@cs.columbia.edu>
To: P2PSIP Mailing List <p2psip@ietf.org>
In-Reply-To: <0d2101c85468$034c4080$6601a8c0@china.huawei.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Subject: Re: [P2PSIP] HIP: optional, mandatory?
X-Priority: 3
Date: Fri, 11 Jan 2008 10:53:51 -0500
References: <476BA8D9.4010203@ericsson.com> <476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
	<0c3a01c85402$28d821e0$6601a8c0@china.huawei.com>
	<CBAEA83C-A2BB-47E7-AE49-A3E901DDB50C@cs.columbia.edu>
	<4d4304a00801110710x1b7f04b4lcbcbb9eb8702ba1e@mail.gmail.com>
	<0d2101c85468$034c4080$6601a8c0@china.huawei.com>
X-Mailer: Apple Mail (2.915)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.5
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

This is exactly the situation I want to avoid. We're now creating two  
classes of systems, the HIP-capable ones and the rest. From a consumer  
perspective, somebody buys a "VoIP p2p client" to join any number of  
yet-unkown overlays (otherwise, they could just run Skype) - and then  
find out that they can't join some fraction of overlays because they  
didn't look for an acronym they didn't understand. They can only hope  
that the overlay implements "bridging", likely with the need for a  
central server to perform that function.

This also violates the "no cost" requirement I mentioned. Even if I,  
as an implementor consider HIP a waste of time, I still have to  
implement it.

At least we're now clear that the HIP advocates want to essentially  
force systems to implement it. This will hopefully focus the  
discussion a bit.

Henning

On Jan 11, 2008, at 10:38 AM, Spencer Dawkins wrote:

> Hi, David,
>
> I think you're right about the !("one ring to rule them all") part.
>
> After re-reading Henning's email down to the part that said
>
>> On Jan 10, 2008 10:52 PM, Henning Schulzrinne <hgs@cs.columbia.edu>  
>> wrote:
>>> Unless the arrival of a
>>> single non-HIP peer converts the whole overlay to non-HIP usage,  
>>> this
>>> also implies that all nodes must be able to deal with non-HIP peers,
>>> even if they prefer to speak HIP. Among other things, they'll  
>>> probably
>>> have to implement ICE and TLS.
>
> I think we're discussing an application scenarios question.
>
> If you can bridge two overlays, you don't need to convert to non-HIP  
> when a non-HIP peer tries to join - just bootstrap a non-HIP overlay  
> and bridge.
>
> If that's not possible, then you need to figure out what to do when  
> a non-HIP peer joins.
>
> If the expected application is amateur video sharing, you can  
> probably fail the join request and tell someone to upgrade (this is  
> what happens when I try to connect to AIM with an old client,  
> right?). That's a lot simpler than anything else.
>
> If the expected application is first-responder ad-hoc, you probably  
> shouldn't fail the request...
>
> Thanks,
>
> Spencer
>
>
>> Hmmm...(b) and (c) doesn't make sense to me, unless I'm missing
>> something. After reading Spencer's email, (a) and (b) make more sense
>> to me.
>>
>> I agree with Cullen that HIP should me optional both to implement and
>> run. That means that many overlays may simply not support it all, and
>> others may use it exclusively, giving us the (a) scenario. A
>> particular endpoint may choose to implement both, allowing it join
>> both types of overlays, which is (b).
>>
>> (c) makes little sense to me operationally, although I guess I can  
>> see
>> how it could be done technically if there are some (b) type peers  
>> that
>> are effectively relays. It would make for some really odd DHTs,
>> however, since you might have to route calls via the adaptors, and  
>> I'm
>> not sure it really gains you anything.
>>
>> In my mind, this would be a capabilities negotiation issue. Although
>> the mechanics of how you do it might differ a good bit, logically it
>> might be good to think about it like offer-answer in SIP. If I start
>> an overlay, I'm free to choose the DHT and if it is SIP or not. If,  
>> on
>> the other hand a few peers were negotiating among themselves, they
>> could compare capabilities (DHTs, HIP or not, security model, etc.)
>> and choose the best. I don't think we have a "One ring to rule them
>> all..." thing going on where every single peer is in a global  
>> overlay,
>> although there could be some (very) large and essentially public
>> rings. There will be rings with different choices on DHT/transport,
>> and that decision may limit who can join that particular ring.
>>
>> So I guess since we are all picking numbers here, I am the (3)(a and
>> b) camp. I might just not have my head around (c), however...anyone
>> care to take a stab at explaining how it actually works?
>>
>> David (as individual)
>
>
>
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.ietf.org/mailman/listinfo/p2psip


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



From p2psip-bounces@ietf.org Fri Jan 11 11:40:04 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDMvJ-00008Q-Iu; Fri, 11 Jan 2008 11:40:01 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDMvH-00008F-W3
	for p2psip@ietf.org; Fri, 11 Jan 2008 11:40:00 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JDMvH-0002oQ-9I
	for p2psip@ietf.org; Fri, 11 Jan 2008 11:39:59 -0500
X-IronPort-AV: E=Sophos;i="4.24,272,1196668800"; d="scan'208";a="34300168"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 11 Jan 2008 08:39:58 -0800
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m0BGdwBC008296; 
	Fri, 11 Jan 2008 08:39:58 -0800
Received: from [192.168.4.177] (sjc-fluffy-vpn1.cisco.com [10.25.236.82])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with SMTP id m0BGduFL029090;
	Fri, 11 Jan 2008 16:39:58 GMT
In-Reply-To: <465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com>
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
	<465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com>
Impp: xmpp:cullenfluffyjennings@jabber.org
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [P2PSIP] HIP: optional, mandatory?
Date: Fri, 11 Jan 2008 08:38:59 -0800
To: David Barrett <dbarrett@quinthar.com>
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4498; t=1200069598;
	x=1200933598; c=relaxed/simple; s=sjdkim4002;
	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]=20HIP=3A=20optional,=20mandato ry?
	|Sender:=20; bh=1hyschnL7tHq3FVuH1rtYS8u8OI1JsBMcAeB4RiS3LY=;
	b=uNyeWLQTIqmYGY6AZiM1qIbETyMwCTzxQ3kX90ve+TE9zjDLNnoxhUJRf5
	y8pX5jd/l79qv3uNUPv9P57StvF78AsxLSwkjU9n8JVOB2hM8FMONkpwQ2CS
	KPNFrRDXd7;
Authentication-Results: sj-dkim-4; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org


On Jan 10, 2008, at 8:23 PM, David Barrett wrote:

> We don't need more options for what we CAN do, we need decisions on  
> what we WILL do.

Yep - agree.  And what I want to do is standardize something that  
lets me build deployable interoperable solutions soon. Success for me  
involves deployments.

>   If we're not considering making HIP mandatory, then let's stop  
> talking about it and start focusing on those things that *will* be  
> mandatory.

The P2PSIP WG has made very few decisions since it was formed. IMHO,  
what we need to do real soon now is pick something as a starting  
point for a WG document then go and make the decision to change it to  
be what we want.  Until we do that, my belief is that the WG will  
make fairly marginal progress.

>
> That said, I think this HIP discussion is the best thing to happen  
> in P2PSIP for years.  It seems like the most practical and powerful  
> solution, the best layering of functionality, and the most feasible  
> design that I've yet to hear.  Moving the hard P2P code into a  
> reusable HIP layer makes a lot of sense,

this is way outside anything HIP was charted to do or is working on

> not only for P2PSIP, but for the internet as a whole.  It seems  
> like a wagon that we should voluntarily and enthusiastically hitch  
> ourselves to, rather than try to reproduce or compete with it, or  
> toss it in the overflowing bucket of optional extensions.
>
> It seems sensible to have a base HIP layer that either comes pre- 
> installed with the OS or redistributed by the application (similar  
> to WinPCap).  (I could even see making a sort of "HIP-lite" self- 
> contained library that can be linked straight into the application  
> for when installing a   Then P2PSIP can be one of many HIP-using  
> applications that are vastly simplified by being insulated from the  
> gnarly realities of NAT and firewall penetration, mobility, etc.
>
> This makes a lot more sense than continually reproducing this  
> really hard functionality in every application.

Most of the concrete proposals layer the p2p code such that the  
library that provided the p2p part could be used by other  
applications. This is a good design but not something you need HIP to  
accomplish.

>
> -david

Cullen <with my individual hat on>

>
> On Jan 11, 2008, at 7:33 AM, Cullen Jennings wrote:
>
>>
>> I was assuming most folks were talking about (3) given that much  
>> of HIP is still being designed and it will be awhile to get things  
>> build and deployed. I know lots of parts of HIP have been done but  
>> when we are talking about mobility, nat traversal, no DNS, and  
>> easy end user installations, there is still work. Anyway, I am in  
>> the 3 category.
>>
>> Cullen <with my individual hat on>
>> On Jan 10, 2008, at 2:14 PM, Henning Schulzrinne wrote:
>>
>>> One of the issues I don't understand about this discussion is  
>>> whether all instances of P2PSIP would be expected to be running  
>>> HIP or just some. There seem to be at least three options:
>>>
>>> (1) Mandatory to implement and run
>>>
>>> The only non-recursive-dependency model seems to be that peer  
>>> nodes would store the HIT-IP bindings in their routing tables.  
>>> (This largely negates any mobility advantages, but that's a  
>>> separate discussion.)
>>>
>>> (2) Mandatory to implement, but there can be instances of an  
>>> overlay (or maybe even part of an overlay) that don't use HIP
>>>
>>> This would require providing ICE functionality at both the HIP  
>>> level and directly to the P2P protocol.
>>>
>>> (3) Optional to implement and run
>>>
>>> This only works if you can have mixed HIP-non-HIP nodes. Also  
>>> requires implementations of ICE in both layers and the ability to  
>>> mix-and-match HIP and non-HIP nodes within an overlay, unless  
>>> each overlay has a "HIP flag".
>>>
>>> I admit that I'm rather worried about the complexity of this  
>>> whole edifice. I think it would be helpful if the proponents of a  
>>> HIP-based approach stated clearly which of these they have in mind.
>>>
>>> Henning
>>>
>>> _______________________________________________
>>> P2PSIP mailing list
>>> P2PSIP@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/p2psip
>> _______________________________________________
>> P2PSIP mailing list
>> P2PSIP@ietf.org
>> https://www1.ietf.org/mailman/listinfo/p2psip
>>
>


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



From p2psip-bounces@ietf.org Fri Jan 11 11:59:14 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDNDr-0006By-US; Fri, 11 Jan 2008 11:59:11 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDNDp-0006Ao-Ev
	for p2psip@ietf.org; Fri, 11 Jan 2008 11:59:09 -0500
Received: from hs-out-0708.google.com ([64.233.178.240]
	helo=hs-out-2122.google.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JDNDo-0005ZV-HG
	for p2psip@ietf.org; Fri, 11 Jan 2008 11:59:09 -0500
Received: by hs-out-2122.google.com with SMTP id 54so1079231hsz.5
	for <p2psip@ietf.org>; Fri, 11 Jan 2008 08:59:08 -0800 (PST)
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=eDE9Nf8NlUpWN6nuXcmIYHOINjmwhNsSKDi30N3cUJw=;
	b=MyN8/aD73+aNHrTjiq8pIj+FIFIHJzmbG/lJpf39NKSh3OkastBcsBpKb4pv1Q54neKDlmNkn8Pmaeby5EIdnlbNrZN60DRvwtFcHqcX7MAHQGkcCC7OiEjXogeJp4XD3pKgkQl/wOWUmxh922ZO+MRShVi4n5b7gh4Pt0t36LI=
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=nyY7l06lfQ+I92BrlKjA5sbZUBWEG0/g/XyscGxI2HWHfPxPxG+O2TX5PclbG1sLI9T2VF77dJujblh7tR5CY1LH4s4ME8xLzXCEuNgAgTuX7Qy7070lz8gDFue8/LK9h2XEASl1KKUQtYfV5C4kT4JSQ4gkFClfJ5Gxtut6g24=
Received: by 10.142.105.14 with SMTP id d14mr1780500wfc.67.1200070746053;
	Fri, 11 Jan 2008 08:59:06 -0800 (PST)
Received: by 10.65.180.16 with HTTP; Fri, 11 Jan 2008 08:59:05 -0800 (PST)
Message-ID: <4d4304a00801110859t1b7feb53nd3413fcd84ad57cc@mail.gmail.com>
Date: Fri, 11 Jan 2008 11:59:05 -0500
From: "David A. Bryan" <dbryan@sipeerior.com>
To: "Cullen Jennings" <fluffy@cisco.com>
Subject: Re: [P2PSIP] HIP: optional, mandatory?
In-Reply-To: <284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <476BA8D9.4010203@ericsson.com> <476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
	<465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com>
	<284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>
X-Google-Sender-Auth: 90b1c862f57a7ba0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1449ead51a2ff026dcb23465f5379250
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Fully agree with Cullen here as far as the flexibility of the proposed
peer protocols to extend beyond SIP. Ever since the decision was made
(early in the charter process) that while SIP would be the primary
app, we would design the protocol in such a way that it could be
easily reused for other applications, this has been a guiding
principal in all of the "concrete proposals" and I know that all the
various authors/implementors of these things have kept that very much
in mind for at least the last couple of years. I'm quite confident
that the peer protocol can be used for many things besides SIP.

Cullen further points out that much of what you mentioned -- a fully
fleshed out HIP P2P core -- isn't something that is currently
chartered standards-track work for the HIP WG. Building a peer
protocol is in scope for us. We need to make sure that what we deliver
is something that can be used by other applications (including, one
could imagine, HIP), but I don't think we wait for things to emerge
from another group that we are chartered to do!

I want to be clear that I don't think this means we rule out having a
HIP transport, but I think that if we say that we are going to wait
for HIP to provide the complete underlying P2P fabric (peer protocol
and all) that we use, we have things backwards -- that is what we are
chartered here to provide. I also think it will be a long wait, since
that particular work isn't chartered for P2P standards at the moment.
I think deployment is critical here and sooner, rather than later. We
need to be picking a direction and going with it very soon, not
waiting for another group to deliver.

As a completely personal view, I think HIP is interesting, but I think
it is a far longer path (years) to deployment if we make it mandatory.
I want to keep looking at it as it evolves, and I'd love to see us
specify how it would work with a peer protocol as a transport, but I
don't want every P2PSIP app to require HIP.

My 2 cents.

David (as individual)


On Jan 11, 2008 11:38 AM, Cullen Jennings <fluffy@cisco.com> wrote:
>
> On Jan 10, 2008, at 8:23 PM, David Barrett wrote:
>
> > We don't need more options for what we CAN do, we need decisions on
> > what we WILL do.
>
> Yep - agree.  And what I want to do is standardize something that
> lets me build deployable interoperable solutions soon. Success for me
> involves deployments.
>
> >   If we're not considering making HIP mandatory, then let's stop
> > talking about it and start focusing on those things that *will* be
> > mandatory.
>
> The P2PSIP WG has made very few decisions since it was formed. IMHO,
> what we need to do real soon now is pick something as a starting
> point for a WG document then go and make the decision to change it to
> be what we want.  Until we do that, my belief is that the WG will
> make fairly marginal progress.
>
> >
> > That said, I think this HIP discussion is the best thing to happen
> > in P2PSIP for years.  It seems like the most practical and powerful
> > solution, the best layering of functionality, and the most feasible
> > design that I've yet to hear.  Moving the hard P2P code into a
> > reusable HIP layer makes a lot of sense,
>
> this is way outside anything HIP was charted to do or is working on
>
> > not only for P2PSIP, but for the internet as a whole.  It seems
> > like a wagon that we should voluntarily and enthusiastically hitch
> > ourselves to, rather than try to reproduce or compete with it, or
> > toss it in the overflowing bucket of optional extensions.
> >
> > It seems sensible to have a base HIP layer that either comes pre-
> > installed with the OS or redistributed by the application (similar
> > to WinPCap).  (I could even see making a sort of "HIP-lite" self-
> > contained library that can be linked straight into the application
> > for when installing a   Then P2PSIP can be one of many HIP-using
> > applications that are vastly simplified by being insulated from the
> > gnarly realities of NAT and firewall penetration, mobility, etc.
> >
> > This makes a lot more sense than continually reproducing this
> > really hard functionality in every application.
>
> Most of the concrete proposals layer the p2p code such that the
> library that provided the p2p part could be used by other
> applications. This is a good design but not something you need HIP to
> accomplish.
>
> >
> > -david
>
>
> Cullen <with my individual hat on>
>
> >
> > On Jan 11, 2008, at 7:33 AM, Cullen Jennings wrote:
> >
> >>
> >> I was assuming most folks were talking about (3) given that much
> >> of HIP is still being designed and it will be awhile to get things
> >> build and deployed. I know lots of parts of HIP have been done but
> >> when we are talking about mobility, nat traversal, no DNS, and
> >> easy end user installations, there is still work. Anyway, I am in
> >> the 3 category.
> >>
> >> Cullen <with my individual hat on>
> >> On Jan 10, 2008, at 2:14 PM, Henning Schulzrinne wrote:
> >>
> >>> One of the issues I don't understand about this discussion is
> >>> whether all instances of P2PSIP would be expected to be running
> >>> HIP or just some. There seem to be at least three options:
> >>>
> >>> (1) Mandatory to implement and run
> >>>
> >>> The only non-recursive-dependency model seems to be that peer
> >>> nodes would store the HIT-IP bindings in their routing tables.
> >>> (This largely negates any mobility advantages, but that's a
> >>> separate discussion.)
> >>>
> >>> (2) Mandatory to implement, but there can be instances of an
> >>> overlay (or maybe even part of an overlay) that don't use HIP
> >>>
> >>> This would require providing ICE functionality at both the HIP
> >>> level and directly to the P2P protocol.
> >>>
> >>> (3) Optional to implement and run
> >>>
> >>> This only works if you can have mixed HIP-non-HIP nodes. Also
> >>> requires implementations of ICE in both layers and the ability to
> >>> mix-and-match HIP and non-HIP nodes within an overlay, unless
> >>> each overlay has a "HIP flag".
> >>>
> >>> I admit that I'm rather worried about the complexity of this
> >>> whole edifice. I think it would be helpful if the proponents of a
> >>> HIP-based approach stated clearly which of these they have in mind.
> >>>
> >>> Henning
> >>>
> >>> _______________________________________________
> >>> P2PSIP mailing list
> >>> P2PSIP@ietf.org
> >>> https://www1.ietf.org/mailman/listinfo/p2psip
> >> _______________________________________________
> >> P2PSIP mailing list
> >> P2PSIP@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/p2psip
> >>
> >
>
>
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.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://www1.ietf.org/mailman/listinfo/p2psip



From p2psip-bounces@ietf.org Fri Jan 11 12:04:16 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDNIm-000516-2l; Fri, 11 Jan 2008 12:04:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDNIl-000510-0x
	for p2psip@ietf.org; Fri, 11 Jan 2008 12:04:15 -0500
Received: from mxoutps1.us.army.mil ([143.69.250.38])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JDNIg-0000t3-13
	for p2psip@ietf.org; Fri, 11 Jan 2008 12:04:14 -0500
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=RcezIPBdtgKG2lS3VtvUAw3gK/6JxtJpGwua7POYF7YVJ2i/wJHEjQmW
	2r51pK7FQpLKZi8QKNyvj3VIW0ZPiQ==;
From: "Roy, Radhika R Dr CTR USA USAMC" <radhika.r.roy@us.army.mil>
X-AKO: 106069435:10.224.36.65:11 Jan 2008 17:04:09 +0000:$Webmail:None
X-IronPort-AV: E=Sophos;i="4.24,272,1196640000"; d="scan'208";a="106069435"
Received: from mail5.int.ps1.us.army.mil (HELO us.army.mil) ([10.224.36.65])
	by mxoutps1.us.army.mil with ESMTP; 11 Jan 2008 17:04:09 +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); Fri, 11 Jan
	2008 12:04:09 -0500
To: Cullen Jennings <fluffy@cisco.com>
Message-ID: <e1e2f6d96894.47875b39@us.army.mil>
Date: Fri, 11 Jan 2008 12:04:09 -0500
X-Mailer: Sun Java(tm) System Messenger Express 6.2-9.04 (built Jun 11
 2007)
MIME-Version: 1.0
Content-Language: en
Subject: Re: [P2PSIP] HIP: optional, mandatory?
X-Accept-Language: en
Priority: normal
In-Reply-To: <284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
	<465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com>
	<284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

If it is so as Cullen has explained, what is the problem to proceed per P2PSIP charter for accomplishing the mandated work items (may be in a limited way) soon which may be ready for deployment?

Cheers!
Radhika

----- Original Message -----
From: Cullen Jennings 
Date: Friday, January 11, 2008 11:40
Subject: Re: [P2PSIP] HIP: optional, mandatory?
To: David Barrett 
Cc: P2PSIP Mailing List 

> 
> On Jan 10, 2008, at 8:23 PM, David Barrett wrote:
> 
> > We don't need more options for what we CAN do, we need decisions 
> on 
> > what we WILL do.
> 
> Yep - agree. And what I want to do is standardize something that 
> lets me build deployable interoperable solutions soon. Success for 
> me 
> involves deployments.
> 
> > If we're not considering making HIP mandatory, then let's stop 
> 
> > talking about it and start focusing on those things that *will* 
> be 
> > mandatory.
> 
> The P2PSIP WG has made very few decisions since it was formed. 
> IMHO, 
> what we need to do real soon now is pick something as a starting 
> point for a WG document then go and make the decision to change it 
> to 
> be what we want. Until we do that, my belief is that the WG will 
> make fairly marginal progress.
> 
> >
> > That said, I think this HIP discussion is the best thing to 
> happen 
> > in P2PSIP for years. It seems like the most practical and 
> powerful 
> > solution, the best layering of functionality, and the most 
> feasible 
> > design that I've yet to hear. Moving the hard P2P code into a 
> > reusable HIP layer makes a lot of sense,
> 
> this is way outside anything HIP was charted to do or is working on
> 
> > not only for P2PSIP, but for the internet as a whole. It seems 
> > like a wagon that we should voluntarily and enthusiastically 
> hitch 
> > ourselves to, rather than try to reproduce or compete with it, 
> or 
> > toss it in the overflowing bucket of optional extensions.
> >
> > It seems sensible to have a base HIP layer that either comes pre-
> 
> > installed with the OS or redistributed by the application 
> (similar 
> > to WinPCap). (I could even see making a sort of "HIP-lite" self-
> 
> > contained library that can be linked straight into the 
> application 
> > for when installing a Then P2PSIP can be one of many HIP-using 
> 
> > applications that are vastly simplified by being insulated from 
> the 
> > gnarly realities of NAT and firewall penetration, mobility, etc.
> >
> > This makes a lot more sense than continually reproducing this 
> > really hard functionality in every application.
> 
> Most of the concrete proposals layer the p2p code such that the 
> library that provided the p2p part could be used by other 
> applications. This is a good design but not something you need HIP 
> to 
> accomplish.
> 
> >
> > -david
> 
> Cullen 
> 
> >
> > On Jan 11, 2008, at 7:33 AM, Cullen Jennings wrote:
> >
> >>
> >> I was assuming most folks were talking about (3) given that 
> much 
> >> of HIP is still being designed and it will be awhile to get 
> things 
> >> build and deployed. I know lots of parts of HIP have been done 
> but 
> >> when we are talking about mobility, nat traversal, no DNS, and 
> >> easy end user installations, there is still work. Anyway, I am 
> in 
> >> the 3 category.
> >>
> >> Cullen 
> >> On Jan 10, 2008, at 2:14 PM, Henning Schulzrinne wrote:
> >>
> >>> One of the issues I don't understand about this discussion is 
> >>> whether all instances of P2PSIP would be expected to be 
> running 
> >>> HIP or just some. There seem to be at least three options:
> >>>
> >>> (1) Mandatory to implement and run
> >>>
> >>> The only non-recursive-dependency model seems to be that peer 
> >>> nodes would store the HIT-IP bindings in their routing tables. 
> 
> >>> (This largely negates any mobility advantages, but that's a 
> >>> separate discussion.)
> >>>
> >>> (2) Mandatory to implement, but there can be instances of an 
> >>> overlay (or maybe even part of an overlay) that don't use HIP
> >>>
> >>> This would require providing ICE functionality at both the HIP 
> 
> >>> level and directly to the P2P protocol.
> >>>
> >>> (3) Optional to implement and run
> >>>
> >>> This only works if you can have mixed HIP-non-HIP nodes. Also 
> >>> requires implementations of ICE in both layers and the ability 
> to 
> >>> mix-and-match HIP and non-HIP nodes within an overlay, unless 
> >>> each overlay has a "HIP flag".
> >>>
> >>> I admit that I'm rather worried about the complexity of this 
> >>> whole edifice. I think it would be helpful if the proponents 
> of a 
> >>> HIP-based approach stated clearly which of these they have in 
> mind.>>>
> >>> Henning

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



From p2psip-bounces@ietf.org Fri Jan 11 13:14:23 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDOOb-0001w1-8i; Fri, 11 Jan 2008 13:14:21 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDOOa-0001vw-DI
	for p2psip@ietf.org; Fri, 11 Jan 2008 13:14:20 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JDOOZ-0007YZ-Cq
	for p2psip@ietf.org; Fri, 11 Jan 2008 13:14:20 -0500
X-IronPort-AV: E=Sophos;i="4.24,272,1196668800"; d="scan'208";a="34359556"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 11 Jan 2008 10:14:08 -0800
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m0BIE8R0008255; 
	Fri, 11 Jan 2008 10:14:08 -0800
Received: from [192.168.4.177] (sjc-fluffy-vpn1.cisco.com [10.25.236.82])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with SMTP id m0BIDxSa018498;
	Fri, 11 Jan 2008 18:13:59 GMT
In-Reply-To: <474455CD.2040200@idssoftware.com>
References: <E1Itygx-0004tT-O8@ietf.org>
	<B09DAF4E-8430-4D10-8090-7B5082D77BD8@cisco.com>
	<474455CD.2040200@idssoftware.com>
Impp: xmpp:cullenfluffyjennings@jabber.org
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <9E9BE3E2-3331-453A-9262-7EBB5FA2D39B@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [P2PSIP] Merge of ASP and RELOAD - Version Notification
	for	draft-bryan-p2psip-reload-02
Date: Fri, 11 Jan 2008 10:13:04 -0800
To: Michael Chen <michaelc@idssoftware.com>
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4540; t=1200075248;
	x=1200939248; c=relaxed/simple; s=sjdkim4002;
	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]=20Merge=20of=20ASP=20and=20REL
	OAD=20-=20Version=20Notification=20for=09draft-bryan-p2psip-
	reload-02 |Sender:=20;
	bh=NzgFwuh+9PAbuq2SQe0zIsf3LF8GfGYW+n12GnzT7yw=;
	b=XP2tLuEzJR1BRGZlStb5BtIS7VGQkSOvIGXM9WpeZYfMbPMdiJ+c0/64lc
	wEnKw4mrPlB/hTqscH4L4VDutFNQWG80866eHRuef0hGXSuCpr7kMiS9qVzM
	VcQ7piCCyd;
Authentication-Results: sj-dkim-4; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Cc: P2PSIP WG <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org


I've been meaning to reply to you forever on this but, I like this  
idea, thanks.

On Nov 21, 2007, at 7:59 AM, Michael Chen wrote:

> Hi,
>
> I have a practical suggestion for the forwarding header. The last  
> two paragraphs of section 4.1 of the draft describe how the Route- 
> List shrinks while Via-List grow as the Reload message passes  
> through intermediate peers.  If you flip the order of these two  
> lists such that Via-List comes first followed by the Route-list:
>
>   24 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>      |     Via       |    Route      |                               |
>      |     List      |      List     |            Flags              |
>      |     Length    |     Length    |                               |
>   28 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>      |                                                               |
>      //                          Via List                           //
>      |                                                               |
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>      |                                                               |
>      //                          Route List                         //
>      |                                                               |
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>      |                                                               |
>      //                          Route Log                          //
>      |                                                               |
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> Then as the message passes the pre-selected list of peers in Route- 
> list, intermediate peer can simply increment the via-list-length  
> field and decrement the route-list-length field, in effect shrink  
> the route-list by 1 while growing the via-list by 1 without  
> touching the actual Via-List and Route-list that follows.
>
> By the way, I do believe the header should indicate the size of the  
> IDs.
>
> Thanks
>
> --Michael
>
> Cullen Jennings wrote:
>>
>> The various authors of ASP and RELOAD have managed to get these  
>> two proposal merged together into one and we are pretty happy with  
>> the result.
>>
>> You can find it at
>> http://www.ietf.org/internet-drafts/draft-bryan-p2psip-reload-02.txt
>>
>>
>> Begin forwarded message:
>>
>>> From: IETF I-D Submission Tool <idsubmission@ietf.org>
>>> Date: November 18, 2007 8:57:03 PM PST
>>> To: fluffy@cisco.com
>>> Cc: lowekamp@sipeerior.com, ekr@networkresonance.com,  
>>> jdrosen@cisco.com
>>> Subject: New Version Notification for draft-bryan-p2psip-reload-02
>>>
>>>
>>> A new version of I-D, draft-bryan-p2psip-reload-02.txt has been  
>>> successfuly submitted by Cullen Jennings and posted to the IETF  
>>> repository.
>>>
>>> Filename:     draft-bryan-p2psip-reload
>>> Revision:     02
>>> Title:         REsource LOcation And Discovery (RELOAD)
>>> Creation_date:     2007-11-18
>>> WG ID:         Independent Submission
>>> Number_of_pages: 96
>>>
>>> Abstract:
>>> This document defines REsource LOcation And Discovery (RELOAD), a
>>> peer-to-peer (P2P) binary signaling protocol for usage on the
>>> Internet.  A P2P signaling protocol provides its clients with an
>>> abstract hash table service between a set of cooperating peers that
>>> form the overlay network.  RELOAD is designed to support a P2P
>>> Session Initiation Protocol (P2PSIP) network, but it can be utilized
>>> by other applications with similar requirements by defining new
>>> usages that specify the data types that must be stored for a
>>> particular application, such as location for SIP.  RELOAD defines a
>>> security model based on a certificate enrollment service that
>>> provides unique identities.  NAT traversal is a fundamental service
>>> of the protocol.
>>>
>>> This draft represents a concrete proposal for the P2PSIP Peer
>>> Protocol.  The protocol described here builds on the lessons and
>>> experiences from designing and implementing the dSIP, ASP, and  
>>> RELOAD
>>> protocols and is a merge of features from RELOAD-01 and ASP.
>>>
>>>
>>>
>>> The IETF Secretariat.
>>
>> _______________________________________________
>> P2PSIP mailing list
>> P2PSIP@ietf.org
>> https://www1.ietf.org/mailman/listinfo/p2psip
>>
>>


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



From p2psip-bounces@ietf.org Sat Jan 12 08:19:30 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDgGZ-0000f1-5P; Sat, 12 Jan 2008 08:19:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDgGY-0000eu-FO
	for p2psip@ietf.org; Sat, 12 Jan 2008 08:19:14 -0500
Received: from n2.nomadiclab.com ([2001:14b8:400:101::2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JDgGX-0000cm-RI
	for p2psip@ietf.org; Sat, 12 Jan 2008 08:19:14 -0500
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 6F8841EF105;
	Sat, 12 Jan 2008 15:19:12 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 1BAAB1EF104;
	Sat, 12 Jan 2008 15:19:12 +0200 (EET)
In-Reply-To: <478790EE.4050301@uni-tuebingen.de>
References: <476BA8D9.4010203@ericsson.com>	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>	<476E2B7C.9070601@ericsson.com>	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<086801c8530e$611d8030$6601a8c0@china.huawei.com>
	<4785566F.7000700@uni-tuebingen.de>
	<833EB4F9-41EE-41E5-A951-DE2AF0FE9FF8@nomadiclab.com>
	<478790EE.4050301@uni-tuebingen.de>
Mime-Version: 1.0 (Apple Message framework v753)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <9D8B3C2C-EB54-4C8F-986A-065E18C1405B@nomadiclab.com>
Content-Transfer-Encoding: 7bit
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: Re: [P2PSIP] New draft: HIP BONE
Date: Sat, 12 Jan 2008 15:19:10 +0200
To: Ali Fessi <ali.fessi@uni-tuebingen.de>
X-Mailer: Apple Mail (2.753)
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

>> The second, bigger problem is that if both the initiator and the  
>> responder are behind NATs, the you just cannot send the I1 message  
>> directly to the HIP responder.
>> The latter is the reason why we chose to use a Berkeley i3 -like  
>> system in both Hi3 and in HIP BONE, i.e., to forward HIP messages  
>> through the overlay instead of using it in a typical DHT put/get  
>> manner.
>
> i3, Secure-i3 and Hi3 have however an assumption that does not hold  
> here. The overlay consitutes of i3 servers which are considered to  
> be trustworthy, have public addresses and can converge as rendez- 
> vous points for "clients" behind NATs. This assumption does not  
> hold for P2PSIP, since there is not such an overlay.

I understand what you say, but I don't understand the reasons behind,  
i.e., why exactly the assumption does not hold.  Nor do I understand  
how you can make such a system to work in the first place.  In  
particular, I don't understand how you can bootstrap an overlay if  
all nodes are behind NATs.

> So, when the I1 message is forwarded on the overlay, the NAT  
> traversal problem needs to solved for each link on the path between  
> the Initiator and the Responder. And this is not solved by HIP,  
> unless you run HIP for each link on the overlay (including the HIP  
> handshake and ICE for NAT traversal) which would be proably too  
> much overhead.

Indeed we do assume that you typically have an open HIP association  
with each of the nodes in your peer table; see the second paragraph  
in Section 3.2.   Note that once you have an HIP association open, in  
principle it can be open an arbitrary long time.  Hence, the overhead  
is not that big unless you have to keep NAT mappings open or  
whatever, which you would need to do anyway for reachability  
purposes.  Secondly, having an open HIP association allows the nodes  
to inform each others about mobility or multi-homing events and  
maintain connectivity.

> Moreover, the peer protocol needs to cope with NAT traversal for  
> other type of messages for the overlay maintenance, e.g. joins and  
> leaves, anyway. and again this is not solved by HIP, unless you do  
> HIP hop-by-hop.

Well, that depends on how you implement joins and leaves.  Our  
assumption was that you would establish an HIP association as a part  
of a join procedure.  For example, first do an I1-R1 exchange for DoS  
protection, and then piggyback the join messages and ICE candidate  
exchange starting from the I2-R2 exchange (and using UPDATEs if more  
messages are needed.)

> My conslusions from these facts here (please feel free to heavily  
> disagree and let me know if i am wrong) would be that:
>
> - *HIP actually does not solve the NAT traversal problem for  
> P2PSIP*, as it has been assumed.

I would say that it solves it in a particular way, which is not much  
different from using plain ICE.  The message formats are somewhat  
different, and the STUN/TURN servers are unified with the HIP BONE  
routing system (as they would be HIP rendezvous servers in the case  
of HIP).

> - The peer protocol needs to cope with the NAT traversal by itself.

Well, IMHO the peer protocol does not need to cope with NAT, if you  
always establish a HIP association first and let HIP to do it.

Of course, one crucial question is what are the tradeoffs there.  In  
particular, would the added support for security, multi-homing,  
mobility, and the architectural features to pay off for the four  
message exchange and the public key signatures.  OTOH, if you would  
be relying on public key crypto for security anyway, then the  
overhead is minimal, and IMHO the question boils down merely into  
architectural factors.

--Pekka Nikander


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



From p2psip-bounces@ietf.org Sat Jan 12 08:29:34 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDgQY-0001JV-3n; Sat, 12 Jan 2008 08:29:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDgQW-0001JQ-HL
	for p2psip@ietf.org; Sat, 12 Jan 2008 08:29:32 -0500
Received: from n2.nomadiclab.com ([2001:14b8:400:101::2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JDgQW-0000lE-0h
	for p2psip@ietf.org; Sat, 12 Jan 2008 08:29:32 -0500
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 5E2A91EF105;
	Sat, 12 Jan 2008 15:29:31 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 0D7D41EF104;
	Sat, 12 Jan 2008 15:29:31 +0200 (EET)
In-Reply-To: <0cdd01c8545d$2107a520$6601a8c0@china.huawei.com>
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<0bf801c853db$fe101830$6601a8c0@china.huawei.com>
	<B5C4134C-1856-4150-BC88-1D43A45C66F3@nomadiclab.com>
	<0cdd01c8545d$2107a520$6601a8c0@china.huawei.com>
Mime-Version: 1.0 (Apple Message framework v753)
X-Priority: 3
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <FE39DC80-A1C5-4BD3-8BAC-89BD508B2147@nomadiclab.com>
Content-Transfer-Encoding: 7bit
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: Re: [P2PSIP] New draft: HIP BONE
Date: Sat, 12 Jan 2008 15:29:29 +0200
To: Spencer Dawkins <spencer@mcsr-labs.org>
X-Mailer: Apple Mail (2.753)
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

> OK, I'm not the architecture monitor, but I disagree with some of  
> this, and agree with the rest...

:-)

>> In the case of HIP BONE, the peer (or routing) protocol is both a   
>> user of HIP and an enable of HIP.  But so are the routing  
>> protocols  for IP, and in certain sense DNS for IP, too.
>
> OSPF does use IP *encapsulation*, *fragmentation/reassembly*, etc.  
> but OSPF conversations happen with direct adjacencies. Using IP  
> *encapsulation* is very different from using *IP*.

Exactly.  And that is very much how HIP would be used in HIP BONE for  
creating connectivity between peer nodes that are adjacent according  
to their finger (or whatever routing) tables.  In that case the peer  
protocol is a user of HIP for encapsulation, security, mobility,  
multi-homing, and NAT traversal, but not for directly forwarding  
signalling messages from one overlay node to another.

In the case of routing initial HIP signalling messages for creating  
direct peer-to-peer connections, HIP is then a user of the peer  
protocol, the peer protocol being an enabler for HIP.

> IS-IS runs directly over link-layer protocols ("same level as CLNS").

I know.  Did you intentionally leave out e.g. BGP which does use both  
IP and also TCP?  :-)

> DNS looks like a IP enabler to applications that are trying to use  
> DNS names, but it's not - IP ran for years before there was a  
> naming system at all (see HOSTS.TXT).
>
>> Such a circular dependency in itself is not bad, as long as it is  
>> designed (i.e. not accidental) and we have a clear understanding  
>> how  to manage the bootstrap problem.
>
> I would agree with both points here - design and understanding are  
> what's needed, and being able to bootstrap would be the first test  
> that we have a design and understanding.

I couldn't agree more.  Personally, I don't see any big problems in  
bootstrapping.  The only bigger problems I see are related to  
supporting multiple name spaces aka multiple overlays and allowing  
nodes to participate to a number of them same time.  There I see at  
least three or four approaches, and I have big difficulties in  
understanding the tradeoffs, as I don't understand the requirements  
or scenarios well enough.

--Pekka


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



From p2psip-bounces@ietf.org Sat Jan 12 08:51:06 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDglN-0002u8-VQ; Sat, 12 Jan 2008 08:51:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDglM-0002oi-5R
	for p2psip@ietf.org; Sat, 12 Jan 2008 08:51:04 -0500
Received: from n2.nomadiclab.com ([2001:14b8:400:101::2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JDglL-00010z-Ls
	for p2psip@ietf.org; Sat, 12 Jan 2008 08:51:04 -0500
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 089791EF105;
	Sat, 12 Jan 2008 15:51:03 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id A68D51EF104;
	Sat, 12 Jan 2008 15:51:02 +0200 (EET)
In-Reply-To: <77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
Mime-Version: 1.0 (Apple Message framework v753)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F2A2E7E1-AA6E-47B3-9420-EA5A4BEEA428@nomadiclab.com>
Content-Transfer-Encoding: 7bit
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: Re: [P2PSIP] New draft: HIP BONE
Date: Sat, 12 Jan 2008 15:51:01 +0200
To: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
X-Mailer: Apple Mail (2.753)
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Tom,

> Pekka, thanks for your responses (some more discussion inline below)

For some reason, I almost enjoy these exchanges.  :-)  Maybe I'm  
finally getting over some of my past painful experiences with the  
I*.  :-)

>>> There have been proposals to use DHTs to provide this service,  
>>> but they do not presently accommodate the possibility of multiple  
>>> DHTs, which is pretty much a requirement to handle, from my  
>>> perspective.
>>
>> That issue Gonzalo and I have discussed extensively.  On my part I  
>> still don't quite understand the requirement (as is probably  
>> visible from the previous exchange of message between you Tom and  
>> me).
>
> For a given system provided by a provider (example.com), only one  
> overlay is necessary.  But what happens when the user concurrently  
> gets a second provider (example2.com)?  The problem is that the  
> layer trying to resolve the flat identifier doesn't know where to  
> try to resolve it, unless there is metadata about the system that  
> holds bindings for that identifier.  What happens when the user  
> wants to enforce policy on what applications use which overlay, at  
> any given time, to resolve the identifiers?

I think there are a few potential solution categories:

a) add such metadata as an overall system configuration data (IPsec  
SPD is an example of this)

b) allow communicating such metadata through the API

c) multicast the initial request to all overlays.

Of course, each of these has their benefits and drawbacks.

> The Balakrishan et. al paper in Sigcomm 2004 (Section 4.1)  
> elaborated on why multiple name service providers will proliferate  
> in an architecture based on flat names: http://nms.lcs.mit.edu/ 
> papers/layerednames-sigcomm04.pdf

That's on my my reading list.  Don't have time to read it in detail  
right now.

> I do not think it is a show stopper issue, but one that HIP hasn't  
> addressed yet.

We seem to agree.

<The rest of the message was discussed in a separate subthread with  
Spencer, I think.>

--Pekka

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



From p2psip-bounces@ietf.org Mon Jan 14 10:13:31 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JER06-000787-6X; Mon, 14 Jan 2008 10:13:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JER05-0006vD-0V
	for p2psip@ietf.org; Mon, 14 Jan 2008 10:13:21 -0500
Received: from exprod6og105.obsmtp.com ([64.18.1.189])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JER04-0005av-46
	for p2psip@ietf.org; Mon, 14 Jan 2008 10:13:20 -0500
Received: from source ([192.150.20.142]) by exprod6ob105.postini.com
	([64.18.5.12]) with SMTP; Mon, 14 Jan 2008 07:12:57 PST
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
	m0EFCoGb012397; Mon, 14 Jan 2008 07:12:55 -0800 (PST)
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
	m0EFCnRC025493; Mon, 14 Jan 2008 07:12:49 -0800 (PST)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 14 Jan 2008 07:12:49 -0800
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [P2PSIP] HIP: optional, mandatory?
Date: Mon, 14 Jan 2008 07:12:22 -0800
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D223AE4F4@namail5.corp.adobe.com>
In-Reply-To: <e1e2f6d96894.47875b39@us.army.mil>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] HIP: optional, mandatory?
Thread-Index: AchUdAmi1WoonMFpSQmdMmPOKtYEwgCS03Ww
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com><20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com><77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com><7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com><77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com><10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu><4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com><465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com><284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>
	<e1e2f6d96894.47875b39@us.army.mil>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Roy, Radhika R Dr CTR USA USAMC" <radhika.r.roy@us.army.mil>,
	"Cullen Jennings" <fluffy@cisco.com>
X-OriginalArrivalTime: 14 Jan 2008 15:12:49.0429 (UTC)
	FILETIME=[ECF52450:01C856BF]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7e439b86d3292ef5adf93b694a43a576
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Radhika,

> what is the problem to proceed per P2PSIP charter for accomplishing
the mandated > work items (may be in a limited way) soon which may be
ready for deployment?

I presume you share the view that "ready for deployment" means open
available running code and performance reports from actual test
deployments and you don't mean just eloquently written papers?

Henry

-----Original Message-----
From: Roy, Radhika R Dr CTR USA USAMC [mailto:radhika.r.roy@us.army.mil]

Sent: Friday, January 11, 2008 11:04 AM
To: Cullen Jennings
Cc: P2PSIP Mailing List
Subject: Re: [P2PSIP] HIP: optional, mandatory?

If it is so as Cullen has explained, what is the problem to proceed per
P2PSIP charter for accomplishing the mandated work items (may be in a
limited way) soon which may be ready for deployment?

Cheers!
Radhika

----- Original Message -----
From: Cullen Jennings=20
Date: Friday, January 11, 2008 11:40
Subject: Re: [P2PSIP] HIP: optional, mandatory?
To: David Barrett=20
Cc: P2PSIP Mailing List=20

>=20
> On Jan 10, 2008, at 8:23 PM, David Barrett wrote:
>=20
> > We don't need more options for what we CAN do, we need decisions=20
> on=20
> > what we WILL do.
>=20
> Yep - agree. And what I want to do is standardize something that=20
> lets me build deployable interoperable solutions soon. Success for=20
> me=20
> involves deployments.
>=20
> > If we're not considering making HIP mandatory, then let's stop=20
>=20
> > talking about it and start focusing on those things that *will*=20
> be=20
> > mandatory.
>=20
> The P2PSIP WG has made very few decisions since it was formed.=20
> IMHO,=20
> what we need to do real soon now is pick something as a starting=20
> point for a WG document then go and make the decision to change it=20
> to=20
> be what we want. Until we do that, my belief is that the WG will=20
> make fairly marginal progress.
>=20
> >
> > That said, I think this HIP discussion is the best thing to=20
> happen=20
> > in P2PSIP for years. It seems like the most practical and=20
> powerful=20
> > solution, the best layering of functionality, and the most=20
> feasible=20
> > design that I've yet to hear. Moving the hard P2P code into a=20
> > reusable HIP layer makes a lot of sense,
>=20
> this is way outside anything HIP was charted to do or is working on
>=20
> > not only for P2PSIP, but for the internet as a whole. It seems=20
> > like a wagon that we should voluntarily and enthusiastically=20
> hitch=20
> > ourselves to, rather than try to reproduce or compete with it,=20
> or=20
> > toss it in the overflowing bucket of optional extensions.
> >
> > It seems sensible to have a base HIP layer that either comes pre-
>=20
> > installed with the OS or redistributed by the application=20
> (similar=20
> > to WinPCap). (I could even see making a sort of "HIP-lite" self-
>=20
> > contained library that can be linked straight into the=20
> application=20
> > for when installing a Then P2PSIP can be one of many HIP-using=20
>=20
> > applications that are vastly simplified by being insulated from=20
> the=20
> > gnarly realities of NAT and firewall penetration, mobility, etc.
> >
> > This makes a lot more sense than continually reproducing this=20
> > really hard functionality in every application.
>=20
> Most of the concrete proposals layer the p2p code such that the=20
> library that provided the p2p part could be used by other=20
> applications. This is a good design but not something you need HIP=20
> to=20
> accomplish.
>=20
> >
> > -david
>=20
> Cullen=20
>=20
> >
> > On Jan 11, 2008, at 7:33 AM, Cullen Jennings wrote:
> >
> >>
> >> I was assuming most folks were talking about (3) given that=20
> much=20
> >> of HIP is still being designed and it will be awhile to get=20
> things=20
> >> build and deployed. I know lots of parts of HIP have been done=20
> but=20
> >> when we are talking about mobility, nat traversal, no DNS, and=20
> >> easy end user installations, there is still work. Anyway, I am=20
> in=20
> >> the 3 category.
> >>
> >> Cullen=20
> >> On Jan 10, 2008, at 2:14 PM, Henning Schulzrinne wrote:
> >>
> >>> One of the issues I don't understand about this discussion is=20
> >>> whether all instances of P2PSIP would be expected to be=20
> running=20
> >>> HIP or just some. There seem to be at least three options:
> >>>
> >>> (1) Mandatory to implement and run
> >>>
> >>> The only non-recursive-dependency model seems to be that peer=20
> >>> nodes would store the HIT-IP bindings in their routing tables.=20
>=20
> >>> (This largely negates any mobility advantages, but that's a=20
> >>> separate discussion.)
> >>>
> >>> (2) Mandatory to implement, but there can be instances of an=20
> >>> overlay (or maybe even part of an overlay) that don't use HIP
> >>>
> >>> This would require providing ICE functionality at both the HIP=20
>=20
> >>> level and directly to the P2P protocol.
> >>>
> >>> (3) Optional to implement and run
> >>>
> >>> This only works if you can have mixed HIP-non-HIP nodes. Also=20
> >>> requires implementations of ICE in both layers and the ability=20
> to=20
> >>> mix-and-match HIP and non-HIP nodes within an overlay, unless=20
> >>> each overlay has a "HIP flag".
> >>>
> >>> I admit that I'm rather worried about the complexity of this=20
> >>> whole edifice. I think it would be helpful if the proponents=20
> of a=20
> >>> HIP-based approach stated clearly which of these they have in=20
> mind.>>>
> >>> Henning

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

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



From p2psip-bounces@ietf.org Mon Jan 14 11:12:43 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JERvS-0004Tx-RO; Mon, 14 Jan 2008 11:12:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JERvR-0004Tq-Qf
	for p2psip@ietf.org; Mon, 14 Jan 2008 11:12:37 -0500
Received: from mxoutps1.us.army.mil ([143.69.250.38])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JERvM-0006wJ-Ok
	for p2psip@ietf.org; Mon, 14 Jan 2008 11:12:37 -0500
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=oFGYte7Z5sGdv4r3a1wJ68VgRx9Fspo+8UQBsIfmglt8EVvlMjQ7iVAC
	k0wbpb1MUfAHBTyAGmqqOthpK1dwTQ==;
From: "Roy, Radhika R Dr CTR USA USAMC" <radhika.r.roy@us.army.mil>
X-AKO: 90713660:10.224.36.65:14 Jan 2008 16:12:31 +0000:$Webmail:None
X-IronPort-AV: E=Sophos;i="4.24,283,1196640000"; d="scan'208";a="90713660"
Received: from mail5.int.ps1.us.army.mil (HELO us.army.mil) ([10.224.36.65])
	by mxoutps1.us.army.mil with ESMTP; 14 Jan 2008 16:12:31 +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); Mon, 14 Jan
	2008 11:12:31 -0500
To: Henry Sinnreich <hsinnrei@adobe.com>
Message-ID: <da839538289f.478b439f@us.army.mil>
Date: Mon, 14 Jan 2008 11:12:31 -0500
X-Mailer: Sun Java(tm) System Messenger Express 6.2-9.04 (built Jun 11
 2007)
MIME-Version: 1.0
Content-Language: en
Subject: Re: RE: [P2PSIP] HIP: optional, mandatory?
X-Accept-Language: en
Priority: normal
In-Reply-To: <24CCCC428EFEA2469BF046DB3C7A8D223AE4F4@namail5.corp.adobe.com>
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
	<465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com>
	<284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>
	<e1e2f6d96894.47875b39@us.army.mil>
	<24CCCC428EFEA2469BF046DB3C7A8D223AE4F4@namail5.corp.adobe.com>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.0 (----)
X-Scan-Signature: a8041eca2a724d631b098c15e9048ce9
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Henry:

Right, per P2PSIP Charter objectives.

Best regards,
Radhika

----- Original Message -----
From: Henry Sinnreich 
Date: Monday, January 14, 2008 10:13
Subject: RE: [P2PSIP] HIP: optional, mandatory?
To: "Roy, Radhika R Dr CTR USA USAMC" , Cullen Jennings 
Cc: P2PSIP Mailing List 

> Radhika,
> 
> > what is the problem to proceed per P2PSIP charter for accomplishing
> the mandated > work items (may be in a limited way) soon which may be
> ready for deployment?
> 
> I presume you share the view that "ready for deployment" means open
> available running code and performance reports from actual test
> deployments and you don't mean just eloquently written papers?
> 
> Henry
> 
> -----Original Message-----
> From: Roy, Radhika R Dr CTR USA USAMC 
> [mailto:radhika.r.roy@us.army.mil]
> Sent: Friday, January 11, 2008 11:04 AM
> To: Cullen Jennings
> Cc: P2PSIP Mailing List
> Subject: Re: [P2PSIP] HIP: optional, mandatory?
> 
> If it is so as Cullen has explained, what is the problem to 
> proceed per
> P2PSIP charter for accomplishing the mandated work items (may be 
> in a
> limited way) soon which may be ready for deployment?
> 
> Cheers!
> Radhika
> 
> ----- Original Message -----
> From: Cullen Jennings 
> Date: Friday, January 11, 2008 11:40
> Subject: Re: [P2PSIP] HIP: optional, mandatory?
> To: David Barrett 
> Cc: P2PSIP Mailing List 
> 
> > 
> > On Jan 10, 2008, at 8:23 PM, David Barrett wrote:
> > 
> > > We don't need more options for what we CAN do, we need 
> decisions 
> > on 
> > > what we WILL do.
> > 
> > Yep - agree. And what I want to do is standardize something that 
> > lets me build deployable interoperable solutions soon. Success 
> for 
> > me 
> > involves deployments.
> > 
> > > If we're not considering making HIP mandatory, then let's stop 
> > 
> > > talking about it and start focusing on those things that 
> *will* 
> > be 
> > > mandatory.
> > 
> > The P2PSIP WG has made very few decisions since it was formed. 
> > IMHO, 
> > what we need to do real soon now is pick something as a starting 
> > point for a WG document then go and make the decision to change 
> it 
> > to 
> > be what we want. Until we do that, my belief is that the WG will 
> > make fairly marginal progress.
> > 
> > >
> > > That said, I think this HIP discussion is the best thing to 
> > happen 
> > > in P2PSIP for years. It seems like the most practical and 
> > powerful 
> > > solution, the best layering of functionality, and the most 
> > feasible 
> > > design that I've yet to hear. Moving the hard P2P code into a 
> > > reusable HIP layer makes a lot of sense,
> > 
> > this is way outside anything HIP was charted to do or is working on
> > 
> > > not only for P2PSIP, but for the internet as a whole. It seems 
> > > like a wagon that we should voluntarily and enthusiastically 
> > hitch 
> > > ourselves to, rather than try to reproduce or compete with it, 
> > or 
> > > toss it in the overflowing bucket of optional extensions.
> > >
> > > It seems sensible to have a base HIP layer that either comes 
> pre-
> > 
> > > installed with the OS or redistributed by the application 
> > (similar 
> > > to WinPCap). (I could even see making a sort of "HIP-lite" 
> self-
> > 
> > > contained library that can be linked straight into the 
> > application 
> > > for when installing a Then P2PSIP can be one of many HIP-using 
> > 
> > > applications that are vastly simplified by being insulated 
> from 
> > the 
> > > gnarly realities of NAT and firewall penetration, mobility, etc.
> > >
> > > This makes a lot more sense than continually reproducing this 
> > > really hard functionality in every application.
> > 
> > Most of the concrete proposals layer the p2p code such that the 
> > library that provided the p2p part could be used by other 
> > applications. This is a good design but not something you need 
> HIP 
> > to 
> > accomplish.
> > 
> > >
> > > -david
> > 
> > Cullen 
> > 
> > >
> > > On Jan 11, 2008, at 7:33 AM, Cullen Jennings wrote:
> > >
> > >>
> > >> I was assuming most folks were talking about (3) given that 
> > much 
> > >> of HIP is still being designed and it will be awhile to get 
> > things 
> > >> build and deployed. I know lots of parts of HIP have been 
> done 
> > but 
> > >> when we are talking about mobility, nat traversal, no DNS, 
> and 
> > >> easy end user installations, there is still work. Anyway, I 
> am 
> > in 
> > >> the 3 category.
> > >>
> > >> Cullen 
> > >> On Jan 10, 2008, at 2:14 PM, Henning Schulzrinne wrote:
> > >>
> > >>> One of the issues I don't understand about this discussion 
> is 
> > >>> whether all instances of P2PSIP would be expected to be 
> > running 
> > >>> HIP or just some. There seem to be at least three options:
> > >>>
> > >>> (1) Mandatory to implement and run
> > >>>
> > >>> The only non-recursive-dependency model seems to be that 
> peer 
> > >>> nodes would store the HIT-IP bindings in their routing 
> tables. 
> > 
> > >>> (This largely negates any mobility advantages, but that's a 
> > >>> separate discussion.)
> > >>>
> > >>> (2) Mandatory to implement, but there can be instances of an 
> > >>> overlay (or maybe even part of an overlay) that don't use HIP
> > >>>
> > >>> This would require providing ICE functionality at both the 
> HIP 
> > 
> > >>> level and directly to the P2P protocol.
> > >>>
> > >>> (3) Optional to implement and run
> > >>>
> > >>> This only works if you can have mixed HIP-non-HIP nodes. 
> Also 
> > >>> requires implementations of ICE in both layers and the 
> ability 
> > to 
> > >>> mix-and-match HIP and non-HIP nodes within an overlay, 
> unless 
> > >>> each overlay has a "HIP flag".
> > >>>
> > >>> I admit that I'm rather worried about the complexity of this 
> > >>> whole edifice. I think it would be helpful if the proponents 
> > of a 
> > >>> HIP-based approach stated clearly which of these they have 
> in 
> > mind.>>>
> > >>> Henning
> 
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.ietf.org/mailman/listinfo/p2psip
> 

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



From p2psip-bounces@ietf.org Mon Jan 14 11:20:17 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JES2q-0006If-EL; Mon, 14 Jan 2008 11:20:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JES2p-0006I5-8W
	for p2psip@ietf.org; Mon, 14 Jan 2008 11:20:15 -0500
Received: from exprod6og103.obsmtp.com ([64.18.1.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JES2o-00074y-BO
	for p2psip@ietf.org; Mon, 14 Jan 2008 11:20:15 -0500
Received: from source ([192.150.11.134]) by exprod6ob103.postini.com
	([64.18.5.12]) with SMTP; Mon, 14 Jan 2008 08:20:12 PST
Received: from inner-relay-3.eur.adobe.com (inner-relay-3.adobe.com
	[192.150.20.198] (may be forged))
	by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	m0EGHlin027101; Mon, 14 Jan 2008 08:17:47 -0800 (PST)
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
	m0EGK5FX001855; Mon, 14 Jan 2008 08:20:10 -0800 (PST)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by
	apacmail.pac.adobe.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 15 Jan 2008 01:20:08 +0900
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: RE: [P2PSIP] HIP: optional, mandatory?
Date: Mon, 14 Jan 2008 08:20:06 -0800
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D223AE4F8@namail5.corp.adobe.com>
In-Reply-To: <da839538289f.478b439f@us.army.mil>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RE: [P2PSIP] HIP: optional, mandatory?
Thread-Index: AchWyET0IETYm45ATleiujHg8MlRagAACjAg
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
	<465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com>
	<284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>
	<e1e2f6d96894.47875b39@us.army.mil>
	<24CCCC428EFEA2469BF046DB3C7A8D223AE4F4@namail5.corp.adobe.com>
	<da839538289f.478b439f@us.army.mil>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Roy, Radhika R Dr CTR USA USAMC" <radhika.r.roy@us.army.mil>
X-OriginalArrivalTime: 14 Jan 2008 16:20:08.0409 (UTC)
	FILETIME=[54609490:01C856C9]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: d008c19e97860b8641c1851f84665a75
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Thanks Roy!

This is actually orthogonal to the HIP discussion - it was my omission
to specify.

Henry

-----Original Message-----
From: Roy, Radhika R Dr CTR USA USAMC [mailto:radhika.r.roy@us.army.mil]

Sent: Monday, January 14, 2008 10:13 AM
To: Henry Sinnreich
Cc: Cullen Jennings; P2PSIP Mailing List
Subject: Re: RE: [P2PSIP] HIP: optional, mandatory?

Henry:

Right, per P2PSIP Charter objectives.

Best regards,
Radhika

----- Original Message -----
From: Henry Sinnreich=20
Date: Monday, January 14, 2008 10:13
Subject: RE: [P2PSIP] HIP: optional, mandatory?
To: "Roy, Radhika R Dr CTR USA USAMC" , Cullen Jennings=20
Cc: P2PSIP Mailing List=20

> Radhika,
>=20
> > what is the problem to proceed per P2PSIP charter for accomplishing
> the mandated > work items (may be in a limited way) soon which may be
> ready for deployment?
>=20
> I presume you share the view that "ready for deployment" means open
> available running code and performance reports from actual test
> deployments and you don't mean just eloquently written papers?
>=20
> Henry
>=20
> -----Original Message-----
> From: Roy, Radhika R Dr CTR USA USAMC=20
> [mailto:radhika.r.roy@us.army.mil]
> Sent: Friday, January 11, 2008 11:04 AM
> To: Cullen Jennings
> Cc: P2PSIP Mailing List
> Subject: Re: [P2PSIP] HIP: optional, mandatory?
>=20
> If it is so as Cullen has explained, what is the problem to=20
> proceed per
> P2PSIP charter for accomplishing the mandated work items (may be=20
> in a
> limited way) soon which may be ready for deployment?
>=20
> Cheers!
> Radhika
>=20
> ----- Original Message -----
> From: Cullen Jennings=20
> Date: Friday, January 11, 2008 11:40
> Subject: Re: [P2PSIP] HIP: optional, mandatory?
> To: David Barrett=20
> Cc: P2PSIP Mailing List=20
>=20
> >=20
> > On Jan 10, 2008, at 8:23 PM, David Barrett wrote:
> >=20
> > > We don't need more options for what we CAN do, we need=20
> decisions=20
> > on=20
> > > what we WILL do.
> >=20
> > Yep - agree. And what I want to do is standardize something that=20
> > lets me build deployable interoperable solutions soon. Success=20
> for=20
> > me=20
> > involves deployments.
> >=20
> > > If we're not considering making HIP mandatory, then let's stop=20
> >=20
> > > talking about it and start focusing on those things that=20
> *will*=20
> > be=20
> > > mandatory.
> >=20
> > The P2PSIP WG has made very few decisions since it was formed.=20
> > IMHO,=20
> > what we need to do real soon now is pick something as a starting=20
> > point for a WG document then go and make the decision to change=20
> it=20
> > to=20
> > be what we want. Until we do that, my belief is that the WG will=20
> > make fairly marginal progress.
> >=20
> > >
> > > That said, I think this HIP discussion is the best thing to=20
> > happen=20
> > > in P2PSIP for years. It seems like the most practical and=20
> > powerful=20
> > > solution, the best layering of functionality, and the most=20
> > feasible=20
> > > design that I've yet to hear. Moving the hard P2P code into a=20
> > > reusable HIP layer makes a lot of sense,
> >=20
> > this is way outside anything HIP was charted to do or is working on
> >=20
> > > not only for P2PSIP, but for the internet as a whole. It seems=20
> > > like a wagon that we should voluntarily and enthusiastically=20
> > hitch=20
> > > ourselves to, rather than try to reproduce or compete with it,=20
> > or=20
> > > toss it in the overflowing bucket of optional extensions.
> > >
> > > It seems sensible to have a base HIP layer that either comes=20
> pre-
> >=20
> > > installed with the OS or redistributed by the application=20
> > (similar=20
> > > to WinPCap). (I could even see making a sort of "HIP-lite"=20
> self-
> >=20
> > > contained library that can be linked straight into the=20
> > application=20
> > > for when installing a Then P2PSIP can be one of many HIP-using=20
> >=20
> > > applications that are vastly simplified by being insulated=20
> from=20
> > the=20
> > > gnarly realities of NAT and firewall penetration, mobility, etc.
> > >
> > > This makes a lot more sense than continually reproducing this=20
> > > really hard functionality in every application.
> >=20
> > Most of the concrete proposals layer the p2p code such that the=20
> > library that provided the p2p part could be used by other=20
> > applications. This is a good design but not something you need=20
> HIP=20
> > to=20
> > accomplish.
> >=20
> > >
> > > -david
> >=20
> > Cullen=20
> >=20
> > >
> > > On Jan 11, 2008, at 7:33 AM, Cullen Jennings wrote:
> > >
> > >>
> > >> I was assuming most folks were talking about (3) given that=20
> > much=20
> > >> of HIP is still being designed and it will be awhile to get=20
> > things=20
> > >> build and deployed. I know lots of parts of HIP have been=20
> done=20
> > but=20
> > >> when we are talking about mobility, nat traversal, no DNS,=20
> and=20
> > >> easy end user installations, there is still work. Anyway, I=20
> am=20
> > in=20
> > >> the 3 category.
> > >>
> > >> Cullen=20
> > >> On Jan 10, 2008, at 2:14 PM, Henning Schulzrinne wrote:
> > >>
> > >>> One of the issues I don't understand about this discussion=20
> is=20
> > >>> whether all instances of P2PSIP would be expected to be=20
> > running=20
> > >>> HIP or just some. There seem to be at least three options:
> > >>>
> > >>> (1) Mandatory to implement and run
> > >>>
> > >>> The only non-recursive-dependency model seems to be that=20
> peer=20
> > >>> nodes would store the HIT-IP bindings in their routing=20
> tables.=20
> >=20
> > >>> (This largely negates any mobility advantages, but that's a=20
> > >>> separate discussion.)
> > >>>
> > >>> (2) Mandatory to implement, but there can be instances of an=20
> > >>> overlay (or maybe even part of an overlay) that don't use HIP
> > >>>
> > >>> This would require providing ICE functionality at both the=20
> HIP=20
> >=20
> > >>> level and directly to the P2P protocol.
> > >>>
> > >>> (3) Optional to implement and run
> > >>>
> > >>> This only works if you can have mixed HIP-non-HIP nodes.=20
> Also=20
> > >>> requires implementations of ICE in both layers and the=20
> ability=20
> > to=20
> > >>> mix-and-match HIP and non-HIP nodes within an overlay,=20
> unless=20
> > >>> each overlay has a "HIP flag".
> > >>>
> > >>> I admit that I'm rather worried about the complexity of this=20
> > >>> whole edifice. I think it would be helpful if the proponents=20
> > of a=20
> > >>> HIP-based approach stated clearly which of these they have=20
> in=20
> > mind.>>>
> > >>> Henning
>=20
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.ietf.org/mailman/listinfo/p2psip
>=20

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



From p2psip-bounces@ietf.org Mon Jan 14 14:26:33 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JEUx2-0006u3-3V; Mon, 14 Jan 2008 14:26:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JEUx0-0006tj-Rb
	for p2psip@ietf.org; Mon, 14 Jan 2008 14:26:26 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JEUx0-0003HD-8w
	for p2psip@ietf.org; Mon, 14 Jan 2008 14:26:26 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	AFB1620487; Mon, 14 Jan 2008 20:26:25 +0100 (CET)
X-AuditID: c1b4fb3e-aee9fbb00000459d-cc-478bb761ec21
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	84AE820196; Mon, 14 Jan 2008 20:26:25 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 14 Jan 2008 20:26:25 +0100
Received: from [131.160.126.6] ([131.160.126.6]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 14 Jan 2008 20:26:24 +0100
Message-ID: <478BB75F.5080409@ericsson.com>
Date: Mon, 14 Jan 2008 21:26:23 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [P2PSIP] HIP: optional, mandatory?
References: <476BA8D9.4010203@ericsson.com>
	<476E2B7C.9070601@ericsson.com>	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>	<4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>	<0c3a01c85402$28d821e0$6601a8c0@china.huawei.com>	<CBAEA83C-A2BB-47E7-AE49-A3E901DDB50C@cs.columbia.edu>	<4d4304a00801110710x1b7f04b4lcbcbb9eb8702ba1e@mail.gmail.com>	<0d2101c85468$034c4080$6601a8c0@china.huawei.com>
	<1B79D7E7-A67B-42D9-9F00-66E69080C358@cs.columbia.edu>
In-Reply-To: <1B79D7E7-A67B-42D9-9F00-66E69080C358@cs.columbia.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Jan 2008 19:26:24.0955 (UTC)
	FILETIME=[5A1E28B0:01C856E3]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hi Henning,

> At least we're now clear that the HIP advocates want to essentially 
> force systems to implement it. This will hopefully focus the discussion 
> a bit.

not at all. I, for one, do not want to force anyone to implement HIP if 
he or she does not want to.

I agree with you that if you buy a product that supports "IETF P2PSIP" 
and I buy another product that also supports "IETF P2PSIP", they should 
be able to talk to each other... of course, we may find out that our 
boxes do not implement the right DHT, but that is a different story.

Of course, it would be OK for the P2PSIP WG to decide not to use HIP for 
"IETF P2PSIP" applications, if this is what most people want (this is 
what is being discussed). You are also right that, lately, we tend to 
build too complex systems and that we should be aplying the kiss 
principle more often... but I come from a different perspective.

I want to build a HIP-based overlay. If the P2PSIP WG decides that 
P2PSIP should be HIP-free, that's OK. If that was the case, I would run 
other types of applications on top of my HIP-based overlays.

The thing is that, in order to build my HIP-based overlay, I need a peer 
protocol whose functionality is a subset of the functionality provided 
by the peer protocols designed in the P2PSIP WG... therefore, in order 
to avoid reinventing the wheel once more, I would like to use those peer 
protocols for my HIP-based overlay.

Consequently, my requirement on the peer protocol is documented on 
Section 5 of the HIP BONE draft:

        ... the peer protocol
        standardized by the WG is kept functionally and specification
        wise reasonably modular so that the HIP community can use the
        peer protocol minus the connection management and NAT traversal
        modules to experiment with HIP-based overlays.  Note that, at
        present, this is the case with several peer protocols.

I really hope nobody has a problem with this requirement.

With respect to whether or not option 3 (optional to implement and run) 
is actually an option, we can discuss whether or not making HIP optional 
to run for any given node in any given overlay adds too much complexity 
to a system (the capability negotiation mechanism needed for that and 
the stuff that would need to be implemented twice). I personally tend to 
think that the complexity would be relatively high, but some folks do 
not think so.

Cheers,

Gonzalo

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



From p2psip-bounces@ietf.org Mon Jan 14 15:13:23 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JEVgQ-0002ua-16; Mon, 14 Jan 2008 15:13:22 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JEVgP-0002rl-7C
	for p2psip@ietf.org; Mon, 14 Jan 2008 15:13:21 -0500
Received: from exprod6og104.obsmtp.com ([64.18.1.187])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JEVgO-000504-Do
	for p2psip@ietf.org; Mon, 14 Jan 2008 15:13:21 -0500
Received: from source ([192.150.11.134]) by exprod6ob104.postini.com
	([64.18.5.12]) with SMTP; Mon, 14 Jan 2008 12:13:12 PST
Received: from inner-relay-3.eur.adobe.com (inner-relay-3.adobe.com
	[192.150.20.198] (may be forged))
	by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	m0EKAgin000271; Mon, 14 Jan 2008 12:10:43 -0800 (PST)
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
	m0EKD4FV023516; Mon, 14 Jan 2008 12:13:05 -0800 (PST)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by
	apacmail.pac.adobe.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 15 Jan 2008 05:13:03 +0900
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [P2PSIP] HIP: optional, mandatory?
Date: Mon, 14 Jan 2008 12:12:40 -0800
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D223AE4FB@namail5.corp.adobe.com>
In-Reply-To: <4d4304a00801110710x1b7f04b4lcbcbb9eb8702ba1e@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] HIP: optional, mandatory?
Thread-Index: AchUZCP9dsAsKcq5TvaSuSDoUjWf9wChSREg
References: <476BA8D9.4010203@ericsson.com>
	<476E2B7C.9070601@ericsson.com><20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com><77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com><7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com><77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com><10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu><4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com><0c3a01c85402$28d821e0$6601a8c0@china.huawei.com><CBAEA83C-A2BB-47E7-AE49-A3E901DDB50C@cs.columbia.edu>
	<4d4304a00801110710x1b7f04b4lcbcbb9eb8702ba1e@mail.gmail.com>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "David A. Bryan" <dbryan@sipeerior.com>,
	"Henning Schulzrinne" <hgs@cs.columbia.edu>
X-OriginalArrivalTime: 14 Jan 2008 20:13:03.0412 (UTC)
	FILETIME=[DE20CF40:01C856E9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org


>...anyone care to take a stab at explaining how it actually works?

Part of the explanation has just been posted:

http://www.ietf.org/internet-drafts/draft-ahrenholz-hiprg-dht-02.txt=20

I understand Gonzalo Camarillo is about to publish an update to the
HIP-BONE I-D.
Let's wait and see if these will explain the issues discussed here.

Henry

-----Original Message-----
From: David A. Bryan [mailto:dbryan@sipeerior.com]=20
Sent: Friday, January 11, 2008 9:10 AM
To: Henning Schulzrinne
Cc: P2PSIP Mailing List
Subject: Re: [P2PSIP] HIP: optional, mandatory?

Hmmm...(b) and (c) doesn't make sense to me, unless I'm missing
something. After reading Spencer's email, (a) and (b) make more sense
to me.

I agree with Cullen that HIP should me optional both to implement and
run. That means that many overlays may simply not support it all, and
others may use it exclusively, giving us the (a) scenario. A
particular endpoint may choose to implement both, allowing it join
both types of overlays, which is (b).

(c) makes little sense to me operationally, although I guess I can see
how it could be done technically if there are some (b) type peers that
are effectively relays. It would make for some really odd DHTs,
however, since you might have to route calls via the adaptors, and I'm
not sure it really gains you anything.

In my mind, this would be a capabilities negotiation issue. Although
the mechanics of how you do it might differ a good bit, logically it
might be good to think about it like offer-answer in SIP. If I start
an overlay, I'm free to choose the DHT and if it is SIP or not. If, on
the other hand a few peers were negotiating among themselves, they
could compare capabilities (DHTs, HIP or not, security model, etc.)
and choose the best. I don't think we have a "One ring to rule them
all..." thing going on where every single peer is in a global overlay,
although there could be some (very) large and essentially public
rings. There will be rings with different choices on DHT/transport,
and that decision may limit who can join that particular ring.

So I guess since we are all picking numbers here, I am the (3)(a and
b) camp. I might just not have my head around (c), however...anyone
care to take a stab at explaining how it actually works?

David (as individual)

On Jan 10, 2008 10:52 PM, Henning Schulzrinne <hgs@cs.columbia.edu>
wrote:
> I'm assuming that the goal is that a P2PSIP-compliant application will
> be able to participate in any P2PSIP-compliant overlay, subject to
> having code for the DHT  the overlay is running. Thus, this means that
> non-HIP peers must be able to be full peers. Unless the arrival of a
> single non-HIP peer converts the whole overlay to non-HIP usage, this
> also implies that all nodes must be able to deal with non-HIP peers,
> even if they prefer to speak HIP. Among other things, they'll probably
> have to implement ICE and TLS.
>
> Thus, it's something like (b) and (c).
>
> Henning
>
> On Jan 10, 2008, at 10:29 PM, Spencer Dawkins wrote:
>
> > Hi, Cullen and Henning,
> >
> > I guess today is a good day for me to be confused.
> >
> > I thought I understood "optional to implement, optional to run", and
> > I understood Cullen's reasons stated below, but I'm very confused
> > about why "this only works if you can have mixed HIP-non-HIP" ...
> >
> > ... and that's probably because I'm not quite sure what "mixed HIP-
> > non-HIP" means.
> >
> > Are you talking about
> >
> > a - mixed within P2PSIP technology, so that some overlays use HIP
> > and others do not?
> >
> > b - mixed within the same endpoint, that can join a HIP overlay and
> > a non-HIP overlay?
> >
> > c - mixed within the same overlay, so some peers use HIP and others
> > do not?
> >
> > I'll stop talking now ...
>
>
>
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.ietf.org/mailman/listinfo/p2psip
>



--=20
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://www1.ietf.org/mailman/listinfo/p2psip

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



From p2psip-bounces@ietf.org Tue Jan 15 14:32:04 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JErVw-0004WY-4V; Tue, 15 Jan 2008 14:32:00 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JErVu-0004V6-Pw
	for p2psip@ietf.org; Tue, 15 Jan 2008 14:31:58 -0500
Received: from mxoutps1.us.army.mil ([143.69.250.38])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JErVr-0003rs-GH
	for p2psip@ietf.org; Tue, 15 Jan 2008 14:31:57 -0500
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=UqzFwhBwFvlkDb563QK7EBGJ957oEsqNYQXJB0mRz+rM3qM7LLyQL1E2
	ysEBl+CnzPho9IRIe/iE7ysYUlyf+Q==;
From: "Roy, Radhika R Dr CTR USA USAMC" <radhika.r.roy@us.army.mil>
X-AKO: 105122150:10.224.36.65:15 Jan 2008 19:31:52 +0000:$Webmail:None
X-IronPort-AV: E=Sophos;i="4.24,288,1196640000"; d="scan'208";a="105122150"
Received: from mail5.int.ps1.us.army.mil (HELO us.army.mil) ([10.224.36.65])
	by mxoutps1.us.army.mil with ESMTP; 15 Jan 2008 19:31:52 +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, 15 Jan
	2008 14:31:51 -0500
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Message-ID: <e1df81d5b8ce.478cc3d7@us.army.mil>
Date: Tue, 15 Jan 2008 14:31:51 -0500
X-Mailer: Sun Java(tm) System Messenger Express 6.2-9.04 (built Jun 11
 2007)
MIME-Version: 1.0
Content-Language: en
Subject: Re: [P2PSIP] HIP: optional, mandatory?
X-Accept-Language: en
Priority: normal
In-Reply-To: <478BB75F.5080409@ericsson.com>
References: <476BA8D9.4010203@ericsson.com> <476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
	<0c3a01c85402$28d821e0$6601a8c0@china.huawei.com>
	<CBAEA83C-A2BB-47E7-AE49-A3E901DDB50C@cs.columbia.edu>
	<4d4304a00801110710x1b7f04b4lcbcbb9eb8702ba1e@mail.gmail.com>
	<0d2101c85468$034c4080$6601a8c0@china.huawei.com>
	<1B79D7E7-A67B-42D9-9F00-66E69080C358@cs.columbia.edu>
	<478BB75F.5080409@ericsson.com>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Gonzalo:

Good.

It is what is required for clarifications especially from the author of the draft as follows:

1. P2PSIP WG will develop the peer protocol.
2. The peer protocol will be simple one using KISS principles.

Let us focus on this and finish the development of the peer protocol first.

So, I, personally, want to help and expedite the above item of the WG. Once we have this one ready, the rest are the use cases of the peer protocol. In fact, this is the beauty of the entire process - to proceed step-by-step.

Best regards,
Radhika

PS: 

1. In fact, like you, we have also many more ideas how to solve many other problems using the standard peer protocol. You cannot believe that the emerging MANET networks are hungry for building applications once the peer protocol is standardized. It is a huge area as all applications need to migrate in peer-to-peer communications environments.

2. If the peer protocol development is completed on time by this WG, it will be an enormous help to the industry because a whole new areas for building the p2p-applications will be made open. We are yet to imagine what will be the impact of it in the future. So, let us finish our first task of the WG first as Cullen pointed out.

----- Original Message -----
From: Gonzalo Camarillo 
Date: Monday, January 14, 2008 14:26
Subject: Re: [P2PSIP] HIP: optional, mandatory?
To: Henning Schulzrinne 
Cc: P2PSIP Mailing List 

> Hi Henning,
> 
> > At least we're now clear that the HIP advocates want to 
> essentially 
> > force systems to implement it. This will hopefully focus the 
> discussion 
> > a bit.
> 
> not at all. I, for one, do not want to force anyone to implement 
> HIP if 
> he or she does not want to.
> 
> I agree with you that if you buy a product that supports "IETF 
> P2PSIP" 
> and I buy another product that also supports "IETF P2PSIP", they 
> should 
> be able to talk to each other... of course, we may find out that 
> our 
> boxes do not implement the right DHT, but that is a different story.
> 
> Of course, it would be OK for the P2PSIP WG to decide not to use 
> HIP for 
> "IETF P2PSIP" applications, if this is what most people want (this 
> is 
> what is being discussed). You are also right that, lately, we tend 
> to 
> build too complex systems and that we should be aplying the kiss 
> principle more often... but I come from a different perspective.
> 
> I want to build a HIP-based overlay. If the P2PSIP WG decides that 
> P2PSIP should be HIP-free, that's OK. If that was the case, I 
> would run 
> other types of applications on top of my HIP-based overlays.
> 
> The thing is that, in order to build my HIP-based overlay, I need 
> a peer 
> protocol whose functionality is a subset of the functionality 
> provided 
> by the peer protocols designed in the P2PSIP WG... therefore, in 
> order 
> to avoid reinventing the wheel once more, I would like to use 
> those peer 
> protocols for my HIP-based overlay.
> 
> Consequently, my requirement on the peer protocol is documented on 
> Section 5 of the HIP BONE draft:
> 
> ... the peer protocol
> standardized by the WG is kept functionally and specification
> wise reasonably modular so that the HIP community can use the
> peer protocol minus the connection management and NAT 
> traversal modules to experiment with HIP-based overlays. 
> Note that, at
> present, this is the case with several peer protocols.
> 
> I really hope nobody has a problem with this requirement.
> 
> With respect to whether or not option 3 (optional to implement and 
> run) 
> is actually an option, we can discuss whether or not making HIP 
> optional 
> to run for any given node in any given overlay adds too much 
> complexity 
> to a system (the capability negotiation mechanism needed for that 
> and 
> the stuff that would need to be implemented twice). I personally 
> tend to 
> think that the complexity would be relatively high, but some folks 
> do 
> not think so.
> 
> Cheers,
> 
> Gonzalo
> 
> 

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



From p2psip-bounces@ietf.org Thu Jan 17 02:21:28 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JFP3k-0005Qt-2r; Thu, 17 Jan 2008 02:21:08 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JFP3i-0005Qo-8j
	for p2psip@ietf.org; Thu, 17 Jan 2008 02:21:06 -0500
Received: from szxga02-in.huawei.com ([61.144.161.54])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JFP3g-0004Fa-MZ
	for p2psip@ietf.org; Thu, 17 Jan 2008 02:21:06 -0500
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 <0JUS004N11Q5MY@szxga02-in.huawei.com> for
	p2psip@ietf.org; Thu, 17 Jan 2008 15:20:29 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JUS008VU1Q4J1@szxga02-in.huawei.com> for
	p2psip@ietf.org; Thu, 17 Jan 2008 15:20:28 +0800 (CST)
Received: from j36340 ([10.164.9.45])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JUS00JGN1Q4JU@szxml04-in.huawei.com> for
	p2psip@ietf.org; Thu, 17 Jan 2008 15:20:28 +0800 (CST)
Date: Thu, 17 Jan 2008 15:20:28 +0800
From: JiangXingFeng <jiang.x.f@huawei.com>
Subject: RE: [P2PSIP] HIP: optional, mandatory?
In-reply-to: <4d4304a00801110859t1b7feb53nd3413fcd84ad57cc@mail.gmail.com>
To: "'David A. Bryan'" <dbryan@sipeerior.com>,
	'Cullen Jennings' <fluffy@cisco.com>
Message-id: <004301c858d9$6fafd140$2d09a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Thread-index: AchUc1mGwIYWYZVQRDynN8aVruG0TgEZUuZg
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

> I want to be clear that I don't think this means we rule out having a
> HIP transport, but I think that if we say that we are going to wait
> for HIP to provide the complete underlying P2P fabric (peer protocol
> and all) that we use, we have things backwards -- that is what we are
> chartered here to provide. I also think it will be a long wait, since
> that particular work isn't chartered for P2P standards at the moment.
> I think deployment is critical here and sooner, rather than later. We
> need to be picking a direction and going with it very soon, not
> waiting for another group to deliver.

David, I fully agree with you. HIP has not been widely deployed and NAT
traversal, mobility and multihome are still developing. All in all, HIP is
not mature enough to provide stable service for upper applications. 

On the other hand, the requirements from HIP-BONE as pointed out by Gonzalo
should be considered while designing peer protocol. Fortunately, it is not
hard to be met. Most of the existing proposals have taken modular approach. 

Regards!
JiangXingFeng


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



From p2psip-bounces@ietf.org Thu Jan 17 03:10:10 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JFPp9-0007lL-Vn; Thu, 17 Jan 2008 03:10:07 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JFPp8-0007ci-Jd
	for p2psip@ietf.org; Thu, 17 Jan 2008 03:10:06 -0500
Received: from sernt4.essex.ac.uk ([155.245.48.30])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JFPp8-0005DQ-20
	for p2psip@ietf.org; Thu, 17 Jan 2008 03:10:06 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [P2PSIP] HIP: optional, mandatory?
Date: Thu, 17 Jan 2008 08:10:05 -0000
Message-ID: <811D385AE1CEBB42839C50DF0B0D38E005B544E2@sernt4.essex.ac.uk>
In-Reply-To: <004301c858d9$6fafd140$2d09a40a@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] HIP: optional, mandatory?
Thread-Index: AchUc1mGwIYWYZVQRDynN8aVruG0TgEZUuZgAAFd3IA=
From: "Oredope, Adetola" <aoredo@essex.ac.uk>
To: "JiangXingFeng" <jiang.x.f@huawei.com>,
	"David A. Bryan" <dbryan@sipeerior.com>,
	"Cullen Jennings" <fluffy@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Interestingly, I was thinking p2psip is supposed to replace the
centralised systems in conventional SIP with an overlay network. So,
what role does HIP precisely play in achieving this goal? NAT
transversal? What then happens if the firewall decides block these
packets? Am I missing something here? Or is there going to be a future
proposal for conventional SIP to also support HIP?
IMHO, I will suggest that p2psip should be designed in such a way that
it can be easily extended to support any future plugins. At least
conventional SIP has the advantage of being highly extendable. Who ever
though SIP would be used to manage optical networks.

Regards,

Tola

-----Original Message-----
From: JiangXingFeng [mailto:jiang.x.f@huawei.com]=20
Sent: 17 January 2008 07:20
To: 'David A. Bryan'; 'Cullen Jennings'
Cc: 'P2PSIP Mailing List'
Subject: RE: [P2PSIP] HIP: optional, mandatory?

> I want to be clear that I don't think this means we rule out having a
> HIP transport, but I think that if we say that we are going to wait
> for HIP to provide the complete underlying P2P fabric (peer protocol
> and all) that we use, we have things backwards -- that is what we are
> chartered here to provide. I also think it will be a long wait, since
> that particular work isn't chartered for P2P standards at the moment.
> I think deployment is critical here and sooner, rather than later. We
> need to be picking a direction and going with it very soon, not
> waiting for another group to deliver.

David, I fully agree with you. HIP has not been widely deployed and NAT
traversal, mobility and multihome are still developing. All in all, HIP
is
not mature enough to provide stable service for upper applications.=20

On the other hand, the requirements from HIP-BONE as pointed out by
Gonzalo
should be considered while designing peer protocol. Fortunately, it is
not
hard to be met. Most of the existing proposals have taken modular
approach.=20

Regards!
JiangXingFeng


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

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



From p2psip-bounces@ietf.org Thu Jan 17 04:32:37 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JFR6m-0005Nn-Up; Thu, 17 Jan 2008 04:32:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JFR6m-0005NN-Af
	for p2psip@ietf.org; Thu, 17 Jan 2008 04:32:24 -0500
Received: from quinthar.com ([72.52.120.178])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1JFR6j-0005QO-NP
	for p2psip@ietf.org; Thu, 17 Jan 2008 04:32:24 -0500
Received: from 60.254.174.14 ([60.254.174.14]) by quinthar.com for
	<p2psip@ietf.org>; Thu, 17 Jan 2008 01:32:14 -0800
Message-Id: <DD40D2FF-809B-4B1F-B43B-0E8F41ED21DB@quinthar.com>
From: David Barrett <dbarrett@quinthar.com>
To: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Subject: Re: [P2PSIP] HIP: optional, mandatory?
Date: Thu, 17 Jan 2008 15:02:06 +0530
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
	<465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com>
	<284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>
X-Mailer: Apple Mail (2.915)
X-Spam-Score: 2.6 (++)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org


On Jan 11, 2008, at 10:08 PM, Cullen Jennings wrote:
> On Jan 10, 2008, at 8:23 PM, David Barrett wrote:
>
>> We don't need more options for what we CAN do, we need decisions on  
>> what we WILL do.
>
> Yep - agree.  And what I want to do is standardize something that  
> lets me build deployable interoperable solutions soon. Success for  
> me involves deployments.

100% agree.  That's why I like the HIP layer (whether or not it's  
chartered as I dream):
- P2PSIP builds a decentralized SIP for a fictional "end-to-end"  
internet, and then
- HIP makes that "end-to-end" internet a reality.

This lets us each focus on what we care about, planning to come  
together in the future.  Granted, if they fail, then we're screwed --  
we can't deploy in the real world.  But that's the nature of open  
standards and implementations.  If we don't buy into this ethos and  
instead feel that the only way to do it "right" is to build a custom  
stack from top to bottom, then that doesn't bode well for our faith in  
the IETF.


>>  If we're not considering making HIP mandatory, then let's stop  
>> talking about it and start focusing on those things that *will* be  
>> mandatory.
>
> The P2PSIP WG has made very few decisions since it was formed. IMHO,  
> what we need to do real soon now is pick something as a starting  
> point for a WG document then go and make the decision to change it  
> to be what we want.  Until we do that, my belief is that the WG will  
> make fairly marginal progress.

Agreed.  Every call for more extensibility and more support for more  
plugins just puts another nail in the coffin for a practical, real- 
world P2PSIP.  I mean, if we can't get *anything* working, why should  
we expect to get it working *and* extensible?  Let's get it working  
first, and then worry about extensibility.  In my experience, it's far  
easier to extend something that exists than something that doesn't.


>> That said, I think this HIP discussion is the best thing to happen  
>> in P2PSIP for years.  It seems like the most practical and powerful  
>> solution, the best layering of functionality, and the most feasible  
>> design that I've yet to hear.  Moving the hard P2P code into a  
>> reusable HIP layer makes a lot of sense,
>
> this is way outside anything HIP was charted to do or is working on

Even if that's true, that's not a satisfying answer.  Good design  
should trump IETF charters.  If HIP or P2PSIP needs rechartering, so  
be it.


>> not only for P2PSIP, but for the internet as a whole.  It seems  
>> like a wagon that we should voluntarily and enthusiastically hitch  
>> ourselves to, rather than try to reproduce or compete with it, or  
>> toss it in the overflowing bucket of optional extensions.
>>
>> It seems sensible to have a base HIP layer that either comes pre- 
>> installed with the OS or redistributed by the application (similar  
>> to WinPCap).  (I could even see making a sort of "HIP-lite" self- 
>> contained library that can be linked straight into the application  
>> for when installing a   Then P2PSIP can be one of many HIP-using  
>> applications that are vastly simplified by being insulated from the  
>> gnarly realities of NAT and firewall penetration, mobility, etc.
>>
>> This makes a lot more sense than continually reproducing this  
>> really hard functionality in every application.
>
> Most of the concrete proposals layer the p2p code such that the  
> library that provided the p2p part could be used by other  
> applications. This is a good design but not something you need HIP  
> to accomplish.

Agreed, but HIP seems like as good a place as any.

-david


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



From p2psip-bounces@ietf.org Thu Jan 17 12:13:05 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JFYIR-0000jJ-8E; Thu, 17 Jan 2008 12:12:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JFYIQ-0000eB-39
	for p2psip@ietf.org; Thu, 17 Jan 2008 12:12:54 -0500
Received: from exprod6og103.obsmtp.com ([64.18.1.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JFYIP-0000TF-5O
	for p2psip@ietf.org; Thu, 17 Jan 2008 12:12:54 -0500
Received: from source ([192.150.11.134]) by exprod6ob103.postini.com
	([64.18.5.12]) with SMTP; Thu, 17 Jan 2008 09:12:29 PST
Received: from inner-relay-1.corp.adobe.com ([153.32.1.51])
	by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	m0HH9nin011445; Thu, 17 Jan 2008 09:09:51 -0800 (PST)
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
	m0HHCDRC012146; Thu, 17 Jan 2008 09:12:13 -0800 (PST)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 17 Jan 2008 09:12:13 -0800
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [P2PSIP] HIP: optional, mandatory?
Date: Thu, 17 Jan 2008 09:12:07 -0800
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D223AE531@namail5.corp.adobe.com>
In-Reply-To: <DD40D2FF-809B-4B1F-B43B-0E8F41ED21DB@quinthar.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] HIP: optional, mandatory?
Thread-Index: AchY6/f3hzHbxXFXSd62E76EI/ZxDwAPjfcg
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com><20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com><77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com><7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com><77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com><10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu><4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com><465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com><284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>
	<DD40D2FF-809B-4B1F-B43B-0E8F41ED21DB@quinthar.com>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "David Barrett" <dbarrett@quinthar.com>,
	"Cullen Jennings" <fluffy@cisco.com>
X-OriginalArrivalTime: 17 Jan 2008 17:12:13.0677 (UTC)
	FILETIME=[1A6BE1D0:01C8592C]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

I fully agree with Dave Barrett and would like to illustrate the
pressure to get P2PSIP ASAP to market. For what ti is worth, please look
at=20

http://www.spiegel.de/fotostrecke/0,5538,PB64-SUQ9MjY4OTgmbnI9OA_3_3,00.
html=20

The note on the right side specifies this statistic is for the consumer
market and enterprise networks may use more SIP based VoIP.
Clicking the "back" links will show more interesting numbers on P2P.

Opinion: This call to urgency can be best met IMHO by using P2PP
implemented on 600 nodes on Planet Lab since it meets the criteria of
running code, open available free code and large footprint deployment.

Thanks, Henry

-----Original Message-----
From: David Barrett [mailto:dbarrett@quinthar.com]=20
Sent: Thursday, January 17, 2008 3:32 AM
To: Cullen Jennings
Cc: P2PSIP Mailing List
Subject: Re: [P2PSIP] HIP: optional, mandatory?


On Jan 11, 2008, at 10:08 PM, Cullen Jennings wrote:
> On Jan 10, 2008, at 8:23 PM, David Barrett wrote:
>
>> We don't need more options for what we CAN do, we need decisions on =20
>> what we WILL do.
>
> Yep - agree.  And what I want to do is standardize something that =20
> lets me build deployable interoperable solutions soon. Success for =20
> me involves deployments.

100% agree.  That's why I like the HIP layer (whether or not it's =20
chartered as I dream):
- P2PSIP builds a decentralized SIP for a fictional "end-to-end" =20
internet, and then
- HIP makes that "end-to-end" internet a reality.

This lets us each focus on what we care about, planning to come =20
together in the future.  Granted, if they fail, then we're screwed -- =20
we can't deploy in the real world.  But that's the nature of open =20
standards and implementations.  If we don't buy into this ethos and =20
instead feel that the only way to do it "right" is to build a custom =20
stack from top to bottom, then that doesn't bode well for our faith in =20
the IETF.


>>  If we're not considering making HIP mandatory, then let's stop =20
>> talking about it and start focusing on those things that *will* be =20
>> mandatory.
>
> The P2PSIP WG has made very few decisions since it was formed. IMHO, =20
> what we need to do real soon now is pick something as a starting =20
> point for a WG document then go and make the decision to change it =20
> to be what we want.  Until we do that, my belief is that the WG will =20
> make fairly marginal progress.

Agreed.  Every call for more extensibility and more support for more =20
plugins just puts another nail in the coffin for a practical, real-=20
world P2PSIP.  I mean, if we can't get *anything* working, why should =20
we expect to get it working *and* extensible?  Let's get it working =20
first, and then worry about extensibility.  In my experience, it's far =20
easier to extend something that exists than something that doesn't.


>> That said, I think this HIP discussion is the best thing to happen =20
>> in P2PSIP for years.  It seems like the most practical and powerful =20
>> solution, the best layering of functionality, and the most feasible =20
>> design that I've yet to hear.  Moving the hard P2P code into a =20
>> reusable HIP layer makes a lot of sense,
>
> this is way outside anything HIP was charted to do or is working on

Even if that's true, that's not a satisfying answer.  Good design =20
should trump IETF charters.  If HIP or P2PSIP needs rechartering, so =20
be it.


>> not only for P2PSIP, but for the internet as a whole.  It seems =20
>> like a wagon that we should voluntarily and enthusiastically hitch =20
>> ourselves to, rather than try to reproduce or compete with it, or =20
>> toss it in the overflowing bucket of optional extensions.
>>
>> It seems sensible to have a base HIP layer that either comes pre-=20
>> installed with the OS or redistributed by the application (similar =20
>> to WinPCap).  (I could even see making a sort of "HIP-lite" self-=20
>> contained library that can be linked straight into the application =20
>> for when installing a   Then P2PSIP can be one of many HIP-using =20
>> applications that are vastly simplified by being insulated from the =20
>> gnarly realities of NAT and firewall penetration, mobility, etc.
>>
>> This makes a lot more sense than continually reproducing this =20
>> really hard functionality in every application.
>
> Most of the concrete proposals layer the p2p code such that the =20
> library that provided the p2p part could be used by other =20
> applications. This is a good design but not something you need HIP =20
> to accomplish.

Agreed, but HIP seems like as good a place as any.

-david


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

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



From p2psip-bounces@ietf.org Fri Jan 18 15:29:55 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JFxqZ-0005o8-3K; Fri, 18 Jan 2008 15:29:51 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JFxqX-0005o2-8y
	for p2psip@ietf.org; Fri, 18 Jan 2008 15:29:49 -0500
Received: from smtp.nokia.com ([192.100.122.230] helo=mgw-mx03.nokia.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JFxqW-0003ak-70
	for p2psip@ietf.org; Fri, 18 Jan 2008 15:29:49 -0500
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m0IKTb85020508; Fri, 18 Jan 2008 22:29:38 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 18 Jan 2008 22:29:02 +0200
Received: from esebe102.NOE.Nokia.com ([172.21.138.217]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 18 Jan 2008 22:29:02 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [P2PSIP] HIP: optional, mandatory?
Date: Fri, 18 Jan 2008 22:31:41 +0200
Message-ID: <3F18E76823C95E4795181D74BAC7664F05B951F1@esebe102.NOE.Nokia.com>
In-Reply-To: <24CCCC428EFEA2469BF046DB3C7A8D223AE531@namail5.corp.adobe.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] HIP: optional, mandatory?
Thread-Index: AchY6/f3hzHbxXFXSd62E76EI/ZxDwAPjfcgADhVDlA=
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com><20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com><77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com><7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com><77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com><10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu><4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com><465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com><284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>
	<DD40D2FF-809B-4B1F-B43B-0E8F41ED21DB@quinthar.com>
	<24CCCC428EFEA2469BF046DB3C7A8D223AE531@namail5.corp.adobe.com>
From: <marcin.matuszewski@nokia.com>
To: <hsinnrei@adobe.com>, <dbarrett@quinthar.com>, <fluffy@cisco.com>
X-OriginalArrivalTime: 18 Jan 2008 20:29:02.0265 (UTC)
	FILETIME=[C34D2A90:01C85A10]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78
Cc: p2psip@ietf.org
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org


>Opinion: This call to urgency can be best met IMHO by using=20
>P2PP implemented on 600 nodes on Planet Lab since it meets the=20
>criteria of running code, open available free code and large=20
>footprint deployment.

I fully agree. Besides Nokia's implementation shows that P2PP can also
work on mobile devices. Some of you who visited Nokia's P2PSIP demo
stand in Las Vegas could see a demo of the P2PP implementation on Nokia
phones. At the stand we were showing how a mobile phone that implements
P2PP can join the Columbia Univ.'s 600 nodes overlay on Planet Lab and
allow users to use basic SIP services. The demo was done in colaboration
with Columbia Univ.=20
Everyone who whould like to join the P2PP trial network please send an
email to Salman, Henning or me.
=20
Our goal is to specify a protocol based on our implementation
experience. It is very easy to write protocol specifications that are
difficult to implement and therefore have high chances to fail in the
market, what we could see in the past.=20

Marcin=20

>-----Original Message-----
>From: ext Henry Sinnreich [mailto:hsinnrei@adobe.com]=20
>Sent: 17 January, 2008 19:12
>To: David Barrett; Cullen Jennings
>Cc: P2PSIP Mailing List
>Subject: RE: [P2PSIP] HIP: optional, mandatory?
>
>I fully agree with Dave Barrett and would like to illustrate=20
>the pressure to get P2PSIP ASAP to market. For what ti is=20
>worth, please look at=20
>
>http://www.spiegel.de/fotostrecke/0,5538,PB64-SUQ9MjY4OTgmbnI9O
A_3_3,00.
>html=20
>
>The note on the right side specifies this statistic is for the=20
>consumer market and enterprise networks may use more SIP based VoIP.
>Clicking the "back" links will show more interesting numbers on P2P.
>
>Opinion: This call to urgency can be best met IMHO by using=20
>P2PP implemented on 600 nodes on Planet Lab since it meets the=20
>criteria of running code, open available free code and large=20
>footprint deployment.
>
>Thanks, Henry
>
>-----Original Message-----
>From: David Barrett [mailto:dbarrett@quinthar.com]
>Sent: Thursday, January 17, 2008 3:32 AM
>To: Cullen Jennings
>Cc: P2PSIP Mailing List
>Subject: Re: [P2PSIP] HIP: optional, mandatory?
>
>
>On Jan 11, 2008, at 10:08 PM, Cullen Jennings wrote:
>> On Jan 10, 2008, at 8:23 PM, David Barrett wrote:
>>
>>> We don't need more options for what we CAN do, we need=20
>decisions on =20
>>> what we WILL do.
>>
>> Yep - agree.  And what I want to do is standardize something that =20
>> lets me build deployable interoperable solutions soon. Success for =20
>> me involves deployments.
>
>100% agree.  That's why I like the HIP layer (whether or not it's =20
>chartered as I dream):
>- P2PSIP builds a decentralized SIP for a fictional "end-to-end" =20
>internet, and then
>- HIP makes that "end-to-end" internet a reality.
>
>This lets us each focus on what we care about, planning to come =20
>together in the future.  Granted, if they fail, then we're screwed -- =20
>we can't deploy in the real world.  But that's the nature of open =20
>standards and implementations.  If we don't buy into this ethos and =20
>instead feel that the only way to do it "right" is to build a custom =20
>stack from top to bottom, then that doesn't bode well for our=20
>faith in =20
>the IETF.
>
>
>>>  If we're not considering making HIP mandatory, then let's stop =20
>>> talking about it and start focusing on those things that *will* be =20
>>> mandatory.
>>
>> The P2PSIP WG has made very few decisions since it was=20
>formed. IMHO, =20
>> what we need to do real soon now is pick something as a starting =20
>> point for a WG document then go and make the decision to change it =20
>> to be what we want.  Until we do that, my belief is that the=20
>WG will =20
>> make fairly marginal progress.
>
>Agreed.  Every call for more extensibility and more support for more =20
>plugins just puts another nail in the coffin for a practical, real-=20
>world P2PSIP.  I mean, if we can't get *anything* working, why should =20
>we expect to get it working *and* extensible?  Let's get it working =20
>first, and then worry about extensibility.  In my experience,=20
>it's far =20
>easier to extend something that exists than something that doesn't.
>
>
>>> That said, I think this HIP discussion is the best thing to happen =20
>>> in P2PSIP for years.  It seems like the most practical and=20
>powerful =20
>>> solution, the best layering of functionality, and the most=20
>feasible =20
>>> design that I've yet to hear.  Moving the hard P2P code into a =20
>>> reusable HIP layer makes a lot of sense,
>>
>> this is way outside anything HIP was charted to do or is working on
>
>Even if that's true, that's not a satisfying answer.  Good design =20
>should trump IETF charters.  If HIP or P2PSIP needs rechartering, so =20
>be it.
>
>
>>> not only for P2PSIP, but for the internet as a whole.  It seems =20
>>> like a wagon that we should voluntarily and enthusiastically hitch =20
>>> ourselves to, rather than try to reproduce or compete with it, or =20
>>> toss it in the overflowing bucket of optional extensions.
>>>
>>> It seems sensible to have a base HIP layer that either comes pre-=20
>>> installed with the OS or redistributed by the application (similar =20
>>> to WinPCap).  (I could even see making a sort of "HIP-lite" self-=20
>>> contained library that can be linked straight into the application =20
>>> for when installing a   Then P2PSIP can be one of many HIP-using =20
>>> applications that are vastly simplified by being insulated=20
>from the =20
>>> gnarly realities of NAT and firewall penetration, mobility, etc.
>>>
>>> This makes a lot more sense than continually reproducing this =20
>>> really hard functionality in every application.
>>
>> Most of the concrete proposals layer the p2p code such that the =20
>> library that provided the p2p part could be used by other =20
>> applications. This is a good design but not something you need HIP =20
>> to accomplish.
>
>Agreed, but HIP seems like as good a place as any.
>
>-david
>
>
>_______________________________________________
>P2PSIP mailing list
>P2PSIP@ietf.org
>https://www1.ietf.org/mailman/listinfo/p2psip
>

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



From p2psip-bounces@ietf.org Mon Jan 21 04:58:47 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JGtQO-0006EM-Pf; Mon, 21 Jan 2008 04:58:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JGtQM-0006E0-PW
	for p2psip@ietf.org; Mon, 21 Jan 2008 04:58:38 -0500
Received: from ousrvr.oulu.fi ([130.231.240.1] helo=oulu.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JGtQL-0000Id-2C
	for p2psip@ietf.org; Mon, 21 Jan 2008 04:58:38 -0500
Received: from paju.oulu.fi (paju.oulu.fi [130.231.240.20])
	by oulu.fi (8.13.7/8.13.7) with ESMTP id m0L9wZdn006416;
	Mon, 21 Jan 2008 11:58:35 +0200 (EET)
Received: from [127.0.0.1] (paju.oulu.fi [130.231.240.20])
	by paju.oulu.fi (8.13.7/8.13.7) with ESMTP id m0L9wZep010547;
	Mon, 21 Jan 2008 11:58:35 +0200 (EET)
Message-ID: <47946CC9.4080806@ee.oulu.fi>
Date: Mon, 21 Jan 2008 11:58:33 +0200
From: Erkki Harjula <erkkih@ee.oulu.fi>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: marcin.matuszewski@nokia.com, p2psip@ietf.org
Subject: Re: [P2PSIP] HIP: optional, mandatory?
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com><20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com><77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com><7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com><77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com><10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu><4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com><465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com><284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>	<DD40D2FF-809B-4B1F-B43B-0E8F41ED21DB@quinthar.com>	<24CCCC428EFEA2469BF046DB3C7A8D223AE531@namail5.corp.adobe.com>
	<3F18E76823C95E4795181D74BAC7664F05B951F1@esebe102.NOE.Nokia.com>
In-Reply-To: <3F18E76823C95E4795181D74BAC7664F05B951F1@esebe102.NOE.Nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: 
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hi, we at the University of Oulu are collaborating with Nokia and 
Columbia University with the P2PP prototype. Together with Nokia we are 
implementing a mobile version (works on Nokia's S60 phones) of P2PP 
prototype, which is able to act as both P2PSIP peer and client. We are 
currently working on mobile version's interoperability with fixed 
version of P2PP, aiming to provide full compatibility between them.

Columbia's overlay on PlanetLab provides an excellent testing 
environment for the prototypes. Thus, I also encourage you to join this 
P2PP trial network to increase the node population.

-Erkki


marcin.matuszewski@nokia.com wrote:
> I fully agree. Besides Nokia's implementation shows that P2PP can also
> work on mobile devices. Some of you who visited Nokia's P2PSIP demo
> stand in Las Vegas could see a demo of the P2PP implementation on Nokia
> phones. At the stand we were showing how a mobile phone that implements
> P2PP can join the Columbia Univ.'s 600 nodes overlay on Planet Lab and
> allow users to use basic SIP services. The demo was done in colaboration
> with Columbia Univ. 
> Everyone who whould like to join the P2PP trial network please send an
> email to Salman, Henning or me.
>  
> Our goal is to specify a protocol based on our implementation
> experience. It is very easy to write protocol specifications that are
> difficult to implement and therefore have high chances to fail in the
> market, what we could see in the past. 
>
> Marcin 
>   
>




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



From p2psip-bounces@ietf.org Mon Jan 21 09:12:45 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JGxOF-00026E-Mu; Mon, 21 Jan 2008 09:12:43 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JGxOE-0001up-LP
	for p2psip@ietf.org; Mon, 21 Jan 2008 09:12:42 -0500
Received: from mxoutps1.us.army.mil ([143.69.250.38])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JGxOD-00086j-PJ
	for p2psip@ietf.org; Mon, 21 Jan 2008 09:12:42 -0500
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=ufdvi7rAsIJBC+uAC6jCYZp11IT1/aYSOcO/B68rh5LFbHTlEJODgZhq
	Pip2gnTtLHwCr8rWHHKXbUyQUkSylQ==;
From: "Roy, Radhika R Dr CTR USA USAMC" <radhika.r.roy@us.army.mil>
X-AKO: 95181908:10.224.36.65:21 Jan 2008 14:12:40 +0000:$Webmail:None
X-IronPort-AV: E=Sophos;i="4.25,227,1199664000"; d="scan'208";a="95181908"
Received: from mail5.int.ps1.us.army.mil (HELO us.army.mil) ([10.224.36.65])
	by mxoutps1.us.army.mil with ESMTP; 21 Jan 2008 14:12:40 +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); Mon, 21 Jan
	2008 09:12:40 -0500
To: marcin.matuszewski@nokia.com
Message-ID: <e3c8ad9a1429b.47946208@us.army.mil>
Date: Mon, 21 Jan 2008 09:12:40 -0500
X-Mailer: Sun Java(tm) System Messenger Express 6.2-9.04 (built Jun 11
 2007)
MIME-Version: 1.0
Content-Language: en
Subject: Re: RE: [P2PSIP] HIP: optional, mandatory?
X-Accept-Language: en
Priority: normal
In-Reply-To: <3F18E76823C95E4795181D74BAC7664F05B951F1@esebe102.NOE.Nokia.com>
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
	<465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com>
	<284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>
	<DD40D2FF-809B-4B1F-B43B-0E8F41ED21DB@quinthar.com>
	<24CCCC428EFEA2469BF046DB3C7A8D223AE531@namail5.corp.adobe.com>
	<3F18E76823C95E4795181D74BAC7664F05B951F1@esebe102.NOE.Nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: hsinnrei@adobe.com, p2psip@ietf.org
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Inline [RRR]

----- Original Message -----
From: marcin.matuszewski@nokia.com
Date: Friday, January 18, 2008 15:30
Subject: RE: [P2PSIP] HIP: optional, mandatory?
To: hsinnrei@adobe.com, dbarrett@quinthar.com, fluffy@cisco.com
Cc: p2psip@ietf.org

> 
> >Opinion: This call to urgency can be best met IMHO by using 
> >P2PP implemented on 600 nodes on Planet Lab since it meets the 
> >criteria of running code, open available free code and large 
> >footprint deployment.
> 
> I fully agree. Besides Nokia's implementation shows that P2PP can also
> work on mobile devices. Some of you who visited Nokia's P2PSIP demo
> stand in Las Vegas could see a demo of the P2PP implementation on 
> Nokiaphones. At the stand we were showing how a mobile phone that 
> implementsP2PP can join the Columbia Univ.'s 600 nodes overlay on 
> Planet Lab and
> allow users to use basic SIP services. The demo was done in 
> colaborationwith Columbia Univ. 
> Everyone who whould like to join the P2PP trial network please 
> send an
> email to Salman, Henning or me.
> 
> Our goal is to specify a protocol based on our implementation
> experience. It is very easy to write protocol specifications that are
> difficult to implement and therefore have high chances to fail in the
> market, what we could see in the past. 
> 
> Marcin 

[RRR] Yes, you are right. So, please help this P2PSIP WG to complete the spec for the base P2PSIP protocol based on these implementation experiences as soon as possible. We would appreciate this.

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



From p2psip-bounces@ietf.org Mon Jan 21 12:50:28 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JH0ml-0000Yy-J6; Mon, 21 Jan 2008 12:50:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JH0mk-0000XS-Us
	for p2psip@ietf.org; Mon, 21 Jan 2008 12:50:14 -0500
Received: from exprod6og101.obsmtp.com ([64.18.1.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JH0mk-0006Fn-8O
	for p2psip@ietf.org; Mon, 21 Jan 2008 12:50:14 -0500
Received: from source ([192.150.20.142]) by exprod6ob101.postini.com
	([64.18.5.12]) with SMTP; Mon, 21 Jan 2008 09:50:07 PST
Received: from inner-relay-3.eur.adobe.com (inner-relay-3b [10.128.4.236])
	by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	m0LHo3Gb014701; Mon, 21 Jan 2008 09:50:03 -0800 (PST)
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
	m0LHnxFX024153; Mon, 21 Jan 2008 09:50:02 -0800 (PST)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by
	apacmail.pac.adobe.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 Jan 2008 02:49:59 +0900
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [P2PSIP] HIP: optional, mandatory?
Date: Mon, 21 Jan 2008 09:49:57 -0800
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D223AE557@namail5.corp.adobe.com>
In-Reply-To: <47946CC9.4080806@ee.oulu.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] HIP: optional, mandatory?
Thread-Index: AchcFEBQK8Y307JQRrqz9GKGSKXASQAQFZog
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com><20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com><77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com><7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com><77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com><10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu><4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com><465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com><284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>	<DD40D2FF-809B-4B1F-B43B-0E8F41ED21DB@quinthar.com>	<24CCCC428EFEA2469BF046DB3C7A8D223AE531@namail5.corp.adobe.com><3F18E76823C95E4795181D74BAC7664F05B951F1@esebe102.NOE.Nokia.com>
	<47946CC9.4080806@ee.oulu.fi>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Erkki Harjula" <erkkih@ee.oulu.fi>, <marcin.matuszewski@nokia.com>,
	<p2psip@ietf.org>
X-OriginalArrivalTime: 21 Jan 2008 17:49:59.0827 (UTC)
	FILETIME=[0ACDEE30:01C85C56]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: 
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

>we at the University of Oulu are collaborating with Nokia and=20
>Columbia University with the P2PP prototype. Together with Nokia we are

>implementing a mobile version

Is there any chance it may run on my N810 Nokia Tablet at some future
point in time?

Thanks, Henry

-----Original Message-----
From: Erkki Harjula [mailto:erkkih@ee.oulu.fi]=20
Sent: Monday, January 21, 2008 1:59 AM
To: marcin.matuszewski@nokia.com; p2psip@ietf.org
Subject: Re: [P2PSIP] HIP: optional, mandatory?

Hi, we at the University of Oulu are collaborating with Nokia and=20
Columbia University with the P2PP prototype. Together with Nokia we are=20
implementing a mobile version (works on Nokia's S60 phones) of P2PP=20
prototype, which is able to act as both P2PSIP peer and client. We are=20
currently working on mobile version's interoperability with fixed=20
version of P2PP, aiming to provide full compatibility between them.

Columbia's overlay on PlanetLab provides an excellent testing=20
environment for the prototypes. Thus, I also encourage you to join this=20
P2PP trial network to increase the node population.

-Erkki


marcin.matuszewski@nokia.com wrote:
> I fully agree. Besides Nokia's implementation shows that P2PP can also
> work on mobile devices. Some of you who visited Nokia's P2PSIP demo
> stand in Las Vegas could see a demo of the P2PP implementation on
Nokia
> phones. At the stand we were showing how a mobile phone that
implements
> P2PP can join the Columbia Univ.'s 600 nodes overlay on Planet Lab and
> allow users to use basic SIP services. The demo was done in
colaboration
> with Columbia Univ.=20
> Everyone who whould like to join the P2PP trial network please send an
> email to Salman, Henning or me.
> =20
> Our goal is to specify a protocol based on our implementation
> experience. It is very easy to write protocol specifications that are
> difficult to implement and therefore have high chances to fail in the
> market, what we could see in the past.=20
>
> Marcin=20
>  =20
>




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

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



From p2psip-bounces@ietf.org Tue Jan 22 03:00:24 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHE3O-0007TQ-Uy; Tue, 22 Jan 2008 03:00:18 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHE3N-0007TK-82
	for p2psip@ietf.org; Tue, 22 Jan 2008 03:00:17 -0500
Received: from maile.telecomitalia.it ([156.54.233.31])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHE3M-0000d4-G0
	for p2psip@ietf.org; Tue, 22 Jan 2008 03:00:17 -0500
Received: from ptpxch007ba020.idc.cww.telecomitalia.it ([156.54.240.50]) by
	maile.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 Jan 2008 09:00:13 +0100
Received: from PTPXCH029BA020.idc.cww.telecomitalia.it ([156.54.240.46]) by
	ptpxch007ba020.idc.cww.telecomitalia.it with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 22 Jan 2008 09:00:13 +0100
Received: from [10.229.8.45] ([10.229.8.45]) by
	PTPXCH029BA020.idc.cww.telecomitalia.it over TLS secured
	channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 Jan 2008 09:00:11 +0100
Message-ID: <4795A323.3080401@telecomitalia.it>
Date: Tue, 22 Jan 2008 09:02:43 +0100
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla-Thunderbird 2.0.0.9 (X11/20080110)
MIME-Version: 1.0
To: marcin.matuszewski@nokia.com
Subject: Re: [P2PSIP] HIP: optional, mandatory?
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com><20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com><77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com><7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com><77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com><10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu><4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com><465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com><284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>	<DD40D2FF-809B-4B1F-B43B-0E8F41ED21DB@quinthar.com>	<24CCCC428EFEA2469BF046DB3C7A8D223AE531@namail5.corp.adobe.com>
	<3F18E76823C95E4795181D74BAC7664F05B951F1@esebe102.NOE.Nokia.com>
In-Reply-To: <3F18E76823C95E4795181D74BAC7664F05B951F1@esebe102.NOE.Nokia.com>
X-OriginalArrivalTime: 22 Jan 2008 08:00:12.0043 (UTC)
	FILETIME=[D0745DB0:01C85CCC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Cc: hsinnrei@adobe.com, p2psip@ietf.org
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0287993142=="
Errors-To: p2psip-bounces@ietf.org

This is a cryptographically signed message in MIME format.

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

This is a cryptographically signed message in MIME format.

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

marcin.matuszewski@nokia.com wrote:
>> Opinion: This call to urgency can be best met IMHO by using 
>> P2PP implemented on 600 nodes on Planet Lab since it meets the 
>> criteria of running code, open available free code and large 
>> footprint deployment.
> 
> I fully agree. Besides Nokia's implementation shows that P2PP can also
> work on mobile devices. Some of you who visited Nokia's P2PSIP demo
> stand in Las Vegas could see a demo of the P2PP implementation on Nokia
> phones. At the stand we were showing how a mobile phone that implements
> P2PP can join the Columbia Univ.'s 600 nodes overlay on Planet Lab and
> allow users to use basic SIP services. The demo was done in colaboration
> with Columbia Univ. 

Marcin, could you provide some more details about your mobile nodes
joining a 600-peers overlay on PlanetLab?  As far as I know, PlanetLab
is a federated testbed made of very stable public servers; how did you
manage to make mobile devices part of it?  Or were the mobile nodes
participating only as clients, through a XML-RPC-like interface?

-- 
Ciao,
Enrico

--------------ms000901040501020202090907
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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJ4zCC
Az8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQI
EwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENv
bnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAi
BgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVy
c29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5
NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBM
dGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzAN
BgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9Vvy
Gna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOC
dz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCB
kTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhh
d3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNV
HREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQAD
gYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFi
w9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpb
NU1341YheILcIRk13iSx0x1G/11fZU8wggNMMIICtaADAgECAhA93pW98AVSLKZipzI5De0E
MA0GCSqGSIb3DQEBBQUAMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3Vs
dGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNz
dWluZyBDQTAeFw0wNzAzMjkxNTAyNTVaFw0wODAzMjgxNTAyNTVaMHoxHzAdBgNVBAMTFlRo
YXd0ZSBGcmVlbWFpbCBNZW1iZXIxLjAsBgkqhkiG9w0BCQEWH2Vucmljby5tYXJvY2NvQHRl
bGVjb21pdGFsaWEuaXQxJzAlBgkqhkiG9w0BCQEWGGVucmljby5tYXJvY2NvQGdtYWlsLmNv
bTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALaNEnc2tIvvdDv1eOEaoTRKfQ9V
C7AIlpPaGqPQsyZ1pnGe8dHLmsucl9RAvlft1Pl4FCKodpuSuPn/fWINHExh+GaAvUnGiIIP
1Jk+jm3/Wd0tJByGRgf6Aouk6rLKTE5v/BFldbCdSpdT/1htx5ME9aoYxQ/Vg/CU+X7rTPCR
5tFF8nOEqiFCUFcI9zxy4nfetgUpoomAJwtyX96bYD/ueaKcCMjSaUctpFxy/FRrEalDMQGy
v6OzcyugZVUbYxmHoZqUH27vkf+t0DMf4/LEPrfOnJqCAtQbAWSEJJcn6kDGtjTDFs+tbQFv
EMqtJhuzIyw4v08o/5paI3Diq1cCAwEAAaNnMGUwDwYDVR0PAQH/BAUDAwf5gDBEBgNVHREE
PTA7gR9lbnJpY28ubWFyb2Njb0B0ZWxlY29taXRhbGlhLml0gRhlbnJpY28ubWFyb2Njb0Bn
bWFpbC5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOBgQA3J5m3GoDt0TWtO24H
GMEX44VbMtvD/e0ZSCPfHQxF347LtbC0yyDtvbioV1mB8joVrj48rGC6/cJxs+xqZ6A1EEUd
saeF3T+F8mZh8BYeZo1eqFzgy0ucSJiFJkf38hts/edSqJqFm+CQdP33RVRZ0e0c0Feqoj4h
QvoGE5Tx5zCCA0wwggK1oAMCAQICED3elb3wBVIspmKnMjkN7QQwDQYJKoZIhvcNAQEFBQAw
YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x
LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDMy
OTE1MDI1NVoXDTA4MDMyODE1MDI1NVowejEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1l
bWJlcjEuMCwGCSqGSIb3DQEJARYfZW5yaWNvLm1hcm9jY29AdGVsZWNvbWl0YWxpYS5pdDEn
MCUGCSqGSIb3DQEJARYYZW5yaWNvLm1hcm9jY29AZ21haWwuY29tMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEAto0Sdza0i+90O/V44RqhNEp9D1ULsAiWk9oao9CzJnWmcZ7x
0cuay5yX1EC+V+3U+XgUIqh2m5K4+f99Yg0cTGH4ZoC9ScaIgg/UmT6Obf9Z3S0kHIZGB/oC
i6TqsspMTm/8EWV1sJ1Kl1P/WG3HkwT1qhjFD9WD8JT5futM8JHm0UXyc4SqIUJQVwj3PHLi
d962BSmiiYAnC3Jf3ptgP+55opwIyNJpRy2kXHL8VGsRqUMxAbK/o7NzK6BlVRtjGYehmpQf
bu+R/63QMx/j8sQ+t86cmoIC1BsBZIQklyfqQMa2NMMWz61tAW8Qyq0mG7MjLDi/Tyj/mloj
cOKrVwIDAQABo2cwZTAPBgNVHQ8BAf8EBQMDB/mAMEQGA1UdEQQ9MDuBH2Vucmljby5tYXJv
Y2NvQHRlbGVjb21pdGFsaWEuaXSBGGVucmljby5tYXJvY2NvQGdtYWlsLmNvbTAMBgNVHRMB
Af8EAjAAMA0GCSqGSIb3DQEBBQUAA4GBADcnmbcagO3RNa07bgcYwRfjhVsy28P97RlII98d
DEXfjsu1sLTLIO29uKhXWYHyOhWuPjysYLr9wnGz7GpnoDUQRR2xp4XdP4XyZmHwFh5mjV6o
XODLS5xImIUmR/fyG2z951KomoWb4JB0/fdFVFnR7RzQV6qiPiFC+gYTlPHnMYIDcTCCA20C
AQEwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkg
THRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECED3e
lb3wBVIspmKnMjkN7QQwCQYFKw4DAhoFAKCCAdAwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEH
ATAcBgkqhkiG9w0BCQUxDxcNMDgwMTIyMDgwMjQzWjAjBgkqhkiG9w0BCQQxFgQUz/1fok7r
e0vu+fUjOV5cXEGbEX0wXwYJKoZIhvcNAQkPMVIwUDALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMIGFBgkrBgEEAYI3EAQxeDB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUg
Q29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1h
aWwgSXNzdWluZyBDQQIQPd6VvfAFUiymYqcyOQ3tBDCBhwYLKoZIhvcNAQkQAgsxeKB2MGIx
CzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSww
KgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQPd6VvfAFUiym
YqcyOQ3tBDANBgkqhkiG9w0BAQEFAASCAQAx00SmTX78+ZR6FUgp8e7lcZ6HU4+oCzWJ3rJq
KGqg7wyhwPDi1CXIPJUq7lOY/AR1iyfQufOputl9q8h2CBOglFyG+YdtOMMS5VWs+pde3dIW
g7wU4mP+RTrmenxCnqD6kR8FTta6qtkvHtNMk+D5Fz0JRQGw7dLPpcZYmQrihHq9pP3RiPW9
iPUhQvsRHeX9ZMUOv9nEgFw9C1M7Pmeg53TBWriyqUzcFHxjUBFwH9D7dK14W7wN18yKv/y8
2nCquH27dA7mhAfo7E+GBHOYYLMj162F+ZLuUr6YNYngB0SoxAo7PKiDknWq/9uMer/Lq9PV
N9ifils6lv4DVR1SAAAAAAAA
--------------ms000901040501020202090907--


--===============0287993142==
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://www1.ietf.org/mailman/listinfo/p2psip

--===============0287993142==--




From p2psip-bounces@ietf.org Tue Jan 22 04:38:12 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHFa7-0004zL-A6; Tue, 22 Jan 2008 04:38:11 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHFa5-0004zG-9d
	for p2psip@ietf.org; Tue, 22 Jan 2008 04:38:09 -0500
Received: from szxga02-in.huawei.com ([61.144.161.54])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHFa3-0002ml-1I
	for p2psip@ietf.org; Tue, 22 Jan 2008 04:38:08 -0500
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 <0JV100J0MHEA7W@szxga02-in.huawei.com> for
	p2psip@ietf.org; Tue, 22 Jan 2008 17:37:23 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JV1003E4HE833@szxga02-in.huawei.com> for
	p2psip@ietf.org; Tue, 22 Jan 2008 17:37:22 +0800 (CST)
Received: from j36340 ([10.164.9.45])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JV10051OHE61Z@szxml04-in.huawei.com> for
	p2psip@ietf.org; Tue, 22 Jan 2008 17:37:20 +0800 (CST)
Date: Tue, 22 Jan 2008 17:37:18 +0800
From: JiangXingFeng <jiang.x.f@huawei.com>
To: 'P2PSIP Mailing List' <p2psip@ietf.org>
Message-id: <003a01c85cda$61991f30$2d09a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Office Outlook 11
Thread-index: Achc2mE+N3Ev8YYNRpCsDNPfo2q5cg==
X-Spam-Score: 1.4 (+)
X-Scan-Signature: bec09d1709ba59869cec93c1a1c207e5
Subject: [P2PSIP] Choice of STUN peer or TURN peer
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1776720240=="
Errors-To: p2psip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1776720240==
Content-type: multipart/related;
	boundary="Boundary_(ID_7WstEYdk/Itu8fvSo0uArw)"

This is a multi-part message in MIME format.

--Boundary_(ID_7WstEYdk/Itu8fvSo0uArw)
Content-type: multipart/alternative;
	boundary="Boundary_(ID_mk2ZcZc5YrfDvb7iIlxj2w)"


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

Hi, all:

 

In order to make the peers serve each other, some peers with special
capabilities could be exploited to play the STUN/TURN server role for other
peers who are behind NAT. Guys in P2PSIP community has agreed with that peer
behind NAT should seek help from other peers, not centralized STUN/TURN
server.

 

But which kinds of peers are qualified for playing STUN/TURN server? Of
course, Peers on the public internet could take this responsibility. I also
learned from the list that peers behind p2p-friendly NAT (with end-point
independent mapping and filtering behavior) also could do the same work. But
from my point of view, ICE negotiation procedure may fail if choosing this
kind of peer as STUN/TURN server.

 

Let's show an example: 



Peer A and peer B want to communicate directly. NAT2 is a p2p-friendly NAT.
So peer C would be considered as a candidate STUN server. If peer A choose
the Peer C as its STUN server, peer A will get a mapping on the NAT1 which
is in the address realm of private network. And Peer A will tell peer B this
server reflexive address. But peer B could not reach it because it is in
different address realm.  

 

Am I missing something? Comments are appreciated!

 

Regards!

--

Jiang XingFeng

 

 


--Boundary_(ID_mk2ZcZc5YrfDvb7iIlxj2w)
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="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]-->
<style>
<!--
 /* Font Definitions */
 @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:SimSun;
	panose-1:2 1 6 0 3 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:KaiTi_GB2312;
	panose-1:2 1 6 9 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:"\@DotumChe";
	panose-1:2 11 6 9 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;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	line-height:150%;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";
	layout-grid-mode:line;}
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:l8 level1 lfo35;
	font-size:16.0pt;
	font-family:Arial;}
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:l8 level2 lfo35;
	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:l8 level3 lfo35;
	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:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	line-height:150%;
	text-autospace:none;
	font-size:9.0pt;
	font-family:Arial;
	layout-grid-mode:line;}
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:l6 level9 lfo5;
	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:l6 level8 lfo5;
	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;
	line-height:150%;
	text-autospace:none;
	font-size:18.0pt;
	font-family:Arial;
	layout-grid-mode:line;}
p.a5, li.a5, div.a5
	{margin:0cm;
	margin-bottom:.0001pt;
	line-height:150%;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";
	layout-grid-mode:line;}
p.a6, li.a6, div.a6
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	line-height:150%;
	text-autospace:none;
	border:none;
	padding:0cm;
	font-size:9.0pt;
	font-family:Arial;
	layout-grid-mode:line;}
p.a7, li.a7, div.a7
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:18.0pt;
	line-height:150%;
	text-autospace:none;
	border:none;
	padding:0cm;
	font-size:9.0pt;
	font-family:Arial;
	layout-grid-mode:line;}
p.a8, li.a8, div.a8
	{margin:0cm;
	margin-bottom:.0001pt;
	text-indent:21.0pt;
	line-height:150%;
	text-autospace:none;
	font-size:10.5pt;
	font-family:Arial;
	color:blue;
	layout-grid-mode:line;
	font-style:italic;}
span.a9
	{font-family:SimSun;
	color:black;
	font-weight:bold;}
span.aa
	{font-family:SimSun;
	color:black;
	font-weight:bold;}
 /* Page Definitions */
 @page
	{mso-endnote-separator:url("cid:header.htm\@01C85D1D.6F536430") es;
	mso-endnote-continuation-separator:url("cid:header.htm\@01C85D1D.6F536430") ecs;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:65.6pt 126.65pt 72.0pt 126.65pt;
	mso-footer:url("cid:header.htm\@01C85D1D.6F536430") f1;
	layout-grid:15.6pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:171800355;
	mso-list-template-ids:-1278163850;}
@list l0:level1
	{mso-level-text:%1;
	mso-level-tab-stop:21.6pt;
	mso-level-number-position:left;
	margin-left:21.6pt;
	text-indent:-21.6pt;}
@list l0:level2
	{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 l0:level3
	{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 l0:level4
	{mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l0: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 l0: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 l0: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 l0: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 l0: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;}
@list l1
	{mso-list-id:191647984;
	mso-list-template-ids:345692754;}
@list l1:level1
	{mso-level-number-format:alpha-upper;
	mso-level-text:\9644\5F55%1;
	mso-level-tab-stop:64.15pt;
	mso-level-number-position:left;
	margin-left:64.15pt;
	text-indent:-21.6pt;}
@list l1:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:71.35pt;
	mso-level-number-position:left;
	margin-left:71.35pt;
	text-indent:-28.8pt;}
@list l1:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:78.55pt;
	mso-level-number-position:left;
	margin-left:78.55pt;
	text-indent:-36.0pt;}
@list l1:level4
	{mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:89.35pt;
	text-indent:-34.0pt;}
@list l1:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:89.35pt;
	text-indent:-34.0pt;}
@list l1:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:89.35pt;
	text-indent:-34.0pt;}
@list l1:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:89.35pt;
	text-indent:-34.0pt;}
@list l1:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:114.55pt;
	mso-level-number-position:left;
	margin-left:114.55pt;
	text-indent:-72.0pt;}
@list l1:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:121.75pt;
	mso-level-number-position:left;
	margin-left:121.75pt;
	text-indent:-79.2pt;}
@list l2
	{mso-list-id:541409008;
	mso-list-template-ids:-249166292;}
@list l2:level1
	{mso-level-number-format:alpha-upper;
	mso-level-text:\9644\5F55%1;
	mso-level-tab-stop:21.6pt;
	mso-level-number-position:left;
	margin-left:21.6pt;
	text-indent:-21.6pt;}
@list l2:level2
	{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 l2:level3
	{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 l2:level4
	{mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l2: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 l2: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 l2: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 l2: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 l2: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;}
@list l3
	{mso-list-id:818422186;
	mso-list-template-ids:1344984950;}
@list l3:level1
	{mso-level-text:%1;
	mso-level-tab-stop:21.6pt;
	mso-level-number-position:left;
	margin-left:21.6pt;
	text-indent:-21.6pt;}
@list l3:level2
	{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 l3:level3
	{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 l3:level4
	{mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l3: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 l3: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 l3: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 l3: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 l3: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;}
@list l4
	{mso-list-id:838886720;
	mso-list-template-ids:-819953982;}
@list l4:level1
	{mso-level-text:%1;
	mso-level-tab-stop:21.6pt;
	mso-level-number-position:left;
	margin-left:21.6pt;
	text-indent:-21.6pt;
	mso-ansi-font-size:18.0pt;
	mso-bidi-font-size:18.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l4:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:28.8pt;
	mso-level-number-position:left;
	margin-left:28.8pt;
	text-indent:-28.8pt;
	mso-ansi-font-size:15.0pt;
	mso-bidi-font-size:15.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l4:level3
	{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;
	mso-ansi-font-size:12.0pt;
	mso-bidi-font-size:12.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l4:level4
	{mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l4: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;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l4: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;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l4: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;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l4: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;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l4: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;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l5
	{mso-list-id:942373150;
	mso-list-template-ids:67698717;}
@list l5:level1
	{mso-level-text:%1;
	mso-level-tab-stop:21.25pt;
	mso-level-number-position:left;
	margin-left:21.25pt;
	text-indent:-21.25pt;}
@list l5:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:57.25pt;
	mso-level-number-position:left;
	margin-left:49.6pt;
	text-indent:-1.0cm;}
@list l5:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:96.55pt;
	mso-level-number-position:left;
	margin-left:70.9pt;
	text-indent:-1.0cm;}
@list l5:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:135.8pt;
	mso-level-number-position:left;
	margin-left:99.2pt;
	text-indent:-35.4pt;}
@list l5:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:175.05pt;
	mso-level-number-position:left;
	margin-left:127.55pt;
	text-indent:-42.5pt;}
@list l5:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:214.3pt;
	mso-level-number-position:left;
	margin-left:163.0pt;
	text-indent:-2.0cm;}
@list l5:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:253.55pt;
	mso-level-number-position:left;
	margin-left:191.35pt;
	text-indent:-63.8pt;}
@list l5:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:292.8pt;
	mso-level-number-position:left;
	margin-left:219.7pt;
	text-indent:-70.9pt;}
@list l5:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:332.1pt;
	mso-level-number-position:left;
	margin-left:255.1pt;
	text-indent:-85.0pt;}
@list l6
	{mso-list-id:1123964682;
	mso-list-template-ids:301907670;}
@list l6: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 l6: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 l6: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 l6: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 l6: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 l6: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 l6: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 l6: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 l6: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 l7
	{mso-list-id:1380013528;
	mso-list-template-ids:-1435872280;}
@list l7:level1
	{mso-level-number-format:none;
	mso-level-text:"\9644\5F55A ";
	mso-level-tab-stop:21.25pt;
	mso-level-number-position:left;
	margin-left:21.25pt;
	text-indent:-21.25pt;}
@list l7:level2
	{mso-level-text:"A\.%2";
	mso-level-tab-stop:49.6pt;
	mso-level-number-position:left;
	margin-left:49.6pt;
	text-indent:-1.0cm;}
@list l7:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:70.9pt;
	text-indent:-1.0cm;}
@list l7:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:99.2pt;
	mso-level-number-position:left;
	margin-left:99.2pt;
	text-indent:-35.4pt;}
@list l7:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:127.55pt;
	mso-level-number-position:left;
	margin-left:127.55pt;
	text-indent:-42.5pt;}
@list l7:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:163.0pt;
	mso-level-number-position:left;
	margin-left:163.0pt;
	text-indent:-2.0cm;}
@list l7:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:191.35pt;
	mso-level-number-position:left;
	margin-left:191.35pt;
	text-indent:-63.8pt;}
@list l7:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:219.7pt;
	mso-level-number-position:left;
	margin-left:219.7pt;
	text-indent:-70.9pt;}
@list l7:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:255.1pt;
	mso-level-number-position:left;
	margin-left:255.1pt;
	text-indent:-85.0pt;}
@list l8
	{mso-list-id:1666475049;
	mso-list-template-ids:-28945502;}
@list l8:level1
	{mso-level-style-link:"\6807\9898 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 l8:level2
	{mso-level-style-link:"\6807\9898 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 l8:level3
	{mso-level-style-link:"\6807\9898 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 l8:level4
	{mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l8: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 l8: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 l8: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 l8: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 l8: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;}
@list l9
	{mso-list-id:1916042858;
	mso-list-template-ids:-648263936;}
@list l9:level1
	{mso-level-number-format:alpha-upper;
	mso-level-text:\9644\5F55%1;
	mso-level-tab-stop:21.6pt;
	mso-level-number-position:left;
	margin-left:21.6pt;
	text-indent:-21.6pt;}
@list l9:level2
	{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 l9:level3
	{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 l9:level4
	{mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l9: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 l9: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 l9: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 l9: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 l9: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;}
@list l10
	{mso-list-id:2114861838;
	mso-list-template-ids:-433129230;}
@list l10:level1
	{mso-level-number-format:none;
	mso-level-text:"\9644\5F55A ";
	mso-level-tab-stop:21.25pt;
	mso-level-number-position:left;
	margin-left:21.25pt;
	text-indent:-21.25pt;}
@list l10:level2
	{mso-level-text:"A\.%2";
	mso-level-tab-stop:49.6pt;
	mso-level-number-position:left;
	margin-left:49.6pt;
	text-indent:-1.0cm;}
@list l10:level3
	{mso-level-text:"%1A\.%2\.%3";
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:70.9pt;
	text-indent:-1.0cm;}
@list l10:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:99.2pt;
	mso-level-number-position:left;
	margin-left:99.2pt;
	text-indent:-35.4pt;}
@list l10:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:127.55pt;
	mso-level-number-position:left;
	margin-left:127.55pt;
	text-indent:-42.5pt;}
@list l10:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:163.0pt;
	mso-level-number-position:left;
	margin-left:163.0pt;
	text-indent:-2.0cm;}
@list l10:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:191.35pt;
	mso-level-number-position:left;
	margin-left:191.35pt;
	text-indent:-63.8pt;}
@list l10:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:219.7pt;
	mso-level-number-position:left;
	margin-left:219.7pt;
	text-indent:-70.9pt;}
@list l10:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:255.1pt;
	mso-level-number-position:left;
	margin-left:255.1pt;
	text-indent:-85.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="3074" />
</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=purple style='text-justify-trim:punctuation'>

<div class=Section1 style='layout-grid:15.6pt'>

<p class=MsoPlainText><font size=1 face=Arial><span lang=EN-US
style='font-size:9.0pt;line-height:150%'>Hi, all:<o:p></o:p></span></font></p>

<p class=MsoPlainText><font size=1 face=Arial><span lang=EN-US
style='font-size:9.0pt;line-height:150%'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoPlainText><font size=1 face=Arial><span lang=EN-US
style='font-size:9.0pt;line-height:150%'>In order to make the peers serve each other,
some peers with special capabilities could be exploited to play the STUN/TURN server
role for other peers who are behind NAT. Guys in P2PSIP community has agreed with
that peer behind NAT should seek help from other peers, not centralized STUN/TURN
server.<o:p></o:p></span></font></p>

<p class=MsoPlainText><font size=1 face=Arial><span lang=EN-US
style='font-size:9.0pt;line-height:150%'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoPlainText><font size=1 face=Arial><span lang=EN-US
style='font-size:9.0pt;line-height:150%'>But which kinds of peers are qualified
for playing STUN/TURN server? Of course, Peers on the public internet could take
this responsibility. I also learned from the list that peers behind p2p-friendly
NAT (with end-point independent mapping and filtering behavior) also could do the
same work. But from my point of view, ICE negotiation procedure may fail if choosing
this kind of peer as STUN/TURN server.<o:p></o:p></span></font></p>

<p class=MsoPlainText><font size=1 face=Arial><span lang=EN-US
style='font-size:9.0pt;line-height:150%'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoPlainText><font size=1 face=Arial><span lang=EN-US
style='font-size:9.0pt;line-height:150%'>Let's show an example: <o:p></o:p></span></font></p>

<p class=MsoPlainText><font size=1 face=Arial><span lang=EN-US
style='font-size:9.0pt;line-height:150%'><img width=455 height=268
id="_x0000_i1028" src="cid:image003.gif@01C85D1C.EDBF8C00"><o:p></o:p></span></font></p>

<p class=MsoPlainText><font size=1 face=Arial><span lang=EN-US
style='font-size:9.0pt;line-height:150%'>Peer A and peer B want to communicate directly.
NAT2 is a p2p-friendly NAT. So peer C would be considered as a candidate STUN server.
If peer A choose the Peer C as its STUN server, peer A will get a mapping on the
NAT1 which is in the address realm of private network. And Peer A will tell peer
B this server reflexive address. But peer B could not reach it because it is in
different address realm. &nbsp;<o:p></o:p></span></font></p>

<p class=MsoPlainText><font size=1 face=Arial><span lang=EN-US
style='font-size:9.0pt;line-height:150%'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoPlainText><font size=1 face=Arial><span lang=EN-US
style='font-size:9.0pt;line-height:150%'>Am I missing something? Comments are appreciated!<o:p></o:p></span></font></p>

<p class=MsoPlainText><font size=1 face=Arial><span lang=EN-US
style='font-size:9.0pt;line-height:150%'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoPlainText><font size=1 face=Arial><span lang=EN-US
style='font-size:9.0pt;line-height:150%'>Regards!<o:p></o:p></span></font></p>

<p class=MsoPlainText><font size=1 face=Arial><span lang=EN-US
style='font-size:9.0pt;line-height:150%'>--<o:p></o:p></span></font></p>

<p class=MsoPlainText><font size=1 face=Arial><span lang=EN-US
style='font-size:9.0pt;line-height:150%'>Jiang XingFeng<o:p></o:p></span></font></p>

<p class=MsoPlainText><font size=1 face=Arial><span lang=EN-US
style='font-size:9.0pt;line-height:150%'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoPlainText><font size=1 face=Arial><span lang=EN-US
style='font-size:9.0pt;line-height:150%'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

--Boundary_(ID_mk2ZcZc5YrfDvb7iIlxj2w)--

--Boundary_(ID_7WstEYdk/Itu8fvSo0uArw)
Content-id: <image003.gif@01C85D1C.EDBF8C00>
Content-type: image/gif; name=image003.gif
Content-transfer-encoding: base64
Content-disposition: attachment; filename=image003.gif

R0lGODlhxwEMAXcAMSH+GlNvZnR3YXJlOiBNaWNyb3NvZnQgT2ZmaWNlACH5BAEAAAAALAAAAADD
AQwBhwAAAAAAAAAAMwAAZgAAmQAAzAAA/wAzAAAzMwAzZgAzmQAzzAAz/wBmAABmMwBmZgBmmQBm
zABm/wCZAACZMwCZZgCZmQCZzACZ/wDMAADMMwDMZgDMmQDMzADM/wD/AAD/MwD/ZgD/mQD/zAD/
/zMAADMAMzMAZjMAmTMAzDMA/zMzADMzMzMzZjMzmTMzzDMz/zNmADNmMzNmZjNmmTNmzDNm/zOZ
ADOZMzOZZjOZmTOZzDOZ/zPMADPMMzPMZjPMmTPMzDPM/zP/ADP/MzP/ZjP/mTP/zDP//2YAAGYA
M2YAZmYAmWYAzGYA/2YzAGYzM2YzZmYzmWYzzGYz/2ZmAGZmM2ZmZmZmmWZmzGZm/2aZAGaZM2aZ
ZmaZmWaZzGaZ/2bMAGbMM2bMZmbMmWbMzGbM/2b/AGb/M2b/Zmb/mWb/zGb//5kAAJkAM5kAZpkA
mZkAzJkA/5kzAJkzM5kzZpkzmZkzzJkz/5lmAJlmM5lmZplmmZlmzJlm/5mZAJmZM5mZZpmZmZmZ
zJmZ/5nMAJnMM5nMZpnMmZnMzJnM/5n/AJn/M5n/Zpn/mZn/zJn//8wAAMwAM8wAZswAmcwAzMwA
/8wzAMwzM8wzZswzmcwzzMwz/8xmAMxmM8xmZsxmmcxmzMxm/8yZAMyZM8yZZsyZmcyZzMyZ/8zM
AMzMM8zMZszMmczMzMzM/8z/AMz/M8z/Zsz/mcz/zMz///8AAP8AM/8AZv8Amf8AzP8A//8zAP8z
M/8zZv8zmf8zzP8z//9mAP9mM/9mZv9mmf9mzP9m//+ZAP+ZM/+ZZv+Zmf+ZzP+Z///MAP/MM//M
Zv/Mmf/MzP/M////AP//M///Zv//mf//zP///wECAwECAwECAwECAwECAwECAwECAwECAwECAwEC
AwECAwECAwECAwECAwECAwECAwECAwECAwECAwECAwECAwECAwECAwECAwECAwECAwECAwECAwEC
AwECAwECAwECAwECAwECAwECAwECAwECAwECAwECAwj/AAEIHEiwoMGDCBMqXMiwocOHECNKnFjw
iiCLGCUKAnBxI8WPIEOKHEmypMmTKFOqXMmSIUZBglrFnNlR4UuLNGFabMmzp8+fQIMKHUr0Ic6Y
rVphS6qUqUyYBmHCTLqUqlOpEa9cKcq1q9evYMOKxbm0bFOzaHUKnHq2Ldqkag3elHpTrN27ePPq
zXvFqVW/TQF39FuVMGCZBaUidVr4qce9kCNLnkzZ4ZW3mN22lZm5c1uPZDVnfrq1sunTqFMTRVq4
NVPXf+HGhh249sXZr3PHvlhate/fwIMbteq5eGBBxjuzFs3cbKveBy+uLf1YuPXr2LtaNAy4se7D
3Q97/5cJfnxtv9XpKp6qeGf29/Djo4yZvLn9+s7v68f2crln0tXJJ+CABMoFE20IfpcgbgzWtqCD
37H1IGw6BVjghRgC1x9x+3WIn4f6Pcfhh85Bl+GJKFLG1lOxMSbei+HFyN2MLoa34nnf1SiYhSn2
6KNXt4FIopBEDmmkZjz+qOSSLYXW4IQKRvmklBBOaWWVWLqWJJNcdikSfUWGeeSYYna4pZdopskQ
mDLq6GaOcLYYJ45y1knnnebliZiafPaZ0IFlkilooISmdaafiDJpEZRXMpollY5GCumkVEGV6KVo
9lXopoN2WuZzmIbK5WJv2qlnm3OeSmOqMK5q6mHSif8qa4/IcWqrp7h6aOmsvF64naSNUvposMQO
a+yCh/aqrHCA5ursrdBmluyy1Pq2mKql4tlqttiyiuqr355nYrXkBndZtOg+q+6e5bYLHJvHCgts
vMXOa29SL7mrL2q/puvvuoIuVuG+BEumKbfbeuuqtuF2C+7C5pEKV6wFVywWcpoC/O/GnlJs8cdF
CVyvvCSPbDK9KNMGKsgsB5UxviNyLLPGH67c8s0sbYdewwk/jDDPQEPcM8PojRtUAAHgTC2YNM/s
9KDTrhTAFSzMwAILAWCNNdJKIwroyYUhLbaUAbgWQCtnP5k2bGWXDOHZ9xIbdUoBICBQIq3cnTdH
SXf/3efLnba9FNyaEV6W4PYZ3pbiYyLetM1H901LIgJNfnfffqsp4dB6pp1U257DfTbSTI1eett+
gY522mOvjrrpZZN++uiyO0z0m3OjxMLeALTiikB7Y555pjE3bpbohw+uOjaxD66U42g/j3z0zCe/
uvLOV/+89k1XZbRPLFgOgPiWCz98l/DG7brs0X/+eVWqs44g66W/Tz31a+fvvvuEg01p7ifJmt4G
CIAZmO98iipekaDHveXhT3uMa8r0ICg9sWXvfqITW/NkBkCTCHB8lAOhQK5wQAQq6UY+g1P/6ue8
9jGPf8+LEf1aSL/Uwa90Laxf0H7GFKR8rydT8x3w/37XO1ewwIRpYlqg1nYWwYFueRucoAS3R8UJ
OpBwVuReusR2RKIEYAbkC+HkZoBENJHqXjDxXGs0+D7SOS90TKRKDdsnu9a9MIZ4ZB7SsOc2Rz1H
gyVsSQC8QEC8CQRrZfRSrcYkle49LV27EhsAApkSFpQmjIekZCJRBC8ekud2CvNkKEeZwlJOzCCA
BGLvBiLEVdptk+gj0icdSUtIeuwgGpyk1LyASRB2EZaKSh+VZtnHYvrvmChzDFYaAkhNUiQAiWgm
13QJTC4B7j7+eWQtjVShmZSlg5J0JkSgWbkQTvOX1VzSVLrVSVKC0pS2iyfnttXBSeZSJElr5TR9
J//OdGKoX55R4ja1aSvIReSeH0na5JAWxn7601c30lKtkKm+ihozZT38oUNSKRHaGRIAH3XoQ/9Z
vGsOtD7RMIUyPrHSln5iGKZIqUxjOrNd4XOaD2FBNKUpEJGOFENS2dkO3SlPZQyDF7yohVKXytSm
OtWpSI0qUofx0mFY1arKUClNwaXRiSB0IflkJRFbEc2fJnFD5zopc5SBiaQqlapZxUxMtZpSl8L1
pZgYRlvzGomn+nWpvNirXuGKCUyoRJIKESA5RTg+EpqVT6XpF0WNqYyk8mIYyrjovOqq0qpS9ahR
/atfAaBUgdTCq1wrIQLyRjoC+vSxKUorQbGh0r7/1iKzah3THj5xWtL2trS+9W1pgctMex7wCuYU
m/jQCdskEnWeMqqsUnlhiqHCE7qr6qBTOzpNAfKziKRzbHMhq0CafcKyn4jGbMtUT4I8daMaPOJC
x6dc5o7XS4vSLMmkywvc6neywWqvQrbLkFxKMqT35ZNA/aWMWlA3t5u65UmauhCq3VN8r00wUIVm
XaWYIqnDeG6H5YkqAU9kqQiZWu8SYTWxXWEQ9tWwNRfsrA/fdr1kasXu3BMUFBckABsRXyK2htMA
IkBrAtDakbOW5KwtmQVNZsGTozxlJSNZazIWiWQxyhkF8ZYX6gUwl7H0SVhlrast8XFPY+LajSDW
/yQscEUrJpeUycmZznNOxJ3xluc911nPef6zn+eMyCyDBKBEWnA0kooJCNesQnWhJldOi2JoSpOc
PB2JTifH6UR0+tOeDjWoRy3qUndavIb+CE5EWSnADOOtrH6nrLFlU4JkmCVKbcMQh5hP8311IuED
tJ37TOxhG1vYyN6zsvsc41Q/pG9BGlKXscHbWsDU0SAy6I9vvZJa9BUTZC2nQkvI0YhEgg6fILW6
Tc3udYMazc5OMea2srkGKTMplhWzRe2tlcRyeyUlwESuPxE81iYkaW9mSFN5QdY/OzzQEMezxPk8
8YfTotDxHucBO7LqmQCIx6aIxIP/lc0c8/jgdv8JAC020tdIlFPSBy/3QZ4qCXe3++Y2P/W/ZVzk
P0XaINPFbqwldt1TblQsfUMbAGxrbVP49NcD8aspaDHnYlfd2FcXdtbvvPWrNzvj8iZJaWULsHV+
6uTM3HkAK5f0JLjV5Qf9tdRxTvec3xzeYIc5SHz8tTE/aDA6epBjnimWnTYzb7ZFLWKlLuiII7vx
Ex/0seuM8byHfSTEXUvZQdORkmvmOTVJqNpNMt9eCre3cUdaCZiuVEzY/fV1DzWqLY/K0Qs3OuUR
utET05/19IckPS9KF1vZSlRTmLurXyq45wzIZR/b+cgGZLH1/HXLB//Ema8IjWWJdoRIJyN0+8r/
B3s5e9MydSIlKAEdph5qaHJa5bFXN/wXym68p/r6EVGzQuqdsmWGBf9C8VECyDszd3wQsVqBBn+f
w2djQ2etQwujg2fQ9GdnI3GVR3v2tHfD9RCdV15uAWl3AYBB0Uvio3AGuBCb1n6iBn/uF02eNn8s
OH8v+GkyODnlR3siOGD6BxEbAh4TA355kYM8oWKrtGsAcIEmmH0GEWx31nzMR3UQKGcViDZ6pnJZ
N4VUB01cd3EYaGvctoMfwXFi+HOQYXsgYUkvx1jVp4NKOBApSH+gBkgvqEFwuII0+G5dOBBCWIBq
YoYhMYAE9BHnt4R+Bn+FeGwVKGxpM2wTmGeJ/0h5fghMe1gQg9iHXKFQYpSJYod6blhqLdhpLeh+
MFiH7weK9ReJsDSJp8eJllgUATAIRqhPm1gQTMh80Cc2ishQVYiIbPR8a5hle3iCfqKKKIEAHtFL
v/gQG3iE8deMsGeDXZiDwpgoxOhBILU3A4iKwIWAFed4Fkdx4PiNFoeEziaNrCgq1VgSmJiG81US
5/eGzhiP63aD9ydObRgqqPhsXnAFXkBIRpiPpVWLUGh1UKh1BbmFBEmQyThe5niOspKOmsZFgLQ1
KwGPzyiP9Zd35kguEMkSHekQceZ4kvd40wd54Ch55MhzmnSPvJKPkGGRGHmROhdvIgiGy/KRqP8h
kMk2fdDXkzzJbBkHgDZJLS6pFzApkzGZCPYHTEzVBivpkOVSlHjBjeHojVbZjVhJcSk5Uk5VQpVI
MDhZGUeZlBdJj1xJYJTIku0SlpQhkF03kFh3kFeXkHG5kNVyaXiZlwFQAk/llGKTfElQApnmLmwp
GXp5mIiJmCwzTYB4jYWEjdhoCk/FCwNUCwRXSHaJj3l4ItNEgpJTVhiWXKynVFxDC6BwWp65L4W5
mWJJfGP1O0hDRAEwVgjXSnzJVJ/QO0mTVHvjmkcIllLJmiFIgpSjcn2zWBA4SRgWAEmQV6bAdq82
DJooQq+kL6spnGXYN41ZVhOYNIZkaXqDNH3/MUABAFzbmZnoGJzYKX6fyY7HCZrwqVCI1FCklZuM
RT7q+SP5uZ5dsTtiBTw99V2Yw1GxCaCTJJmUyTvEl0kFs5/86YrEqZzFiWn4iYviBgBJxY6aiAAO
iiLX+aBIp52QeTnhCVIiak+C4J2stZe10AbbiY3omZ4gmh2dOZ0RKkKDZKMid5822qEp4qMzCj6+
WUSx+JoF9EVFylufYKRESqQx+pBBeh2JOaXN5G1U+jEfGqWqUZNQmTlAqqUh+JSp+KVgChbSKIlk
WqZewaXVlKZq6kXOpJbnk6XwBXWJlWL4xJo52FfpRKfFZWt5GhJu2jJCKKdz+qW+podFllqS/xZO
OIVYCNdTixqp0dhPXVpGiPpjPaWHm5qBx8mpAwqqn9qpxzmoWGqpl4pEiFpuodqo1JSonapLrfqq
nIqDDmWoJgSks2pc3QWqijqqvEqpwRqrploxhZqqiaSrgBqrtSqrqOSqy6p30Ap8WpM11lqt2Hqt
2pqt3Lqt1solwYismOqjwjOro8qormqu0wqsqIgTieAFMDEIUvGu8Tqv8CoI8goT9Iqv9lqv+nqv
XlCsZmqP4pqsHQqrxuWFziqppfqrzJpwdgoSiUCWFEsLXvCk2DGJBWuwZVgZQPZ8PwmyIruTx5ai
SqKx9yWwteenHjmxSPmyonaxdjGGCTEXov+njCmrssLhBeJ4lVWZld+YCFjgAkT7FR34gwESVBMj
YRVRe8q4sRxbLi5bsfJItEQ7AC7AFaGBGZCmQAbVe/mSgQ6Bq5IYlYIQl3RpkGmLkHb2BVb7tqtB
dHQit+exEavGHYKwlQgBtZvEspw5tTB7kW77tkUrFIj2H4vUHIe7GVOjUdVBtm0KRBH7rDF3QAN6
Twl3EoIwkpwrkp4beXM2tIRbuEBxLf8lG8YSK53ne1sBuZErSNF6p3j6sJZLrCoBuFRrd4qAtYTr
Ms1SUGZiUoGxB7VgWMConuXqsJtqYLIrqZS7q+p4tiQ7vT45sss2uFZbukobayS2IwvzaqH/l2B+
+7C2K7b9FKoIC73Ah7tyGLhzWIOJoAik6xMRRVAeuBTRYG27l7KChFCtqr7bBqgIm7AqwbMJKIE/
m8AWt4iLyGdl5RNbtm9+Bym8ZQqFYWJzCruUS6vMinIc3KwAPBLsa4fvC4pIM4M1mMKfJrP0i2NE
EliGIr7BSW61GsKaOqzk28HAJ71NWJAVaIVRGD1ZuFNwGU1ziXUm2xPt9CqtExiecydP/FyvFmbH
oWF+S8Ok2qwbPMDJq8MjAU2eqEEqCIejCL8Q6G4BS6VqjFhktx8OhB8MBCL5G2JvoW1mdcXyZq7C
6oW1q8UEnBKbe8CPB0gLxUaNyIgnCXGD/9BdDWu+jczIzktNpnsl8mNBNRQ7e2RB11MySBUlGDw8
4zsgIxyHpqbCpXyHMYuxEfG7cLxHGFRFTURBWpQcFdwZS5mKvfKxiuh8s2mLVCiFRvx8hmiIeZbE
TTJU/RM6NPQ5pMM6TQwuCGonTHvHuTzKpayLhSyK8ofNqazEiQvHxzNFfIQ8b9whr1YcQNhcoSwf
Bgy0Ptuz7vzAPDHJxqJG+iM9EtTMT6RGVDLHj6IeDKmzp4G77vuMLDzP24dtaNHJxbFItfZT+TiY
fyxzC1vD/ju5O4y2Gq22G822WmfMAJC1C1G0cCvSf8IiI6Z7PiOZwyBP09ynh7XFOby8N//cxV18
WASdu/HHwqPb0z7d03JRKQntwg2mXkPyyTjjpwNc0dAKq4l60yoRyKA71YlM1SaZFIssEEAd0iI9
vwYxulqNBROMGysEJWWtG508Mkh9My651DMNrFkswLGbEjld0Dv9Sy4wACRB0nntAlgwCIOAK3Fc
HIPtYZY5JreMQHTq1jgc1zWsqRSNErpcvdQbspU9OSCdEn+NBaLrAoNwO2zEzK5DRzHUOmMjP4dR
1BxWNLC12Df82jUd23LtE2Bs1zJ50FE9UViQBUT7zYUzReScPM3jRA00y2fRVmKS2Iot2bDN1Mvq
1JANFO2swO9c3d0ozyrxMkwxtGJNNvD/o0fNDNzREzoYxD6uYW1oFNBr99pwrcXq+tg/Udc6jcaq
7BCsrBSCMLSf7Ry1gkX3o0WmU9zE/d9N0WD+ddTKfajrvW0A7GuT+mYHy8NHzNEU7tEWXnWZDchw
IrqfrbR3REf6LEftM9ojPkeB4WDP9dB3LNBleAUz4AUz4OIwjgUvHuM1TuMwLuMzgOM2PuM1ruM8
LuNXwxPCWxWie7/pUsvZFhfii4+P/OSRDMmOHOXtHdWBlxTcrW/CguLGokzdx5BvShBFHhND69uO
NMUdQkxrDcphPhArcsFY7tkpHTT+3L1wAYxtThD1ViuuQLRYsE1tZcHJfbx5Lubs8ReD/+DXWj4b
LK0+L73ihR4V35zoLnDmkWDUyb3mfrPOqSa3id7d3Nsz+pvSmu6lkR4VmMHd5lULgm5y9Xjqel4l
+r3orZDW6V2OLF5Ni9vnWYAu+XvgQsLk9wfret5OiS5Udv4avCU0KzIwYMfpqba1TcHZZjHUH3LO
aR62IwXlU56wUv7t3A7tOHO3VJHogT0x/zXqXa7i/pQ1XTTkR/ju8n6EHwTv9j7v8X5I8663WbYh
fv59g9IKxNvq9gF6DHmjvYSkPKqhDM9Yua4vGCG6bn5G0CUIaK4q7L7tBtqkSgdeq2StsqlBIZ9P
Y/WfvUNG/Em6940fFoHc//Hlj9We9/9ZmvA5SUlcesVZPghf3xqm8md0NcNit8WrGMqU8a39opP0
wGdzOVgTUiNqoo/pWg/q1ctBQi8fddMBAOBX6l4aocbZU2KkXOakiSfc8BgGovNL9EAPKx7juk3O
8bTZU65A8giHSN/lm2fDpMTH8zLm1RxhYeQRE9qO9Zsp8/gJ9piYSjj/cvBn9nzf8yYdwFp/Jm4v
vkg/gfbEWt9ZaEsP9Z6P9NKKnX4vtiaop14fmhI6SZyfiRa68A4fpKN/q3xrxRu/oLHISiQ0nre/
+xyP8jMa+2M7++JrNVRT/FVjSchPNcSf/Ftj/MrP/M/v/MdvlqIf+ZG8EJVvxeG+/VT/3v3drqV5
7bSlT+xzTf4IYf1eDHTCr6UP31x+j6rmL/nxfxDvP/7z78f3r9XoT7D5r6j9TxAA4cIFAIIEAwQo
mFBhrVoKHT6EGFHiRIoVLV7EmFHjRo4UD3YEGVLkSJIlTW4cmPDjRIYnXb6EGVOmSIQzbd7EmdOk
QIcDUkJsqVPoUKJFC640mlTp0pEuBigU6PPnwoZMrV7FOhFpVq5dmU4VGJanw6pezZ4luhXtWrY7
f7YQG9ZhkrJt7d4dWRPvXr4HA7AIgOCvXxZwB8ON6wIwYMFtapUYLBjwQcaDKavlm9mrXs2dz/4l
SCtR6NEAsqSkRSOxi9KiAdTi1Vo2/2naAGhx9pzbKm7dvZfOaOWKYKuCrQK4wEIcYWIsAPwehA0g
uMHiwqVXd+5be1Le273nZOHaduvjNEQjVCQViwDSCFvVGjbeeYDZ8uV3/57/JWb9/U+CBiAR4gIk
TgAX2HNOuRkQom/AAIir5RMHjSOQIAEtHDAR/PzjMCT+OgRxIwDFc+04BOlz7goGxUOxFmVkQ4jE
+m4LsUYPN7QxR4mAs2466Qx0zhWEvPgoOPeEBACTqnwMoEcnhxMORx2ndEhKKq8Mb0Yg6UNIkOc+
Og+AYapiccbZrLySyg/TVJMFDN+ES7kHnfMiw5oe5CW2DCm8sEI/NWQz0CrRFLTDEf9n86k0FOkj
z6BEeKlFxhjNDI3QQkO09NL+eByuONWuIwiwTqEkKDrpesQO1FOz01TQNVvtEAFBrvDiilkJEsQF
Gmy9ItQAar0VgFlr5SUSXGnl9VhgexWW1kxh7e9ZaHtbqdrlBrjzS4OyrSUSa7cFd75wp01TWnL1
G0slieo6t91B3U1zqnEfCgpee8W9V0d58QWK3XzPNfdfz9Klbl2B7Q34YM3kldJfhWF99WHfCOaX
Xonbjfji3BjG0WGNC83444Wn6thjkQMN+WS8nFI3onpV1jRhmL1Kt+GZW5X55qxqZknnS1P2+ayx
Xn056CuBNprmeckyOekac3Y6qaH/e476aKirHmpql5vGmkOku15qIKK5BjvastsSu+Szdfx6baF4
iphst7dre+6c0qbabhCv1tslgRqWu2/d6hY8pr9ZCrzwzghX3O+KmW7cP8YjJwnvrSk3G/OiDl83
cc3x4vvzjDi/XHTvQje9ItJdTp3u1nESm6KiX9dsctpVFwDw26lFffeEFCvZc9836314uDuffXjQ
lS9J662FZx4r2+3+snrrq0fs+uoZgkzb6Nmafm4WrhCt/ETMR/989WkZxCnW0ocfE1PWF7D472Gy
H+tfE3GlFdH6/5//+CdAACZCNVnAwiAIuMAAtmKA/wPU/dYSvrWND370u2AGMbhB//NFUIJoyV/U
fiXAVpDQhKIpIQpPKKAVppCFKgzTB22iPRrW0IbWqyD5OLhDDfZwgxSS4UwSwUMi+tCIXnDT2UZI
Cwb6r4lMDCAUnzhFCIYwiM4RRBSdqEUoPnCLXuwiAL8oRi+tDQE6NGIR1Zg+D17RJYxKYxzXeD4k
rm2JD3whHl1YwD2ukI8MbKMbTyKIP0Yxj4XUIyD7qMJBWLFdFpyjHNMIREG6ZIiSjGQR66hEL+Cx
gJ8EJCgNKUpPBrKSecmiJ0O5ylGyEo9lPBskMTnLDZrylB66ZCZpCb9Nlu2OJfxSHl04zBaSMAAw
zKMjg1inYiKTmM5spjAdqExyyf/yfMdUH312ec3bXJCSt7RYRnK5zV32EmxLFOCDoIhNIR2ki35x
Ipe2aBwNzbOKHEne7fL5kACkUoxhtCcYqShQLcKybGdEHzbPw02GalND13Ro+Y6pUPrZEnFBwWg4
qVIqhzUto2ShV1X2WbrZlVSk0MNoR8O5T4aMVCXj1GVM0WfOrt2xf8G8KQvpIyQUYlOdL2yS/x4E
yEy11KhHhRzTjuovky41qQlZakufWpCoTpWqVd0oVbAKVaY6VatGrQghjfkcZCLSrMZ5TiIbmcOE
wu9L50lrN+kXzPR90yJSTalGocrRUun1qnwFaWDzmlWuAhYjgy1sVl0aUsNeFaz/FYFpRCk6S4pG
lI5J9GUnC/jTzTIwqAHcKQHZyU4CWlR20IvcYo/iT6F2Fq6hvY076wnbev6PtKIxKNisKde2NjSb
DJVobztITQnC8bfBfehCeTtRy/I2ueujqf7qpMIGndAv1D1IOk1Y3fOskLgSZGZPyVq/nna3u9zV
6ZeIadqk7Vam77UrOEMS2Q3S9a2TBe5zyxfdqqGTiwP9J4AD6gr2yhcj/YziMT0LUHVqV4rmFWpB
vwsrhL6XnEOccPSMq9y5HlehE3Wr+ZrLXxFON5GGXOQh/bjiGBpYJGItbyLhKd6govemaf3jWmOJ
RgvDN8PRg+mFJUlip+2PlEd23CWSR1lgF1cEwapsZZShPOUC5rZr7hXyHJncZK0EucdDxuw5TfxM
aULTzGVOJpdDEl40k9nN0Vzvjy+F5S/PMb5qxoiXs3zEMNd0ugJ+MEEFHeB74llErA00oQc9YEYz
0cpYq/CeM7llQ1dJz3Xmsx0RwAJOd3rTnfY0qEMtahZ8WtSmBjUFDQxjFZeVxa2GdQl1rMRwfQtf
tsZ1tmpdaY5cWtIZJDKvhc1PRFM5ycc25KOHvWxLY1qmwWY2s//CaVNXe9Slvra1qZ3tTss52rTL
da11fetxh/sqAQEAOw==

--Boundary_(ID_7WstEYdk/Itu8fvSo0uArw)--


--===============1776720240==
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://www1.ietf.org/mailman/listinfo/p2psip

--===============1776720240==--




From p2psip-bounces@ietf.org Tue Jan 22 05:38:32 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHGWM-0001Z3-EB; Tue, 22 Jan 2008 05:38:22 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHGWK-0001Yn-P2
	for p2psip@ietf.org; Tue, 22 Jan 2008 05:38:20 -0500
Received: from smtp.nokia.com ([192.100.122.230] helo=mgw-mx03.nokia.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHGWK-0004Ba-4N
	for p2psip@ietf.org; Tue, 22 Jan 2008 05:38:20 -0500
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m0MAc9p8006004; Tue, 22 Jan 2008 12:38:13 +0200
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 Jan 2008 12:38:05 +0200
Received: from esebe102.NOE.Nokia.com ([172.21.138.217]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 Jan 2008 12:38:04 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [P2PSIP] HIP: optional, mandatory?
Date: Tue, 22 Jan 2008 12:42:29 +0200
Message-ID: <3F18E76823C95E4795181D74BAC7664F05B95CAE@esebe102.NOE.Nokia.com>
In-Reply-To: <24CCCC428EFEA2469BF046DB3C7A8D223AE557@namail5.corp.adobe.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] HIP: optional, mandatory?
Thread-Index: AchcFEBQK8Y307JQRrqz9GKGSKXASQAQFZogACOWWzA=
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com><20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com><77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com><7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com><77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com><10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu><4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com><465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com><284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>	<DD40D2FF-809B-4B1F-B43B-0E8F41ED21DB@quinthar.com>	<24CCCC428EFEA2469BF046DB3C7A8D223AE531@namail5.corp.adobe.com><3F18E76823C95E4795181D74BAC7664F05B951F1@esebe102.NOE.Nokia.com>
	<47946CC9.4080806@ee.oulu.fi>
	<24CCCC428EFEA2469BF046DB3C7A8D223AE557@namail5.corp.adobe.com>
From: <marcin.matuszewski@nokia.com>
To: <hsinnrei@adobe.com>, <erkkih@ee.oulu.fi>, <p2psip@ietf.org>
X-OriginalArrivalTime: 22 Jan 2008 10:38:04.0475 (UTC)
	FILETIME=[DE76C8B0:01C85CE2]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: 
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hi Henry,

There are no major reasons why it should not run. The previous version
of the software was running on N800.=20

Erkki: any comments?

Marcin=20

>-----Original Message-----
>From: ext Henry Sinnreich [mailto:hsinnrei@adobe.com]=20
>Sent: 21 January, 2008 19:50
>To: Erkki Harjula; Matuszewski Marcin (Nokia-NRC/Helsinki);=20
>p2psip@ietf.org
>Subject: RE: [P2PSIP] HIP: optional, mandatory?
>
>>we at the University of Oulu are collaborating with Nokia and=20
>Columbia=20
>>University with the P2PP prototype. Together with Nokia we are
>
>>implementing a mobile version
>
>Is there any chance it may run on my N810 Nokia Tablet at some=20
>future point in time?
>
>Thanks, Henry
>
>-----Original Message-----
>From: Erkki Harjula [mailto:erkkih@ee.oulu.fi]
>Sent: Monday, January 21, 2008 1:59 AM
>To: marcin.matuszewski@nokia.com; p2psip@ietf.org
>Subject: Re: [P2PSIP] HIP: optional, mandatory?
>
>Hi, we at the University of Oulu are collaborating with Nokia=20
>and Columbia University with the P2PP prototype. Together with=20
>Nokia we are implementing a mobile version (works on Nokia's=20
>S60 phones) of P2PP prototype, which is able to act as both=20
>P2PSIP peer and client. We are currently working on mobile=20
>version's interoperability with fixed version of P2PP, aiming=20
>to provide full compatibility between them.
>
>Columbia's overlay on PlanetLab provides an excellent testing=20
>environment for the prototypes. Thus, I also encourage you to=20
>join this P2PP trial network to increase the node population.
>
>-Erkki
>
>
>marcin.matuszewski@nokia.com wrote:
>> I fully agree. Besides Nokia's implementation shows that=20
>P2PP can also=20
>> work on mobile devices. Some of you who visited Nokia's P2PSIP demo=20
>> stand in Las Vegas could see a demo of the P2PP implementation on
>Nokia
>> phones. At the stand we were showing how a mobile phone that
>implements
>> P2PP can join the Columbia Univ.'s 600 nodes overlay on=20
>Planet Lab and=20
>> allow users to use basic SIP services. The demo was done in
>colaboration
>> with Columbia Univ.=20
>> Everyone who whould like to join the P2PP trial network=20
>please send an=20
>> email to Salman, Henning or me.
>> =20
>> Our goal is to specify a protocol based on our implementation=20
>> experience. It is very easy to write protocol specifications=20
>that are=20
>> difficult to implement and therefore have high chances to=20
>fail in the=20
>> market, what we could see in the past.
>>
>> Marcin
>>  =20
>>
>
>
>
>
>_______________________________________________
>P2PSIP mailing list
>P2PSIP@ietf.org
>https://www1.ietf.org/mailman/listinfo/p2psip
>

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



From p2psip-bounces@ietf.org Tue Jan 22 06:02:26 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHGtd-0006Ec-G1; Tue, 22 Jan 2008 06:02:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHGtc-0006EX-En
	for p2psip@ietf.org; Tue, 22 Jan 2008 06:02:24 -0500
Received: from smtp.nokia.com ([192.100.105.134] helo=mgw-mx09.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHGta-00055v-8p
	for p2psip@ietf.org; Tue, 22 Jan 2008 06:02:24 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m0MB36It028800; Tue, 22 Jan 2008 05:03:15 -0600
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 Jan 2008 13:02:09 +0200
Received: from esebe102.NOE.Nokia.com ([172.21.138.217]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 Jan 2008 13:02:09 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: RE: [P2PSIP] HIP: optional, mandatory?
Date: Tue, 22 Jan 2008 13:06:34 +0200
Message-ID: <3F18E76823C95E4795181D74BAC7664F05B95CF4@esebe102.NOE.Nokia.com>
In-Reply-To: <e3c8ad9a1429b.47946208@us.army.mil>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RE: [P2PSIP] HIP: optional, mandatory?
Thread-Index: AchcN7YEiSyoB8RCTcWFi7rcujwvOgAq/Zgg
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
	<465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com>
	<284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>
	<DD40D2FF-809B-4B1F-B43B-0E8F41ED21DB@quinthar.com>
	<24CCCC428EFEA2469BF046DB3C7A8D223AE531@namail5.corp.adobe.com>
	<3F18E76823C95E4795181D74BAC7664F05B951F1@esebe102.NOE.Nokia.com>
	<e3c8ad9a1429b.47946208@us.army.mil>
From: <marcin.matuszewski@nokia.com>
To: <radhika.r.roy@us.army.mil>
X-OriginalArrivalTime: 22 Jan 2008 11:02:09.0538 (UTC)
	FILETIME=[3BC9E620:01C85CE6]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: p2psip@ietf.org
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org


>[RRR] Yes, you are right. So, please help this P2PSIP WG to=20
>complete the spec for the base P2PSIP protocol based on these=20
>implementation experiences as soon as possible. We would=20
>appreciate this.

We are constantly improving our software implementation and protocol
specification. We published a paper at CCNC conference (Mobile P2PSIP -
Peer-to-Peer SIP communication in mobile communities). It should be
available from ieeexplore.=20

Do you think that an implementation report (with some measurements)
would be useful?

Marcin

>-----Original Message-----
>From: ext Roy, Radhika R Dr CTR USA USAMC=20
>[mailto:radhika.r.roy@us.army.mil]=20
>Sent: 21 January, 2008 16:13
>To: Matuszewski Marcin (Nokia-NRC/Helsinki)
>Cc: hsinnrei@adobe.com; dbarrett@quinthar.com;=20
>fluffy@cisco.com; p2psip@ietf.org
>Subject: Re: RE: [P2PSIP] HIP: optional, mandatory?
>
>Inline [RRR]
>
>----- Original Message -----
>From: marcin.matuszewski@nokia.com
>Date: Friday, January 18, 2008 15:30
>Subject: RE: [P2PSIP] HIP: optional, mandatory?
>To: hsinnrei@adobe.com, dbarrett@quinthar.com, fluffy@cisco.com
>Cc: p2psip@ietf.org
>
>>=20
>> >Opinion: This call to urgency can be best met IMHO by using P2PP=20
>> >implemented on 600 nodes on Planet Lab since it meets the=20
>criteria of=20
>> >running code, open available free code and large footprint=20
>> >deployment.
>>=20
>> I fully agree. Besides Nokia's implementation shows that=20
>P2PP can also=20
>> work on mobile devices. Some of you who visited Nokia's P2PSIP demo=20
>> stand in Las Vegas could see a demo of the P2PP implementation on=20
>> Nokiaphones. At the stand we were showing how a mobile phone that=20
>> implementsP2PP can join the Columbia Univ.'s 600 nodes overlay on=20
>> Planet Lab and allow users to use basic SIP services. The demo was=20
>> done in colaborationwith Columbia Univ.
>> Everyone who whould like to join the P2PP trial network=20
>please send an=20
>> email to Salman, Henning or me.
>>=20
>> Our goal is to specify a protocol based on our implementation=20
>> experience. It is very easy to write protocol specifications=20
>that are=20
>> difficult to implement and therefore have high chances to=20
>fail in the=20
>> market, what we could see in the past.
>>=20
>> Marcin
>
>[RRR] Yes, you are right. So, please help this P2PSIP WG to=20
>complete the spec for the base P2PSIP protocol based on these=20
>implementation experiences as soon as possible. We would=20
>appreciate this.
>

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



From p2psip-bounces@ietf.org Tue Jan 22 08:13:01 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHIvy-0007kP-W4; Tue, 22 Jan 2008 08:12:59 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHIvy-0007jw-4M
	for p2psip@ietf.org; Tue, 22 Jan 2008 08:12:58 -0500
Received: from brinza.cc.columbia.edu ([128.59.29.8])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHIvx-0000aM-PJ
	for p2psip@ietf.org; Tue, 22 Jan 2008 08:12:58 -0500
Received: from Upstairs-Mac (pool-71-250-50-170.nwrknj.east.verizon.net
	[71.250.50.170]) (user=hgs10 mech=PLAIN bits=0)
	by brinza.cc.columbia.edu (8.14.1/8.14.1) with ESMTP id m0MDCqpk010101
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Tue, 22 Jan 2008 08:12:53 -0500 (EST)
Message-Id: <C4CA168C-0627-4EB9-818F-C88A4826412E@cs.columbia.edu>
From: Henning Schulzrinne <hgs@cs.columbia.edu>
To: Enrico Marocco <enrico.marocco@telecomitalia.it>
In-Reply-To: <4795A323.3080401@telecomitalia.it>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Subject: Re: [P2PSIP] HIP: optional, mandatory?
Date: Tue, 22 Jan 2008 08:13:06 -0500
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com><20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com><77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com><7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com><77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com><10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu><4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com><465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com><284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>	<DD40D2FF-809B-4B1F-B43B-0E8F41ED21DB@quinthar.com>	<24CCCC428EFEA2469BF046DB3C7A8D223AE531@namail5.corp.adobe.com>
	<3F18E76823C95E4795181D74BAC7664F05B951F1@esebe102.NOE.Nokia.com>
	<4795A323.3080401@telecomitalia.it>
X-Mailer: Apple Mail (2.915)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.8
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: hsinnrei@adobe.com, p2psip@ietf.org
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

>

PlanetLab is many things, but stable is not the adjective I would  
use... These are generally servers run on a volunteer basis by  
graduate students in various university labs; they routinely get  
disconnected, crash or get overloaded with other experiments.

Relative to consumer nodes, they do tend to have public IP addresses.

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

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


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



From p2psip-bounces@ietf.org Tue Jan 22 09:05:12 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHJkS-0004vH-MI; Tue, 22 Jan 2008 09:05:08 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHJkR-0004v9-Dr
	for p2psip@ietf.org; Tue, 22 Jan 2008 09:05:07 -0500
Received: from maile.telecomitalia.it ([156.54.233.31])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHJkQ-00040P-TC
	for p2psip@ietf.org; Tue, 22 Jan 2008 09:05:07 -0500
Received: from ptpxch010ba020.idc.cww.telecomitalia.it ([156.54.240.53]) by
	maile.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 Jan 2008 15:05:05 +0100
Received: from ptpxch006ba020.idc.cww.telecomitalia.it ([156.54.240.45]) by
	ptpxch010ba020.idc.cww.telecomitalia.it with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 22 Jan 2008 15:05:05 +0100
Received: from [10.229.8.45] ([10.229.8.45]) by
	ptpxch006ba020.idc.cww.telecomitalia.it over TLS secured
	channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 Jan 2008 15:05:04 +0100
Message-ID: <4795F8A9.9090206@telecomitalia.it>
Date: Tue, 22 Jan 2008 15:07:37 +0100
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla-Thunderbird 2.0.0.9 (X11/20080110)
MIME-Version: 1.0
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [P2PSIP] HIP: optional, mandatory?
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com><20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com><77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com><7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com><77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com><10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu><4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com><465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com><284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>	<DD40D2FF-809B-4B1F-B43B-0E8F41ED21DB@quinthar.com>	<24CCCC428EFEA2469BF046DB3C7A8D223AE531@namail5.corp.adobe.com>
	<3F18E76823C95E4795181D74BAC7664F05B951F1@esebe102.NOE.Nokia.com>
	<4795A323.3080401@telecomitalia.it>
	<C4CA168C-0627-4EB9-818F-C88A4826412E@cs.columbia.edu>
In-Reply-To: <C4CA168C-0627-4EB9-818F-C88A4826412E@cs.columbia.edu>
X-OriginalArrivalTime: 22 Jan 2008 14:05:04.0661 (UTC)
	FILETIME=[C978C450:01C85CFF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: hsinnrei@adobe.com, p2psip@ietf.org
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0996338095=="
Errors-To: p2psip-bounces@ietf.org

This is a cryptographically signed message in MIME format.

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

This is a cryptographically signed message in MIME format.

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

Henning Schulzrinne wrote:
> PlanetLab is many things, but stable is not the adjective I would use...
> These are generally servers run on a volunteer basis by graduate
> students in various university labs; they routinely get disconnected,
> crash or get overloaded with other experiments.
> 
> Relative to consumer nodes, they do tend to have public IP addresses.

So, if I understand correctly, Marcin's mobile devices connect directly
to P2PP peers running on PlanetLab nodes without effectively being part
of PlanetLab, establishing an overlay made of both PL and non-PL nodes,
right?

-- 
Ciao,
Enrico

--------------ms070801080007010201030604
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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJ4zCC
Az8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQI
EwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENv
bnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAi
BgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVy
c29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5
NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBM
dGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzAN
BgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9Vvy
Gna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOC
dz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCB
kTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhh
d3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNV
HREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQAD
gYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFi
w9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpb
NU1341YheILcIRk13iSx0x1G/11fZU8wggNMMIICtaADAgECAhA93pW98AVSLKZipzI5De0E
MA0GCSqGSIb3DQEBBQUAMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3Vs
dGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNz
dWluZyBDQTAeFw0wNzAzMjkxNTAyNTVaFw0wODAzMjgxNTAyNTVaMHoxHzAdBgNVBAMTFlRo
YXd0ZSBGcmVlbWFpbCBNZW1iZXIxLjAsBgkqhkiG9w0BCQEWH2Vucmljby5tYXJvY2NvQHRl
bGVjb21pdGFsaWEuaXQxJzAlBgkqhkiG9w0BCQEWGGVucmljby5tYXJvY2NvQGdtYWlsLmNv
bTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALaNEnc2tIvvdDv1eOEaoTRKfQ9V
C7AIlpPaGqPQsyZ1pnGe8dHLmsucl9RAvlft1Pl4FCKodpuSuPn/fWINHExh+GaAvUnGiIIP
1Jk+jm3/Wd0tJByGRgf6Aouk6rLKTE5v/BFldbCdSpdT/1htx5ME9aoYxQ/Vg/CU+X7rTPCR
5tFF8nOEqiFCUFcI9zxy4nfetgUpoomAJwtyX96bYD/ueaKcCMjSaUctpFxy/FRrEalDMQGy
v6OzcyugZVUbYxmHoZqUH27vkf+t0DMf4/LEPrfOnJqCAtQbAWSEJJcn6kDGtjTDFs+tbQFv
EMqtJhuzIyw4v08o/5paI3Diq1cCAwEAAaNnMGUwDwYDVR0PAQH/BAUDAwf5gDBEBgNVHREE
PTA7gR9lbnJpY28ubWFyb2Njb0B0ZWxlY29taXRhbGlhLml0gRhlbnJpY28ubWFyb2Njb0Bn
bWFpbC5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOBgQA3J5m3GoDt0TWtO24H
GMEX44VbMtvD/e0ZSCPfHQxF347LtbC0yyDtvbioV1mB8joVrj48rGC6/cJxs+xqZ6A1EEUd
saeF3T+F8mZh8BYeZo1eqFzgy0ucSJiFJkf38hts/edSqJqFm+CQdP33RVRZ0e0c0Feqoj4h
QvoGE5Tx5zCCA0wwggK1oAMCAQICED3elb3wBVIspmKnMjkN7QQwDQYJKoZIhvcNAQEFBQAw
YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4x
LDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDMy
OTE1MDI1NVoXDTA4MDMyODE1MDI1NVowejEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1l
bWJlcjEuMCwGCSqGSIb3DQEJARYfZW5yaWNvLm1hcm9jY29AdGVsZWNvbWl0YWxpYS5pdDEn
MCUGCSqGSIb3DQEJARYYZW5yaWNvLm1hcm9jY29AZ21haWwuY29tMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEAto0Sdza0i+90O/V44RqhNEp9D1ULsAiWk9oao9CzJnWmcZ7x
0cuay5yX1EC+V+3U+XgUIqh2m5K4+f99Yg0cTGH4ZoC9ScaIgg/UmT6Obf9Z3S0kHIZGB/oC
i6TqsspMTm/8EWV1sJ1Kl1P/WG3HkwT1qhjFD9WD8JT5futM8JHm0UXyc4SqIUJQVwj3PHLi
d962BSmiiYAnC3Jf3ptgP+55opwIyNJpRy2kXHL8VGsRqUMxAbK/o7NzK6BlVRtjGYehmpQf
bu+R/63QMx/j8sQ+t86cmoIC1BsBZIQklyfqQMa2NMMWz61tAW8Qyq0mG7MjLDi/Tyj/mloj
cOKrVwIDAQABo2cwZTAPBgNVHQ8BAf8EBQMDB/mAMEQGA1UdEQQ9MDuBH2Vucmljby5tYXJv
Y2NvQHRlbGVjb21pdGFsaWEuaXSBGGVucmljby5tYXJvY2NvQGdtYWlsLmNvbTAMBgNVHRMB
Af8EAjAAMA0GCSqGSIb3DQEBBQUAA4GBADcnmbcagO3RNa07bgcYwRfjhVsy28P97RlII98d
DEXfjsu1sLTLIO29uKhXWYHyOhWuPjysYLr9wnGz7GpnoDUQRR2xp4XdP4XyZmHwFh5mjV6o
XODLS5xImIUmR/fyG2z951KomoWb4JB0/fdFVFnR7RzQV6qiPiFC+gYTlPHnMYIDcTCCA20C
AQEwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkg
THRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECED3e
lb3wBVIspmKnMjkN7QQwCQYFKw4DAhoFAKCCAdAwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEH
ATAcBgkqhkiG9w0BCQUxDxcNMDgwMTIyMTQwNzM3WjAjBgkqhkiG9w0BCQQxFgQUcZ9U/Mv0
3K6Bpt4Ky2bz7Vn+RbwwXwYJKoZIhvcNAQkPMVIwUDALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMIGFBgkrBgEEAYI3EAQxeDB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUg
Q29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1h
aWwgSXNzdWluZyBDQQIQPd6VvfAFUiymYqcyOQ3tBDCBhwYLKoZIhvcNAQkQAgsxeKB2MGIx
CzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSww
KgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQPd6VvfAFUiym
YqcyOQ3tBDANBgkqhkiG9w0BAQEFAASCAQCiK2pG89WdzO7U6QcIcVkQUcvNOcV1yz/d8hNU
cQBheAV+DaFJ5ZDj+fhYI0R4KLbl+AZzFfHkOu+pFvJapVUqhBpWjv24T0hWy4bpvPgwmOEQ
Z7JY2R5u5rT87CuKOGDO5SKI5gLUvgVeao4OdAVtDmAcpAMYu1KONubTnKNF2+N+98ACRhIr
0FvsSIUeO8LSmygO+KYudkLS65JxCMizqNjHMHO5Df3kxbDNJeOynQyzkI8g8BXSWyWhZmkN
C38zP9OcySo3BOBvf9++L9czTBgvyvPHdn02tOGtmVBjY1xLDBcmYXETA06eYiQDEZXXBK6Z
eAoeTJVlaptp9EEwAAAAAAAA
--------------ms070801080007010201030604--


--===============0996338095==
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://www1.ietf.org/mailman/listinfo/p2psip

--===============0996338095==--




From p2psip-bounces@ietf.org Tue Jan 22 09:16:01 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHJux-0002fa-Dd; Tue, 22 Jan 2008 09:15:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHJuu-0002fV-NR
	for p2psip@ietf.org; Tue, 22 Jan 2008 09:15:56 -0500
Received: from mxoutps1.us.army.mil ([143.69.250.38])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHJuq-0003GJ-Ph
	for p2psip@ietf.org; Tue, 22 Jan 2008 09:15:56 -0500
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=HM9WUnJ2UE9jSXngWmPPJbjk1lwX+VIm5ptJ/hf8gKmfSLcsb+MNapfY
	t7BsTo61v8xV1LfIiQ3a945C3NPesA==;
From: "Roy, Radhika R Dr CTR USA USAMC" <radhika.r.roy@us.army.mil>
X-AKO: 95466489:10.224.36.65:22 Jan 2008 14:15:51 +0000:$Webmail:None
X-IronPort-AV: E=Sophos;i="4.25,233,1199664000"; d="scan'208";a="95466489"
Received: from mail5.int.ps1.us.army.mil (HELO us.army.mil) ([10.224.36.65])
	by mxoutps1.us.army.mil with ESMTP; 22 Jan 2008 14:15:51 +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, 22 Jan
	2008 09:15:50 -0500
To: marcin.matuszewski@nokia.com
Message-ID: <d4accb881f22e.4795b446@us.army.mil>
Date: Tue, 22 Jan 2008 09:15:50 -0500
X-Mailer: Sun Java(tm) System Messenger Express 6.2-9.04 (built Jun 11
 2007)
MIME-Version: 1.0
Content-Language: en
Subject: Re: RE: RE: [P2PSIP] HIP: optional, mandatory?
X-Accept-Language: en
Priority: normal
In-Reply-To: <3F18E76823C95E4795181D74BAC7664F05B95CF4@esebe102.NOE.Nokia.com>
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
	<465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com>
	<284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>
	<DD40D2FF-809B-4B1F-B43B-0E8F41ED21DB@quinthar.com>
	<24CCCC428EFEA2469BF046DB3C7A8D223AE531@namail5.corp.adobe.com>
	<3F18E76823C95E4795181D74BAC7664F05B951F1@esebe102.NOE.Nokia.com>
	<e3c8ad9a1429b.47946208@us.army.mil>
	<3F18E76823C95E4795181D74BAC7664F05B95CF4@esebe102.NOE.Nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: p2psip@ietf.org
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hi, Mercin:

What we want is to develop the P2PSIP protocol standard for this WG. The P2PSIP protocol drafts are there. You can help to provide insights which proposals are good and if needed what improvements need to be done to finalize the specs or you can proposed a new one or a modified draft combining with the existing ones.

In this way, you can play a role to standardize the P2PSIP protocol for this WG. Then we can proceed to build other P2P things (e.g. HIP-overlay using the standardized P2PSIP protocol of this WG).

Best regards,
Radhika

----- Original Message -----
From: marcin.matuszewski@nokia.com
Date: Tuesday, January 22, 2008 6:02
Subject: RE: RE: [P2PSIP] HIP: optional, mandatory?
To: radhika.r.roy@us.army.mil
Cc: p2psip@ietf.org, salman@cs.columbia.edu, marcin.matuszewski@nokia.com

> 
> >[RRR] Yes, you are right. So, please help this P2PSIP WG to 
> >complete the spec for the base P2PSIP protocol based on these 
> >implementation experiences as soon as possible. We would 
> >appreciate this.
> 
> We are constantly improving our software implementation and protocol
> specification. We published a paper at CCNC conference (Mobile 
> P2PSIP -
> Peer-to-Peer SIP communication in mobile communities). It should be
> available from ieeexplore. 
> 
> Do you think that an implementation report (with some measurements)
> would be useful?
> 
> Marcin
> 
> >-----Original Message-----
> >From: ext Roy, Radhika R Dr CTR USA USAMC 
> >[mailto:radhika.r.roy@us.army.mil] 
> >Sent: 21 January, 2008 16:13
> >To: Matuszewski Marcin (Nokia-NRC/Helsinki)
> >Cc: hsinnrei@adobe.com; dbarrett@quinthar.com; 
> >fluffy@cisco.com; p2psip@ietf.org
> >Subject: Re: RE: [P2PSIP] HIP: optional, mandatory?
> >
> >Inline [RRR]
> >
> >----- Original Message -----
> >From: marcin.matuszewski@nokia.com
> >Date: Friday, January 18, 2008 15:30
> >Subject: RE: [P2PSIP] HIP: optional, mandatory?
> >To: hsinnrei@adobe.com, dbarrett@quinthar.com, fluffy@cisco.com
> >Cc: p2psip@ietf.org
> >
> >> 
> >> >Opinion: This call to urgency can be best met IMHO by using 
> P2PP 
> >> >implemented on 600 nodes on Planet Lab since it meets the 
> >criteria of 
> >> >running code, open available free code and large footprint 
> >> >deployment.
> >> 
> >> I fully agree. Besides Nokia's implementation shows that 
> >P2PP can also 
> >> work on mobile devices. Some of you who visited Nokia's P2PSIP 
> demo 
> >> stand in Las Vegas could see a demo of the P2PP implementation 
> on 
> >> Nokiaphones. At the stand we were showing how a mobile phone 
> that 
> >> implementsP2PP can join the Columbia Univ.'s 600 nodes overlay 
> on 
> >> Planet Lab and allow users to use basic SIP services. The demo 
> was 
> >> done in colaborationwith Columbia Univ.
> >> Everyone who whould like to join the P2PP trial network 
> >please send an 
> >> email to Salman, Henning or me.
> >> 
> >> Our goal is to specify a protocol based on our implementation 
> >> experience. It is very easy to write protocol specifications 
> >that are 
> >> difficult to implement and therefore have high chances to 
> >fail in the 
> >> market, what we could see in the past.
> >> 
> >> Marcin
> >
> >[RRR] Yes, you are right. So, please help this P2PSIP WG to 
> >complete the spec for the base P2PSIP protocol based on these 
> >implementation experiences as soon as possible. We would 
> >appreciate this.
> >
> 

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



From p2psip-bounces@ietf.org Tue Jan 22 09:24:35 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHK3G-0004Lt-BI; Tue, 22 Jan 2008 09:24:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHK3E-0004Lm-Sa
	for p2psip@ietf.org; Tue, 22 Jan 2008 09:24:32 -0500
Received: from smtp.nokia.com ([192.100.122.233] helo=mgw-mx06.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHK3D-0003Rg-Bh
	for p2psip@ietf.org; Tue, 22 Jan 2008 09:24:32 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m0MENh8d001093; Tue, 22 Jan 2008 16:24:16 +0200
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 Jan 2008 16:24:10 +0200
Received: from esebe102.NOE.Nokia.com ([172.21.138.217]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 Jan 2008 16:24:10 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [P2PSIP] HIP: optional, mandatory?
Date: Tue, 22 Jan 2008 16:28:36 +0200
Message-ID: <3F18E76823C95E4795181D74BAC7664F05BE150A@esebe102.NOE.Nokia.com>
In-Reply-To: <4795F8A9.9090206@telecomitalia.it>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] HIP: optional, mandatory?
Thread-Index: Achc/8wTWNIA9g4GTw2vH72aIygtVAAAMStw
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com><20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com><77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com><7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com><77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com><10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu><4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com><465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com><284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>	<DD40D2FF-809B-4B1F-B43B-0E8F41ED21DB@quinthar.com>	<24CCCC428EFEA2469BF046DB3C7A8D223AE531@namail5.corp.adobe.com>
	<3F18E76823C95E4795181D74BAC7664F05B951F1@esebe102.NOE.Nokia.com>
	<4795A323.3080401@telecomitalia.it>
	<C4CA168C-0627-4EB9-818F-C88A4826412E@cs.columbia.edu>
	<4795F8A9.9090206@telecomitalia.it>
From: <marcin.matuszewski@nokia.com>
To: <enrico.marocco@telecomitalia.it>, <hgs@cs.columbia.edu>
X-OriginalArrivalTime: 22 Jan 2008 14:24:10.0843 (UTC)
	FILETIME=[74A642B0:01C85D02]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: hsinnrei@adobe.com, p2psip@ietf.org
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hi Enrico,

You are correct. In the demo P2PP enabled mobile phones connect to P2PP
nodes on PlanetLab. Mobile phones are not part of PlanetLab.=20

Mobile phones can also form a separate overlay (they don't have to
connect to PlanetLab).

Marcin=20

>-----Original Message-----
>From: ext Enrico Marocco [mailto:enrico.marocco@telecomitalia.it]=20
>Sent: 22 January, 2008 16:08
>To: Henning Schulzrinne
>Cc: Matuszewski Marcin (Nokia-NRC/Helsinki);=20
>hsinnrei@adobe.com; p2psip@ietf.org
>Subject: Re: [P2PSIP] HIP: optional, mandatory?
>
>Henning Schulzrinne wrote:
>> PlanetLab is many things, but stable is not the adjective I=20
>would use...
>> These are generally servers run on a volunteer basis by graduate=20
>> students in various university labs; they routinely get=20
>disconnected,=20
>> crash or get overloaded with other experiments.
>>=20
>> Relative to consumer nodes, they do tend to have public IP addresses.
>
>So, if I understand correctly, Marcin's mobile devices connect=20
>directly to P2PP peers running on PlanetLab nodes without=20
>effectively being part of PlanetLab, establishing an overlay=20
>made of both PL and non-PL nodes, right?
>
>--
>Ciao,
>Enrico
>

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



From p2psip-bounces@ietf.org Tue Jan 22 10:30:32 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHL54-0003dv-Sh; Tue, 22 Jan 2008 10:30:30 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHL53-0003dh-Vs
	for p2psip@ietf.org; Tue, 22 Jan 2008 10:30:30 -0500
Received: from exprod6og107.obsmtp.com ([64.18.1.208])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHL53-0007GO-Es
	for p2psip@ietf.org; Tue, 22 Jan 2008 10:30:29 -0500
Received: from source ([192.150.20.142]) by exprod6ob107.postini.com
	([64.18.5.12]) with SMTP; Tue, 22 Jan 2008 07:30:16 PST
Received: from inner-relay-3.eur.adobe.com (inner-relay-3b [10.128.4.236])
	by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	m0MFUDGb018188; Tue, 22 Jan 2008 07:30:13 -0800 (PST)
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
	m0MFU8FV014380; Tue, 22 Jan 2008 07:30:09 -0800 (PST)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 Jan 2008 07:30:08 -0800
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [P2PSIP] HIP: optional, mandatory?
Date: Tue, 22 Jan 2008 07:29:59 -0800
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D223AE562@namail5.corp.adobe.com>
In-Reply-To: <4795F8A9.9090206@telecomitalia.it>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] HIP: optional, mandatory?
Thread-Index: Achc/81qfVF32UzhRmudgRKC0cbLWwACy4iw
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com><20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com><77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com><7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com><77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com><10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu><4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com><465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com><284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>	<DD40D2FF-809B-4B1F-B43B-0E8F41ED21DB@quinthar.com>	<24CCCC428EFEA2469BF046DB3C7A8D223AE531@namail5.corp.adobe.com>
	<3F18E76823C95E4795181D74BAC7664F05B951F1@esebe102.NOE.Nokia.com>
	<4795A323.3080401@telecomitalia.it>
	<C4CA168C-0627-4EB9-818F-C88A4826412E@cs.columbia.edu>
	<4795F8A9.9090206@telecomitalia.it>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Enrico Marocco" <enrico.marocco@telecomitalia.it>,
	<marcin.matuszewski@nokia.com>
X-OriginalArrivalTime: 22 Jan 2008 15:30:08.0033 (UTC)
	FILETIME=[AB518910:01C85D0B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: p2psip@ietf.org
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Enrico,

>So, if I understand correctly, Marcin's mobile devices connect directly
>to P2PP peers running on PlanetLab nodes without effectively being part
>of PlanetLab, establishing an overlay made of both PL and non-PL nodes,

The mobile devices run the _client protocol_ that has been the topic of
many discussions on this list.

Maybe Marcin can give us the reference to the latest description of the
client protocol for P2PP implemented for this trial.=20

Thanks, Henry

-----Original Message-----
From: Enrico Marocco [mailto:enrico.marocco@telecomitalia.it]=20
Sent: Tuesday, January 22, 2008 6:08 AM
To: Henning Schulzrinne
Cc: marcin.matuszewski@nokia.com; Henry Sinnreich; p2psip@ietf.org
Subject: Re: [P2PSIP] HIP: optional, mandatory?

Henning Schulzrinne wrote:
> PlanetLab is many things, but stable is not the adjective I would
use...
> These are generally servers run on a volunteer basis by graduate
> students in various university labs; they routinely get disconnected,
> crash or get overloaded with other experiments.
>=20
> Relative to consumer nodes, they do tend to have public IP addresses.

So, if I understand correctly, Marcin's mobile devices connect directly
to P2PP peers running on PlanetLab nodes without effectively being part
of PlanetLab, establishing an overlay made of both PL and non-PL nodes,
right?

--=20
Ciao,
Enrico

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



From p2psip-bounces@ietf.org Tue Jan 22 11:11:19 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHLiX-00088I-EU; Tue, 22 Jan 2008 11:11:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHLiW-00088D-Dm
	for p2psip@ietf.org; Tue, 22 Jan 2008 11:11:16 -0500
Received: from ousrvr.oulu.fi ([130.231.240.1] helo=oulu.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHLiU-0007og-PD
	for p2psip@ietf.org; Tue, 22 Jan 2008 11:11:16 -0500
Received: from paju.oulu.fi (paju.oulu.fi [130.231.240.20])
	by oulu.fi (8.13.7/8.13.7) with ESMTP id m0MGB9ME014676;
	Tue, 22 Jan 2008 18:11:09 +0200 (EET)
Received: from [127.0.0.1] (paju.oulu.fi [130.231.240.20])
	by paju.oulu.fi (8.13.7/8.13.7) with ESMTP id m0MGB9MU010634;
	Tue, 22 Jan 2008 18:11:09 +0200 (EET)
Message-ID: <4796159C.4090203@ee.oulu.fi>
Date: Tue, 22 Jan 2008 18:11:08 +0200
From: Erkki Harjula <erkkih@ee.oulu.fi>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Henry Sinnreich <hsinnrei@adobe.com>
Subject: Re: [P2PSIP] HIP: optional, mandatory?
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com><20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com><77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com><7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com><77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com><10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu><4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com><465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com><284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>	<DD40D2FF-809B-4B1F-B43B-0E8F41ED21DB@quinthar.com>	<24CCCC428EFEA2469BF046DB3C7A8D223AE531@namail5.corp.adobe.com>	<3F18E76823C95E4795181D74BAC7664F05B951F1@esebe102.NOE.Nokia.com>	<4795A323.3080401@telecomitalia.it>	<C4CA168C-0627-4EB9-818F-C88A4826412E@cs.columbia.edu>	<4795F8A9.9090206@telecomitalia.it>
	<24CCCC428EFEA2469BF046DB3C7A8D223AE562@namail5.corp.adobe.com>
In-Reply-To: <24CCCC428EFEA2469BF046DB3C7A8D223AE562@namail5.corp.adobe.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: p2psip@ietf.org
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org


Henry Sinnreich wrote:
> The mobile devices run the _client protocol_ that has been the topic 
> of many discussions on this list.
Actually we are currently implementing the _peer_ prototype at the Univ. 
of Oulu. At the moment it is based on the older version of P2PP, and we 
are currently converting it to P2PP version -01. The next goal is the 
integration with Nokia's client version (which was demonstrated in CCNC) 
and Salman's new prototype implementation.

-Erkki

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



From p2psip-bounces@ietf.org Tue Jan 22 14:06:35 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHOS5-0005Vd-P1; Tue, 22 Jan 2008 14:06:29 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHOS4-0005VS-LW
	for p2psip@ietf.org; Tue, 22 Jan 2008 14:06:28 -0500
Received: from exprod6og105.obsmtp.com ([64.18.1.189])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHOS4-0006PI-2r
	for p2psip@ietf.org; Tue, 22 Jan 2008 14:06:28 -0500
Received: from source ([192.150.20.142]) by exprod6ob105.postini.com
	([64.18.5.12]) with SMTP; Tue, 22 Jan 2008 11:06:23 PST
Received: from inner-relay-3.eur.adobe.com (inner-relay-3b [10.128.4.236])
	by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	m0MJ6JGb024473; Tue, 22 Jan 2008 11:06:19 -0800 (PST)
Received: from fe2.corp.adobe.com (fe2.corp.adobe.com [10.8.192.72])
	by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id
	m0MJ6IFV007083; Tue, 22 Jan 2008 11:06:18 -0800 (PST)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe2.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 Jan 2008 11:06:17 -0800
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [P2PSIP] HIP: optional, mandatory?
Date: Tue, 22 Jan 2008 11:06:13 -0800
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D223AE56F@namail5.corp.adobe.com>
In-Reply-To: <4796159C.4090203@ee.oulu.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] HIP: optional, mandatory?
Thread-Index: AchdEWofpP0YhQBCQB6vQDy7qngwKQAF0EIg
References: <476BA8D9.4010203@ericsson.com><20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com><476E2B7C.9070601@ericsson.com><20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com><77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com><7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com><77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com><10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu><4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com><465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com><284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>	<DD40D2FF-809B-4B1F-B43B-0E8F41ED21DB@quinthar.com>	<24CCCC428EFEA2469BF046DB3C7A8D223AE531@namail5.corp.adobe.com>	<3F18E76823C95E4795181D74BAC7664F05B951F1@esebe102.NOE.Nokia.com>	<4795A323.3080401@telecomitalia.it>	<C4CA168C-0627-4EB9-818F-C88A4826412E@cs.columbia.edu>	<4795F8A9.9090206@telecomitalia.it>
	<24CCCC428EFEA2469BF046DB3C7A8D223AE562@namail5.corp.adobe.com>
	<4796159C.4090203@ee.oulu.fi>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Erkki Harjula" <erkkih@ee.oulu.fi>
X-OriginalArrivalTime: 22 Jan 2008 19:06:17.0749 (UTC)
	FILETIME=[DDDF2450:01C85D29]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: p2psip@ietf.org
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

> we are currently implementing the _peer_ prototype at the Univ.=20
> of Oulu. At the moment it is based on the older version of P2PP, and
we=20
> are currently converting it to P2PP version -01.

It is very encouraging to see one more organization contributing to
deploying and testing a P2PSIP protocol that has the benefits of free
code, deployment experience, peer review and continued enhancements from
various sources.

This may or may not have been a requirement in the WG charter, but makes
many of us comfortable the emerging P2PSIP standard may be based on all
these benefits coming from cooperation in the IETF.

Henry

-----Original Message-----
From: Erkki Harjula [mailto:erkkih@ee.oulu.fi]=20
Sent: Tuesday, January 22, 2008 8:11 AM
To: Henry Sinnreich
Cc: p2psip@ietf.org
Subject: Re: [P2PSIP] HIP: optional, mandatory?


Henry Sinnreich wrote:
> The mobile devices run the _client protocol_ that has been the topic=20
> of many discussions on this list.
Actually we are currently implementing the _peer_ prototype at the Univ.

of Oulu. At the moment it is based on the older version of P2PP, and we=20
are currently converting it to P2PP version -01. The next goal is the=20
integration with Nokia's client version (which was demonstrated in CCNC)

and Salman's new prototype implementation.

-Erkki

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



From p2psip-bounces@ietf.org Tue Jan 22 21:07:58 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHV1s-0003rC-Vr; Tue, 22 Jan 2008 21:07:52 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHV1r-0003r7-Q7
	for p2psip@ietf.org; Tue, 22 Jan 2008 21:07:51 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHV1r-0002eH-Cm
	for p2psip@ietf.org; Tue, 22 Jan 2008 21:07:51 -0500
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 22 Jan 2008 18:07:50 -0800
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m0N27oNd010343; 
	Tue, 22 Jan 2008 18:07:50 -0800
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id m0N27oAl012528;
	Wed, 23 Jan 2008 02:07:50 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'JiangXingFeng'" <jiang.x.f@huawei.com>,
	"'P2PSIP Mailing List'" <p2psip@ietf.org>
References: <003a01c85cda$61991f30$2d09a40a@china.huawei.com>
Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
Date: Tue, 22 Jan 2008 18:07:50 -0800
Message-ID: <44e301c85d64$c1a11010$c3f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <003a01c85cda$61991f30$2d09a40a@china.huawei.com>
Thread-Index: Achc2mE+N3Ev8YYNRpCsDNPfo2q5cgAijS9Q
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1953; t=1201054070;
	x=1201918070; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[P2PSIP]=20Choice=20of=20STUN=20peer=20
	or=20TURN=20peer |Sender:=20;
	bh=/be3dE4Cjd8cLrezMnfrMT2RCV1mte6dDaMKJbR3/mc=;
	b=n3dAKlMFi3ITf0PwQ9slja9jqbF3UDzsVtvFR2EdmxXJXU/ya0j9PJ2AlW
	zhMGhDYonflJg8gTwPBn061ks79xAPRPNAb5BrtMd+JJtjZF0VOfs9hMwWML
	sVo0MoPfjk;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: 
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

ICE allows you to have multiple STUN servers.  In the diagram you provided,
Peer A could contact Peer C, Peer D, and Peer B, and would notice different
answers from some (or all) of them.  All of those different answers can be
provided as different candidates (a=candidate) in the call setup message.

-d


> -----Original Message-----
> From: JiangXingFeng [mailto:jiang.x.f@huawei.com] 
> Sent: Tuesday, January 22, 2008 1:37 AM
> To: 'P2PSIP Mailing List'
> Subject: [P2PSIP] Choice of STUN peer or TURN peer
> 
> Hi, all:
> 
>  
> 
> In order to make the peers serve each other, some peers with 
> special capabilities could be exploited to play the STUN/TURN 
> server role for other peers who are behind NAT. Guys in 
> P2PSIP community has agreed with that peer behind NAT should 
> seek help from other peers, not centralized STUN/TURN server.
> 
>  
> 
> But which kinds of peers are qualified for playing STUN/TURN 
> server? Of course, Peers on the public internet could take 
> this responsibility. I also learned from the list that peers 
> behind p2p-friendly NAT (with end-point independent mapping 
> and filtering behavior) also could do the same work. But from 
> my point of view, ICE negotiation procedure may fail if 
> choosing this kind of peer as STUN/TURN server.
> 
>  
> 
> Let's show an example: 
> 
> 
> 
> Peer A and peer B want to communicate directly. NAT2 is a 
> p2p-friendly NAT. So peer C would be considered as a 
> candidate STUN server. If peer A choose the Peer C as its 
> STUN server, peer A will get a mapping on the NAT1 which is 
> in the address realm of private network. And Peer A will tell 
> peer B this server reflexive address. But peer B could not 
> reach it because it is in different address realm.  
> 
>  
> 
> Am I missing something? Comments are appreciated!
> 
>  
> 
> Regards!
> 
> --
> 
> Jiang XingFeng
> 
>  
> 
>  
> 
> 


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



From p2psip-bounces@ietf.org Tue Jan 22 22:02:07 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHVsM-0003DU-16; Tue, 22 Jan 2008 22:02:06 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHVsL-0003DL-F8
	for p2psip@ietf.org; Tue, 22 Jan 2008 22:02:05 -0500
Received: from smtpoutwbe02.prod.mesa1.secureserver.net ([208.109.78.113])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1JHVsK-0003lg-Rj
	for p2psip@ietf.org; Tue, 22 Jan 2008 22:02:05 -0500
Received: (qmail 11684 invoked from network); 23 Jan 2008 03:02:03 -0000
Received: from unknown (HELO gem-wbe20.prod.mesa1.secureserver.net)
	(64.202.189.175)
	by smtpoutwbe02.prod.mesa1.secureserver.net with SMTP;
	23 Jan 2008 03:02:03 -0000
Received: (qmail 28376 invoked by uid 99); 23 Jan 2008 03:02:03 -0000
Date: Tue, 22 Jan 2008 20:02:03 -0700
From: michaelc@idssoftware.com
To: p2psip@ietf.org
Message-ID: <20080122200203.59ca11a9ba9389561a029f06442e67fa.ff22e2cc50.wbe@email.secureserver.net>
MIME-Version: 1.0
User-Agent: Web-Based Email 4.12.20
X-Originating-IP: 72.87.190.177
X-Spam-Score: 1.7 (+)
X-Scan-Signature: bb8eae9af85e4fcfe76f325e38493bf4
Subject: [P2PSIP] Status of RELOAD
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1927128924=="
Errors-To: p2psip-bounces@ietf.org

--===============1927128924==
Content-Type: TEXT/html; CHARSET=US-ASCII

<html><body>Hi Cullen,<br><br>RELOAD-1 was a solid protocol with strengths like the flexibility of TLV, 32-bit alignment, full 160-bit IDs, well defined symbolic values, etc.&nbsp; By comparison, the ASP draft was pretty rough.&nbsp; When these two merged into RELOAD-2, most of the RELOAD-1 pros were lost.&nbsp; Is RELOAD-3 on its way?<br><br>Many fields in RELOAD-2 are variable size values or arrays, so why not use Type-Length-Value to make the protocol more "binary readable" and extensible?&nbsp; RELOAD-1 defines a single fixed header and everything else in TLV.&nbsp; That is too good to abandon, not to mention being a perfect construct for supporting multiple DHTs.<br><br> By the way, I have seen several drafts use 128-bit ID in fixed structures, which means truncating the low 32-bit of a SHA-1 hash.&nbsp; Is there a potential risk?&nbsp; Any formal paper about this?<br> <br> Thanks<br> <br> --Michael </body></html>


--===============1927128924==
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://www1.ietf.org/mailman/listinfo/p2psip

--===============1927128924==--



From p2psip-bounces@ietf.org Tue Jan 22 23:40:32 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHXPS-0000UD-W1; Tue, 22 Jan 2008 23:40:22 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHXPQ-0000IA-Uk
	for p2psip@ietf.org; Tue, 22 Jan 2008 23:40:20 -0500
Received: from szxga01-in.huawei.com ([61.144.161.53])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHXPQ-0006ac-9A
	for p2psip@ietf.org; Tue, 22 Jan 2008 23:40:20 -0500
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 <0JV200ELTY9WTJ@szxga01-in.huawei.com> for
	p2psip@ietf.org; Wed, 23 Jan 2008 12:39:33 +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 <0JV20068WY9WED@szxga01-in.huawei.com> for
	p2psip@ietf.org; Wed, 23 Jan 2008 12:39:32 +0800 (CST)
Received: from j36340 ([10.164.9.45])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JV200GNOY9VUD@szxml04-in.huawei.com> for
	p2psip@ietf.org; Wed, 23 Jan 2008 12:39:32 +0800 (CST)
Date: Wed, 23 Jan 2008 12:39:31 +0800
From: JiangXingFeng <jiang.x.f@huawei.com>
Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
In-reply-to: <44e301c85d64$c1a11010$c3f0200a@cisco.com>
To: 'Dan Wing' <dwing@cisco.com>, 'P2PSIP Mailing List' <p2psip@ietf.org>
Message-id: <003601c85d79$f261a290$2d09a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: Achc2mE+N3Ev8YYNRpCsDNPfo2q5cgAijS9QAAUvrwA=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: 
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hi, Dan:

Thanks for your comments.

ICE does support multiple servers. But I guess ICE has not considered
whether STUN server or TURN server is behind NAT. (Is my understanding
right?) So if STUN server or TURN server behind NAT are involved, the ICE
connectivity procedure will take more time to complete. I am not sure how
longer it is. 

--
JiangXingFeng

> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com]
> Sent: Wednesday, January 23, 2008 10:08 AM
> To: 'JiangXingFeng'; 'P2PSIP Mailing List'
> Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
> 
> ICE allows you to have multiple STUN servers.  In the diagram you
provided,
> Peer A could contact Peer C, Peer D, and Peer B, and would notice
different
> answers from some (or all) of them.  All of those different answers can be
> provided as different candidates (a=candidate) in the call setup message.
> 
> -d
> 
> 
> > -----Original Message-----
> > From: JiangXingFeng [mailto:jiang.x.f@huawei.com]
> > Sent: Tuesday, January 22, 2008 1:37 AM
> > To: 'P2PSIP Mailing List'
> > Subject: [P2PSIP] Choice of STUN peer or TURN peer
> >
> > Hi, all:
> >
> >
> >
> > In order to make the peers serve each other, some peers with
> > special capabilities could be exploited to play the STUN/TURN
> > server role for other peers who are behind NAT. Guys in
> > P2PSIP community has agreed with that peer behind NAT should
> > seek help from other peers, not centralized STUN/TURN server.
> >
> >
> >
> > But which kinds of peers are qualified for playing STUN/TURN
> > server? Of course, Peers on the public internet could take
> > this responsibility. I also learned from the list that peers
> > behind p2p-friendly NAT (with end-point independent mapping
> > and filtering behavior) also could do the same work. But from
> > my point of view, ICE negotiation procedure may fail if
> > choosing this kind of peer as STUN/TURN server.
> >
> >
> >
> > Let's show an example:
> >
> >
> >
> > Peer A and peer B want to communicate directly. NAT2 is a
> > p2p-friendly NAT. So peer C would be considered as a
> > candidate STUN server. If peer A choose the Peer C as its
> > STUN server, peer A will get a mapping on the NAT1 which is
> > in the address realm of private network. And Peer A will tell
> > peer B this server reflexive address. But peer B could not
> > reach it because it is in different address realm.
> >
> >
> >
> > Am I missing something? Comments are appreciated!
> >
> >
> >
> > Regards!
> >
> > --
> >
> > Jiang XingFeng
> >
> >
> >
> >
> >
> >


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



From p2psip-bounces@ietf.org Wed Jan 23 03:12:54 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHaj2-0001vJ-M8; Wed, 23 Jan 2008 03:12:48 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHaj1-0001v5-Dn
	for p2psip@ietf.org; Wed, 23 Jan 2008 03:12:47 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHaj0-0004ev-CK
	for p2psip@ietf.org; Wed, 23 Jan 2008 03:12:47 -0500
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 23 Jan 2008 00:12:45 -0800
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m0N8Cji4021958; 
	Wed, 23 Jan 2008 00:12:45 -0800
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m0N8Cj3V011601;
	Wed, 23 Jan 2008 08:12:45 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'JiangXingFeng'" <jiang.x.f@huawei.com>,
	"'P2PSIP Mailing List'" <p2psip@ietf.org>
References: <44e301c85d64$c1a11010$c3f0200a@cisco.com>
	<003601c85d79$f261a290$2d09a40a@china.huawei.com>
Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
Date: Wed, 23 Jan 2008 00:12:45 -0800
Message-ID: <4b8701c85d97$bc072990$c3f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <003601c85d79$f261a290$2d09a40a@china.huawei.com>
Thread-Index: Achc2mE+N3Ev8YYNRpCsDNPfo2q5cgAijS9QAAUvrwAAByAy4A==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4041; t=1201075965;
	x=1201939965; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[P2PSIP]=20Choice=20of=20STUN=20peer=20
	or=20TURN=20peer |Sender:=20;
	bh=z358AINMUi7I1JkkTFtMObXcrA/lno8SI/UZJ1mphjo=;
	b=cvBXCj6efEet/Hzndy4YfeOLgYA2hZDP3UwtBV4vloc1vlL1V3J2KjlOVN
	wDGPZNmqQrfPjFDxCibxmkLi0t3lMRMC7UptaAZNdIgomhhMstkMftYCR/N4
	qzRFjm5Aaaqm/2NEd/bBFCyWr0Jv8eS1/X1uZTlxkDHGp2jffriYc=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
Cc: 
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

 

> -----Original Message-----
> From: JiangXingFeng [mailto:jiang.x.f@huawei.com] 
> Sent: Tuesday, January 22, 2008 8:40 PM
> To: 'Dan Wing'; 'P2PSIP Mailing List'
> Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
> 
> Hi, Dan:
> 
> Thanks for your comments.
> 
> ICE does support multiple servers. But I guess ICE has not considered
> whether STUN server or TURN server is behind NAT. (Is my understanding
> right?) So if STUN server or TURN server behind NAT are 
> involved, the ICE
> connectivity procedure will take more time to complete.
> I am not sure how longer it is. 

There are two variables:

  1. how many candidates you could gather
  2. how quickly your peer can send connectivity checks
     to those candidates

To the first point, in the diagram you provided in your earlier email, there
are only three candidate addresses:  one from the local interface, one from
the STUN server that is behind the same NAT you're behind, and another from a
STUN server on the Internet.  Are there network topologies where more
candidate addresses would be learned?

To the second point, the additional delay depends on how quickly you can send
the connectivity checks to the additional candidates.  This rate depends on
the RTP sending rate.  So, for example, if the endpoint is going to send an
~200 byte RTP packet every 20ms, the endpoint is permitted to send a ~200 byte
connectivity check (to a new candidate) every 20ms.  With 3 different
candidates, that is 3*20ms=60ms of additional time.  60ms does not seem
significant to me.

-d


> --
> JiangXingFeng
> 
> > -----Original Message-----
> > From: Dan Wing [mailto:dwing@cisco.com]
> > Sent: Wednesday, January 23, 2008 10:08 AM
> > To: 'JiangXingFeng'; 'P2PSIP Mailing List'
> > Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
> > 
> > ICE allows you to have multiple STUN servers.  In the diagram you
> provided,
> > Peer A could contact Peer C, Peer D, and Peer B, and would notice
> different
> > answers from some (or all) of them.  All of those different 
> answers can be
> > provided as different candidates (a=candidate) in the call 
> setup message.
> > 
> > -d
> > 
> > 
> > > -----Original Message-----
> > > From: JiangXingFeng [mailto:jiang.x.f@huawei.com]
> > > Sent: Tuesday, January 22, 2008 1:37 AM
> > > To: 'P2PSIP Mailing List'
> > > Subject: [P2PSIP] Choice of STUN peer or TURN peer
> > >
> > > Hi, all:
> > >
> > >
> > >
> > > In order to make the peers serve each other, some peers with
> > > special capabilities could be exploited to play the STUN/TURN
> > > server role for other peers who are behind NAT. Guys in
> > > P2PSIP community has agreed with that peer behind NAT should
> > > seek help from other peers, not centralized STUN/TURN server.
> > >
> > >
> > >
> > > But which kinds of peers are qualified for playing STUN/TURN
> > > server? Of course, Peers on the public internet could take
> > > this responsibility. I also learned from the list that peers
> > > behind p2p-friendly NAT (with end-point independent mapping
> > > and filtering behavior) also could do the same work. But from
> > > my point of view, ICE negotiation procedure may fail if
> > > choosing this kind of peer as STUN/TURN server.
> > >
> > >
> > >
> > > Let's show an example:
> > >
> > >
> > >
> > > Peer A and peer B want to communicate directly. NAT2 is a
> > > p2p-friendly NAT. So peer C would be considered as a
> > > candidate STUN server. If peer A choose the Peer C as its
> > > STUN server, peer A will get a mapping on the NAT1 which is
> > > in the address realm of private network. And Peer A will tell
> > > peer B this server reflexive address. But peer B could not
> > > reach it because it is in different address realm.
> > >
> > >
> > >
> > > Am I missing something? Comments are appreciated!
> > >
> > >
> > >
> > > Regards!
> > >
> > > --
> > >
> > > Jiang XingFeng
> > >
> > >
> > >
> > >
> > >
> > >
> 


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



From p2psip-bounces@ietf.org Wed Jan 23 04:59:39 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHcOQ-0002Hj-4q; Wed, 23 Jan 2008 04:59:38 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHcOO-0002He-Of
	for p2psip@ietf.org; Wed, 23 Jan 2008 04:59:36 -0500
Received: from szxga01-in.huawei.com ([61.144.161.53])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHcOO-0008Im-5N
	for p2psip@ietf.org; Wed, 23 Jan 2008 04:59:36 -0500
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 <0JV300CXID229V@szxga01-in.huawei.com> for
	p2psip@ietf.org; Wed, 23 Jan 2008 17:58:51 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JV300E7GD21D7@szxga01-in.huawei.com> for
	p2psip@ietf.org; Wed, 23 Jan 2008 17:58:50 +0800 (CST)
Received: from j36340 ([10.164.9.45])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JV300JF2D210V@szxml03-in.huawei.com> for
	p2psip@ietf.org; Wed, 23 Jan 2008 17:58:49 +0800 (CST)
Date: Wed, 23 Jan 2008 17:58:49 +0800
From: JiangXingFeng <jiang.x.f@huawei.com>
Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
In-reply-to: <4b8701c85d97$bc072990$c3f0200a@cisco.com>
To: 'Dan Wing' <dwing@cisco.com>, 'P2PSIP Mailing List' <p2psip@ietf.org>
Message-id: <005601c85da6$8d2314e0$2d09a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: Achc2mE+N3Ev8YYNRpCsDNPfo2q5cgAijS9QAAUvrwAAByAy4AAD4osw
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: 
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

> From: Dan Wing [mailto:dwing@cisco.com]
> Sent: Wednesday, January 23, 2008 4:13 PM
> To: 'JiangXingFeng'; 'P2PSIP Mailing List'
> Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
> 
> 
> 
> > -----Original Message-----
> > From: JiangXingFeng [mailto:jiang.x.f@huawei.com]
> > Sent: Tuesday, January 22, 2008 8:40 PM
> > To: 'Dan Wing'; 'P2PSIP Mailing List'
> > Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
> > ICE does support multiple servers. But I guess ICE has not considered
> > whether STUN server or TURN server is behind NAT. (Is my understanding
> > right?) So if STUN server or TURN server behind NAT are
> > involved, the ICE
> > connectivity procedure will take more time to complete.
> > I am not sure how longer it is.
> 
> There are two variables:
> 
>   1. how many candidates you could gather
>   2. how quickly your peer can send connectivity checks
>      to those candidates
> 
> To the first point, in the diagram you provided in your earlier email,
there
> are only three candidate addresses:  one from the local interface, one
from
> the STUN server that is behind the same NAT you're behind, and another
from a
> STUN server on the Internet.  Are there network topologies where more
> candidate addresses would be learned?

Even if there are enough candidates who could be learned by using enough
servers, how could ICE sort the candidate pairs in the order so that the
workable pairs could be considered as soon as possible? 

Regards!
JiangXingFeng


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



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


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

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

Marcin=20

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

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



From p2psip-bounces@ietf.org Wed Jan 23 07:31:22 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHekQ-000185-FC; Wed, 23 Jan 2008 07:30:30 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHekO-00017u-7M
	for p2psip@ietf.org; Wed, 23 Jan 2008 07:30:28 -0500
Received: from smtp.nokia.com ([192.100.122.230] helo=mgw-mx03.nokia.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHekN-0005Jn-Es
	for p2psip@ietf.org; Wed, 23 Jan 2008 07:30:28 -0500
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m0NCThwO004945; Wed, 23 Jan 2008 14:30:17 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 23 Jan 2008 14:29:52 +0200
Received: from esebe102.NOE.Nokia.com ([172.21.138.217]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 23 Jan 2008 14:29:52 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: RE: RE: [P2PSIP] HIP: optional, mandatory?
Date: Wed, 23 Jan 2008 14:34:19 +0200
Message-ID: <3F18E76823C95E4795181D74BAC7664F05BE199F@esebe102.NOE.Nokia.com>
In-Reply-To: <d4accb881f22e.4795b446@us.army.mil>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RE: RE: [P2PSIP] HIP: optional, mandatory?
Thread-Index: AchdAU+oBHXnBCxfT8ClO76zGHZqxQAuTCGQ
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
	<465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com>
	<284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>
	<DD40D2FF-809B-4B1F-B43B-0E8F41ED21DB@quinthar.com>
	<24CCCC428EFEA2469BF046DB3C7A8D223AE531@namail5.corp.adobe.com>
	<3F18E76823C95E4795181D74BAC7664F05B951F1@esebe102.NOE.Nokia.com>
	<e3c8ad9a1429b.47946208@us.army.mil>
	<3F18E76823C95E4795181D74BAC7664F05B95CF4@esebe102.NOE.Nokia.com>
	<d4accb881f22e.4795b446@us.army.mil>
From: <marcin.matuszewski@nokia.com>
To: <radhika.r.roy@us.army.mil>
X-OriginalArrivalTime: 23 Jan 2008 12:29:52.0328 (UTC)
	FILETIME=[A711AC80:01C85DBB]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Cc: p2psip@ietf.org
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hi Radhika,

We share the same goal.=20

Salman, Henning and me are specifying the P2PP protocol
http://tools.ietf.org/wg/p2psip/draft-baset-p2psip-p2pp-01.txt. The
version of the document is going to be updated based on our recent
implementation experience. =20

We would appreciate your suggestions and comments. The cooperation on
software development is also appreciated. This will allow P2PSIP WG to
converge much faster.

Marcin


>-----Original Message-----
>From: ext Roy, Radhika R Dr CTR USA USAMC=20
>[mailto:radhika.r.roy@us.army.mil]=20
>Sent: 22 January, 2008 16:16
>To: Matuszewski Marcin (Nokia-NRC/Helsinki)
>Cc: p2psip@ietf.org; salman@cs.columbia.edu; Matuszewski=20
>Marcin (Nokia-NRC/Helsinki)
>Subject: Re: RE: RE: [P2PSIP] HIP: optional, mandatory?
>
>Hi, Mercin:
>
>What we want is to develop the P2PSIP protocol standard for=20
>this WG. The P2PSIP protocol drafts are there. You can help to=20
>provide insights which proposals are good and if needed what=20
>improvements need to be done to finalize the specs or you can=20
>proposed a new one or a modified draft combining with the=20
>existing ones.
>
>In this way, you can play a role to standardize the P2PSIP=20
>protocol for this WG. Then we can proceed to build other P2P=20
>things (e.g. HIP-overlay using the standardized P2PSIP=20
>protocol of this WG).
>
>Best regards,
>Radhika
>
>----- Original Message -----
>From: marcin.matuszewski@nokia.com
>Date: Tuesday, January 22, 2008 6:02
>Subject: RE: RE: [P2PSIP] HIP: optional, mandatory?
>To: radhika.r.roy@us.army.mil
>Cc: p2psip@ietf.org, salman@cs.columbia.edu,=20
>marcin.matuszewski@nokia.com
>
>>=20
>> >[RRR] Yes, you are right. So, please help this P2PSIP WG to=20
>complete=20
>> >the spec for the base P2PSIP protocol based on these implementation=20
>> >experiences as soon as possible. We would appreciate this.
>>=20
>> We are constantly improving our software implementation and protocol=20
>> specification. We published a paper at CCNC conference=20
>(Mobile P2PSIP=20
>> - Peer-to-Peer SIP communication in mobile communities). It=20
>should be=20
>> available from ieeexplore.
>>=20
>> Do you think that an implementation report (with some measurements)=20
>> would be useful?
>>=20
>> Marcin
>>=20
>> >-----Original Message-----
>> >From: ext Roy, Radhika R Dr CTR USA USAMC=20
>> >[mailto:radhika.r.roy@us.army.mil]
>> >Sent: 21 January, 2008 16:13
>> >To: Matuszewski Marcin (Nokia-NRC/Helsinki)
>> >Cc: hsinnrei@adobe.com; dbarrett@quinthar.com; fluffy@cisco.com;=20
>> >p2psip@ietf.org
>> >Subject: Re: RE: [P2PSIP] HIP: optional, mandatory?
>> >
>> >Inline [RRR]
>> >
>> >----- Original Message -----
>> >From: marcin.matuszewski@nokia.com
>> >Date: Friday, January 18, 2008 15:30
>> >Subject: RE: [P2PSIP] HIP: optional, mandatory?
>> >To: hsinnrei@adobe.com, dbarrett@quinthar.com, fluffy@cisco.com
>> >Cc: p2psip@ietf.org
>> >
>> >>=20
>> >> >Opinion: This call to urgency can be best met IMHO by using
>> P2PP
>> >> >implemented on 600 nodes on Planet Lab since it meets the
>> >criteria of
>> >> >running code, open available free code and large footprint=20
>> >> >deployment.
>> >>=20
>> >> I fully agree. Besides Nokia's implementation shows that
>> >P2PP can also
>> >> work on mobile devices. Some of you who visited Nokia's P2PSIP
>> demo
>> >> stand in Las Vegas could see a demo of the P2PP implementation
>> on
>> >> Nokiaphones. At the stand we were showing how a mobile phone
>> that
>> >> implementsP2PP can join the Columbia Univ.'s 600 nodes overlay
>> on
>> >> Planet Lab and allow users to use basic SIP services. The demo
>> was
>> >> done in colaborationwith Columbia Univ.
>> >> Everyone who whould like to join the P2PP trial network
>> >please send an
>> >> email to Salman, Henning or me.
>> >>=20
>> >> Our goal is to specify a protocol based on our implementation=20
>> >> experience. It is very easy to write protocol specifications
>> >that are
>> >> difficult to implement and therefore have high chances to
>> >fail in the
>> >> market, what we could see in the past.
>> >>=20
>> >> Marcin
>> >
>> >[RRR] Yes, you are right. So, please help this P2PSIP WG to=20
>complete=20
>> >the spec for the base P2PSIP protocol based on these implementation=20
>> >experiences as soon as possible. We would appreciate this.
>> >
>>=20
>

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



From p2psip-bounces@ietf.org Wed Jan 23 09:16:04 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHgNj-00005c-NO; Wed, 23 Jan 2008 09:15:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHgNi-00005K-D1
	for p2psip@ietf.org; Wed, 23 Jan 2008 09:15:10 -0500
Received: from mxoutps1.us.army.mil ([143.69.250.38])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHgNd-0008R4-Pp
	for p2psip@ietf.org; Wed, 23 Jan 2008 09:15:10 -0500
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=T28yheQbOiuKqmV6cZRe1z5x41yWBao+84+v3xj5ZivV9zZ57cNNuMq7
	G13wvHAzmPk+QuicVs7hSE3phB4ZPQ==;
From: "Roy, Radhika R Dr CTR USA USAMC" <radhika.r.roy@us.army.mil>
X-AKO: 105926420:10.224.36.65:23 Jan 2008 14:15:01 +0000:$Webmail:None
X-IronPort-AV: E=Sophos;i="4.25,238,1199664000"; d="scan'208";a="105926420"
Received: from mail5.int.ps1.us.army.mil (HELO us.army.mil) ([10.224.36.65])
	by mxoutps1.us.army.mil with ESMTP; 23 Jan 2008 14:15:01 +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); Wed, 23 Jan
	2008 09:15:01 -0500
To: marcin.matuszewski@nokia.com
Message-ID: <e044864a19844.47970595@us.army.mil>
Date: Wed, 23 Jan 2008 09:15:01 -0500
X-Mailer: Sun Java(tm) System Messenger Express 6.2-9.04 (built Jun 11
 2007)
MIME-Version: 1.0
Content-Language: en
Subject: RE: [P2PSIP] HIP: optional, mandatory?
X-Accept-Language: en
Priority: normal
In-Reply-To: <3F18E76823C95E4795181D74BAC7664F05BE199F@esebe102.NOE.Nokia.com>
References: <476BA8D9.4010203@ericsson.com>
	<20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com>
	<476E2B7C.9070601@ericsson.com>
	<20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com>
	<7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com>
	<10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu>
	<4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com>
	<465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com>
	<284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com>
	<DD40D2FF-809B-4B1F-B43B-0E8F41ED21DB@quinthar.com>
	<24CCCC428EFEA2469BF046DB3C7A8D223AE531@namail5.corp.adobe.com>
	<3F18E76823C95E4795181D74BAC7664F05B951F1@esebe102.NOE.Nokia.com>
	<e3c8ad9a1429b.47946208@us.army.mil>
	<3F18E76823C95E4795181D74BAC7664F05B95CF4@esebe102.NOE.Nokia.com>
	<d4accb881f22e.4795b446@us.army.mil>
	<3F18E76823C95E4795181D74BAC7664F05BE199F@esebe102.NOE.Nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: p2psip@ietf.org
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Marcin:

Yes, that is what this WG, I believe, wants - helping to finalize the base P2PSIP protocol through implementation experiences as soon as possible.

Best regards,
Radhika

----- Original Message -----
From: marcin.matuszewski@nokia.com
Date: Wednesday, January 23, 2008 7:30
Subject: RE: RE: RE: [P2PSIP] HIP: optional, mandatory?
To: radhika.r.roy@us.army.mil
Cc: p2psip@ietf.org, salman@cs.columbia.edu, hgs@cs.columbia.edu, marcin.matuszewski@nokia.com

> Hi Radhika,
> 
> We share the same goal. 
> 
> Salman, Henning and me are specifying the P2PP protocol
> http://tools.ietf.org/wg/p2psip/draft-baset-p2psip-p2pp-01.txt. The
> version of the document is going to be updated based on our recent
> implementation experience. 
> 
> We would appreciate your suggestions and comments. The cooperation on
> software development is also appreciated. This will allow P2PSIP 
> WG to
> converge much faster.
> 
> Marcin
> 
> 
> >-----Original Message-----
> >From: ext Roy, Radhika R Dr CTR USA USAMC 
> >[mailto:radhika.r.roy@us.army.mil] 
> >Sent: 22 January, 2008 16:16
> >To: Matuszewski Marcin (Nokia-NRC/Helsinki)
> >Cc: p2psip@ietf.org; salman@cs.columbia.edu; Matuszewski 
> >Marcin (Nokia-NRC/Helsinki)
> >Subject: Re: RE: RE: [P2PSIP] HIP: optional, mandatory?
> >
> >Hi, Mercin:
> >
> >What we want is to develop the P2PSIP protocol standard for 
> >this WG. The P2PSIP protocol drafts are there. You can help to 
> >provide insights which proposals are good and if needed what 
> >improvements need to be done to finalize the specs or you can 
> >proposed a new one or a modified draft combining with the 
> >existing ones.
> >
> >In this way, you can play a role to standardize the P2PSIP 
> >protocol for this WG. Then we can proceed to build other P2P 
> >things (e.g. HIP-overlay using the standardized P2PSIP 
> >protocol of this WG).
> >
> >Best regards,
> >Radhika
> >

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



From p2psip-bounces@ietf.org Wed Jan 23 09:32:07 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHgdH-0006Bv-Fo; Wed, 23 Jan 2008 09:31:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHgdG-00066O-D5
	for p2psip@ietf.org; Wed, 23 Jan 2008 09:31:14 -0500
Received: from nz-out-0506.google.com ([64.233.162.224])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHgdF-0000NT-SB
	for p2psip@ietf.org; Wed, 23 Jan 2008 09:31:14 -0500
Received: by nz-out-0506.google.com with SMTP id n1so1696701nzf.4
	for <p2psip@ietf.org>; Wed, 23 Jan 2008 06:31:13 -0800 (PST)
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=euPpeCr5BdyiiD/4WSBaXY9KJrECu23XU9i+EyeOeBo=;
	b=sfHwbXP/Tc47gb492Aed9U/dFsE65imDCmNAF5bXP8MpoJrqdGmpyI8ldLf7A3SAqvPcpuZeeTArkLeTrlu9meu/q4/CBdNrcj86a5YoPWzTF1uxsUtqqOuv/CV+7d8lwySN1Xw/GX0VeJ0WsV/zHLzXTSAZC/IxUloBi87Tb0Q=
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=t89TY+j1gmbGtIGtc/86/eooXmsm7pw6YWLblntaZlzqvIUyhOiabtzZ14h4b6qhCis7H9E0x+b7nH1ms90FHnewPK6xtQM3Ggoa/nc/LmOhLGdGkjpRWC6jDp1EN2X48MjcnT9EyjnajUd+NIbO0Fbh0BtxqaLb9OCz3eEMQp0=
Received: by 10.115.79.1 with SMTP id g1mr882016wal.2.1201098673143;
	Wed, 23 Jan 2008 06:31:13 -0800 (PST)
Received: by 10.114.209.13 with HTTP; Wed, 23 Jan 2008 06:31:13 -0800 (PST)
Message-ID: <20d2bdfb0801230631h4b40a4dbr1d03fae14f8852ea@mail.gmail.com>
Date: Wed, 23 Jan 2008 09:31:13 -0500
From: "Bruce Lowekamp" <lowekamp@sipeerior.com>
To: JiangXingFeng <jiang.x.f@huawei.com>
Subject: Re: [P2PSIP] Choice of STUN peer or TURN peer
In-Reply-To: <005601c85da6$8d2314e0$2d09a40a@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4b8701c85d97$bc072990$c3f0200a@cisco.com>
	<005601c85da6$8d2314e0$2d09a40a@china.huawei.com>
X-Google-Sender-Auth: 014508d1170c5ab9
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

On Jan 23, 2008 4:58 AM, JiangXingFeng <jiang.x.f@huawei.com> wrote:
> > From: Dan Wing [mailto:dwing@cisco.com]
> > Sent: Wednesday, January 23, 2008 4:13 PM
> > To: 'JiangXingFeng'; 'P2PSIP Mailing List'
> > Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
> >
> >
> >
> > > -----Original Message-----
> > > From: JiangXingFeng [mailto:jiang.x.f@huawei.com]
> > > Sent: Tuesday, January 22, 2008 8:40 PM
> > > To: 'Dan Wing'; 'P2PSIP Mailing List'
> > > Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
> > > ICE does support multiple servers. But I guess ICE has not considered
> > > whether STUN server or TURN server is behind NAT. (Is my understanding
> > > right?) So if STUN server or TURN server behind NAT are
> > > involved, the ICE
> > > connectivity procedure will take more time to complete.
> > > I am not sure how longer it is.

A STUN server being behind a NAT is irrelevant from the view of the
STUN client (assuming it knows how to contact the STUN server).  The
NAT in front of the STUN server doesn't change the address of an
incoming request from another client.

Similarly, a TURN server being behind a NAT is irrelevant as long as
both peers can contact it.  A peer that wishes to be a TURN server but
is behind a bad NAT is probably better off not being a TURN server,
but that is about it.

What matters is the kind of NATs the client (A and B in your example) is behind.

> >
> > There are two variables:
> >
> >   1. how many candidates you could gather
> >   2. how quickly your peer can send connectivity checks
> >      to those candidates
> >
> > To the first point, in the diagram you provided in your earlier email,
> there
> > are only three candidate addresses:  one from the local interface, one
> from
> > the STUN server that is behind the same NAT you're behind, and another
> from a
> > STUN server on the Internet.  Are there network topologies where more
> > candidate addresses would be learned?
>
> Even if there are enough candidates who could be learned by using enough
> servers, how could ICE sort the candidate pairs in the order so that the
> workable pairs could be considered as soon as possible?

The reload-02 section I pointed you to describes this very briefly,
but let me try to provide more details. In almost all cases, A and B
will be behind friendly NATs.  In your particular example, no matter
how many STUN servers B uses, it will know two candidate addresses.
In A's case, it will know two or maybe three if it has C in its list
of STUN servers.

Two points to note here.  First, for peer protocol connections, there
is no need to gather candidate addresses when you wish to establish a
new connection because you can do that over time.  Second, reload-02
suggests that you maintain sets of peers grouped according to the
reflexive address they return, then make one query to each when you
gather candidates for media connections (or refresh your peer protocol
addresses).

Now the less common, but important case, is when A or B is behind a
p2p unfriendly NAT.  Any of your NAT1, NAT2, NAT3 could be unfriendly.
 In this case, what will happen is that A or B will discover that as
they make connections with new peers, the number of different
reflexive addresses that they see grows.  In B's case, it will
probably grow infinitely large.  In A's case, assuming there is more
than Peer C behind NAT 2 with it, if NAT 2 is the unfriendly NAT A may
observe several peers reporting the same reflexive address because
they are also behind NAT2.  In these cases, A and B should provide
addresses they see repeated as ICE candidates, but there's unlikely to
be any point in providing a list of every reflexive address ever seen.

In any event, when ordering the candidates for an ice offer, start
with the local address and list the learned addresses in the order of
their frequency.  That will very rarely be more than two.

Bruce

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



From p2psip-bounces@ietf.org Wed Jan 23 10:21:33 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHhP5-0005ln-7r; Wed, 23 Jan 2008 10:20:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHhP4-0005lc-B1
	for p2psip@ietf.org; Wed, 23 Jan 2008 10:20:38 -0500
Received: from wa-out-1112.google.com ([209.85.146.179])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHhOS-0001eR-Ag
	for p2psip@ietf.org; Wed, 23 Jan 2008 10:20:38 -0500
Received: by wa-out-1112.google.com with SMTP id k40so6907679wah.25
	for <p2psip@ietf.org>; Wed, 23 Jan 2008 07:17:10 -0800 (PST)
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=Hy9Hk9gRyd+4Rv9giVhggSskgd9ceLrMWFiV0LY0QJ8=;
	b=qN6gJ0dn4Cv2GjigYzPkxqWSkW+xzfoQ1iTinrcef8v/avEaptiNKbFgV25clm55TVB6ysBfLkPhWvbMseUH+G5zWa3GVS/mv5+wcMms8Q5SmlKRD1lmEP5exl4pxTstRumEuMZ3TkfuaqSKk51N1ZjfBRREZgl091bpMoccP1k=
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=J1NuNVvRbEVMRq4ZY/cCGDw0AKDKNAf3CaIJGijqzSBw2PIiy5sIFAnBZeJsb5gHyz53X7OaDqCQ4EbqR1Tr1sMDKaf3cYUMsrgI9U6OXkL/Lkr+4s3Z2BBbegwi+WQNCdkj5WAQPxN4uCX1CZnBZp50wymwV199pq+Se/ruHwY=
Received: by 10.114.134.1 with SMTP id h1mr8411206wad.4.1201101430183;
	Wed, 23 Jan 2008 07:17:10 -0800 (PST)
Received: by 10.114.209.13 with HTTP; Wed, 23 Jan 2008 07:17:10 -0800 (PST)
Message-ID: <20d2bdfb0801230717l579cfc30ic10b6cb678a18321@mail.gmail.com>
Date: Wed, 23 Jan 2008 10:17:10 -0500
From: "Bruce Lowekamp" <lowekamp@sipeerior.com>
To: michaelc@idssoftware.com
Subject: Re: [P2PSIP] Status of RELOAD
In-Reply-To: <20080122200203.59ca11a9ba9389561a029f06442e67fa.ff22e2cc50.wbe@email.secureserver.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20080122200203.59ca11a9ba9389561a029f06442e67fa.ff22e2cc50.wbe@email.secureserver.net>
X-Google-Sender-Auth: 48ef063c82b4c139
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: p2psip@ietf.org
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Michael,

Of course, there is always a new version of a draft on the way...

You're right that reload-01 used a very simple and uniform TLV
structure for everything.  The uniformity of that is nice, but it has
a couple of problems:
- because it allowed the various parameters to be in any order,
parsing it and locating elements of the structure was fairly
complicated.
- for fields that must be there exactly once and have a fixed length
(i.e. a uint32), it's a lot of overhead.

The goal of the reload-02 encoding structure was to get rid of the TLV
structure when it's not necessary.  i.e. when you know what type
you're encoding, give that type a predefined structure when it can
have one.  For example, in reload-02, the CONNECT request in 5.1.2.1
is a good example.  You know what the fields of a connect (it's
encoding the information needed by ICE) need to be.  In this case,
they can be variable length, and there can be varying numbers of
candidate addresses.  The structure there is of a predefined order,
but allows the length of each field to be specified.  Essentially, the
T of TLV isn't needed because we know the order of the types of a
CONNECT request.

Unfortunately, you're absolutely right in observing that the structure
used in reload-02 isn't as clear as it should be.  Basically, we ran
out of time.  There is an underlying type definition language being
used here (thanks to ekr) that ultimately would make things a lot
clearer and easier to implement, but right now it's a bit confusing
until you spend time with it.  I think ultimately this way of encoding
will be much easier to parse.

The header is still basically fixed.  It allows the via and route list
to vary (their order will be reversed in the next version, which will
simplify processing), but otherwise it's very similar.

I don't know of a formal paper on it, but 128-bits is more than enough
to provide reasonable guarantees of uniqueness.  Technically, if what
you do is truncate a hash (rather than using a hash that naturally
produces that length), as long as it's a good hash, all bits are
equally random, so truncating it is still safe.

Bruce




On Jan 22, 2008 10:02 PM,  <michaelc@idssoftware.com> wrote:
> Hi Cullen,
>
> RELOAD-1 was a solid protocol with strengths like the flexibility of TLV,
> 32-bit alignment, full 160-bit IDs, well defined symbolic values, etc.  By
> comparison, the ASP draft was pretty rough.  When these two merged into
> RELOAD-2, most of the RELOAD-1 pros were lost.  Is RELOAD-3 on its way?
>
> Many fields in RELOAD-2 are variable size values or arrays, so why not use
> Type-Length-Value to make the protocol more "binary readable" and
> extensible?  RELOAD-1 defines a single fixed header and everything else in
> TLV.  That is too good to abandon, not to mention being a perfect construct
> for supporting multiple DHTs.
>
>  By the way, I have seen several drafts use 128-bit ID in fixed structures,
> which means truncating the low 32-bit of a SHA-1 hash.  Is there a potential
> risk?  Any formal paper about this?
>
>  Thanks
>
>  --Michael
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.ietf.org/mailman/listinfo/p2psip
>
>

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



From p2psip-bounces@ietf.org Wed Jan 23 22:46:18 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHt1k-0007PA-QC; Wed, 23 Jan 2008 22:45:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHt1j-0007KL-Dc
	for p2psip@ietf.org; Wed, 23 Jan 2008 22:45:19 -0500
Received: from elasmtp-dupuy.atl.sa.earthlink.net ([209.86.89.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHt1i-0008LX-QY
	for p2psip@ietf.org; Wed, 23 Jan 2008 22:45:19 -0500
Received: from [72.87.190.177] (helo=[10.9.0.1])
	by elasmtp-dupuy.atl.sa.earthlink.net with asmtp (Exim 4.34)
	id 1JHt1e-0000zw-VI; Wed, 23 Jan 2008 22:45:15 -0500
Message-ID: <479809DC.4050607@idssoftware.com>
Date: Wed, 23 Jan 2008 19:45:32 -0800
From: Michael Chen <michaelc@idssoftware.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Bruce Lowekamp <lowekamp@sipeerior.com>
Subject: Re: [P2PSIP] Status of RELOAD
References: <20080122200203.59ca11a9ba9389561a029f06442e67fa.ff22e2cc50.wbe@email.secureserver.net>
	<20d2bdfb0801230717l579cfc30ic10b6cb678a18321@mail.gmail.com>
In-Reply-To: <20d2bdfb0801230717l579cfc30ic10b6cb678a18321@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 68edf72dbb77893ca35f5539f9d485d07e972de0d01da940f226d258e3499bd3e525543785178fff350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 72.87.190.177
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: p2psip@ietf.org
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Bruce,

I appreciate the clarification and look forward to Reload-3. Just a 
reminder, in early December, Cullen and I had the following Q&A, which I 
hope to be formally defined in the upcoming draft.

Thanks

--Michael

On Nov 28, 2007, at 6:57 PM, Michael Chen wrote:
> I don't see where the protocol sends the originator's peer-ID. At the 
> end of section 4.1, it says the via list starts out empty and the 
> route list has the intermediate and destination peer IDs.  Say A wants 
> to reach C through B, then in the forwarding header sent by A, the 
> route-list contains [B, C], and the via list is empty.  Where does C 
> or B for that matter know the peer ID of A when it's time to send the 
> respond back?
>
> Should the via-list in the forwarding header sent by A contains the 
> peer ID of A?
Yes, we do need the A to get in the list,  but the ID is inserted by B. 
The logic behind this had to do with some security issues and logic 
about what B inserts. B actually inserts the peer it perceives the 
message came from. This helps with spoofing return routes by having 
responses go to where they came from. Sorry this email is brief, I will 
try and write a clearer one if this does make sense.



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



From p2psip-bounces@ietf.org Thu Jan 24 02:24:19 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHwQg-0005A5-4y; Thu, 24 Jan 2008 02:23:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHwQe-00059r-T4
	for p2psip@ietf.org; Thu, 24 Jan 2008 02:23:16 -0500
Received: from szxga01-in.huawei.com ([61.144.161.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHwQc-0003tq-Kw
	for p2psip@ietf.org; Thu, 24 Jan 2008 02:23:16 -0500
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 <0JV50009X0HLN9@szxga01-in.huawei.com> for
	p2psip@ietf.org; Thu, 24 Jan 2008 15:22:34 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JV500ESK0HKBE@szxga01-in.huawei.com> for
	p2psip@ietf.org; Thu, 24 Jan 2008 15:22:33 +0800 (CST)
Received: from j36340 ([10.164.9.45])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JV5002LR0HK4W@szxml03-in.huawei.com> for
	p2psip@ietf.org; Thu, 24 Jan 2008 15:22:32 +0800 (CST)
Date: Thu, 24 Jan 2008 15:22:31 +0800
From: JiangXingFeng <jiang.x.f@huawei.com>
Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
In-reply-to: <20d2bdfb0801230631h4b40a4dbr1d03fae14f8852ea@mail.gmail.com>
To: 'Bruce Lowekamp' <lowekamp@sipeerior.com>
Message-id: <005d01c85e59$e25fd250$2d09a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AchdzJ90kFg6Xq4fTZOyCgPVF+N/zwAif+RQ
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org


> Similarly, a TURN server being behind a NAT is irrelevant as long as
> both peers can contact it.  A peer that wishes to be a TURN server but
> is behind a bad NAT is probably better off not being a TURN server,
> but that is about it.

The following is another story. For peer to be a TURN server, how could TURN
clients get their allocated transport address belonging to the TURN server
if the TURN server is behind NAT? Because in TURN, the allocated address is
encapsulated in the message and then communicated with the clients, but due
to NAT, the allocated address could not be contacted by the clients in the
future. 

Am I missing soothing?  
> 
> 
> The reload-02 section I pointed you to describes this very briefly,
> but let me try to provide more details. In almost all cases, A and B
> will be behind friendly NATs.  In your particular example, no matter
> how many STUN servers B uses, it will know two candidate addresses.
> In A's case, it will know two or maybe three if it has C in its list
> of STUN servers.

> 
> Two points to note here.  First, for peer protocol connections, there
> is no need to gather candidate addresses when you wish to establish a
> new connection because you can do that over time.  Second, reload-02
> suggests that you maintain sets of peers grouped according to the
> reflexive address they return, then make one query to each when you
> gather candidates for media connections (or refresh your peer protocol
> addresses).

Thanks for your explanations. You mean that reload-2 uses the reflexive
address from its peers as its peer reflexive address candidate?

What my concern is how the peer learns the reflexive address when it just
joins the overlay? It should find a bootstrap peer? Must the bootstrap peer
have a public address? If not, how could the peer contact directly with the
bootstrap peer? 

Another concern is: although a peer could gather candidates over time, the
first reflexive address SHOULD be on the public Internet (If bootstrap peer
has to have a public address). The peer must actively find the STUN servers
and only passively relying on the packets from its peers to get reflexive
candidate is not enough because its peers could not contact him directly due
to NAT. 

One more question here is: how do you define p2p-friendly NAT in terms of
filtering behavior? Do you refer to end-point independent filtering or
others? If it is the case, the security property would be sacrificed.  

> 
> Now the less common, but important case, is when A or B is behind a
> p2p unfriendly NAT.  Any of your NAT1, NAT2, NAT3 could be unfriendly.
>  In this case, what will happen is that A or B will discover that as
> they make connections with new peers, the number of different
> reflexive addresses that they see grows.  In B's case, it will
> probably grow infinitely large.  In A's case, assuming there is more
> than Peer C behind NAT 2 with it, if NAT 2 is the unfriendly NAT A may
> observe several peers reporting the same reflexive address because
> they are also behind NAT2.  In these cases, A and B should provide
> addresses they see repeated as ICE candidates, but there's unlikely to
> be any point in providing a list of every reflexive address ever seen.
> 
> In any event, when ordering the candidates for an ice offer, start
> with the local address and list the learned addresses in the order of
> their frequency.  That will very rarely be more than two.

Whatever method being used to sort the candidate, if two candidates in the
candidate pair is not within the same realm, the connectivity check must
fail, hence the connectivity check time will be prolonged. 




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



From p2psip-bounces@ietf.org Thu Jan 24 13:04:37 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JI6QO-0007Vy-9a; Thu, 24 Jan 2008 13:03:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JI6QN-0007Vm-3P
	for p2psip@ietf.org; Thu, 24 Jan 2008 13:03:39 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1JI6QL-0004gI-9U
	for p2psip@ietf.org; Thu, 24 Jan 2008 13:03:39 -0500
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-3.cisco.com with ESMTP; 24 Jan 2008 10:03:36 -0800
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m0OI3au0020480; 
	Thu, 24 Jan 2008 10:03:36 -0800
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m0OI3TjA007888;
	Thu, 24 Jan 2008 18:03:35 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'JiangXingFeng'" <jiang.x.f@huawei.com>,
	"'Bruce Lowekamp'" <lowekamp@sipeerior.com>
References: <20d2bdfb0801230631h4b40a4dbr1d03fae14f8852ea@mail.gmail.com>
	<005d01c85e59$e25fd250$2d09a40a@china.huawei.com>
Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
Date: Thu, 24 Jan 2008 10:03:28 -0800
Message-ID: <000b01c85eb3$70cc6720$c3f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AchdzJ90kFg6Xq4fTZOyCgPVF+N/zwAif+RQABT2TDA=
In-Reply-To: <005d01c85e59$e25fd250$2d09a40a@china.huawei.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5438; t=1201197816;
	x=1202061816; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[P2PSIP]=20Choice=20of=20STUN=20peer=20
	or=20TURN=20peer |Sender:=20;
	bh=0QGs0jttF+GHeKKSNedxYviJNIugU7dqXRVEpHfmaBc=;
	b=B8Ac4H7jhK8brZU1/a5rDlSZT8eVxm108kCGZoDlY6tii8DhJj1XRG8WqF
	fpvs25sdl69NO0q21Gx4aZgnrDZ3oLTCDkUauuZEC6itMS7QJEq6xkZ45S9M
	yXukJuT9Qh;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

> > Similarly, a TURN server being behind a NAT is irrelevant as long as
> > both peers can contact it.  A peer that wishes to be a TURN 
> > server but
> > is behind a bad NAT is probably better off not being a TURN server,
> > but that is about it.
> 
> The following is another story. For peer to be a TURN server, 
> how could TURN
> clients get their allocated transport address belonging to 
> the TURN server
> if the TURN server is behind NAT? Because in TURN, the 
> allocated address is
> encapsulated in the message and then communicated with the 
> clients, but due
> to NAT, the allocated address could not be contacted by the 
> clients in the future. 
>
> Am I missing soothing?  


The TURN server is responsible for obtaining a publicly-routable
address, and giving that address to the TURN client.  The TURN
specification, as currently written, expects the TURN server
itself to be on a publicly-routable network ("on the Internet").

If, however, the TURN server is behind a NAT, and we want the 
TURN server to still be responsible for obtaining a 
publicly-routable IP address, you could do that.  Here is a 
new technique that could be used:  the TURN server could use 
STUN (or NAT-PMP or UPnP, if there is only one NAT between 
the TURN server and the Internet), and obtain a publicly-
routable mapping:


  TURN client         STUN server          NAT  TURN server
       |                   |                |      |
 1.    |------give me a TURN address------->|----->|
 2.    |                   |<--STUN Request--------|
 3.    |                   |-STUN Response->|----->|
 4.    |<-----here is your TURN address------------|


Messages 2-3 are normal STUN request/response messages, and
tell the TURN server a publicly-routable IP address and UDP
port.  The IP address and UDP port returned in in the STUN 
Response (message 3) is the TURN server's publicly-routable
transport address, and is given to the TURN client in message 
4.

For the above message flow to work, the NAT has to be
p2p-friendly, of course -- that is a requirement for a
successful TURN server behind a NAT.

-d



> > 
> > 
> > The reload-02 section I pointed you to describes this very briefly,
> > but let me try to provide more details. In almost all cases, A and B
> > will be behind friendly NATs.  In your particular example, no matter
> > how many STUN servers B uses, it will know two candidate addresses.
> > In A's case, it will know two or maybe three if it has C in its list
> > of STUN servers.
> 
> > 
> > Two points to note here.  First, for peer protocol 
> connections, there
> > is no need to gather candidate addresses when you wish to 
> establish a
> > new connection because you can do that over time.  Second, reload-02
> > suggests that you maintain sets of peers grouped according to the
> > reflexive address they return, then make one query to each when you
> > gather candidates for media connections (or refresh your 
> peer protocol
> > addresses).
> 
> Thanks for your explanations. You mean that reload-2 uses the 
> reflexive
> address from its peers as its peer reflexive address candidate?
> 
> What my concern is how the peer learns the reflexive address 
> when it just
> joins the overlay? It should find a bootstrap peer? Must the 
> bootstrap peer
> have a public address? If not, how could the peer contact 
> directly with the
> bootstrap peer? 
> 
> Another concern is: although a peer could gather candidates 
> over time, the
> first reflexive address SHOULD be on the public Internet (If 
> bootstrap peer
> has to have a public address). The peer must actively find 
> the STUN servers
> and only passively relying on the packets from its peers to 
> get reflexive
> candidate is not enough because its peers could not contact 
> him directly due
> to NAT. 
> 
> One more question here is: how do you define p2p-friendly NAT 
> in terms of
> filtering behavior? Do you refer to end-point independent filtering or
> others? If it is the case, the security property would be 
> sacrificed.  
> 
> > 
> > Now the less common, but important case, is when A or B is behind a
> > p2p unfriendly NAT.  Any of your NAT1, NAT2, NAT3 could be 
> unfriendly.
> >  In this case, what will happen is that A or B will discover that as
> > they make connections with new peers, the number of different
> > reflexive addresses that they see grows.  In B's case, it will
> > probably grow infinitely large.  In A's case, assuming there is more
> > than Peer C behind NAT 2 with it, if NAT 2 is the 
> unfriendly NAT A may
> > observe several peers reporting the same reflexive address because
> > they are also behind NAT2.  In these cases, A and B should provide
> > addresses they see repeated as ICE candidates, but there's 
> unlikely to
> > be any point in providing a list of every reflexive address 
> ever seen.
> > 
> > In any event, when ordering the candidates for an ice offer, start
> > with the local address and list the learned addresses in 
> the order of
> > their frequency.  That will very rarely be more than two.
> 
> Whatever method being used to sort the candidate, if two 
> candidates in the
> candidate pair is not within the same realm, the connectivity 
> check must
> fail, hence the connectivity check time will be prolonged. 
> 
> 
> 


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



From p2psip-bounces@ietf.org Thu Jan 24 13:15:22 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JI6ar-0007KZ-Qa; Thu, 24 Jan 2008 13:14:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JI6aq-0007F3-JP
	for p2psip@ietf.org; Thu, 24 Jan 2008 13:14:28 -0500
Received: from exprod6og105.obsmtp.com ([64.18.1.189])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JI6ap-0004so-Mh
	for p2psip@ietf.org; Thu, 24 Jan 2008 13:14:28 -0500
Received: from source ([192.150.20.142]) by exprod6ob105.postini.com
	([64.18.5.12]) with SMTP; Thu, 24 Jan 2008 10:14:22 PST
Received: from inner-relay-3.eur.adobe.com (inner-relay-3b [10.128.4.236])
	by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	m0OIEDGb007604; Thu, 24 Jan 2008 10:14:13 -0800 (PST)
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
	m0OIDtFl010254; Thu, 24 Jan 2008 10:14:12 -0800 (PST)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by
	apacmail.pac.adobe.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 25 Jan 2008 03:14:09 +0900
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
Date: Thu, 24 Jan 2008 10:13:31 -0800
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D223AE595@namail5.corp.adobe.com>
In-Reply-To: <000b01c85eb3$70cc6720$c3f0200a@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] Choice of STUN peer or TURN peer
Thread-Index: AchdzJ90kFg6Xq4fTZOyCgPVF+N/zwAif+RQABT2TDAAAn79QA==
References: <20d2bdfb0801230631h4b40a4dbr1d03fae14f8852ea@mail.gmail.com><005d01c85e59$e25fd250$2d09a40a@china.huawei.com>
	<000b01c85eb3$70cc6720$c3f0200a@cisco.com>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Dan Wing" <dwing@cisco.com>, "JiangXingFeng" <jiang.x.f@huawei.com>,
	"Bruce Lowekamp" <lowekamp@sipeerior.com>
X-OriginalArrivalTime: 24 Jan 2008 18:14:09.0680 (UTC)
	FILETIME=[EA393100:01C85EB4]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

This is a very creative contribution to solving NAT traversal for peers
behind NAT to act as TURN servers.

Good job Dan!

Henry


-----Original Message-----
From: Dan Wing [mailto:dwing@cisco.com]=20
Sent: Thursday, January 24, 2008 10:03 AM
To: 'JiangXingFeng'; 'Bruce Lowekamp'
Cc: 'P2PSIP Mailing List'
Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer

> > Similarly, a TURN server being behind a NAT is irrelevant as long as
> > both peers can contact it.  A peer that wishes to be a TURN=20
> > server but
> > is behind a bad NAT is probably better off not being a TURN server,
> > but that is about it.
>=20
> The following is another story. For peer to be a TURN server,=20
> how could TURN
> clients get their allocated transport address belonging to=20
> the TURN server
> if the TURN server is behind NAT? Because in TURN, the=20
> allocated address is
> encapsulated in the message and then communicated with the=20
> clients, but due
> to NAT, the allocated address could not be contacted by the=20
> clients in the future.=20
>
> Am I missing soothing? =20


The TURN server is responsible for obtaining a publicly-routable
address, and giving that address to the TURN client.  The TURN
specification, as currently written, expects the TURN server
itself to be on a publicly-routable network ("on the Internet").

If, however, the TURN server is behind a NAT, and we want the=20
TURN server to still be responsible for obtaining a=20
publicly-routable IP address, you could do that.  Here is a=20
new technique that could be used:  the TURN server could use=20
STUN (or NAT-PMP or UPnP, if there is only one NAT between=20
the TURN server and the Internet), and obtain a publicly-
routable mapping:


  TURN client         STUN server          NAT  TURN server
       |                   |                |      |
 1.    |------give me a TURN address------->|----->|
 2.    |                   |<--STUN Request--------|
 3.    |                   |-STUN Response->|----->|
 4.    |<-----here is your TURN address------------|


Messages 2-3 are normal STUN request/response messages, and
tell the TURN server a publicly-routable IP address and UDP
port.  The IP address and UDP port returned in in the STUN=20
Response (message 3) is the TURN server's publicly-routable
transport address, and is given to the TURN client in message=20
4.

For the above message flow to work, the NAT has to be
p2p-friendly, of course -- that is a requirement for a
successful TURN server behind a NAT.

-d



> >=20
> >=20
> > The reload-02 section I pointed you to describes this very briefly,
> > but let me try to provide more details. In almost all cases, A and B
> > will be behind friendly NATs.  In your particular example, no matter
> > how many STUN servers B uses, it will know two candidate addresses.
> > In A's case, it will know two or maybe three if it has C in its list
> > of STUN servers.
>=20
> >=20
> > Two points to note here.  First, for peer protocol=20
> connections, there
> > is no need to gather candidate addresses when you wish to=20
> establish a
> > new connection because you can do that over time.  Second, reload-02
> > suggests that you maintain sets of peers grouped according to the
> > reflexive address they return, then make one query to each when you
> > gather candidates for media connections (or refresh your=20
> peer protocol
> > addresses).
>=20
> Thanks for your explanations. You mean that reload-2 uses the=20
> reflexive
> address from its peers as its peer reflexive address candidate?
>=20
> What my concern is how the peer learns the reflexive address=20
> when it just
> joins the overlay? It should find a bootstrap peer? Must the=20
> bootstrap peer
> have a public address? If not, how could the peer contact=20
> directly with the
> bootstrap peer?=20
>=20
> Another concern is: although a peer could gather candidates=20
> over time, the
> first reflexive address SHOULD be on the public Internet (If=20
> bootstrap peer
> has to have a public address). The peer must actively find=20
> the STUN servers
> and only passively relying on the packets from its peers to=20
> get reflexive
> candidate is not enough because its peers could not contact=20
> him directly due
> to NAT.=20
>=20
> One more question here is: how do you define p2p-friendly NAT=20
> in terms of
> filtering behavior? Do you refer to end-point independent filtering or
> others? If it is the case, the security property would be=20
> sacrificed. =20
>=20
> >=20
> > Now the less common, but important case, is when A or B is behind a
> > p2p unfriendly NAT.  Any of your NAT1, NAT2, NAT3 could be=20
> unfriendly.
> >  In this case, what will happen is that A or B will discover that as
> > they make connections with new peers, the number of different
> > reflexive addresses that they see grows.  In B's case, it will
> > probably grow infinitely large.  In A's case, assuming there is more
> > than Peer C behind NAT 2 with it, if NAT 2 is the=20
> unfriendly NAT A may
> > observe several peers reporting the same reflexive address because
> > they are also behind NAT2.  In these cases, A and B should provide
> > addresses they see repeated as ICE candidates, but there's=20
> unlikely to
> > be any point in providing a list of every reflexive address=20
> ever seen.
> >=20
> > In any event, when ordering the candidates for an ice offer, start
> > with the local address and list the learned addresses in=20
> the order of
> > their frequency.  That will very rarely be more than two.
>=20
> Whatever method being used to sort the candidate, if two=20
> candidates in the
> candidate pair is not within the same realm, the connectivity=20
> check must
> fail, hence the connectivity check time will be prolonged.=20
>=20
>=20
>=20


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

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



From p2psip-bounces@ietf.org Thu Jan 24 13:54:32 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JI7Cl-0000sm-Cj; Thu, 24 Jan 2008 13:53:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JI7Ck-0000sh-7E
	for p2psip@ietf.org; Thu, 24 Jan 2008 13:53:38 -0500
Received: from smtp.mitel.com ([216.191.234.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JI7Cj-0005pq-Tm
	for p2psip@ietf.org; Thu, 24 Jan 2008 13:53:38 -0500
Received: from localhost (smtp.mitel.com [127.0.0.1])
	by smtp.mitel.com (Postfix) with ESMTP id 9B6C02C015;
	Thu, 24 Jan 2008 13:53:37 -0500 (EST)
X-Virus-Scanned: by amavisd-new (virusonly) at mitel.com
Received: from smtp.mitel.com ([127.0.0.1])
	by localhost (smtp.mitel.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AnxjJVxdEvRH; Thu, 24 Jan 2008 13:53:36 -0500 (EST)
Received: from LT4GKCG41 (unknown [10.31.8.26])
	by smtp.mitel.com (Postfix) with SMTP id 24FFF2C022;
	Thu, 24 Jan 2008 13:53:36 -0500 (EST)
From: "Jerry Yin" <jerry_yin@mitel.com>
To: "Dan Wing" <dwing@cisco.com>
Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
Date: Thu, 24 Jan 2008 13:53:36 -0500
Message-ID: <GDEOKMPIPEGAEADGFFKEEEHAHLAA.jerry_yin@mitel.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <000b01c85eb3$70cc6720$c3f0200a@cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

>
>
>   TURN client         STUN server          NAT  TURN server
>        |                   |                |      |
>  1.    |------give me a TURN address------->|----->|
>  2.    |                   |<--STUN Request--------|
>  3.    |                   |-STUN Response->|----->|
>  4.    |<-----here is your TURN address------------|
>
>
> Messages 2-3 are normal STUN request/response messages, and
> tell the TURN server a publicly-routable IP address and UDP
> port.  The IP address and UDP port returned in in the STUN
> Response (message 3) is the TURN server's publicly-routable
> transport address, and is given to the TURN client in message
> 4.
>
>

Does the "p2p-friendly" mean the NAT allows the STUN messages pass through?
How does the message 1 (STUN) go through the NAT?

I guess the TURN server has to send STUN keep alive messages to keep the NAT
hole open before the TURN request expire?

thanks,
Jerry


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



From p2psip-bounces@ietf.org Thu Jan 24 17:34:42 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JIAdl-0002PR-IR; Thu, 24 Jan 2008 17:33:45 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JIAdk-0002PM-Ge
	for p2psip@ietf.org; Thu, 24 Jan 2008 17:33:44 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JIAdk-0005gC-4M
	for p2psip@ietf.org; Thu, 24 Jan 2008 17:33:44 -0500
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 24 Jan 2008 14:33:43 -0800
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m0OMXhMm006384; 
	Thu, 24 Jan 2008 14:33:43 -0800
Received: from dwingwxp01 (dhcp-128-107-163-68.cisco.com [128.107.163.68])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id m0OMXKp5029088;
	Thu, 24 Jan 2008 22:33:38 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Jerry Yin'" <jerry_yin@mitel.com>
References: <000b01c85eb3$70cc6720$c3f0200a@cisco.com>
	<GDEOKMPIPEGAEADGFFKEEEHAHLAA.jerry_yin@mitel.com>
Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
Date: Thu, 24 Jan 2008 14:33:21 -0800
Message-ID: <002501c85ed9$2cbfca60$44a36b80@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcheunYyW4zdec+fSxm/JgJ4n7HZ7gAAYpXQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <GDEOKMPIPEGAEADGFFKEEEHAHLAA.jerry_yin@mitel.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1975; t=1201214023;
	x=1202078023; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[P2PSIP]=20Choice=20of=20STUN=20peer=20
	or=20TURN=20peer |Sender:=20;
	bh=C0TWyFChWdAIerJp1Immda8oV5S/LUU5qxjLM3uiJGU=;
	b=SE2H6E88cV0HghLKVRKJOihnWb3faiZGZwNLCc765XpQn+o1962L35pJRV
	tz0vydT4/NqrpftATWGv1HKxYtl9kQADyPhxU3N/eagqFqitqlxI1J9FykOc
	VGv8l85S0B;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

 

> -----Original Message-----
> From: Jerry Yin [mailto:jerry_yin@mitel.com] 
> Sent: Thursday, January 24, 2008 10:54 AM
> To: Dan Wing
> Cc: 'P2PSIP Mailing List'
> Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
> 
> >
> >
> >   TURN client         STUN server          NAT  TURN server
> >        |                   |                |      |
> >  1.    |------give me a TURN address------->|----->|
> >  2.    |                   |<--STUN Request--------|
> >  3.    |                   |-STUN Response->|----->|
> >  4.    |<-----here is your TURN address------------|
> >
> >
> > Messages 2-3 are normal STUN request/response messages, and
> > tell the TURN server a publicly-routable IP address and UDP
> > port.  The IP address and UDP port returned in in the STUN
> > Response (message 3) is the TURN server's publicly-routable
> > transport address, and is given to the TURN client in message
> > 4.
> >
> >
> 
> Does the "p2p-friendly" mean the NAT allows the STUN messages 
> pass through?
> How does the message 1 (STUN) go through the NAT?

The p2p-sip TURN server, prior to those messages above, 
determined its publicly-routable IP address and publicly-
routable UDP port.  It may have determined that via STUN 
(or, if there is only one level of NAT, it might have 
determined that via UPnP or NAT-PMP).

The p2p-sip TURN server also determines that it can receive 
STUN requests from arbitrary STUN clients via that port; Bruce 
I believe has written up how a TURN server makes that 
determination.  Once the TURN server has made that determination, 
it would register itself as a TURN server in the p2p overlay 
network.

> I guess the TURN server has to send STUN keep alive messages 
> to keep the NAT
> hole open before the TURN request expire?

Yes, the p2p-sip TURN server would be responsible for keeping 
open all of the pinholes necessary for the p2p-sip TURN server 
to operate.

-d


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



From p2psip-bounces@ietf.org Thu Jan 24 21:09:58 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JIE07-0003FF-7k; Thu, 24 Jan 2008 21:09:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JIE06-0003F9-QO
	for p2psip@ietf.org; Thu, 24 Jan 2008 21:09:02 -0500
Received: from szxga03-in.huawei.com ([61.144.161.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JIE04-000839-Op
	for p2psip@ietf.org; Thu, 24 Jan 2008 21:09:02 -0500
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 <0JV600MXIGM06X@szxga03-in.huawei.com> for
	p2psip@ietf.org; Fri, 25 Jan 2008 10:08:24 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JV60061WGLY20@szxga03-in.huawei.com> for
	p2psip@ietf.org; Fri, 25 Jan 2008 10:08:24 +0800 (CST)
Received: from j36340 ([10.164.9.45])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JV6005L1GLXK3@szxml03-in.huawei.com> for
	p2psip@ietf.org; Fri, 25 Jan 2008 10:08:22 +0800 (CST)
Date: Fri, 25 Jan 2008 10:08:21 +0800
From: JiangXingFeng <jiang.x.f@huawei.com>
Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
In-reply-to: <000b01c85eb3$70cc6720$c3f0200a@cisco.com>
To: 'Dan Wing' <dwing@cisco.com>, 'Bruce Lowekamp' <lowekamp@sipeerior.com>
Message-id: <002b01c85ef7$29410840$2d09a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Thread-index: AchdzJ90kFg6Xq4fTZOyCgPVF+N/zwAif+RQABT2TDAAEsYpMA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

> 
> The TURN server is responsible for obtaining a publicly-routable
> address, and giving that address to the TURN client.  The TURN
> specification, as currently written, expects the TURN server
> itself to be on a publicly-routable network ("on the Internet").
> 
> If, however, the TURN server is behind a NAT, and we want the
> TURN server to still be responsible for obtaining a
> publicly-routable IP address, you could do that.  Here is a
> new technique that could be used:  the TURN server could use
> STUN (or NAT-PMP or UPnP, if there is only one NAT between
> the TURN server and the Internet), and obtain a publicly-
> routable mapping:
> 
> 
>   TURN client         STUN server          NAT  TURN server
>        |                   |                |      |
>  1.    |------give me a TURN address------->|----->|
>  2.    |                   |<--STUN Request--------|
>  3.    |                   |-STUN Response->|----->|
>  4.    |<-----here is your TURN address------------|
> 
> 
> Messages 2-3 are normal STUN request/response messages, and
> tell the TURN server a publicly-routable IP address and UDP
> port.  The IP address and UDP port returned in in the STUN
> Response (message 3) is the TURN server's publicly-routable
> transport address, and is given to the TURN client in message
> 4.
> 
> For the above message flow to work, the NAT has to be
> p2p-friendly, of course -- that is a requirement for a
> successful TURN server behind a NAT.


If the NAT is nested, the location of the STUN server may fail the above the
method. For example, if the STUN server is also behind the NAT and reflects
the inner NAT mapping, not outer most NAT mapping, to the TURN server, the
relayed address will not be used for the TURN client to contact with TURN
server. In order to avoid this kind of failure, stun server's location
should be learned by its clients. In china, due to the lack of the IPv4
address, nested NAT is not a rare situation. 
Comments?

Regards!
JiangXingFeng


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



From p2psip-bounces@ietf.org Thu Jan 24 21:14:05 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JIE48-00057w-Mk; Thu, 24 Jan 2008 21:13:12 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JIE47-00057h-9F
	for p2psip@ietf.org; Thu, 24 Jan 2008 21:13:11 -0500
Received: from szxga01-in.huawei.com ([61.144.161.53])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JIE46-00044T-OZ
	for p2psip@ietf.org; Thu, 24 Jan 2008 21:13:11 -0500
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 <0JV600A1RGSP3G@szxga01-in.huawei.com> for
	p2psip@ietf.org; Fri, 25 Jan 2008 10:12:25 +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 <0JV600EEHGSPBK@szxga01-in.huawei.com> for
	p2psip@ietf.org; Fri, 25 Jan 2008 10:12:25 +0800 (CST)
Received: from j36340 ([10.164.9.45])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JV600ELAGSOCD@szxml04-in.huawei.com> for
	p2psip@ietf.org; Fri, 25 Jan 2008 10:12:25 +0800 (CST)
Date: Fri, 25 Jan 2008 10:12:24 +0800
From: JiangXingFeng <jiang.x.f@huawei.com>
Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
In-reply-to: <002501c85ed9$2cbfca60$44a36b80@cisco.com>
To: 'Dan Wing' <dwing@cisco.com>, 'Jerry Yin' <jerry_yin@mitel.com>
Message-id: <002c01c85ef7$ba1b3f20$2d09a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Thread-index: AcheunYyW4zdec+fSxm/JgJ4n7HZ7gAAYpXQAA7K4uA=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

> The p2p-sip TURN server, prior to those messages above,
> determined its publicly-routable IP address and publicly-
> routable UDP port.  It may have determined that via STUN
> (or, if there is only one level of NAT, it might have
> determined that via UPnP or NAT-PMP).
> 
> The p2p-sip TURN server also determines that it can receive
> STUN requests from arbitrary STUN clients via that port; Bruce
> I believe has written up how a TURN server makes that
> determination.  Once the TURN server has made that determination,
> it would register itself as a TURN server in the p2p overlay
> network.

How do you assume the filtering behavior of the NAT which is in the front of
the TURN server? If it is not end-point independent filtering, how could the
TURN client's request reach the TURN peer behind the NAT? 





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



From p2psip-bounces@ietf.org Thu Jan 24 22:54:17 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JIFd5-00060w-11; Thu, 24 Jan 2008 22:53:23 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JIFd3-0005wM-9z
	for p2psip@ietf.org; Thu, 24 Jan 2008 22:53:21 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JIFd2-0006eE-Da
	for p2psip@ietf.org; Thu, 24 Jan 2008 22:53:21 -0500
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 24 Jan 2008 19:53:19 -0800
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m0P3rJ3t005486; 
	Thu, 24 Jan 2008 19:53:19 -0800
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id m0P3rHAl023127;
	Fri, 25 Jan 2008 03:53:17 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'JiangXingFeng'" <jiang.x.f@huawei.com>,
	"'Bruce Lowekamp'" <lowekamp@sipeerior.com>
References: <000b01c85eb3$70cc6720$c3f0200a@cisco.com>
	<002b01c85ef7$29410840$2d09a40a@china.huawei.com>
Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
Date: Thu, 24 Jan 2008 19:53:16 -0800
Message-ID: <0dc701c85f05$d23f7b30$44a36b80@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AchdzJ90kFg6Xq4fTZOyCgPVF+N/zwAif+RQABT2TDAAEsYpMAAECZOQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <002b01c85ef7$29410840$2d09a40a@china.huawei.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2557; t=1201233199;
	x=1202097199; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[P2PSIP]=20Choice=20of=20STUN=20peer=20
	or=20TURN=20peer |Sender:=20;
	bh=dpRYfiBzda/fecnnzOJLXUJumTT0B7FHY/Dgke5z5+k=;
	b=MNGpgS4rcS3Imr2/4VOp1ga7fX5QKPBWqj/cg8IzK3fU0oqUXkoW8vlRj+
	g4fBtcaN4vZr/VDPCyYbJevzKB2GKzGMsyIctGs9HkKk2CkqhqA4iPFYgRdx
	N7Iq5rivh/;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

 

> -----Original Message-----
> From: JiangXingFeng [mailto:jiang.x.f@huawei.com] 
> Sent: Thursday, January 24, 2008 6:08 PM
> To: 'Dan Wing'; 'Bruce Lowekamp'
> Cc: 'P2PSIP Mailing List'
> Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
> 
> > 
> > The TURN server is responsible for obtaining a publicly-routable
> > address, and giving that address to the TURN client.  The TURN
> > specification, as currently written, expects the TURN server
> > itself to be on a publicly-routable network ("on the Internet").
> > 
> > If, however, the TURN server is behind a NAT, and we want the
> > TURN server to still be responsible for obtaining a
> > publicly-routable IP address, you could do that.  Here is a
> > new technique that could be used:  the TURN server could use
> > STUN (or NAT-PMP or UPnP, if there is only one NAT between
> > the TURN server and the Internet), and obtain a publicly-
> > routable mapping:
> > 
> > 
> >   TURN client         STUN server          NAT  TURN server
> >        |                   |                |      |
> >  1.    |------give me a TURN address------->|----->|
> >  2.    |                   |<--STUN Request--------|
> >  3.    |                   |-STUN Response->|----->|
> >  4.    |<-----here is your TURN address------------|
> > 
> > 
> > Messages 2-3 are normal STUN request/response messages, and
> > tell the TURN server a publicly-routable IP address and UDP
> > port.  The IP address and UDP port returned in in the STUN
> > Response (message 3) is the TURN server's publicly-routable
> > transport address, and is given to the TURN client in message
> > 4.
> > 
> > For the above message flow to work, the NAT has to be
> > p2p-friendly, of course -- that is a requirement for a
> > successful TURN server behind a NAT.
> 
> 
> If the NAT is nested, the location of the STUN server may 
> fail the above the
> method. For example, if the STUN server is also behind the 
> NAT and reflects
> the inner NAT mapping, not outer most NAT mapping, to the 
> TURN server, the
> relayed address will not be used for the TURN client to 
> contact with TURN
> server. In order to avoid this kind of failure, stun server's location
> should be learned by its clients.

Yep.  That is part of the qualification a p2p-sip TURN server 
would have to do before it declares itself a TURN server.

-d

> In china, due to the lack 
> of the IPv4
> address, nested NAT is not a rare situation. 
> Comments?
> 
> Regards!
> JiangXingFeng
> 


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



From p2psip-bounces@ietf.org Thu Jan 24 22:56:46 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JIFfW-00044s-Ea; Thu, 24 Jan 2008 22:55:54 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JIFfV-00044j-Tz
	for p2psip@ietf.org; Thu, 24 Jan 2008 22:55:53 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JIFfV-0006hb-Hm
	for p2psip@ietf.org; Thu, 24 Jan 2008 22:55:53 -0500
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 24 Jan 2008 19:55:53 -0800
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m0P3tqpo025487; 
	Thu, 24 Jan 2008 19:55:52 -0800
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m0P3to3V018475;
	Fri, 25 Jan 2008 03:55:51 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'JiangXingFeng'" <jiang.x.f@huawei.com>,
	"'Jerry Yin'" <jerry_yin@mitel.com>
References: <002501c85ed9$2cbfca60$44a36b80@cisco.com>
	<002c01c85ef7$ba1b3f20$2d09a40a@china.huawei.com>
Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
Date: Thu, 24 Jan 2008 19:55:50 -0800
Message-ID: <0deb01c85f06$2dc3d370$44a36b80@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcheunYyW4zdec+fSxm/JgJ4n7HZ7gAAYpXQAA7K4uAAA6nYQA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <002c01c85ef7$ba1b3f20$2d09a40a@china.huawei.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1708; t=1201233352;
	x=1202097352; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[P2PSIP]=20Choice=20of=20STUN=20peer=20
	or=20TURN=20peer |Sender:=20;
	bh=h6DhCDYb54B3sAF8B20YXf7Ag2/cOh4fQ2UUg+YNpZo=;
	b=n6+eZn4zqjGYBcOeiLk/l9viZCZkRO+Ni/z/BDcQ9k2xrhbzL7MqXNqAtK
	+UblvKoA+DoiPBoyDR5sNluHAvxTOJGmUS+hB+av1uYppsCF+gd9auSUyFEK
	l7aANFMetd;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

 

> -----Original Message-----
> From: JiangXingFeng [mailto:jiang.x.f@huawei.com] 
> Sent: Thursday, January 24, 2008 6:12 PM
> To: 'Dan Wing'; 'Jerry Yin'
> Cc: 'P2PSIP Mailing List'
> Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
> 
> > The p2p-sip TURN server, prior to those messages above,
> > determined its publicly-routable IP address and publicly-
> > routable UDP port.  It may have determined that via STUN
> > (or, if there is only one level of NAT, it might have
> > determined that via UPnP or NAT-PMP).
> > 
> > The p2p-sip TURN server also determines that it can receive
> > STUN requests from arbitrary STUN clients via that port; Bruce
> > I believe has written up how a TURN server makes that
> > determination.  Once the TURN server has made that determination,
> > it would register itself as a TURN server in the p2p overlay
> > network.
> 
> How do you assume the filtering behavior of the NAT which is 
> in the front of the TURN server?

You can test it, and hope your test accurately reflects the
NAT's filtering behavior when real traffic is attempting to
traverse the NAT.  

I am not aware of a better technique, unless you know you
are behind only one NAT (in which case you can use UPnP or
NAT-PMP, both of which require no filtering on the NAT).

> If it is not end-point independent 
> filtering, how could the
> TURN client's request reach the TURN peer behind the NAT? 

It wouldn't.  The p2p-sip TURN server needs to determine if 
it's behind that kind of NAT prior to declaring, to the 
p2p-sip network, that it is a TURN server.  That is part
of the qualification procedure the p2p-sip TURN server
needs to do.

-d


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



From p2psip-bounces@ietf.org Fri Jan 25 04:18:26 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JIKgk-0003Oh-VE; Fri, 25 Jan 2008 04:17:30 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JIKgj-0003OE-ND
	for p2psip@ietf.org; Fri, 25 Jan 2008 04:17:29 -0500
Received: from szxga04-in.huawei.com ([61.144.161.7])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JIKgj-0006xT-3P
	for p2psip@ietf.org; Fri, 25 Jan 2008 04:17:29 -0500
Received: from huawei.com (szxga04-in [172.24.2.12])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JV700DDQ0FJYS@szxga04-in.huawei.com> for
	p2psip@ietf.org; Fri, 25 Jan 2008 17:16:32 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JV7004KC0FJYK@szxga04-in.huawei.com> for
	p2psip@ietf.org; Fri, 25 Jan 2008 17:16:31 +0800 (CST)
Received: from j36340 ([10.164.9.45])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JV7004320FJMW@szxml03-in.huawei.com> for
	p2psip@ietf.org; Fri, 25 Jan 2008 17:16:31 +0800 (CST)
Date: Fri, 25 Jan 2008 17:16:31 +0800
From: JiangXingFeng <jiang.x.f@huawei.com>
Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
In-reply-to: <0dc701c85f05$d23f7b30$44a36b80@cisco.com>
To: 'Dan Wing' <dwing@cisco.com>, 'Bruce Lowekamp' <lowekamp@sipeerior.com>
Message-id: <003301c85f32$f9474460$2d09a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Thread-index: AchdzJ90kFg6Xq4fTZOyCgPVF+N/zwAif+RQABT2TDAAEsYpMAAECZOQAArhadA=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hi, 

I'd like to see your proposed method works, because it could make full use
of decentralized resource in the overlay to serve each other. 

Regards!

JiangXingFeng

> 
> Yep.  That is part of the qualification a p2p-sip TURN server
> would have to do before it declares itself a TURN server.
> 
I'm just worried about that rare end-point independent filtering NAT exists
according the data in the paper http://saikat.guha.cc/pub/imc05-tcpnat.pdf.
It said the proportion of the end-point independent filtering NAT is about
5.8%


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



From p2psip-bounces@ietf.org Fri Jan 25 12:31:48 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JISP3-0005ya-II; Fri, 25 Jan 2008 12:31:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JISP1-0005y8-Vv
	for p2psip@ietf.org; Fri, 25 Jan 2008 12:31:43 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1JISP1-0004PR-Em
	for p2psip@ietf.org; Fri, 25 Jan 2008 12:31:43 -0500
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-2.cisco.com with ESMTP; 25 Jan 2008 09:31:42 -0800
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m0PHVgng011824; 
	Fri, 25 Jan 2008 09:31:42 -0800
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m0PHVYj5018788;
	Fri, 25 Jan 2008 17:31:34 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'JiangXingFeng'" <jiang.x.f@huawei.com>,
	"'Bruce Lowekamp'" <lowekamp@sipeerior.com>
References: <0dc701c85f05$d23f7b30$44a36b80@cisco.com>
	<003301c85f32$f9474460$2d09a40a@china.huawei.com>
Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
Date: Fri, 25 Jan 2008 09:31:33 -0800
Message-ID: <174701c85f78$24a386b0$44a36b80@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AchdzJ90kFg6Xq4fTZOyCgPVF+N/zwAif+RQABT2TDAAEsYpMAAECZOQAArhadAAEYVQEA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <003301c85f32$f9474460$2d09a40a@china.huawei.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1405; t=1201282302;
	x=1202146302; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[P2PSIP]=20Choice=20of=20STUN=20peer=20
	or=20TURN=20peer |Sender:=20;
	bh=qg1qjVflBguVxEhsHtFxMLoQOjPfRuhcP62qOfo0u60=;
	b=iXuCcP4DanSQC/voPm+PV8QgaoT5eleTJLULWgUVolzKerZ5Sf49OMOmsu
	iivfnERSgG0MX3UJ+YOHZJ0cVv0VKKpi+DsN0MAV9z8S0LJhFJNAhekBjqDI
	R1ulCjekCO;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

 

> -----Original Message-----
> From: JiangXingFeng [mailto:jiang.x.f@huawei.com] 
> Sent: Friday, January 25, 2008 1:17 AM
> To: 'Dan Wing'; 'Bruce Lowekamp'
> Cc: 'P2PSIP Mailing List'
> Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
> 
> Hi, 
> 
> I'd like to see your proposed method works, because it could 
> make full use
> of decentralized resource in the overlay to serve each other. 

It seems useful to phase this for p2p-sip:  initially, just have
p2p-sip nodes advertise their TURN servers if the p2p-sip node
is not behind a NAT.

Once we know how to have p2p-sip TURN servers qualify their 
NAT's p2p-friendlyness, then can have p2p-sip nodes advertise 
those TURN servers, too.  If we make fast progress on a document
that describes the qualification procedure, and running code
that shows it works, we should be good to go.  No?


> Regards!
> 
> JiangXingFeng
> 
> > 
> > Yep.  That is part of the qualification a p2p-sip TURN server
> > would have to do before it declares itself a TURN server.
> > 
> I'm just worried about that rare end-point independent 
> filtering NAT exists
> according the data in the paper 
> http://saikat.guha.cc/pub/imc05-tcpnat.pdf.
> It said the proportion of the end-point independent filtering 
> NAT is about 5.8%

That paper is for TCP.  I thought the primary concern here, for
TURN, was UDP?

-d


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



From p2psip-bounces@ietf.org Sun Jan 27 21:33:23 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JJJo7-000576-1h; Sun, 27 Jan 2008 21:33:11 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JJJo5-00056R-Iy
	for p2psip@ietf.org; Sun, 27 Jan 2008 21:33:09 -0500
Received: from szxga02-in.huawei.com ([61.144.161.54])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JJJo5-0004w2-3a
	for p2psip@ietf.org; Sun, 27 Jan 2008 21:33:09 -0500
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 <0JVC005ZQ1Q149@szxga02-in.huawei.com> for
	p2psip@ietf.org; Mon, 28 Jan 2008 10:32:26 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JVC00ANZ1Q1SA@szxga02-in.huawei.com> for
	p2psip@ietf.org; Mon, 28 Jan 2008 10:32:25 +0800 (CST)
Received: from j36340 ([10.164.9.45])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JVC00N0D1Q13P@szxml04-in.huawei.com> for
	p2psip@ietf.org; Mon, 28 Jan 2008 10:32:25 +0800 (CST)
Date: Mon, 28 Jan 2008 10:32:24 +0800
From: JiangXingFeng <jiang.x.f@huawei.com>
Subject: RE: [P2PSIP] Choice of STUN peer or TURN peer
In-reply-to: <174701c85f78$24a386b0$44a36b80@cisco.com>
To: 'Dan Wing' <dwing@cisco.com>, 'Bruce Lowekamp' <lowekamp@sipeerior.com>
Message-id: <001501c86156$04a31ee0$2d09a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Thread-index: AchdzJ90kFg6Xq4fTZOyCgPVF+N/zwAif+RQABT2TDAAEsYpMAAECZOQAArhadAAEYVQEAB3Nztw
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

> It seems useful to phase this for p2p-sip:  initially, just have
> p2p-sip nodes advertise their TURN servers if the p2p-sip node
> is not behind a NAT.
> 
> Once we know how to have p2p-sip TURN servers qualify their
> NAT's p2p-friendlyness, then can have p2p-sip nodes advertise
> those TURN servers, too.  If we make fast progress on a document
> that describes the qualification procedure, and running code
> that shows it works, we should be good to go.  No?


Yes. It is same to what I have in mind. First of all, we should determine
the p2psip node is not behind a NAT. 

Regard

JiangXingFeng



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



From p2psip-bounces@ietf.org Mon Jan 28 11:01:10 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JJWQ0-0004st-35; Mon, 28 Jan 2008 11:01:08 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JJWPy-0004rz-Jk
	for p2psip@ietf.org; Mon, 28 Jan 2008 11:01:06 -0500
Received: from wr-out-0506.google.com ([64.233.184.235])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JJWPy-0008LF-8B
	for p2psip@ietf.org; Mon, 28 Jan 2008 11:01:06 -0500
Received: by wr-out-0506.google.com with SMTP id 68so747484wra.13
	for <p2psip@ietf.org>; Mon, 28 Jan 2008 08:01:06 -0800 (PST)
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=8zoqZoq8ZdKA75V7WkmOJdPKMmgBKLovMmyqo1Ap6sk=;
	b=sDmG9/WEo32Xluna44oc73B33lmXSsh1IyRKlNwb2R8ZnK7rKw9aenrMFtT0xnQCzwIDzXDZ1N4pR+rThf9qXl5KA5pwCRdUAeX2zLHq+guSdlQiXD7t5q3Gu1FhHwustEwyNz8+byYRjlLJGW1i/zcIZRS7es26PiuLlvYNUpg=
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=Kjp0J/TZk0MmM6mnU5ZWqfjmdxGCrLVJS/LJ7L654jDCyll9LQZO8C2W/XPZt3D+p6YjERneiKbh82AxtOjF4Hi1iyCDwOE+FpSULirucgCalRB6+GkXvf/bbk1YpeiJtlpKPTwlACSyGF77Dh4UaDnDgh5Y39q5faJ75cb4DjM=
Received: by 10.114.77.1 with SMTP id z1mr4260718waa.56.1201536065183;
	Mon, 28 Jan 2008 08:01:05 -0800 (PST)
Received: by 10.115.19.18 with HTTP; Mon, 28 Jan 2008 08:01:05 -0800 (PST)
Message-ID: <20d2bdfb0801280801s5058a661td76c82985b54918@mail.gmail.com>
Date: Mon, 28 Jan 2008 11:01:05 -0500
From: "Bruce Lowekamp" <lowekamp@sipeerior.com>
To: JiangXingFeng <jiang.x.f@huawei.com>
Subject: Re: [P2PSIP] Choice of STUN peer or TURN peer
In-Reply-To: <001501c86156$04a31ee0$2d09a40a@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <174701c85f78$24a386b0$44a36b80@cisco.com>
	<001501c86156$04a31ee0$2d09a40a@china.huawei.com>
X-Google-Sender-Auth: c0bd62f88e278cff
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Sorry for dropping off the thread for so long...

On 1/27/08, JiangXingFeng <jiang.x.f@huawei.com> wrote:
> > It seems useful to phase this for p2p-sip:  initially, just have
> > p2p-sip nodes advertise their TURN servers if the p2p-sip node
> > is not behind a NAT.
> >

This seems like the best first step.  It also seems likely that
different overlays will have different policies for what defines a
good TURN relay.  Some provider-based overlays might actually have the
provider provision TURN servers, whereas at the other end of the
spectrum are overlays that may deploy nothing and rely entirely on
individuals who have eligible peers.


> > Once we know how to have p2p-sip TURN servers qualify their
> > NAT's p2p-friendlyness, then can have p2p-sip nodes advertise
> > those TURN servers, too.  If we make fast progress on a document
> > that describes the qualification procedure, and running code
> > that shows it works, we should be good to go.  No?
>


This seems like a fairly straightforward application of
nat-behavior-discovery.

> >
> >   TURN client         STUN server          NAT  TURN server
> >        |                   |                |      |
> >  1.    |------give me a TURN address------->|----->|
> >  2.    |                   |<--STUN Request--------|
> >  3.    |                   |-STUN Response->|----->|
> >  4.    |<-----here is your TURN address------------|
> >

If we allow a TURN server to be behind a NAT, then the only change I
would see necessary would that 1 and 4 would have to be routed over
the overlay (a reload tunnel, for example).  But otherwise, the TURN
protocol seems to work as is.  For the purposes of a TURN server, a
NAT having endpoint independent mapping seems to be the only real
requirement on the NAT as long as the two voice endpoints support ICE;
the connectivity checks should take care of any form of filtering the
NAT uses.

Bruce

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



From p2psip-bounces@ietf.org Mon Jan 28 12:20:29 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JJXem-00058x-CK; Mon, 28 Jan 2008 12:20:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JJXek-00058q-Kv
	for p2psip@ietf.org; Mon, 28 Jan 2008 12:20:26 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JJXei-0005gT-Cd
	for p2psip@ietf.org; Mon, 28 Jan 2008 12:20:26 -0500
Received: from msgtransport04.qualcomm.com (msgtransport04.qualcomm.com
	[129.46.61.156])
	by numenor.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id
	m0SHKIfT009788
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <p2psip@ietf.org>; Mon, 28 Jan 2008 09:20:19 -0800
Received: from [24.4.239.115] (carbuncle.qualcomm.com [129.46.226.27])
	by msgtransport04.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id
	m0SHKHeN014754 for <p2psip@ietf.org>; Mon, 28 Jan 2008 09:20:18 -0800
Mime-Version: 1.0
Message-Id: <p06240606c3c3bdf86fe6@[24.4.239.115]>
Date: Mon, 28 Jan 2008 09:20:24 -0800
To: p2psip@ietf.org
From: Ted Hardie <hardie@qualcomm.com>
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Subject: [P2PSIP] Fwd: I-D Action:draft-hardie-p2poverlay-pointers-00.txt
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Howdy,
	I wrote this as a first take on the "how to use a web page, IM,
or email message to give a pointer to an overlay" problem.  I'd appreciate
folks' thoughts on it.  There are several places in the document where what
I've put forward is pretty close to a strawman (the included schema
being one example), so please do not expect me to defend to the
death any of the details here.  I'd like us, however, to have something
in this space and this seemed like a good way to kick off discussion.
			regards,
				Ted






>
>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
>	Title           : Mechanisms for use in pointing to overlay networks, nodes, or resources
>	Author(s)       : T. Hardie
>	Filename        : draft-hardie-p2poverlay-pointers-00.txt
>	Pages           : 10
>	Date            : 2008-01-27
>
>Discovering overlay networks and the resources found within in them
>presents a number of bootstrapping problems.  While those hard
>problems are under discussion, this draft proposes a small set of
>mechanisms which are intended to be generically useful for
>providing pointers to peer-to-peer overlay networks in web pages,
>email messages, and other textual media.  While the mechanisms
>described below each meet similar needs, they are not mutually
>exclusive; it is expected that each will find some useful
>deployment during the early days of peer-to-peer overlay
>deployment.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-hardie-p2poverlay-pointers-00.txt
>
>To remove yourself from the I-D Announcement list, send a message to
>i-d-announce-request@ietf.org with the word unsubscribe in the body of
>the message.
>You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
>to change your subscription settings.
>
>Internet-Drafts are also available by anonymous FTP. Login with the
>username "anonymous" and a password of your e-mail address. After
>logging in, type "cd internet-drafts" and then
>	"get draft-hardie-p2poverlay-pointers-00.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>	mailserv@ietf.org.
>In the body type:
>	"FILE /internet-drafts/draft-hardie-p2poverlay-pointers-00.txt".
>
>NOTE:   The mail server at ietf.org can return the document in
>	MIME-encoded form by using the "mpack" utility.  To use this
>	feature, insert the command "ENCODING mime" before the "FILE"
>	command.  To decode the response(s), you will need "munpack" or
>	a MIME-compliant mail reader.  Different MIME-compliant mail readers
>	exhibit different behavior, especially when dealing with
>	"multipart" MIME messages (i.e. documents which have been split
>	up into multiple messages), so check your local documentation on
>	how to manipulate these messages.
>
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>
>
>[The following attachment must be fetched by mail. Command-click the URL below and send the resulting message to get the attachment.]
><mailto:mailserv@ietf.org?body=ENCODING%20mime%0D%0AFILE%20/internet-drafts/draft-hardie-p2poverlay-pointers-00.txt>
>[The following attachment must be fetched by ftp.  Command-click the URL below to ask your ftp client to fetch it.]
><ftp://ftp.ietf.org/internet-drafts/draft-hardie-p2poverlay-pointers-00.txt>
>_______________________________________________
>I-D-Announce mailing list
>I-D-Announce@ietf.org
>https://www1.ietf.org/mailman/listinfo/i-d-announce


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



From p2psip-bounces@ietf.org Tue Jan 29 05:01:35 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JJnHT-0006Ln-JN; Tue, 29 Jan 2008 05:01:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JJnHS-0006Lg-K4
	for p2psip@ietf.org; Tue, 29 Jan 2008 05:01:26 -0500
Received: from szxga02-in.huawei.com ([61.144.161.54])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JJnHQ-00076x-Md
	for p2psip@ietf.org; Tue, 29 Jan 2008 05:01:26 -0500
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 <0JVE00LPGH5B1Q@szxga02-in.huawei.com> for
	p2psip@ietf.org; Tue, 29 Jan 2008 18:00:47 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JVE003F2H5A37@szxga02-in.huawei.com> for
	p2psip@ietf.org; Tue, 29 Jan 2008 18:00:47 +0800 (CST)
Received: from s64081 ([10.164.9.47])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JVE0066MH5A84@szxml04-in.huawei.com> for
	p2psip@ietf.org; Tue, 29 Jan 2008 18:00:46 +0800 (CST)
Date: Tue, 29 Jan 2008 18:00:45 +0800
From: Song Yongchao <melodysong@huawei.com>
To: 'P2PSIP Mailing List' <p2psip@ietf.org>
Message-id: <!&!AAAAAAAAAAAYAAAAAAAAAIILieByQXtOrs7W/bI503TCgAAAEAAAAPP06lQRhk5Kqs/2dzGyy2QBAAAAAA==@huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AchiXdDUEMq1kFnuRJGxPAyGuY4xng==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Subject: [P2PSIP] A tiny question about P2PP
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Section 8.2
   Authenticate the user and generates a certificate binding user-ID, peer
or client ID, and public key of the peer.

Is it a clerical error or still "public key of the peer" when the
certificate is for a client?

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



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



From p2psip-bounces@ietf.org Tue Jan 29 05:56:15 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JJo8U-0007jP-5Q; Tue, 29 Jan 2008 05:56:14 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JJo8S-0007j5-Py
	for p2psip@ietf.org; Tue, 29 Jan 2008 05:56:12 -0500
Received: from szxga04-in.huawei.com ([61.144.161.7])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JJo8S-0002q5-88
	for p2psip@ietf.org; Tue, 29 Jan 2008 05:56:12 -0500
Received: from huawei.com (szxga04-in [172.24.2.12])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JVE00C85JOHS6@szxga04-in.huawei.com> for
	p2psip@ietf.org; Tue, 29 Jan 2008 18:55:29 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JVE00FEXJOGNG@szxga04-in.huawei.com> for
	p2psip@ietf.org; Tue, 29 Jan 2008 18:55:29 +0800 (CST)
Received: from s64081 ([10.164.9.47])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JVE00BJDJOGTB@szxml04-in.huawei.com> for
	p2psip@ietf.org; Tue, 29 Jan 2008 18:55:28 +0800 (CST)
Date: Tue, 29 Jan 2008 18:55:28 +0800
From: Song Yongchao <melodysong@huawei.com>
To: 'P2PSIP Mailing List' <p2psip@ietf.org>
Message-id: <!&!AAAAAAAAAAAYAAAAAAAAAIILieByQXtOrs7W/bI503TCgAAAEAAAAK2atB6ek1dDnENOFPMnnZkBAAAAAA==@huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AchiZXWSSVDQyY9hSGe9iUcx/Bj3eg==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Subject: [P2PSIP] Open issues with client has multiple associated peers
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hi, all

I think most proposals agree that one client can have multiple associated
peers to keep the service continuity. The open issues are:

(1) Should there be a primary associated peer? And when this peer fails, the
client switches to another associated peer? I am not sure of about it.

(2)Should the client learn more peers information that can be the client's
associated peers? And when one of its associated peer fails, it joins
another? I think probably this is what we needed.

(3)Should there be a notification mechanism between a client and its
associated peer? So the client can timely know the status of the associated
peer, and avoid choosing the congested or busy peer to serve him? I think we
do need it.

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



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



From p2psip-bounces@ietf.org Tue Jan 29 06:06:14 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JJoIA-00034h-6a; Tue, 29 Jan 2008 06:06:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JJoI8-00034W-LF
	for p2psip@ietf.org; Tue, 29 Jan 2008 06:06:12 -0500
Received: from szxga02-in.huawei.com ([61.144.161.54])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JJoI6-0001WX-M9
	for p2psip@ietf.org; Tue, 29 Jan 2008 06:06:12 -0500
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 <0JVE00L2IK561Q@szxga02-in.huawei.com> for
	p2psip@ietf.org; Tue, 29 Jan 2008 19:05:30 +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 <0JVE00JWPK51BR@szxga02-in.huawei.com> for
	p2psip@ietf.org; Tue, 29 Jan 2008 19:05:30 +0800 (CST)
Received: from s64081 ([10.164.9.47])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JVE0035EK51JD@szxml03-in.huawei.com> for
	p2psip@ietf.org; Tue, 29 Jan 2008 19:05:25 +0800 (CST)
Date: Tue, 29 Jan 2008 19:05:25 +0800
From: Song Yongchao <melodysong@huawei.com>
Subject: RE: [P2PSIP] Open issues with client has multiple associated peers
In-reply-to: <!&!AAAAAAAAAAAYAAAAAAAAAIILieByQXtOrs7W/bI503TCgAAAEAAAAK2atB6ek1dDnENOFPMnnZkBAAAAAA==@huawei.com>
To: 'Song Yongchao' <melodysong@huawei.com>,
	'P2PSIP Mailing List' <p2psip@ietf.org>
Message-id: <!&!AAAAAAAAAAAYAAAAAAAAAIILieByQXtOrs7W/bI503TCgAAAEAAAAF5bAMcw6eBIqcQfYqsneRQBAAAAAA==@huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AchiZXWSSVDQyY9hSGe9iUcx/Bj3egAALe0Q
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: 
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

I need to modify the second question to make it more clear.
 
 I think most proposals agree that one client can have multiple associated
peers to keep the service continuity. The open issues are:
 
(1) Should there be a primary associated peer? And when this peer fails, the
client switches to another associated peer? I am not sure of about it.
 
(2)Should the client learn more peers information that can be the client's
associated peers through its now associated peer? And when one of its
associated peers fails, it joins another to keep enough associated peers for
choice? I think probably this is what we needed.
 
(3)Should there be a notification mechanism between a client and its
associated peer? So the client can timely know the status of the associated
peer, and avoid choosing the congested or busy peer to serve him? I think we
do need it.
 
 Best Regards,
 Song Yongchao
 Email: melodysong@huawei.com
 


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



From p2psip-bounces@ietf.org Tue Jan 29 09:17:03 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JJrGl-0002qg-N3; Tue, 29 Jan 2008 09:16:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JJrGk-0002qP-IG
	for p2psip@ietf.org; Tue, 29 Jan 2008 09:16:58 -0500
Received: from mxoutps1.us.army.mil ([143.69.250.38])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JJrGf-0000WU-Kq
	for p2psip@ietf.org; Tue, 29 Jan 2008 09:16:58 -0500
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=qIRqJj3INuPO1huTGIqz6vfn9Jw96Z+GflrEEaBS+tfkT8GyifSwCMad
	fZ+0WdMv0912qOvfCokgsH5EV0utNA==;
From: "Roy, Radhika R Dr CTR USA USAMC" <radhika.r.roy@us.army.mil>
X-AKO: 97033817:10.224.36.65:29 Jan 2008 14:16:46 +0000:$Webmail:None
X-IronPort-AV: E=Sophos;i="4.25,269,1199664000"; d="scan'208";a="97033817"
Received: from mail5.int.ps1.us.army.mil (HELO us.army.mil) ([10.224.36.65])
	by mxoutps1.us.army.mil with ESMTP; 29 Jan 2008 14:16:46 +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, 29 Jan
	2008 09:16:46 -0500
To: Song Yongchao <melodysong@huawei.com>
Message-ID: <df51fa9c2c5cf.479eeefe@us.army.mil>
Date: Tue, 29 Jan 2008 09:16:46 -0500
X-Mailer: Sun Java(tm) System Messenger Express 6.2-9.04 (built Jun 11
 2007)
MIME-Version: 1.0
Content-Language: en
Subject: Re: RE: [P2PSIP] Open issues with client has multiple associated peers
X-Accept-Language: en
Priority: normal
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAAIILieByQXtOrs7W/bI503TCgAAAEAAAAF5bAMcw6eBIqcQfYqsneRQBAAAAAA==@huawei.com>
References: <!&!AAAAAAAAAAAYAAAAAAAAAIILieByQXtOrs7W/bI503TCgAAAEAAAAK2atB6ek1dDnENOFPMnnZkBAAAAAA==@huawei.com>
	<!&!AAAAAAAAAAAYAAAAAAAAAIILieByQXtOrs7W/bI503TCgAAAEAAAAF5bAMcw6eBIqcQfYqsneRQBAAAAAA==@huawei.com>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.0 (----)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Please see my inputs inline [RRR]

----- Original Message -----
From: Song Yongchao 
Date: Tuesday, January 29, 2008 6:06
Subject: RE: [P2PSIP] Open issues with client has multiple associated peers
To: 'Song Yongchao' , 'P2PSIP Mailing List' 

> I need to modify the second question to make it more clear.
> 
> I think most proposals agree that one client can have multiple 
> associatedpeers to keep the service continuity. The open issues are:
> 
> (1) Should there be a primary associated peer? And when this peer 
> fails, the
> client switches to another associated peer? I am not sure of about it.

[RRR] I think the answer is none from the protocol point of view. However, if clients wants to make something as its primary, secondary, etc., it should be left for implementations. It is a different area how a client will these choices.

> (2)Should the client learn more peers information that can be the 
> client'sassociated peers through its now associated peer? And when 
> one of its
> associated peers fails, it joins another to keep enough associated 
> peers for
> choice? I think probably this is what we needed.

[RRR] Yes, definitely. I guess that it is the beauty of the P2P protocol to make as reliable as one can make.
> 
> (3)Should there be a notification mechanism between a client and its
> associated peer? So the client can timely know the status of the 
> associatedpeer, and avoid choosing the congested or busy peer to 
> serve him? I think we
> do need it.

[RRR] I think that the performance criteria for choosing a peer should be a general one as it is the usual case in any communications networks. For example, in the IP network, the routers also have some general criteria how to choose the netxt hop router out of many neighboring routers. In the same token, the P2P protocol should also follow the similar mechanisms that are obvious.
> 
> Best Regards,
> Song Yongchao
> Email: melodysong@huawei.com
> 
> 
> 
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.ietf.org/mailman/listinfo/p2psip
> 

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



From p2psip-bounces@ietf.org Tue Jan 29 09:25:27 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JJrOv-0002Fo-Bj; Tue, 29 Jan 2008 09:25:25 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JJrOt-0002E0-Pg
	for p2psip@ietf.org; Tue, 29 Jan 2008 09:25:23 -0500
Received: from wx-out-0506.google.com ([66.249.82.230])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JJrOt-00042x-Db
	for p2psip@ietf.org; Tue, 29 Jan 2008 09:25:23 -0500
Received: by wx-out-0506.google.com with SMTP id s8so4854473wxc.31
	for <p2psip@ietf.org>; Tue, 29 Jan 2008 06:25:23 -0800 (PST)
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=a52YCOWVdT9zSMTg2XPwNJx+81WXvJyy2E1O6elTyUg=;
	b=Kr0N+craYWngEB1Mpw1hmy1Ssy+qKhqSLi4WoN5f89irG9OGWXASGoAza4D7WE7mk+q5QKJ7RtytiLAgNbwvdnhNHIoqHemYhRKcnAuu5JAVTPoG4i+bPrg3L9+jln9iaoYfdVh4PYy/r7WtZO5BebuwCP5XgEnjRxqD/rBE2ek=
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=DmO/WL8lX5AyewHmVNdnMMwG0WgOjlzlFwhbi5AJuQ4wbixWNi4M1q+kQ8Qz9Yozyx9tJtIIIFZCHd8tEcqu+wT4rHBKHBpSaEST/Q7KYeWV6OmJalGrr5fnW+DySpF0LRYofA828XlEXzel4u0XJHCj13edaaxgy4ULh6/Zvr4=
Received: by 10.110.2.2 with SMTP id 2mr2773587tib.14.1201616720809;
	Tue, 29 Jan 2008 06:25:20 -0800 (PST)
Received: by 10.110.8.18 with HTTP; Tue, 29 Jan 2008 06:25:20 -0800 (PST)
Message-ID: <1d38a3350801290625m42ee8adfs13ab9346f5602186@mail.gmail.com>
Date: Tue, 29 Jan 2008 22:25:20 +0800
From: "Hui Deng" <denghui02@gmail.com>
To: "Roy, Radhika R Dr CTR USA USAMC" <radhika.r.roy@us.army.mil>
Subject: Re: RE: [P2PSIP] Open issues with client has multiple associated peers
In-Reply-To: <df51fa9c2c5cf.479eeefe@us.army.mil>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <!&!AAAAAAAAAAAYAAAAAAAAAIILieByQXtOrs7W/bI503TCgAAAEAAAAK2atB6ek1dDnENOFPMnnZkBAAAAAA==@huawei.com>
	<!&!AAAAAAAAAAAYAAAAAAAAAIILieByQXtOrs7W/bI503TCgAAAEAAAAF5bAMcw6eBIqcQfYqsneRQBAAAAAA==@huawei.com>
	<df51fa9c2c5cf.479eeefe@us.army.mil>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

sorry for mine cutting in,

2008/1/29, Roy, Radhika R Dr CTR USA USAMC <radhika.r.roy@us.army.mil>:
> Please see my inputs inline [RRR]
>
> ----- Original Message -----
> From: Song Yongchao
> Date: Tuesday, January 29, 2008 6:06
> Subject: RE: [P2PSIP] Open issues with client has multiple associated peers
> To: 'Song Yongchao' , 'P2PSIP Mailing List'
>
> > I need to modify the second question to make it more clear.
> >
> > I think most proposals agree that one client can have multiple
> > associatedpeers to keep the service continuity. The open issues are:
> >
> > (1) Should there be a primary associated peer? And when this peer
> > fails, the
> > client switches to another associated peer? I am not sure of about it.
>
> [RRR] I think the answer is none from the protocol point of view. However, if clients wants to make something as its primary, secondary, etc., it should be left for implementations. It is a different area how a client will these choices.
[Hui] I have different image here, there could be client involvement for this,
for example, peer could say himself being a primary, who else being a secondary
through client protocl extension, make sense?

-Hui

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



From p2psip-bounces@ietf.org Tue Jan 29 10:39:13 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JJsYK-0000Xh-S8; Tue, 29 Jan 2008 10:39:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JJsYJ-0000Wd-Vz
	for p2psip@ietf.org; Tue, 29 Jan 2008 10:39:12 -0500
Received: from mxoutps1.us.army.mil ([143.69.250.38])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JJsYD-00030F-Vi
	for p2psip@ietf.org; Tue, 29 Jan 2008 10:39:11 -0500
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=xZZ83el4Am9/yUlj3exjqBk+4TST2RYAZBpxfERPY0hjfQe+StmWWilH
	6pLtIrQMiqPHWJiuyZ70fXzb+UsKvg==;
From: "Roy, Radhika R Dr CTR USA USAMC" <radhika.r.roy@us.army.mil>
X-AKO: 95551655:10.224.36.65:29 Jan 2008 15:38:58 +0000:$Webmail:None
X-IronPort-AV: E=Sophos;i="4.25,270,1199664000"; d="scan'208";a="95551655"
Received: from mail5.int.ps1.us.army.mil (HELO us.army.mil) ([10.224.36.65])
	by mxoutps1.us.army.mil with ESMTP; 29 Jan 2008 15:36:37 +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, 29 Jan
	2008 10:36:37 -0500
To: Hui Deng <denghui02@gmail.com>
Message-ID: <dcd28a142cd88.479f01b5@us.army.mil>
Date: Tue, 29 Jan 2008 10:36:37 -0500
X-Mailer: Sun Java(tm) System Messenger Express 6.2-9.04 (built Jun 11
 2007)
MIME-Version: 1.0
Content-Language: en
Subject: Re: RE: [P2PSIP] Open issues with client has multiple associated peers
X-Accept-Language: en
Priority: normal
In-Reply-To: <1d38a3350801290625m42ee8adfs13ab9346f5602186@mail.gmail.com>
References: <!&!AAAAAAAAAAAYAAAAAAAAAIILieByQXtOrs7W/bI503TCgAAAEAAAAK2atB6ek1dDnENOFPMnnZkBAAAAAA==@huawei.com>
	<!&!AAAAAAAAAAAYAAAAAAAAAIILieByQXtOrs7W/bI503TCgAAAEAAAAF5bAMcw6eBIqcQfYqsneRQBAAAAAA==@huawei.com>
	<df51fa9c2c5cf.479eeefe@us.army.mil>
	<1d38a3350801290625m42ee8adfs13ab9346f5602186@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hi Hu:

Here is the approach how to resolve it creating some uniform principles for the peer-to-peer protocol:

1. From P2P protocol point of view, there should be a uniform guideline what should be the primary, secnodary, and other criteria including the choosing the clients who cannot override the decision of the Peer entities.

2. What clients would do for implementing their criteria (e.g. policy, primary peer, or others) may depend on many things for which peer to peer protocol characteristics must not change.

To answer your question, item 1 will determine this if we think this is what we want. However, it has to come from the general principles of the P2P protocol, but not from the clinet-peer protocol.

Best regards,
Radhika

----- Original Message -----
From: Hui Deng 
Date: Tuesday, January 29, 2008 9:25
Subject: Re: RE: [P2PSIP] Open issues with client has multiple associated peers
To: "Roy, Radhika R Dr CTR USA USAMC" 
Cc: Song Yongchao , P2PSIP Mailing List 

> sorry for mine cutting in,
> 
> 2008/1/29, Roy, Radhika R Dr CTR USA USAMC 
> :> Please see my inputs inline [RRR]
> >
> > ----- Original Message -----
> > From: Song Yongchao
> > Date: Tuesday, January 29, 2008 6:06
> > Subject: RE: [P2PSIP] Open issues with client has multiple 
> associated peers
> > To: 'Song Yongchao' , 'P2PSIP Mailing List'
> >
> > > I need to modify the second question to make it more clear.
> > >
> > > I think most proposals agree that one client can have multiple
> > > associatedpeers to keep the service continuity. The open 
> issues are:
> > >
> > > (1) Should there be a primary associated peer? And when this peer
> > > fails, the
> > > client switches to another associated peer? I am not sure of 
> about it.
> >
> > [RRR] I think the answer is none from the protocol point of 
> view. However, if clients wants to make something as its primary, 
> secondary, etc., it should be left for implementations. It is a 
> different area how a client will these choices.
> [Hui] I have different image here, there could be client 
> involvement for this,
> for example, peer could say himself being a primary, who else 
> being a secondary
> through client protocl extension, make sense?
> 
> -Hui
> 

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



From p2psip-bounces@ietf.org Tue Jan 29 10:50:04 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JJsip-0000Ll-BZ; Tue, 29 Jan 2008 10:50:03 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JJsio-0000Lg-G8
	for p2psip@ietf.org; Tue, 29 Jan 2008 10:50:02 -0500
Received: from wx-out-0506.google.com ([66.249.82.227])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JJsio-0006N3-2K
	for p2psip@ietf.org; Tue, 29 Jan 2008 10:50:02 -0500
Received: by wx-out-0506.google.com with SMTP id s8so4888846wxc.31
	for <p2psip@ietf.org>; Tue, 29 Jan 2008 07:50:01 -0800 (PST)
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=ZUCe3Owgt8U3kXvAEgtzVCZ+tbOA8S+9CWg5Elp3cGg=;
	b=NoJ5IFda6ewZhwhKhKKct9E3Fx8sm/iLsrdbPH3OBXKu+ZDm2KILvv/hCJH7AytdcHQz0ukPAdP9PJODLYRHYMxvIQtLVqbqIfRW7qEpbTbWC/EBTZjUTTBBfAaeA3j4u2Darsa/6qq74yVb1U9qjn20dkgf2fIGbI8HK9f9/Ok=
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=c8KYoPKWLkf1d8UAuKOaPllwloBvSvlyHej/d3sLg5GQ2VCAqmgeup7AqAELtyA7SvLSTc+WHglxqXoMPP6owryJCtCzPVkJgfaEfcv4RXNHC0kFf9SnsTX0AdWB6KqQXFpPK/IZDEcS97xcDNTmEOrj6xU6c/bvHPAGNAbilxM=
Received: by 10.110.3.15 with SMTP id 15mr2885162tic.51.1201621799926;
	Tue, 29 Jan 2008 07:49:59 -0800 (PST)
Received: by 10.110.8.18 with HTTP; Tue, 29 Jan 2008 07:49:59 -0800 (PST)
Message-ID: <1d38a3350801290749y52f5a8cbxe9df5349706cf9ce@mail.gmail.com>
Date: Tue, 29 Jan 2008 23:49:59 +0800
From: "Hui Deng" <denghui02@gmail.com>
To: "Roy, Radhika R Dr CTR USA USAMC" <radhika.r.roy@us.army.mil>
Subject: Re: RE: [P2PSIP] Open issues with client has multiple associated peers
In-Reply-To: <dcd28a142cd88.479f01b5@us.army.mil>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <!&!AAAAAAAAAAAYAAAAAAAAAIILieByQXtOrs7W/bI503TCgAAAEAAAAK2atB6ek1dDnENOFPMnnZkBAAAAAA==@huawei.com>
	<!&!AAAAAAAAAAAYAAAAAAAAAIILieByQXtOrs7W/bI503TCgAAAEAAAAF5bAMcw6eBIqcQfYqsneRQBAAAAAA==@huawei.com>
	<df51fa9c2c5cf.479eeefe@us.army.mil>
	<1d38a3350801290625m42ee8adfs13ab9346f5602186@mail.gmail.com>
	<dcd28a142cd88.479f01b5@us.army.mil>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Hi, Radhika,

Thanks for your clarification.
I guess that from what you described below is that there exist the
concept of primary, secondary, et al. I will be happy if it is true.

Regarding to uniform principles, you listed peer side and client side,
you could enforce that uniform principle in peer side will dominate, but
I can't see why we stop Client having his own vision of the world.

thanks again.

-Hui

2008/1/29, Roy, Radhika R Dr CTR USA USAMC <radhika.r.roy@us.army.mil>:
> Hi Hu:
>
> Here is the approach how to resolve it creating some uniform principles for the peer-to-peer protocol:
>
> 1. From P2P protocol point of view, there should be a uniform guideline what should be the primary, secnodary, and other criteria including the choosing the clients who cannot override the decision of the Peer entities.
>
> 2. What clients would do for implementing their criteria (e.g. policy, primary peer, or others) may depend on many things for which peer to peer protocol characteristics must not change.
>
> To answer your question, item 1 will determine this if we think this is what we want. However, it has to come from the general principles of the P2P protocol, but not from the clinet-peer protocol.
>
> Best regards,
> Radhika
>
> ----- Original Message -----
> From: Hui Deng
> Date: Tuesday, January 29, 2008 9:25
> Subject: Re: RE: [P2PSIP] Open issues with client has multiple associated peers
> To: "Roy, Radhika R Dr CTR USA USAMC"
> Cc: Song Yongchao , P2PSIP Mailing List
>
> > sorry for mine cutting in,
> >
> > 2008/1/29, Roy, Radhika R Dr CTR USA USAMC
> > :> Please see my inputs inline [RRR]
> > >
> > > ----- Original Message -----
> > > From: Song Yongchao
> > > Date: Tuesday, January 29, 2008 6:06
> > > Subject: RE: [P2PSIP] Open issues with client has multiple
> > associated peers
> > > To: 'Song Yongchao' , 'P2PSIP Mailing List'
> > >
> > > > I need to modify the second question to make it more clear.
> > > >
> > > > I think most proposals agree that one client can have multiple
> > > > associatedpeers to keep the service continuity. The open
> > issues are:
> > > >
> > > > (1) Should there be a primary associated peer? And when this peer
> > > > fails, the
> > > > client switches to another associated peer? I am not sure of
> > about it.
> > >
> > > [RRR] I think the answer is none from the protocol point of
> > view. However, if clients wants to make something as its primary,
> > secondary, etc., it should be left for implementations. It is a
> > different area how a client will these choices.
> > [Hui] I have different image here, there could be client
> > involvement for this,
> > for example, peer could say himself being a primary, who else
> > being a secondary
> > through client protocl extension, make sense?
> >
> > -Hui
> >
>

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



From p2psip-bounces@ietf.org Tue Jan 29 21:38:09 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JK2px-0004cU-9y; Tue, 29 Jan 2008 21:38:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JK2pv-0004cO-RS
	for p2psip@ietf.org; Tue, 29 Jan 2008 21:38:03 -0500
Received: from szxga01-in.huawei.com ([61.144.161.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JK2pt-0005s0-II
	for p2psip@ietf.org; Tue, 29 Jan 2008 21:38:03 -0500
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 <0JVF00H3GRADTH@szxga01-in.huawei.com> for
	p2psip@ietf.org; Wed, 30 Jan 2008 10:37:26 +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 <0JVF006P4RACY4@szxga01-in.huawei.com> for
	p2psip@ietf.org; Wed, 30 Jan 2008 10:37:25 +0800 (CST)
Received: from s64081 ([10.164.9.47])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JVF002Z9RABXA@szxml04-in.huawei.com> for
	p2psip@ietf.org; Wed, 30 Jan 2008 10:37:24 +0800 (CST)
Date: Wed, 30 Jan 2008 10:37:23 +0800
From: Song Yongchao <melodysong@huawei.com>
Subject: RE: RE: [P2PSIP] Open issues with client has multiple associated peers
In-reply-to: <df51fa9c2c5cf.479eeefe@us.army.mil>
To: "'Roy, Radhika R Dr CTR USA USAMC'" <radhika.r.roy@us.army.mil>
Message-id: <!&!AAAAAAAAAAAYAAAAAAAAAIILieByQXtOrs7W/bI503TCgAAAEAAAAK0H+2ZHSoNCp5BvDgTMie8BAAAAAA==@huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: Achigbu7Dmq55hmhQrqWK8GSMoQzHQAYVdEg
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

See inline [Song].

> -----Original Message-----
> From: Roy, Radhika R Dr CTR USA USAMC [mailto:radhika.r.roy@us.army.mil]
> Sent: Tuesday, January 29, 2008 10:17 PM
> Please see my inputs inline [RRR]
> > I need to modify the second question to make it more clear.
> >
> > I think most proposals agree that one client can have multiple
> > associatedpeers to keep the service continuity. The open issues are:
> >
> > (1) Should there be a primary associated peer? And when this peer
> > fails, the
> > client switches to another associated peer? I am not sure of about it.
> 
> [RRR] I think the answer is none from the protocol point of view. However,
if
> clients wants to make something as its primary, secondary, etc., it should
be
> left for implementations. It is a different area how a client will these
> choices.

[Song] Maybe it is left to the implementations to do the choice in my mind.
If someone thinks there is a need for the choice to be communicated between
a client and its associated peer in some scenarios, then it should be
considered from the protocol point of view?

> > (2)Should the client learn more peers information that can be the
> > client'sassociated peers through its now associated peer? And when
> > one of its
> > associated peers fails, it joins another to keep enough associated
> > peers for
> > choice? I think probably this is what we needed.
> [RRR] Yes, definitely. I guess that it is the beauty of the P2P protocol
to
> make as reliable as one can make.

[Song] Yes, we need to provide reliable service to the clients in the
overlay. I think the associated peer may notice the client with a few peers
information regularly(must not very often if the churn rate of the overlay
is low), and then the client can inquire these peers to make a good choice.
I will add it to the SEP Client Protocol. Thanks.

> > (3)Should there be a notification mechanism between a client and its
> > associated peer? So the client can timely know the status of the
> > associated peer, and avoid choosing the congested or busy peer to
> > serve him? I think we
> > do need it.
> 
> [RRR] I think that the performance criteria for choosing a peer should be
a
> general one as it is the usual case in any communications networks. For
example,
> in the IP network, the routers also have some general criteria how to
choose
> the netxt hop router out of many neighboring routers. In the same token,
the
> P2P protocol should also follow the similar mechanisms that are obvious.

[Song] I agree. There is no such a peer which is eternal powerful in the p2p
overlay. It may be busy, or its bandwidth may get congested, or there is
some device error which makes it go down. In SEP client protocol, we provide
a NOTIFY message for the status notification between a client and its
associated peer, but we don't provide the strict criteria when a NOTIFY
should be sent, it is left to the implementation, or we can describe some
general criterias here?

> > Best Regards,
> > Song Yongchao
> > Email: melodysong@huawei.com
> >
> >
> >
> > _______________________________________________
> > P2PSIP mailing list
> > P2PSIP@ietf.org
> > https://www1.ietf.org/mailman/listinfo/p2psip
> >


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



From p2psip-bounces@ietf.org Tue Jan 29 22:29:58 2008
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JK3e9-0007nt-K4; Tue, 29 Jan 2008 22:29:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JK3e8-0007nn-LO
	for p2psip@ietf.org; Tue, 29 Jan 2008 22:29:56 -0500
Received: from szxga01-in.huawei.com ([61.144.161.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JK3e6-0006YR-GJ
	for p2psip@ietf.org; Tue, 29 Jan 2008 22:29:56 -0500
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 <0JVF00HBOTOQTH@szxga01-in.huawei.com> for
	p2psip@ietf.org; Wed, 30 Jan 2008 11:29:14 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JVF001PHTOPKH@szxga01-in.huawei.com> for
	p2psip@ietf.org; Wed, 30 Jan 2008 11:29:14 +0800 (CST)
Received: from s64081 ([10.164.9.47])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JVF00FV4TOPAY@szxml03-in.huawei.com> for
	p2psip@ietf.org; Wed, 30 Jan 2008 11:29:13 +0800 (CST)
Date: Wed, 30 Jan 2008 11:29:13 +0800
From: Song Yongchao <melodysong@huawei.com>
Subject: RE: RE: [P2PSIP] Open issues with client has multiple associated peers
In-reply-to: <1d38a3350801290749y52f5a8cbxe9df5349706cf9ce@mail.gmail.com>
To: 'Hui Deng' <denghui02@gmail.com>,
	"'Roy, Radhika R Dr CTR USA USAMC'" <radhika.r.roy@us.army.mil>
Message-id: <!&!AAAAAAAAAAAYAAAAAAAAAIILieByQXtOrs7W/bI503TCgAAAEAAAALn73z71B6xLmBQJFha41U8BAAAAAA==@huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AchijqJt05yjdJVtRGGNnoS7zKXzEQAXkxKw
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>,
	<mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

> -----Original Message-----
> From: Hui Deng [mailto:denghui02@gmail.com]
> Sent: Tuesday, January 29, 2008 11:50 PM
 
> I guess that from what you described below is that there exist the
> concept of primary, secondary, et al. I will be happy if it is true.
> 
> Regarding to uniform principles, you listed peer side and client side,
> you could enforce that uniform principle in peer side will dominate, but
> I can't see why we stop Client having his own vision of the world.
> 
> thanks again.
> 
> -Hui
> 
> 2008/1/29, Roy, Radhika R Dr CTR USA USAMC <radhika.r.roy@us.army.mil>:
> > Hi Hu:
> >
> > Here is the approach how to resolve it creating some uniform principles
for
> the peer-to-peer protocol:
> >
> > 1. From P2P protocol point of view, there should be a uniform guideline
what
> should be the primary, secnodary, and other criteria including the
choosing
> the clients who cannot override the decision of the Peer entities.

[Song] Do you mean that the guideline and criteria should be included in the
P2P protocol, and the details are left to the implementation?

> > 2. What clients would do for implementing their criteria (e.g. policy,
primary
> peer, or others) may depend on many things for which peer to peer protocol
> characteristics must not change.

[Song] I am sure the criteria will not change peer protocol characteristics.
However, p2p protocol should provide communication method between clients
and associated peers to implement their criteria if needed.

> > To answer your question, item 1 will determine this if we think this is
what
> we want. However, it has to come from the general principles of the P2P
protocol,
> but not from the clinet-peer protocol.

> > Best regards,
> > Radhika
> >
> > ----- Original Message -----
> > From: Hui Deng
> > Date: Tuesday, January 29, 2008 9:25
> > Subject: Re: RE: [P2PSIP] Open issues with client has multiple
associated
> peers
> > To: "Roy, Radhika R Dr CTR USA USAMC"
> > Cc: Song Yongchao , P2PSIP Mailing List
> >
> > > sorry for mine cutting in,
> > >
> > > 2008/1/29, Roy, Radhika R Dr CTR USA USAMC
> > > :> Please see my inputs inline [RRR]
> > > >
> > > > ----- Original Message -----
> > > > From: Song Yongchao
> > > > Date: Tuesday, January 29, 2008 6:06
> > > > Subject: RE: [P2PSIP] Open issues with client has multiple
> > > associated peers
> > > > To: 'Song Yongchao' , 'P2PSIP Mailing List'
> > > >
> > > > > I need to modify the second question to make it more clear.
> > > > >
> > > > > I think most proposals agree that one client can have multiple
> > > > > associatedpeers to keep the service continuity. The open
> > > issues are:
> > > > >
> > > > > (1) Should there be a primary associated peer? And when this peer
> > > > > fails, the
> > > > > client switches to another associated peer? I am not sure of
> > > about it.
> > > >
> > > > [RRR] I think the answer is none from the protocol point of
> > > view. However, if clients wants to make something as its primary,
> > > secondary, etc., it should be left for implementations. It is a
> > > different area how a client will these choices.
> > > [Hui] I have different image here, there could be client
> > > involvement for this,
> > > for example, peer could say himself being a primary, who else
> > > being a secondary
> > > through client protocl extension, make sense?
> > >
> > > -Hui
> > >
> >


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



From p2psip-bounces@ietf.org  Thu Jan 31 20:42:59 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: ietfarch-p2psip-archive@core3.amsl.com
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E50B028C149;
	Thu, 31 Jan 2008 20:42:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.52
X-Spam-Level: 
X-Spam-Status: No, score=-6.52 tagged_above=-999 required=5 tests=[AWL=0.079,
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cA-AjzYDpLun; Thu, 31 Jan 2008 20:42:59 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 287E428C180;
	Thu, 31 Jan 2008 20:42:59 -0800 (PST)
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 8006328C187
	for <p2psip@core3.amsl.com>; Thu, 31 Jan 2008 20:42:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rhpDH4v+wVyJ for <p2psip@core3.amsl.com>;
	Thu, 31 Jan 2008 20:42:56 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id BC6C328C180
	for <p2psip@ietf.org>; Thu, 31 Jan 2008 20:42:56 -0800 (PST)
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-3.cisco.com with ESMTP; 31 Jan 2008 20:44:30 -0800
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m114iU8n017355; 
	Thu, 31 Jan 2008 20:44:30 -0800
Received: from [192.168.4.177] (sjc-fluffy-vpn1.cisco.com [10.25.236.82])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with SMTP id m114iSqX004936;
	Fri, 1 Feb 2008 04:44:28 GMT
From: Cullen Jennings <fluffy@cisco.com>
To: Bruce Lowekamp <lowekamp@sipeerior.com>
In-Reply-To: <20d2bdfb0801280801s5058a661td76c82985b54918@mail.gmail.com>
Impp: xmpp:cullenfluffyjennings@jabber.org
References: <174701c85f78$24a386b0$44a36b80@cisco.com>
	<001501c86156$04a31ee0$2d09a40a@china.huawei.com>
	<20d2bdfb0801280801s5058a661td76c82985b54918@mail.gmail.com>
Message-Id: <0B983815-ED15-419D-9F59-47EFC094995E@cisco.com>
Mime-Version: 1.0 (Apple Message framework v915)
Date: Thu, 31 Jan 2008 20:44:07 -0800
X-Mailer: Apple Mail (2.915)
Authentication-Results: sj-dkim-1; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: P2PSIP Mailing List <p2psip@ietf.org>
Subject: Re: [P2PSIP] Choice of STUN peer or TURN peer
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: <http://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: <http://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 Jan 28, 2008, at 8:01 AM, Bruce Lowekamp wrote:

> But otherwise, the TURN
> protocol seems to work as is.  For the purposes of a TURN server, a
> NAT having endpoint independent mapping seems to be the only real
> requirement on the NAT

Agree on that but ...
I think the hard part we have not fully solved yet is how a peer that  
is thinking of being a TURN server is going to detect if this is the  
case or not.
_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
http://www.ietf.org/mailman/listinfo/p2psip
From p2psip-bounces@ietf.org  Thu Jan 31 23:02:12 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: ietfarch-p2psip-archive@core3.amsl.com
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 130EC3A6840;
	Thu, 31 Jan 2008 23:02:12 -0800 (PST)
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 core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CIxaj8xREmA4; Thu, 31 Jan 2008 23:02:11 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2714D3A6812;
	Thu, 31 Jan 2008 23:02:11 -0800 (PST)
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 C1E5E3A6812
	for <p2psip@core3.amsl.com>; Thu, 31 Jan 2008 23:02:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id iZFh0adp2jkn for <p2psip@core3.amsl.com>;
	Thu, 31 Jan 2008 23:02:09 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [61.144.161.53])
	by core3.amsl.com (Postfix) with ESMTP id D61EE3A680A
	for <p2psip@ietf.org>; Thu, 31 Jan 2008 23:02:08 -0800 (PST)
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 <0JVJ007UNSY5PO@szxga01-in.huawei.com> for
	p2psip@ietf.org; Fri, 01 Feb 2008 15:03:41 +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 <0JVJ00BB2SXXCL@szxga01-in.huawei.com> for
	p2psip@ietf.org; Fri, 01 Feb 2008 15:03:41 +0800 (CST)
Received: from j36340 ([10.164.9.45])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JVJ00D9ESXX8W@szxml04-in.huawei.com> for
	p2psip@ietf.org; Fri, 01 Feb 2008 15:03:33 +0800 (CST)
Date: Fri, 01 Feb 2008 15:03:33 +0800
From: JiangXingFeng <jiang.x.f@huawei.com>
In-reply-to: <20d2bdfb0801280801s5058a661td76c82985b54918@mail.gmail.com>
To: 'Bruce Lowekamp' <lowekamp@sipeerior.com>
Message-id: <002101c864a0$8f1ac3a0$2d09a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Office Outlook 11
Thread-index: AchhxwRiKwoxy6LaSZ6TgKaHnj8wdgC2F6bg
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
Subject: Re: [P2PSIP] Choice of STUN peer or TURN peer
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: <http://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: <http://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, Bruce:

Sorry for late response. See inline. 

--
Jiang XingFeng

> -----Original Message-----
> 
> > >
> > >   TURN client         STUN server          NAT  TURN server
> > >        |                   |                |      |
> > >  1.    |------give me a TURN address------->|----->|
> > >  2.    |                   |<--STUN Request--------|
> > >  3.    |                   |-STUN Response->|----->|
> > >  4.    |<-----here is your TURN address------------|
> > >
> 
> If we allow a TURN server to be behind a NAT, then the only change I
> would see necessary would that 1 and 4 would have to be routed over
> the overlay (a reload tunnel, for example).  But otherwise, the TURN
> protocol seems to work as is.  For the purposes of a TURN server, a
> NAT having endpoint independent mapping seems to be the only real
> requirement on the NAT as long as the two voice endpoints support ICE;
> the connectivity checks should take care of any form of filtering the
> NAT uses.

While TURN client in question gets its relayed address from the TURN server,
it will exchange them with its peer, say B. According to the connectivity
check in ICE, B and ICE will send message to try to find direct connection. 

So if B send the message destined to the relayed address first, it will be
filtered by the TURN server. Then TURN client sends a message destined to
the B's candidate, it will send the message through the TURN server. But in
the message 1 reached the TURN server in a hop-by-hop way, if the message is
sent directly to the TURN server, it will be filtered. If the message is
sent in a hop-by-hop way through the overlay, the immediate peer to the STUN
server may change over time, so the message may also be filtered. Am I
missing something? 


Regards!

JiangXingFeng

_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
http://www.ietf.org/mailman/listinfo/p2psip
From p2psip-bounces@ietf.org  Thu Jan 31 23:20:21 2008
Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: ietfarch-p2psip-archive@core3.amsl.com
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 664AA3A6854;
	Thu, 31 Jan 2008 23:20:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_44=0.6]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id TZ4rGDOHfaKW; Thu, 31 Jan 2008 23:20:20 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 946873A6811;
	Thu, 31 Jan 2008 23:20:20 -0800 (PST)
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 85ED33A680A
	for <p2psip@core3.amsl.com>; Thu, 31 Jan 2008 23:20:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cJOcJkTgiq6A for <p2psip@core3.amsl.com>;
	Thu, 31 Jan 2008 23:20:18 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [61.144.161.53])
	by core3.amsl.com (Postfix) with ESMTP id 945DC3A6811
	for <p2psip@ietf.org>; Thu, 31 Jan 2008 23:20:18 -0800 (PST)
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 <0JVJ007A7TSEPO@szxga01-in.huawei.com> for
	p2psip@ietf.org; Fri, 01 Feb 2008 15:21:50 +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 <0JVJ00A6GTSDYC@szxga01-in.huawei.com> for
	p2psip@ietf.org; Fri, 01 Feb 2008 15:21:50 +0800 (CST)
Received: from s64081 ([10.164.9.47])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JVJ00D38TSD8W@szxml04-in.huawei.com> for
	p2psip@ietf.org; Fri, 01 Feb 2008 15:21:49 +0800 (CST)
Date: Fri, 01 Feb 2008 15:21:49 +0800
From: Song Yongchao <melodysong@huawei.com>
In-reply-to: <0B983815-ED15-419D-9F59-47EFC094995E@cisco.com>
To: 'Cullen Jennings' <fluffy@cisco.com>,
	'Bruce Lowekamp' <lowekamp@sipeerior.com>
Message-id: <!&!AAAAAAAAAAAYAAAAAAAAAIILieByQXtOrs7W/bI503TCgAAAEAAAAFv5pjyAF5tIpzg0AE9h2Q8BAAAAAA==@huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Office Outlook 11
Thread-index: AchkjSjvQqR3LNQzQrWRrcJxx0588gAEzSEA
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>
Subject: Re: [P2PSIP] Choice of STUN peer or TURN peer
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: <http://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: <http://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

See inline
> On Jan 28, 2008, at 8:01 AM, Bruce Lowekamp wrote:
> > But otherwise, the TURN
> > protocol seems to work as is.  For the purposes of a TURN server, a
> > NAT having endpoint independent mapping seems to be the only real
> > requirement on the NAT
> 
> Agree on that but ...
> I think the hard part we have not fully solved yet is how a peer that
> is thinking of being a TURN server is going to detect if this is the
> case or not.

In that case,each peer that is willing to be the TURN server must dialog
with several STUN servers with public address to detect its NAT mapping
type, only peers with public addresses or behind endpoint independent NATs
could be TURN servers. However, STUN servers may be behind NAT either, in
the worst case, it may be behind the same outermost NAT with the peer, and
these STUN servers response different reflexive addresses with the public
STUN servers. So, in that case STUN servers must be classified in to public
addressed and non-public addressed, and the peer willing to be the TURN
server must dialog with public addressed STUN servers to detect its NAT
mapping type.

For the simplicity, I think we should only admit peers with public addresses
to be the TURN servers at the first step.

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

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