[P2PSIP] Discussion items for the Tuesday teleconference
"Henry Sinnreich" <hsinnrei@adobe.com> Mon, 07 January 2008 13:44 UTC
Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 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, 07 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] 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. <<NGI_SMA_Boeing_VoWLAN_Demo_White_Paper_12-8-07.doc>> 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 _______________________________________________ P2PSIP mailing list P2PSIP@ietf.org https://www1.ietf.org/mailman/listinfo/p2psip
- [P2PSIP] Boeing HIP Implementation of SIP (which … Paine, Richard H
- [P2PSIP] Discussion items for the Tuesday telecon… Henry Sinnreich
- RE: [P2PSIP] Discussion items for the Tuesday tel… Henderson, Thomas R