From thomas.r.henderson@boeing.com Wed Jun 3 16:24:03 2009 Return-Path: X-Original-To: hipsec@core3.amsl.com Delivered-To: hipsec@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 76E783A6E27 for ; Wed, 3 Jun 2009 16:24:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8wQNINLOWm3i for ; Wed, 3 Jun 2009 16:24:02 -0700 (PDT) Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id A68BC3A6D16 for ; Wed, 3 Jun 2009 16:23:56 -0700 (PDT) Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n53NNqBi011026 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 3 Jun 2009 16:23:52 -0700 (PDT) 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 n53NNqCS014710; Wed, 3 Jun 2009 16:23:52 -0700 (PDT) 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 n53NNpZu014691; Wed, 3 Jun 2009 16:23:52 -0700 (PDT) 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.3959); Wed, 3 Jun 2009 16:23:46 -0700 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: Wed, 3 Jun 2009 16:23:46 -0700 Message-ID: <77F357662F8BFA4CA7074B0410171B6D07B0C2DB@XCH-NW-5V1.nw.nos.boeing.com> In-Reply-To: <4A1FE240.20504@ericsson.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Hipsec] Agenda requests Thread-Index: AcngZ2d7irlxb321Q5u7kJlOYLindgEOlN4A References: <4A1FE240.20504@ericsson.com> From: "Henderson, Thomas R" To: "Gonzalo Camarillo" X-OriginalArrivalTime: 03 Jun 2009 23:23:46.0609 (UTC) FILETIME=[57D39A10:01C9E4A2] Cc: HIP Subject: Re: [Hipsec] Agenda requests X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2009 23:24:03 -0000 =20 > -----Original Message----- > From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com]=20 > Sent: Friday, May 29, 2009 6:25 AM > To: HIP > Subject: [Hipsec] Agenda requests >=20 > Folks, >=20 > the HIP WG will be meeting in Stockholm. If you would like to present=20 > something there, please send your agenda request to the chairs. >=20 > Thanks, >=20 > Gonzalo > HIP co-chair Gonzalo, Could you please update us on the following two charter items status? WGLC Legacy NAT traversal specification WGLC Native API specification=20 It seems to me that we may be able to have a WGLC conclude before the meeting and discuss the outcome at the WG meeting. - Tom=20 From Pascal.Urien@enst.fr Fri Jun 5 01:34:03 2009 Return-Path: X-Original-To: hipsec@core3.amsl.com Delivered-To: hipsec@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F1F253A67A5 for ; Fri, 5 Jun 2009 01:34:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.249 X-Spam-Level: X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jAx-toDnZdnD for ; Fri, 5 Jun 2009 01:34:02 -0700 (PDT) Received: from smtp2.enst.fr (revol2.enst.fr [137.194.2.14]) by core3.amsl.com (Postfix) with ESMTP id 1AD7C3A69F0 for ; Fri, 5 Jun 2009 01:33:39 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by smtp2.enst.fr (Postfix) with ESMTP id F02ACB9327; Fri, 5 Jun 2009 10:30:33 +0200 (CEST) X-Virus-Scanned: amavisd-new at enst.fr Received: from PC-de-pascal.enst.fr (pptp20-6.enst.fr [137.194.20.6]) by smtp2.enst.fr (Postfix) with ESMTP id 0F1BFB9245; Fri, 5 Jun 2009 10:30:32 +0200 (CEST) X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 05 Jun 2009 10:30:17 +0200 To: "Gonzalo Camarillo" From: Pascal Urien In-Reply-To: <77F357662F8BFA4CA7074B0410171B6D07B0C2DB@XCH-NW-5V1.nw.nos .boeing.com> References: <4A1FE240.20504@ericsson.com> <77F357662F8BFA4CA7074B0410171B6D07B0C2DB@XCH-NW-5V1.nw.nos.boeing.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Message-Id: <20090605083033.0F1BFB9245@smtp2.enst.fr> Cc: HIP Subject: Re: [Hipsec] Agenda requests X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2009 08:34:03 -0000 Hi Gonzalo, I request a slot for the presentation of the draft HIP-TAGS, and more generally i suggest a discussion for a possible starting of a WG dealing with internet of things (IoT) I suggest an open debate dealing with the following items : - Is IoT identity oriented ? - Is HIP a good protocol for the IoT - Is there strong privacy issues for the IoT Best Regards Pascal From root@core3.amsl.com Tue Jun 9 04:45:01 2009 Return-Path: X-Original-To: hipsec@ietf.org Delivered-To: hipsec@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 90BAE3A6AD3; Tue, 9 Jun 2009 04:45:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20090609114501.90BAE3A6AD3@core3.amsl.com> Date: Tue, 9 Jun 2009 04:45:01 -0700 (PDT) Cc: hipsec@ietf.org Subject: [Hipsec] I-D Action:draft-ietf-hip-nat-traversal-07.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jun 2009 11:45:01 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Host Identity Protocol Working Group of the IETF. Title : Basic HIP Extensions for Traversal of Network Address Translators Author(s) : M. Komu, et al. Filename : draft-ietf-hip-nat-traversal-07.txt Pages : 33 Date : 2009-06-09 This document specifies extensions to the Host Identity Protocol (HIP) to facilitate Network Address Translator (NAT) traversal. The extensions are based on the use of the Interactive Connectivity Establishment (ICE) methodology to discover a working path between two end-hosts, and on standard techniques for encapsulating Encapsulating Security Payload (ESP) packets within the User Datagram Protocol (UDP). This document also defines elements of procedure for NAT traversal, including the optional use of a HIP relay server. With these extensions HIP is able to work in environments that have NATs and provides a generic NAT traversal solution to higher-layer networking applications. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hip-nat-traversal-07.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-hip-nat-traversal-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-06-09043106.I-D@ietf.org> --NextPart-- From ari.keranen@nomadiclab.com Tue Jun 9 05:24:45 2009 Return-Path: X-Original-To: hipsec@core3.amsl.com Delivered-To: hipsec@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 364E63A69D9 for ; Tue, 9 Jun 2009 05:24:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gFYEQNsxzqNN for ; Tue, 9 Jun 2009 05:24:44 -0700 (PDT) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 4C7073A6934 for ; Tue, 9 Jun 2009 05:24:40 -0700 (PDT) X-AuditID: c1b4fb3c-b7b9cae00000140d-9f-4a2e548d9d46 Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw3.ericsson.se (Symantec Mail Security) with SMTP id C5.55.05133.D845E2A4; Tue, 9 Jun 2009 14:24:45 +0200 (CEST) Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 9 Jun 2009 14:24:45 +0200 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 9 Jun 2009 14:24:44 +0200 Received: from [127.0.0.1] (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 9CAD323F6 for ; Tue, 9 Jun 2009 15:24:44 +0300 (EEST) Message-ID: <4A2E548A.30803@nomadiclab.com> Date: Tue, 09 Jun 2009 15:24:42 +0300 From: Ari Keranen User-Agent: Thunderbird 2.0.0.21 (X11/20090318) MIME-Version: 1.0 To: hipsec@ietf.org References: <20090609114501.90BAE3A6AD3@core3.amsl.com> In-Reply-To: <20090609114501.90BAE3A6AD3@core3.amsl.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 09 Jun 2009 12:24:44.0572 (UTC) FILETIME=[456A15C0:01C9E8FD] X-Brightmail-Tracker: AAAAAA== Subject: Re: [Hipsec] I-D Action:draft-ietf-hip-nat-traversal-07.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jun 2009 12:24:45 -0000 Hi all, Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Host Identity Protocol Working Group of the IETF. > > Title : Basic HIP Extensions for Traversal of Network Address Translators > Author(s) : M. Komu, et al. > Filename : draft-ietf-hip-nat-traversal-07.txt > Pages : 33 > Date : 2009-06-09 This updated version of the HIP NAT traversal draft contains the changes that were suggested by Samu Varjonen and discussed earlier on the mailing list. We also added new NOTIFY error types for signaling different error conditions and modified how the I2/R2 packets with UDP-ENCAPSULATION NAT traversal mode are exchanged. The "IPv4-IPv6 Interoperability" appendix was removed since it didn't bring much added value. Cheers, Ari From gonzalo.camarillo@ericsson.com Wed Jun 10 23:59:06 2009 Return-Path: X-Original-To: hipsec@core3.amsl.com Delivered-To: hipsec@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9EB4E3A6821 for ; Wed, 10 Jun 2009 23:59:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a0y9JjlXqtBc for ; Wed, 10 Jun 2009 23:59:05 -0700 (PDT) Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id A0E413A68FF for ; Wed, 10 Jun 2009 23:59:04 -0700 (PDT) X-AuditID: c1b4fb3e-b7b2dae00000205f-47-4a30ab3f8517 Received: from esealmw127.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id 6F.47.08287.F3BA03A4; Thu, 11 Jun 2009 08:59:11 +0200 (CEST) Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 11 Jun 2009 08:59:10 +0200 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 11 Jun 2009 08:59:09 +0200 Received: from [131.160.126.159] (rvi2-126-159.lmf.ericsson.se [131.160.126.159]) by mail.lmf.ericsson.se (Postfix) with ESMTP id D7038246A; Thu, 11 Jun 2009 09:59:09 +0300 (EEST) Message-ID: <4A30AB3D.9020609@ericsson.com> Date: Thu, 11 Jun 2009 09:59:09 +0300 From: Gonzalo Camarillo User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: HIP Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 11 Jun 2009 06:59:09.0926 (UTC) FILETIME=[1EAF2860:01C9EA62] X-Brightmail-Tracker: AAAAAA== Subject: [Hipsec] WGLC: draft-ietf-hip-nat-traversal-07.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jun 2009 06:59:06 -0000 Folks, I would like to start the WGLC on the NAT traversal draft: http://tools.ietf.org/internet-drafts/draft-ietf-hip-nat-traversal-07.txt This WGLC will end on June 28th. Please, send your comments to this mailing list. Thanks, Gonzalo HIP co-chair From jeffrey.m.ahrenholz@boeing.com Tue Jun 16 14:11:29 2009 Return-Path: X-Original-To: hipsec@core3.amsl.com Delivered-To: hipsec@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8993B3A6D71 for ; Tue, 16 Jun 2009 14:11:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9jvEobocp341 for ; Tue, 16 Jun 2009 14:11:28 -0700 (PDT) Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id A24CA3A6BF0 for ; Tue, 16 Jun 2009 14:11:28 -0700 (PDT) Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n5GLB2vK008378 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 16 Jun 2009 14:11:04 -0700 (PDT) Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n5GLB1SN019197 for ; Tue, 16 Jun 2009 14:11:01 -0700 (PDT) Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n5GLAxUD019106 for ; Tue, 16 Jun 2009 14:11:01 -0700 (PDT) Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.53]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 16 Jun 2009 14:11:01 -0700 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: Tue, 16 Jun 2009 14:11:00 -0700 Message-ID: <0DF156EE7414494187B087A3C279BDB404AD7B59@XCH-NW-6V1.nw.nos.boeing.com> In-Reply-To: <4A30AB3D.9020609@ericsson.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Hipsec] WGLC: draft-ietf-hip-nat-traversal-07.txt Thread-Index: AcnqYid9S1Kmhnn4QTKLXbdsdc8f7gEYD6Qg References: <4A30AB3D.9020609@ericsson.com> From: "Ahrenholz, Jeffrey M" To: "HIP" X-OriginalArrivalTime: 16 Jun 2009 21:11:01.0567 (UTC) FILETIME=[F3A964F0:01C9EEC6] Subject: Re: [Hipsec] WGLC: draft-ietf-hip-nat-traversal-07.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jun 2009 21:11:29 -0000 > I would like to start the WGLC on the NAT traversal draft: >=20 > http://tools.ietf.org/internet-drafts/draft-ietf-hip-nat-trave > rsal-07.txt >=20 > This WGLC will end on June 28th. Please, send your comments to this=20 > mailing list. Here are some comments on this latest NAT traversal draft. All of these are just editorial nits, but I do have one general comment: It is not explicitly stated in RFC 5203 or in this NAT draft that when you make a registration with a server, you maintain a HIP association with that server as long as you are registered for that service. This is implied in RFC 5203 Section 6 ("Because they have to store HIP association state anyway..."), and in the NAT draft Section 4.1 ("...the client sends NAT keepalives periodically to the relay..."). Maybe there should be a sentence stating the relationship between the registration and the association? Another comment is that I think the text reads better to have "registers with the relay" rather than "registers to the relay" (specific changes below). Section 4.1 p. 9 Figure 2: Example Registration with a HIP Relay ^^^^ Section 4.2 p. 10 The Initiator takes the role of... ^^^ Section 4.3 p. 10 With registration with a HIP relay it is... ^^^^ Section 4.5 p. 13 MUST contain the same information as the RELAY_FROM ^^^ Section 4.9 p. 17 R1 and answering [to] it with an I2 ^^^^ delete "to" Section 4.9 p. 17 successfully registered with the rendezvous ^^^^ Section 4.9 p. 17 suggest replacing: to be used in case of mobility or multihoming event which causes NAT traversal to be taken in to use during the lifetime of the HIP association with: in case of a mobility or multihoming event which causes NAT traversal to be used during the lifetime of the HIP association Section 4.10 p. 18 pair established for a data channel without ^ Section 4.10 p. 18 registered with the relay MUST utilize the RELAY_TO parameter as in ^^^^ ^^ the base exchange Section 5.1 p. 19 the UDP header already contains a checksum ^^^^^^^^^^^^^^^^ Section 6.3 p. 27 suggest replacing: The relay can protect itself against replay attacks by involving in the base exchange by introducing nonces that the end-hosts (Initiator and Responder) have to sign. with: The relay can protect itself against replay attacks by becoming involved in the base exchange by introducing nonces that the end-hosts (Initiator and Responder) are required to sign. Appendix A p.30 suggest replacing: The value should not be too small so that the checks do not cause congestion in the network or overwhelm=20 the NATs. On the other hand, too high pacing value makes the checks last for a long time and thus increase the connection setup delay. with: The value should not be so small that the checks cause network congestion or overwhelm the NATs. On the other hand, a pacing value that is too high makes the checks last for a long time, thus increasing the connection setup delay. Appendix A p.30 characteristics are not known ^^^^^ -Jeff From miika.komu@hiit.fi Tue Jun 16 23:45:27 2009 Return-Path: X-Original-To: hipsec@core3.amsl.com Delivered-To: hipsec@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7FFF63A692A for ; Tue, 16 Jun 2009 23:45:27 -0700 (PDT) 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_35=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U95r6cSZ7X9K for ; Tue, 16 Jun 2009 23:45:26 -0700 (PDT) Received: from creon.otaverkko.fi (creon.otaverkko.fi [212.68.0.5]) by core3.amsl.com (Postfix) with ESMTP id A79903A6816 for ; Tue, 16 Jun 2009 23:45:26 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by creon.otaverkko.fi (Postfix) with ESMTP id 0D43421AF4F; Wed, 17 Jun 2009 09:45:28 +0300 (EEST) Received: from creon.otaverkko.fi ([127.0.0.1]) by localhost (creon.otaverkko.fi [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26187-08; Wed, 17 Jun 2009 09:45:20 +0300 (EEST) Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by creon.otaverkko.fi (Postfix) with ESMTP id 3FCC321AF3A; Wed, 17 Jun 2009 09:45:20 +0300 (EEST) Received: from [192.168.1.2] (cs27101111.pp.htv.fi [89.27.101.111]) by argo.otaverkko.fi (Postfix) with ESMTP id 1E5A525ED06; Wed, 17 Jun 2009 09:45:20 +0300 (EEST) Message-ID: <4A3891D4.7050502@hiit.fi> Date: Wed, 17 Jun 2009 09:48:52 +0300 From: Miika Komu User-Agent: Thunderbird 2.0.0.21 (X11/20090409) MIME-Version: 1.0 To: "Ahrenholz, Jeffrey M" References: <4A30AB3D.9020609@ericsson.com> <0DF156EE7414494187B087A3C279BDB404AD7B59@XCH-NW-6V1.nw.nos.boeing.com> In-Reply-To: <0DF156EE7414494187B087A3C279BDB404AD7B59@XCH-NW-6V1.nw.nos.boeing.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at otaverkko.fi Cc: HIP Subject: Re: [Hipsec] WGLC: draft-ietf-hip-nat-traversal-07.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: miika.komu@hiit.fi List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jun 2009 06:45:27 -0000 Ahrenholz, Jeffrey M wrote: Hi Jeff, >> I would like to start the WGLC on the NAT traversal draft: >> >> http://tools.ietf.org/internet-drafts/draft-ietf-hip-nat-trave >> rsal-07.txt >> >> This WGLC will end on June 28th. Please, send your comments to this >> mailing list. > > Here are some comments on this latest NAT traversal draft. > > All of these are just editorial nits, but I do have one general comment: > > It is not explicitly stated in RFC 5203 or in this NAT draft that when > you make a registration with a server, you maintain a HIP association > with that server as long as you are registered for that service. This is > implied in RFC 5203 Section 6 ("Because they have to store HIP > association state anyway..."), and in the NAT draft Section 4.1 ("...the > client sends NAT keepalives periodically to the relay..."). Maybe there > should be a sentence stating the relationship between the registration > and the association? strictly speaking, a full-blown HIP association is not necessary for the keepalives. However, HIPL (and hip4inter?) implement this using a full HIP association, so I have no strong objections against your suggestion. From ari.keranen@nomadiclab.com Wed Jun 17 00:49:45 2009 Return-Path: X-Original-To: hipsec@core3.amsl.com Delivered-To: hipsec@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CACF23A6C27 for ; Wed, 17 Jun 2009 00:49:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.949 X-Spam-Level: X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_35=0.6, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rCT5jU+ebfIr for ; Wed, 17 Jun 2009 00:49:44 -0700 (PDT) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 707D63A6BCC for ; Wed, 17 Jun 2009 00:49:44 -0700 (PDT) X-AuditID: c1b4fb3c-b7b0bae00000673a-11-4a38a022ddfe Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with SMTP id D3.CC.26426.220A83A4; Wed, 17 Jun 2009 09:49:54 +0200 (CEST) Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 17 Jun 2009 09:49:53 +0200 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 17 Jun 2009 09:49:52 +0200 Received: from [127.0.0.1] (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 54FE7234B; Wed, 17 Jun 2009 10:49:52 +0300 (EEST) Message-ID: <4A38A01E.6060206@nomadiclab.com> Date: Wed, 17 Jun 2009 10:49:50 +0300 From: Ari Keranen User-Agent: Thunderbird 2.0.0.21 (X11/20090318) MIME-Version: 1.0 To: miika.komu@hiit.fi, "Ahrenholz, Jeffrey M" References: <4A30AB3D.9020609@ericsson.com> <0DF156EE7414494187B087A3C279BDB404AD7B59@XCH-NW-6V1.nw.nos.boeing.com> <4A3891D4.7050502@hiit.fi> In-Reply-To: <4A3891D4.7050502@hiit.fi> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 17 Jun 2009 07:49:52.0598 (UTC) FILETIME=[32BC8F60:01C9EF20] X-Brightmail-Tracker: AAAAAA== Cc: HIP Subject: Re: [Hipsec] WGLC: draft-ietf-hip-nat-traversal-07.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jun 2009 07:49:45 -0000 Hi Miika and Jeff, Miika Komu wrote: > Ahrenholz, Jeffrey M wrote: >>> I would like to start the WGLC on the NAT traversal draft: >>> >>> http://tools.ietf.org/internet-drafts/draft-ietf-hip-nat-trave >>> rsal-07.txt >>> >>> This WGLC will end on June 28th. Please, send your comments to this >>> mailing list. >> >> Here are some comments on this latest NAT traversal draft. >> >> All of these are just editorial nits, but I do have one general comment: >> >> It is not explicitly stated in RFC 5203 or in this NAT draft that when >> you make a registration with a server, you maintain a HIP association >> with that server as long as you are registered for that service. This is >> implied in RFC 5203 Section 6 ("Because they have to store HIP >> association state anyway..."), and in the NAT draft Section 4.1 ("...the >> client sends NAT keepalives periodically to the relay..."). Maybe there >> should be a sentence stating the relationship between the registration >> and the association? > > strictly speaking, a full-blown HIP association is not necessary for the > keepalives. However, HIPL (and hip4inter?) implement this using a full > HIP association, so I have no strong objections against your suggestion. Just to clarify: you don't need to have a Security Association with the HIP relay server, but surely you need to keep some state, i.e., a HIP association, with it. You can also make an SA with the relay server and also our implementation currently does this. The difference regarding NAT traversal comes from the fact that without the SA you don't draw ESP keys from the keying material before drawing the keys used for STUN integrity. But I agree that stating this more explicitly makes sense. I added to the end of the last paragraph of 4.1: The relay client maintains the HIP association with the relay server as long as it requires relaying service from it. Cheers, Ari From ari.keranen@nomadiclab.com Wed Jun 17 03:03:49 2009 Return-Path: X-Original-To: hipsec@core3.amsl.com Delivered-To: hipsec@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E1C8028C20A for ; Wed, 17 Jun 2009 03:03:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.099 X-Spam-Level: X-Spam-Status: No, score=-6.099 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6e5fAtSsVvS8 for ; Wed, 17 Jun 2009 03:03:48 -0700 (PDT) Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id D24373A6A53 for ; Wed, 17 Jun 2009 03:03:45 -0700 (PDT) X-AuditID: c1b4fb3e-b7b1dae000006c99-34-4a38bb7a682f Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id 45.2C.27801.A7BB83A4; Wed, 17 Jun 2009 11:46:34 +0200 (CEST) Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 17 Jun 2009 11:46:31 +0200 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 17 Jun 2009 11:46:30 +0200 Received: from [127.0.0.1] (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id B483B244E; Wed, 17 Jun 2009 12:46:30 +0300 (EEST) Message-ID: <4A38BB74.3070101@nomadiclab.com> Date: Wed, 17 Jun 2009 12:46:28 +0300 From: Ari Keranen User-Agent: Thunderbird 2.0.0.21 (X11/20090318) MIME-Version: 1.0 To: "Ahrenholz, Jeffrey M" References: <4A30AB3D.9020609@ericsson.com> <0DF156EE7414494187B087A3C279BDB404AD7B59@XCH-NW-6V1.nw.nos.boeing.com> In-Reply-To: <0DF156EE7414494187B087A3C279BDB404AD7B59@XCH-NW-6V1.nw.nos.boeing.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 17 Jun 2009 09:46:31.0054 (UTC) FILETIME=[7E2432E0:01C9EF30] X-Brightmail-Tracker: AAAAAA== Cc: HIP Subject: Re: [Hipsec] WGLC: draft-ietf-hip-nat-traversal-07.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jun 2009 10:03:50 -0000 Hi Jeff, Ahrenholz, Jeffrey M wrote: >> I would like to start the WGLC on the NAT traversal draft: >> >> http://tools.ietf.org/internet-drafts/draft-ietf-hip-nat-trave >> rsal-07.txt >> >> This WGLC will end on June 28th. Please, send your comments to this >> mailing list. > > Here are some comments on this latest NAT traversal draft. [...] Thanks for the review and comments! I made all the changes you proposed and a fixed pre-version is available here: http://users.piuha.net/akeranen/drafts/draft-ietf-hip-nat-traversal-08-pre1.txt Also a diff to the -07 version showing just the fixes is available here: http://users.piuha.net/akeranen/drafts/draft-ietf-hip-nat-traversal-08-pre1-diff.html Cheers, Ari From jeffrey.m.ahrenholz@boeing.com Wed Jun 17 08:07:14 2009 Return-Path: X-Original-To: hipsec@core3.amsl.com Delivered-To: hipsec@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7C43E3A6E4E for ; Wed, 17 Jun 2009 08:07:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A9QJM8DF1apE for ; Wed, 17 Jun 2009 08:07:13 -0700 (PDT) Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id B76C63A6ADE for ; Wed, 17 Jun 2009 08:07:13 -0700 (PDT) Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n5HF7GOZ004810 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Jun 2009 08:07:17 -0700 (PDT) Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n5HF7GaW006280; Wed, 17 Jun 2009 08:07:16 -0700 (PDT) Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n5HF7F66006263; Wed, 17 Jun 2009 08:07:15 -0700 (PDT) Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.53]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 17 Jun 2009 08:07:15 -0700 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: Wed, 17 Jun 2009 08:07:09 -0700 Message-ID: <0DF156EE7414494187B087A3C279BDB404AD7B5C@XCH-NW-6V1.nw.nos.boeing.com> In-Reply-To: <4A38A01E.6060206@nomadiclab.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Hipsec] WGLC: draft-ietf-hip-nat-traversal-07.txt Thread-Index: AcnvIDr1nm8q/ywxQ8iaOmWpKdrQywAObHqw References: <4A30AB3D.9020609@ericsson.com> <0DF156EE7414494187B087A3C279BDB404AD7B59@XCH-NW-6V1.nw.nos.boeing.com> <4A3891D4.7050502@hiit.fi> <4A38A01E.6060206@nomadiclab.com> From: "Ahrenholz, Jeffrey M" To: "Ari Keranen" , , "HIP" X-OriginalArrivalTime: 17 Jun 2009 15:07:15.0264 (UTC) FILETIME=[4C959C00:01C9EF5D] Subject: Re: [Hipsec] WGLC: draft-ietf-hip-nat-traversal-07.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jun 2009 15:07:14 -0000 >> strictly speaking, a full-blown HIP association is not=20 >> necessary for the keepalives.=20 Yes, I was thinking that because of the RELAY_HMAC (or RVS_HMAC) parameter you need to maintain a HIP association while registered, due to the required keying material, but I guess these parameters are only used initially. > Just to clarify: you don't need to have a Security=20 > Association with the HIP relay server, but surely > you need to keep some state, i.e., a HIP association To have a HIP association without Security Association I'm assuming you would omit the ESP_INFO and ESP_TRANSFORM parameters, that is interesting. I don't know how useful any SA with the relay would be, since the relay server is not relaying data packets. > But I agree that stating this more explicitly makes sense. I added to=20 > the end of the last paragraph of 4.1: >=20 > The relay client maintains the HIP association with the relay > server as long as it requires relaying service from it. This text looks good. -Jeff From ari.keranen@nomadiclab.com Thu Jun 18 06:09:05 2009 Return-Path: X-Original-To: hipsec@core3.amsl.com Delivered-To: hipsec@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C281A3A6CD2 for ; Thu, 18 Jun 2009 06:09:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.149 X-Spam-Level: X-Spam-Status: No, score=-6.149 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ghDbHQWgrlq1 for ; Thu, 18 Jun 2009 06:09:05 -0700 (PDT) Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id DE9133A672F for ; Thu, 18 Jun 2009 06:08:40 -0700 (PDT) X-AuditID: c1b4fb3e-b7b55ae0000025f6-f7-4a3a3c5f41f4 Received: from esealmw127.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id FD.22.09718.F5C3A3A4; Thu, 18 Jun 2009 15:08:47 +0200 (CEST) Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 18 Jun 2009 15:08:01 +0200 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 18 Jun 2009 15:08:00 +0200 Received: from [127.0.0.1] (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id DF7B5246A; Thu, 18 Jun 2009 16:08:00 +0300 (EEST) Message-ID: <4A3A3C2E.50300@nomadiclab.com> Date: Thu, 18 Jun 2009 16:07:58 +0300 From: Ari Keranen User-Agent: Thunderbird 2.0.0.21 (X11/20090318) MIME-Version: 1.0 To: "Ahrenholz, Jeffrey M" References: <4A30AB3D.9020609@ericsson.com> <0DF156EE7414494187B087A3C279BDB404AD7B59@XCH-NW-6V1.nw.nos.boeing.com> <4A3891D4.7050502@hiit.fi> <4A38A01E.6060206@nomadiclab.com> <0DF156EE7414494187B087A3C279BDB404AD7B5C@XCH-NW-6V1.nw.nos.boeing.com> In-Reply-To: <0DF156EE7414494187B087A3C279BDB404AD7B5C@XCH-NW-6V1.nw.nos.boeing.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 18 Jun 2009 13:08:00.0950 (UTC) FILETIME=[CEB1AD60:01C9F015] X-Brightmail-Tracker: AAAAAA== Cc: HIP Subject: Re: [Hipsec] WGLC: draft-ietf-hip-nat-traversal-07.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jun 2009 13:09:05 -0000 Ahrenholz, Jeffrey M wrote: >>> strictly speaking, a full-blown HIP association is not >>> necessary for the keepalives. > > Yes, I was thinking that because of the RELAY_HMAC (or RVS_HMAC) > parameter you need to maintain a HIP association while registered, due > to the required keying material, but I guess these parameters are only > used initially. Yes, but you need HMACs also for closing the association. And the NAT traversal mobility extensions could have use for (RELAY_)HMACs during the lifetime of HIP association too. >> Just to clarify: you don't need to have a Security >> Association with the HIP relay server, but surely >> you need to keep some state, i.e., a HIP association > > To have a HIP association without Security Association I'm assuming you > would omit the ESP_INFO and ESP_TRANSFORM parameters, that is > interesting. I don't know how useful any SA with the relay would be, > since the relay server is not relaying data packets. Yes, you would omit the ESP_* parameters from the BeX. And you could want to exchange secured data also directly with the relay (i.e., not for relaying) and then making an SA with it would make sense. >> But I agree that stating this more explicitly makes sense. I added to >> the end of the last paragraph of 4.1: >> >> The relay client maintains the HIP association with the relay >> server as long as it requires relaying service from it. > > This text looks good. Thanks. Cheers, Ari From gonzalo.camarillo@ericsson.com Wed Jun 24 09:51:19 2009 Return-Path: X-Original-To: hipsec@core3.amsl.com Delivered-To: hipsec@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A18993A6CE8 for ; Wed, 24 Jun 2009 09:51:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dzBt-SKLNNzv for ; Wed, 24 Jun 2009 09:51:18 -0700 (PDT) Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 6602B3A6D5F for ; Wed, 24 Jun 2009 09:51:18 -0700 (PDT) X-AuditID: c1b4fb3e-b7be1ae000004757-4c-4a42595abf07 Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id 01.DC.18263.A59524A4; Wed, 24 Jun 2009 18:50:34 +0200 (CEST) Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 24 Jun 2009 18:50:34 +0200 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 24 Jun 2009 18:50:33 +0200 Received: from [131.160.126.137] (rvi2-126-137.lmf.ericsson.se [131.160.126.137]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 640AB245E; Wed, 24 Jun 2009 19:50:33 +0300 (EEST) Message-ID: <4A425954.4040500@ericsson.com> Date: Wed, 24 Jun 2009 19:50:28 +0300 From: Gonzalo Camarillo User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: HIP Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 24 Jun 2009 16:50:33.0643 (UTC) FILETIME=[E3FF6FB0:01C9F4EB] X-Brightmail-Tracker: AAAAAA== Subject: [Hipsec] WGLC: draft-ietf-hip-native-api-06 X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jun 2009 16:51:19 -0000 Folks, we would like to start the WGLC on the following draft: http://tools.ietf.org/html/draft-ietf-hip-native-api-06 Some time ago, we decided to wait with this WGLC until the NAT traversal draft was more mature. The WGLC on the NAT traversal draft ends on Sunday. We chose to make both WGLCs overlap a bit just in case somebody wants to review both drafts at the same time. This WGLC will end on July 12th. Cheers, Gonzalo HIP co-chair From gonzalo.camarillo@ericsson.com Wed Jun 24 09:58:01 2009 Return-Path: X-Original-To: hipsec@core3.amsl.com Delivered-To: hipsec@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 226493A6FB9 for ; Wed, 24 Jun 2009 09:58:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5gtleOGLgj4R for ; Wed, 24 Jun 2009 09:58:00 -0700 (PDT) Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 1D4013A6FAA for ; Wed, 24 Jun 2009 09:57:59 -0700 (PDT) X-AuditID: c1b4fb3e-b7be1ae000004757-ad-4a425adf0dee Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id 4D.0D.18263.FDA524A4; Wed, 24 Jun 2009 18:57:03 +0200 (CEST) Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 24 Jun 2009 18:57:00 +0200 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 24 Jun 2009 18:57:00 +0200 Received: from [131.160.126.137] (rvi2-126-137.lmf.ericsson.se [131.160.126.137]) by mail.lmf.ericsson.se (Postfix) with ESMTP id ACACD245E; Wed, 24 Jun 2009 19:57:00 +0300 (EEST) Message-ID: <4A425ADC.20207@ericsson.com> Date: Wed, 24 Jun 2009 19:57:00 +0300 From: Gonzalo Camarillo User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: "Henderson, Thomas R" References: <4A1FE240.20504@ericsson.com> <77F357662F8BFA4CA7074B0410171B6D07B0C2DB@XCH-NW-5V1.nw.nos.boeing.com> In-Reply-To: <77F357662F8BFA4CA7074B0410171B6D07B0C2DB@XCH-NW-5V1.nw.nos.boeing.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 24 Jun 2009 16:57:00.0830 (UTC) FILETIME=[CAC77BE0:01C9F4EC] X-Brightmail-Tracker: AAAAAA== Cc: HIP Subject: Re: [Hipsec] Agenda requests X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jun 2009 16:58:01 -0000 Hi Tom, as you suggested, both WGLCs will be over by Stockholm. Thanks, Gonzalo Henderson, Thomas R wrote: > > >> -----Original Message----- >> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com] >> Sent: Friday, May 29, 2009 6:25 AM >> To: HIP >> Subject: [Hipsec] Agenda requests >> >> Folks, >> >> the HIP WG will be meeting in Stockholm. If you would like to present >> something there, please send your agenda request to the chairs. >> >> Thanks, >> >> Gonzalo >> HIP co-chair > > Gonzalo, > > Could you please update us on the following two charter items status? > > WGLC Legacy NAT traversal specification > WGLC Native API specification > > It seems to me that we may be able to have a WGLC conclude before the > meeting and discuss the outcome at the WG meeting. > > - Tom > From gonzalo.camarillo@ericsson.com Wed Jun 24 10:17:10 2009 Return-Path: X-Original-To: hipsec@core3.amsl.com Delivered-To: hipsec@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E3A7528C489 for ; Wed, 24 Jun 2009 10:17:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dDpDAMOLiUGq for ; Wed, 24 Jun 2009 10:17:10 -0700 (PDT) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id E148D28C339 for ; Wed, 24 Jun 2009 10:17:09 -0700 (PDT) X-AuditID: c1b4fb3c-b7bdcae0000052f9-cf-4a425be538bc Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with SMTP id 10.A8.21241.5EB524A4; Wed, 24 Jun 2009 19:01:25 +0200 (CEST) Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 24 Jun 2009 19:01:25 +0200 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 24 Jun 2009 19:01:25 +0200 Received: from [131.160.126.137] (rvi2-126-137.lmf.ericsson.se [131.160.126.137]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 306BD245E for ; Wed, 24 Jun 2009 20:01:25 +0300 (EEST) Message-ID: <4A425BE5.4000609@ericsson.com> Date: Wed, 24 Jun 2009 20:01:25 +0300 From: Gonzalo Camarillo User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: HIP References: <4A1FE240.20504@ericsson.com> In-Reply-To: <4A1FE240.20504@ericsson.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 24 Jun 2009 17:01:25.0110 (UTC) FILETIME=[684D6960:01C9F4ED] X-Brightmail-Tracker: AAAAAA== Subject: Re: [Hipsec] Agenda requests X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jun 2009 17:17:11 -0000 Hi, I was expecting to get an agenda request on how to move HIP from experimental to proposed standard and, so far, I have not received it. Cheers, Gonzalo Gonzalo Camarillo wrote: > Folks, > > the HIP WG will be meeting in Stockholm. If you would like to present > something there, please send your agenda request to the chairs. > > Thanks, > > Gonzalo > HIP co-chair > > _______________________________________________ > Hipsec mailing list > Hipsec@ietf.org > https://www.ietf.org/mailman/listinfo/hipsec > From root@core3.amsl.com Mon Jun 29 01:15:01 2009 Return-Path: X-Original-To: hipsec@ietf.org Delivered-To: hipsec@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 5A89F28C184; Mon, 29 Jun 2009 01:15:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20090629081501.5A89F28C184@core3.amsl.com> Date: Mon, 29 Jun 2009 01:15:01 -0700 (PDT) Cc: hipsec@ietf.org Subject: [Hipsec] I-D Action:draft-ietf-hip-nat-traversal-08.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 08:15:01 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Host Identity Protocol Working Group of the IETF. Title : Basic HIP Extensions for Traversal of Network Address Translators Author(s) : M. Komu, et al. Filename : draft-ietf-hip-nat-traversal-08.txt Pages : 33 Date : 2009-06-29 This document specifies extensions to the Host Identity Protocol (HIP) to facilitate Network Address Translator (NAT) traversal. The extensions are based on the use of the Interactive Connectivity Establishment (ICE) methodology to discover a working path between two end-hosts, and on standard techniques for encapsulating Encapsulating Security Payload (ESP) packets within the User Datagram Protocol (UDP). This document also defines elements of procedure for NAT traversal, including the optional use of a HIP relay server. With these extensions HIP is able to work in environments that have NATs and provides a generic NAT traversal solution to higher-layer networking applications. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hip-nat-traversal-08.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-hip-nat-traversal-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-06-29010109.I-D@ietf.org> --NextPart-- From ari.keranen@nomadiclab.com Mon Jun 29 01:26:22 2009 Return-Path: X-Original-To: hipsec@core3.amsl.com Delivered-To: hipsec@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0567E3A69D0 for ; Mon, 29 Jun 2009 01:26:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.174 X-Spam-Level: X-Spam-Status: No, score=-6.174 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lzqdJHvhqQmS for ; Mon, 29 Jun 2009 01:26:20 -0700 (PDT) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 45C143A68B3 for ; Mon, 29 Jun 2009 01:26:20 -0700 (PDT) X-AuditID: c1b4fb3c-b7bdcae0000052f9-56-4a487abeb19a Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with SMTP id 3D.3E.21241.EBA784A4; Mon, 29 Jun 2009 10:26:38 +0200 (CEST) Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 29 Jun 2009 10:26:38 +0200 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 29 Jun 2009 10:26:38 +0200 Received: from [127.0.0.1] (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 67E69245E for ; Mon, 29 Jun 2009 11:26:38 +0300 (EEST) Message-ID: <4A487ABC.5050508@nomadiclab.com> Date: Mon, 29 Jun 2009 11:26:36 +0300 From: Ari Keranen User-Agent: Thunderbird 2.0.0.21 (X11/20090318) MIME-Version: 1.0 To: hipsec@ietf.org References: <20090629081501.5A89F28C184@core3.amsl.com> In-Reply-To: <20090629081501.5A89F28C184@core3.amsl.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 29 Jun 2009 08:26:38.0238 (UTC) FILETIME=[525B83E0:01C9F893] X-Brightmail-Tracker: AAAAAA== Subject: Re: [Hipsec] I-D Action:draft-ietf-hip-nat-traversal-08.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 08:26:22 -0000 Hi all, The WGLC for the NAT traversal draft ended yesterday and this is the updated version that addresses all the comments that were given. Cheers, Ari Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Host Identity Protocol Working Group of the IETF. > > > Title : Basic HIP Extensions for Traversal of Network Address Translators > Author(s) : M. Komu, et al. > Filename : draft-ietf-hip-nat-traversal-08.txt > Pages : 33 > Date : 2009-06-29 > > This document specifies extensions to the Host Identity Protocol > (HIP) to facilitate Network Address Translator (NAT) traversal. The > extensions are based on the use of the Interactive Connectivity > Establishment (ICE) methodology to discover a working path between > two end-hosts, and on standard techniques for encapsulating > Encapsulating Security Payload (ESP) packets within the User Datagram > Protocol (UDP). This document also defines elements of procedure for > NAT traversal, including the optional use of a HIP relay server. > With these extensions HIP is able to work in environments that have > NATs and provides a generic NAT traversal solution to higher-layer > networking applications. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-hip-nat-traversal-08.txt > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ From gonzalo.camarillo@ericsson.com Mon Jun 29 03:00:55 2009 Return-Path: X-Original-To: hipsec@core3.amsl.com Delivered-To: hipsec@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 897B328C217 for ; Mon, 29 Jun 2009 03:00:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zU9xHz5-uZoS for ; Mon, 29 Jun 2009 03:00:54 -0700 (PDT) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 9080928C1DB for ; Mon, 29 Jun 2009 03:00:54 -0700 (PDT) X-AuditID: c1b4fb3c-b7bdcae0000052f9-aa-4a4890e98089 Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with SMTP id AA.BB.21241.9E0984A4; Mon, 29 Jun 2009 12:01:13 +0200 (CEST) Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 29 Jun 2009 12:01:13 +0200 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 29 Jun 2009 12:01:13 +0200 Received: from [131.160.37.44] (EV001E681B5FE2.lmf.ericsson.se [131.160.37.44]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 1CE42245E; Mon, 29 Jun 2009 13:01:13 +0300 (EEST) Message-ID: <4A4890E9.1060805@ericsson.com> Date: Mon, 29 Jun 2009 13:01:13 +0300 From: Gonzalo Camarillo User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: HIP Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 29 Jun 2009 10:01:13.0173 (UTC) FILETIME=[88E1E050:01C9F8A0] X-Brightmail-Tracker: AAAAAA== Subject: [Hipsec] Requesting the publication of draft-ietf-hip-nat-traversal-08.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 10:00:55 -0000 Hi, the authors of the NAT traversal draft have submitted a new revision that addresses all the comments received during its WGLC. Please, have a look at it because we will be requesting its publication shortly. Cheers, Gonzalo HIP co-chair From ari.keranen@nomadiclab.com Tue Jun 30 05:09:12 2009 Return-Path: X-Original-To: hipsec@core3.amsl.com Delivered-To: hipsec@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 75DA23A6BDF for ; Tue, 30 Jun 2009 05:09:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.189 X-Spam-Level: X-Spam-Status: No, score=-6.189 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p7iiGcoBCvCh for ; Tue, 30 Jun 2009 05:09:11 -0700 (PDT) Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 020C73A6E23 for ; Tue, 30 Jun 2009 05:08:53 -0700 (PDT) X-AuditID: c1b4fb3e-b7be1ae000004757-8b-4a49f575383a Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id 96.80.18263.575F94A4; Tue, 30 Jun 2009 13:22:29 +0200 (CEST) Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 30 Jun 2009 13:22:03 +0200 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 30 Jun 2009 13:22:02 +0200 Received: from [127.0.0.1] (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id F1A88246A for ; Tue, 30 Jun 2009 14:22:02 +0300 (EEST) Message-ID: <4A49F558.7040304@nomadiclab.com> Date: Tue, 30 Jun 2009 14:22:00 +0300 From: Ari Keranen User-Agent: Thunderbird 2.0.0.21 (X11/20090318) MIME-Version: 1.0 To: HIP References: <4A425954.4040500@ericsson.com> In-Reply-To: <4A425954.4040500@ericsson.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 30 Jun 2009 11:22:02.0853 (UTC) FILETIME=[FDEE1150:01C9F974] X-Brightmail-Tracker: AAAAAA== Subject: Re: [Hipsec] WGLC: draft-ietf-hip-native-api-06 X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2009 12:09:12 -0000 Gonzalo Camarillo wrote: > we would like to start the WGLC on the following draft: > > http://tools.ietf.org/html/draft-ietf-hip-native-api-06 Here are some comments on the HIP native API draft. Indented text is copy-pasted from the draft. The draft does not seem to take NAT traversal into account. For NAT traversal purposes an application that is not using a resolver should be able to get the local UDP port used by the HIP daemon for receiving incoming HIP messages. Also the application should be able create a HIT-to-locator mapping that includes a (possibly non-standard) UDP port number for a peer. Probably this is more of an issue for the shim6 API draft, though. Also, I think it would be worthwhile to clarify in section 3.2 what socket options exactly are used for setting new HIT-to-locator mappings when no (DNS) resolver is used. Maybe add a reference to section 4.6. In section 4.1. Socket Family and Address Structure Extensions: The HIP_HIT_ANY equals to HIP_HIT_ANY_PUB or HIP_HIT_ANY_TMP. Do you mean here that HIP_HIT_ANY = HIP_HIT_ANY_PUB | HIP_HIT_ANY_TMP or that the implementation is free to set HIP_HIP_ANY to any one of the two? I'd guess you mean the binary/logical or, but it wasn't clear while reading this the first time. 4.2. Extensions to Resolver Data Structures: The simultaneous use of both HIP_PREFER_ORCHID and HIP_PREFER_PASSIVE_* flags produces a single sockaddr_hip structure containing a wildcard address that the application can use either for incoming (node argument is NULL in getaddrinfo) or outgoing communications (node argument is non-NULL). I think you should introduce the HIP_PREFER_PASSIVE_* flags before this. Actually, I couldn't find any explanation of their semantics in the whole document. 4.6. Explicit Handling of Locators: An application that initiates a connection using a connection oriented socket to a particular host at a known address or set of addresses can invoke SHIM_LOCLIST_PEER socket option. What about UDP (non-connection oriented) sockets? I hope you can also use the LOCLIST option with them. 4.5. Source HIT Selection by the System: | Public DSA | 130 | 7 | | Public RSA | 140 | 8 | | [RFC3484] rules | 50-100 | 7 | Are the labels for Public DSA and RFC 3484 rules intentionally the same? Editorial nits/comments: The table of contents is partially double-spaced but all the other HIP RFCs have fully single-spaced TOCs, so it would make sense to use only single spacing here too. 4.1. Socket Family and Address Structure Extensions: The port number ship_port is two octets in network byte order. and the ship_hit is 16 octets in A period in the middle of a sentence. 4.4. Validating HITs: short sockaddr_is_srcaddr(struct sockaddr *srcaddr uint64_t flags); Missing comma between the arguments. 4.6. Explicit Handling of Locators: The description for SHIM_LOC_LOCAL_SEND and SHIM_LOC_PEER_SEND in Figure 6 implies that the options have only "set" semantics while they seem to also work with "get". Also, I'd call that a "table" instead of "figure". [...] uses the first address (if multiple are provided, or else the application can override this by setting SHIM_LOC_PEER_PREF to one of the addresses in SHIM_LOCLIST_PEER. Missing closing parenthesis. Cheers, Ari From jeffrey.m.ahrenholz@boeing.com Tue Jun 30 12:11:37 2009 Return-Path: X-Original-To: hipsec@core3.amsl.com Delivered-To: hipsec@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5CB753A68B8 for ; Tue, 30 Jun 2009 12:11:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wTs4d0g9vq1f for ; Tue, 30 Jun 2009 12:11:36 -0700 (PDT) Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 9171D3A68FE for ; Tue, 30 Jun 2009 12:11:36 -0700 (PDT) Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n5UJB6Qs009421 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 30 Jun 2009 12:11:07 -0700 (PDT) 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 n5UJB6PM014527 for ; Tue, 30 Jun 2009 12:11:06 -0700 (PDT) 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 n5UJB4FQ014383 for ; Tue, 30 Jun 2009 12:11:06 -0700 (PDT) Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.53]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 30 Jun 2009 12:11:03 -0700 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: Tue, 30 Jun 2009 12:11:02 -0700 Message-ID: <0DF156EE7414494187B087A3C279BDB404AD7B8F@XCH-NW-6V1.nw.nos.boeing.com> In-Reply-To: <4A425954.4040500@ericsson.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Hipsec] WGLC: draft-ietf-hip-native-api-06 Thread-Index: Acn07BAeo5nNz7hHRHCn8KluptVWCQEyQ9Bg References: <4A425954.4040500@ericsson.com> From: "Ahrenholz, Jeffrey M" To: "HIP" X-OriginalArrivalTime: 30 Jun 2009 19:11:03.0731 (UTC) FILETIME=[83334830:01C9F9B6] Subject: Re: [Hipsec] WGLC: draft-ietf-hip-native-api-06 X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2009 19:11:37 -0000 Here are additional comments on the native API draft, mostly editorial nits. You might reference ORCHIDs earlier on (maybe second or third paragraph of introduction) as the first time they appear in this draft is section 4.2. Should the resolver function be dealing with sockaddr_orchid instead of sockaddr_hip? The naming is a little strange to have the HIP_PREFER_ORCHID flag return sockaddr_hip. (See also a note below about typedef orchid_t ...) Abstract, Page 2 current sockets API for the Host Identity Protocol ^^^ Section 1., Page 4 are of an experimental nature *or* are experimental in nature ^^ ^^(deleted of) ^^ Section 3.1 Page 5 (parenthesis might make these steps more clear in the text) calls the resolver in step (a) to resolve an FQDN in step (b). ^ ^ ^^ ^ ^ and a set of locators in step (c). ^^ ^ ^ Section 3.1 Page 5 caches the HIT to locator mapping with the HIP module ^^^^ Figure 1 Page 5 I'm not sure you need the double text Maybe just or would suffice? Section 3.2 Page 5-6 suggest replacing: The resolver associates implicitly the HIT with the locator(s) by e.g. communicating the HIT-to-IP mapping to the HIP daemon.=20 with this: The resolver may implicitly associate the HIT with its=20 locator(s) by communicating the HIT-to-IP mapping to the HIP daemon. Page 3 says: "This document specifies extensions to [RFC3493] to define a new socket address family, AF_HIP. The macro AF_HIP is used as an alias for PF_HIP in this document because the distinction between AF and PF has been lost in practice." but then Section 4.1 Page 6, 2nd paragraph talks about using PF_HIP "The use of the PF_HIP constant" ... In Figure 2 on Page 6, there is typedef struct in6_addr hip_hit_t. It may be worthwhile to reference the RFC 4843 ORCHIDs so that the HIT is defined as an ORCHID such as: typedef struct in6_addr orchid_t; typedef orchid_t hip_hit_t; Section 4.1 Page 7 identifiers refer to the use of anonymous identifiers ^^ Section 4.1 Page 8 it should be noted that different ^^^^^ (replaced noticed) Section 4.2 Page 8 to be used by applications to query ^ The application must set both the ^^^ The application denotes its preference ^^^ Section 4.2 Page 10 cache the locator mappings with the HIP module ^^^^ it should be noted that the application ^^^^^ Section 4.5 Page 11 When an application using a AF_HIP-based ^^ Section 4.5 Page 12 When the system provides multiple keys of the same type ^^^ ^^^ Section 4.5 Page 12 calls and in the ancillary data of datagram packets ^^^^^^^^^ Section 9 Page 15 Jan Melen appears to have provided twice the feedback :) From thomas.r.henderson@boeing.com Tue Jun 30 13:44:48 2009 Return-Path: X-Original-To: hipsec@core3.amsl.com Delivered-To: hipsec@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 59CE028C3FB for ; Tue, 30 Jun 2009 13:44:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.374 X-Spam-Level: X-Spam-Status: No, score=-6.374 tagged_above=-999 required=5 tests=[AWL=0.225, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uRcnjIPca-L5 for ; Tue, 30 Jun 2009 13:44:47 -0700 (PDT) Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 52C2628C0D0 for ; Tue, 30 Jun 2009 13:44:47 -0700 (PDT) Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n5UKiebS026888 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Jun 2009 15:44:41 -0500 (CDT) Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n5UKieAI007824; Tue, 30 Jun 2009 13:44:40 -0700 (PDT) Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n5UKiZK0007621; Tue, 30 Jun 2009 13:44:40 -0700 (PDT) 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.3959); Tue, 30 Jun 2009 13:44:38 -0700 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: Tue, 30 Jun 2009 13:44:37 -0700 Message-ID: <77F357662F8BFA4CA7074B0410171B6D07B0C3E8@XCH-NW-5V1.nw.nos.boeing.com> In-Reply-To: <4A49F558.7040304@nomadiclab.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Hipsec] WGLC: draft-ietf-hip-native-api-06 Thread-Index: Acn5e6z5MLjVFqklRsKHqwe9VIFfBwARLUJQ References: <4A425954.4040500@ericsson.com> <4A49F558.7040304@nomadiclab.com> From: "Henderson, Thomas R" To: "Ari Keranen" , "HIP" X-OriginalArrivalTime: 30 Jun 2009 20:44:38.0401 (UTC) FILETIME=[95CDEF10:01C9F9C3] Subject: Re: [Hipsec] WGLC: draft-ietf-hip-native-api-06 X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2009 20:44:48 -0000 > -----Original Message----- > From: Ari Keranen [mailto:ari.keranen@nomadiclab.com]=20 > Sent: Tuesday, June 30, 2009 4:22 AM > To: HIP > Subject: Re: [Hipsec] WGLC: draft-ietf-hip-native-api-06 >=20 > Gonzalo Camarillo wrote: > > we would like to start the WGLC on the following draft: > >=20 > > http://tools.ietf.org/html/draft-ietf-hip-native-api-06 >=20 > Here are some comments on the HIP native API draft. Indented text is=20 > copy-pasted from the draft. >=20 > The draft does not seem to take NAT traversal into account. For NAT=20 > traversal purposes an application that is not using a=20 > resolver should be=20 > able to get the local UDP port used by the HIP daemon for receiving=20 > incoming HIP messages. Also the application should be able create a=20 > HIT-to-locator mapping that includes a (possibly=20 > non-standard) UDP port=20 > number for a peer. Probably this is more of an issue for the=20 > shim6 API=20 > draft, though. I'm concerned that you have hit upon a real problem here. The shim6 draft or protocol framework do not seem to have any concept of NAT traversal support. I do not think this is a simple patch for the shim6 document; for instance, is shim6 WG willing to rewrite Figure 1 of http://www.ietf.org/internet-drafts/draft-ietf-shim6-multihome-shim-api- 08.txt to show the shim6 layer sitting on top of UDP? The concept of a locator in shim6 is an IPv6 address, not a transport address. One possibility would be to remove the explicit locator-related messages in the native HIP API document (leaving them for further study), but that would also strip out the support for outbound opportunistic mode. The other options seem to be to ask the shim6-api draft authors, and WG, to support NAT traversal, or to just write a HIP-specific API for these aspects. In either case, I think we (HIP WG) should decide what we want this API to be. >=20 >=20 > 4.5. Source HIT Selection by the System: >=20 > | Public DSA | 130 | 7 | > | Public RSA | 140 | 8 | > | [RFC3484] rules | 50-100 | 7 | >=20 > Are the labels for Public DSA and RFC 3484 rules=20 > intentionally the same? >=20 They shouldn't be the same, but more broadly, I think this section may need some more work. According to RFC 3484, the precedence value is used for sorting destination addresses, and the label for selecting source addresses, but the text here implies that precedence is used for source address selection. It is not clear how RFC3484 rules relate to HITs, or whether they are referring to possible use of IP addresses. =20 Tom