From hipsec-bounces@ietf.org Wed Apr 2 01:39:22 2008 Return-Path: X-Original-To: hipsec-archive@megatron.ietf.org Delivered-To: ietfarch-hipsec-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 306793A6975; Wed, 2 Apr 2008 01:39:22 -0700 (PDT) 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 0E5083A6975 for ; Wed, 2 Apr 2008 01:39:21 -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 BicUXt9xWzMk for ; Wed, 2 Apr 2008 01:39:20 -0700 (PDT) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 129B23A67EB for ; Wed, 2 Apr 2008 01:39:19 -0700 (PDT) Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id E524821E3A for ; Wed, 2 Apr 2008 10:31:09 +0200 (CEST) X-AuditID: c1b4fb3c-ac097bb00000193b-5a-47f3444dc4de Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id CDB7C21E42 for ; Wed, 2 Apr 2008 10:31:09 +0200 (CEST) Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 2 Apr 2008 10:31:09 +0200 Received: from [131.160.37.21] ([131.160.37.21]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 2 Apr 2008 10:31:09 +0200 Message-ID: <47F3444D.4050704@ericsson.com> Date: Wed, 02 Apr 2008 11:31:09 +0300 From: Gonzalo Camarillo User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Gonzalo Camarillo References: <47C278CE.1050007@ericsson.com> In-Reply-To: <47C278CE.1050007@ericsson.com> X-OriginalArrivalTime: 02 Apr 2008 08:31:09.0569 (UTC) FILETIME=[E6F49710:01C8949B] X-Brightmail-Tracker: AAAAAA== Cc: HIP Subject: Re: [Hipsec] Native API draft: way forward 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org Hi, since nobody has objected, we will do 2) (see email below). Cheers, Gonzalo Gonzalo Camarillo wrote: > Folks, > > as you know, the WGLC on the native API draft finished a while ago. > There were a few technical comments on the draft during the WGLC, most > of which have been incorporated into the draft. Now we need to make a > decision on how to proceed with this draft. > > There are some concerns that the API defined in this document may need > to change as soon as we have a little more experience with NAT traversal > and HIP-based overlays. With this in mind, we have two options: > > 1) publish the draft now stressing that it defines an experimental API > and, as soon as we understand how NAT traversal and HIP-based overlays > will affect the API, publish a new spec, most likely modifying the API. > > 2) wait for the NAT traversal and HIP-based overlays work to be more > mature before publishing this draft. This way, the API defined by the > draft will have better chances to be future proof. > > > I lean towards doing 2), but I would like to get feedback from the > community on what is the best way forward. > > Thanks, > > Gonzalo > HIP co-chair > _______________________________________________ > Hipsec mailing list > Hipsec@ietf.org > http://www.ietf.org/mailman/listinfo/hipsec > _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@ietf.org Wed Apr 2 03:53:23 2008 Return-Path: X-Original-To: hipsec-archive@megatron.ietf.org Delivered-To: ietfarch-hipsec-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 830E33A6EED; Wed, 2 Apr 2008 03:53:23 -0700 (PDT) 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 4A6B33A6EED for ; Wed, 2 Apr 2008 03:53:22 -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 a2OgtFh9LRBt for ; Wed, 2 Apr 2008 03:53:21 -0700 (PDT) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 4B1F63A6D3B for ; Wed, 2 Apr 2008 03:53:21 -0700 (PDT) Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 340CE211FA for ; Wed, 2 Apr 2008 12:47:36 +0200 (CEST) X-AuditID: c1b4fb3c-ad89abb00000193b-23-47f364489ee3 Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 19AE4211FB for ; Wed, 2 Apr 2008 12:47:36 +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, 2 Apr 2008 12:47:35 +0200 Received: from [131.160.37.21] ([131.160.37.21]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 2 Apr 2008 12:47:35 +0200 Message-ID: <47F36447.3080802@ericsson.com> Date: Wed, 02 Apr 2008 13:47:35 +0300 From: Gonzalo Camarillo User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: HIP X-OriginalArrivalTime: 02 Apr 2008 10:47:35.0619 (UTC) FILETIME=[F638B130:01C894AE] X-Brightmail-Tracker: AAAAAA== Subject: [Hipsec] [Fwd: HIP NAT Traversal using NICE] 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org Hi, FYI: I just sent the email below to the MMUSIC mailing list. Cheers, Gonzalo -------- Original Message -------- Subject: HIP NAT Traversal using NICE Date: Wed, 02 Apr 2008 13:47:08 +0300 From: Gonzalo Camarillo To: mmusic CC: mmusic-chairs@tools.ietf.org, David Ward , rai-ads@tools.ietf.org, internet-ads@tools.ietf.org Folks involved in the MMUSIC WG, the HIP WG is developing a NAT traversal solution that is based on NICE: http://www.ietf.org/internet-drafts/draft-ietf-hip-nat-traversal-03.txt http://www.ietf.org/internet-drafts/draft-rosenberg-mmusic-ice-nonsip-00.txt This means that we depend on the NICE draft to have a working NAT traversal solution for HIP. However, from the presentation of this draft in the last IETF, it is not clear to us whether or not the MMUSIC WG is going to work on this draft. The HIP WG would like to encourage the MMUSIC WG to work on this specification, since we need it. If the MMUSIC WG decides not to do so, the HIP WG will most likely copy/paste the contents of the NICE draft in our NAT traversal spec. However, we believe that having a stand-alone NICE specification can be useful for protocols other than HIP that will decide to use ICE for NAT traversal in the future. A clarification of the status of this work in the MMUSIC WG would be appreciated. Thanks, Gonzalo HIP WG co-chair _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@ietf.org Wed Apr 2 05:00:52 2008 Return-Path: X-Original-To: hipsec-archive@megatron.ietf.org Delivered-To: ietfarch-hipsec-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B71E63A6EC4; Wed, 2 Apr 2008 05:00:52 -0700 (PDT) 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 3FAFC3A6914 for ; Wed, 2 Apr 2008 05:00:51 -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 Y05pGUxMEobn for ; Wed, 2 Apr 2008 05:00:45 -0700 (PDT) Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id C18B53A6EF7 for ; Wed, 2 Apr 2008 05:00:45 -0700 (PDT) Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 93627222E0; Wed, 2 Apr 2008 13:58:38 +0200 (CEST) X-AuditID: c1b4fb3e-aa991bb000004ec0-79-47f374eea7d5 Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 76482222DF; Wed, 2 Apr 2008 13:58:38 +0200 (CEST) Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 2 Apr 2008 13:58:37 +0200 Received: from [131.160.37.21] ([131.160.37.21]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 2 Apr 2008 13:58:37 +0200 Message-ID: <47F374ED.5050403@ericsson.com> Date: Wed, 02 Apr 2008 14:58:37 +0300 From: Gonzalo Camarillo User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: HIP X-OriginalArrivalTime: 02 Apr 2008 11:58:37.0583 (UTC) FILETIME=[E28CC9F0:01C894B8] X-Brightmail-Tracker: AAAAAA== Subject: [Hipsec] Chartering work on HIP-based overlays 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org Folks, as you know, HIP has gotten a lot of attention from people building overlays (e.g., the P2PSIP WG folks). It seems that we are missing a set of specifications describing how to build HIP-based overlays. With those specifications in place, the set of people interested in HIP could grow dramatically. As we mentioned in our last face-to-face meeting, we would like to ask our area directors to charter us to do that work. In principle, we would need the following deliverables: o Framework to build HIP-based overlays. o How to generate ORCHIDs from a Peer ID defined by a peer protocol. o How to carry certificates in the base exchange. o Lightweight messages to carry upper-layer data. Additionally, we may need to work on the following items at some point: o Something related to delegation. o Use of SRTP to secure traffic. We would like to know if somebody objects to working on the deliverables above. Additionally, we would like to get feedback on the additional deliverables above. Is it something we want to work on right now, or maybe our plates will be full for now and we want to tackle those additional deliverables at a later point? Thanks, Gonzalo HIP co-chair _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@ietf.org Wed Apr 2 07:49:05 2008 Return-Path: X-Original-To: hipsec-archive@megatron.ietf.org Delivered-To: ietfarch-hipsec-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2188E28C518; Wed, 2 Apr 2008 07:49:05 -0700 (PDT) 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 3A04128C518 for ; Wed, 2 Apr 2008 07:49:04 -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 qLATw71lAEEs for ; Wed, 2 Apr 2008 07:49:03 -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 647D928C469 for ; Wed, 2 Apr 2008 07:49:03 -0700 (PDT) Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id m32Emk9X024099 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 2 Apr 2008 07:48:51 -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 m32EmkF4014389; Wed, 2 Apr 2008 07:48:46 -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 m32Emj3p014259; Wed, 2 Apr 2008 07:48:46 -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.1830); Wed, 2 Apr 2008 07:48:46 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 2 Apr 2008 07:48:45 -0700 Message-ID: <77F357662F8BFA4CA7074B0410171B6D04049DB5@XCH-NW-5V1.nw.nos.boeing.com> In-Reply-To: <47F374ED.5050403@ericsson.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Hipsec] Chartering work on HIP-based overlays Thread-Index: AciUuTVSg010OtL7SXKup7eDk/6kCQAFrF/g References: <47F374ED.5050403@ericsson.com> From: "Henderson, Thomas R" To: "Gonzalo Camarillo" , "HIP" X-OriginalArrivalTime: 02 Apr 2008 14:48:46.0053 (UTC) FILETIME=[A745B150:01C894D0] Subject: Re: [Hipsec] Chartering work on HIP-based overlays 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org > -----Original Message----- > From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com] > Sent: Wednesday, April 02, 2008 4:59 AM > To: HIP > Subject: [Hipsec] Chartering work on HIP-based overlays > > Folks, > > as you know, HIP has gotten a lot of attention from people building > overlays (e.g., the P2PSIP WG folks). It seems that we are > missing a set > of specifications describing how to build HIP-based overlays. > With those > specifications in place, the set of people interested in HIP > could grow > dramatically. As we mentioned in our last face-to-face > meeting, we would > like to ask our area directors to charter us to do that work. > > In principle, we would need the following deliverables: > > o Framework to build HIP-based overlays. > o How to generate ORCHIDs from a Peer ID defined by a peer protocol. More generally, I might replace "Peer ID" with "other node identifiers" > o How to carry certificates in the base exchange. > o Lightweight messages to carry upper-layer data. Can you provide more specifics on what you have in mind for the last bullet? Messages that occur outside of the context of a base exchange? > > Additionally, we may need to work on the following items at > some point: > > o Something related to delegation. > o Use of SRTP to secure traffic. > > We would like to know if somebody objects to working on the > deliverables > above. Additionally, we would like to get feedback on the additional > deliverables above. Is it something we want to work on right now, or > maybe our plates will be full for now and we want to tackle those > additional deliverables at a later point? +1 on adding this scope to our charter; I think it is important for HIP deployment. Tom _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@ietf.org Wed Apr 2 13:52:49 2008 Return-Path: X-Original-To: hipsec-archive@megatron.ietf.org Delivered-To: ietfarch-hipsec-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8BD6828C56F; Wed, 2 Apr 2008 13:52:49 -0700 (PDT) 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 93D6A28C565 for ; Wed, 2 Apr 2008 13:52:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.555 X-Spam-Level: X-Spam-Status: No, score=-2.555 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044] 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 Lmbe1g3Lbkaw for ; Wed, 2 Apr 2008 13:52:47 -0700 (PDT) Received: from n2.nomadiclab.com (n2.nomadiclab.com [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id 9D84028C56F for ; Wed, 2 Apr 2008 13:52:47 -0700 (PDT) Received: from n2.nomadiclab.com (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id 064741F0F1C; Wed, 2 Apr 2008 23:52:48 +0300 (EEST) Received: from [127.0.0.1] (localhost [IPv6:::1]) by n2.nomadiclab.com (Postfix) with ESMTP id AF5E31F0F1A; Wed, 2 Apr 2008 23:52:47 +0300 (EEST) In-Reply-To: <47F374ED.5050403@ericsson.com> References: <47F374ED.5050403@ericsson.com> Mime-Version: 1.0 (Apple Message framework v753) Message-Id: <2BCB4A36-BB58-43A0-B89C-70B6673508EC@nomadiclab.com> From: Pekka Nikander Date: Wed, 2 Apr 2008 18:04:06 +0200 To: Gonzalo Camarillo X-Mailer: Apple Mail (2.753) X-Virus-Scanned: ClamAV using ClamSMTP Cc: HIP Subject: Re: [Hipsec] Chartering work on HIP-based overlays 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org Gonzalo, While I generally very much agree with this direction, I think it would be useful to combine two of your proposed items into a single, more general item. Namely, I would combine > o How to generate ORCHIDs from a Peer ID defined by a peer protocol. > o Something related to delegation. into a more general draft that discusses how one can create HIs (and eventually ORCHIDs) from other identifiers, including both cryptographic ones (leading to cryptographic delegation) and non- cryptographic ones (such as Peer IDs). I don't see any fundamental architectural difference between these, and much of the needed machinery is likely to be exactly the same. What comes to the other items, I'd be more careful about the wording of a few, as follows: > o Lightweight messages to carry upper-layer data. I would generalise this to carrying any upper-layer data over specified HIP packets, including UPDATE, perhaps some new packet type, and probably also I2 and R2. R1 needs some further study, and I'm almost convinced that we do *not* want to carry any additional data on I1, but maybe there are optimisations (e.g. with TCP) that may change my mind. But perhaps the latter ones are better left of to another draft, to be completed once the basic one is (almost) ready. --Pekka > As you know, HIP has gotten a lot of attention from people building > overlays (e.g., the P2PSIP WG folks). It seems that we are missing > a set > of specifications describing how to build HIP-based overlays. With > those > specifications in place, the set of people interested in HIP could > grow > dramatically. As we mentioned in our last face-to-face meeting, we > would > like to ask our area directors to charter us to do that work. > > In principle, we would need the following deliverables: > > o Framework to build HIP-based overlays. > o How to generate ORCHIDs from a Peer ID defined by a peer protocol. > o How to carry certificates in the base exchange. > o Lightweight messages to carry upper-layer data. > > Additionally, we may need to work on the following items at some > point: > > o Something related to delegation. > o Use of SRTP to secure traffic. > > We would like to know if somebody objects to working on the > deliverables > above. Additionally, we would like to get feedback on the additional > deliverables above. Is it something we want to work on right now, or > maybe our plates will be full for now and we want to tackle those > additional deliverables at a later point? > > Thanks, > > Gonzalo > HIP co-chair _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@ietf.org Thu Apr 3 05:20:57 2008 Return-Path: X-Original-To: hipsec-archive@megatron.ietf.org Delivered-To: ietfarch-hipsec-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 61ABF28C6B2; Thu, 3 Apr 2008 05:20:57 -0700 (PDT) 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 B4E6428C6B2 for ; Thu, 3 Apr 2008 05:20:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UGowq2B92nMj for ; Thu, 3 Apr 2008 05:20:55 -0700 (PDT) Received: from mail.cs.helsinki.fi (courier.cs.helsinki.fi [128.214.9.1]) by core3.amsl.com (Postfix) with ESMTP id D3D2428C216 for ; Thu, 3 Apr 2008 05:19:58 -0700 (PDT) Received: from [128.214.113.227] (trager.pc.hiit.fi [128.214.113.227]) (AUTH: PLAIN gurtov, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by mail.cs.helsinki.fi with esmtp; Thu, 03 Apr 2008 15:20:00 +0300 id 00068122.47F4CB70.000011A0 Message-ID: <47F4CB6F.9090006@cs.helsinki.fi> Date: Thu, 03 Apr 2008 15:19:59 +0300 From: Andrei Gurtov User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Gonzalo Camarillo References: <47F374ED.5050403@ericsson.com> In-Reply-To: <47F374ED.5050403@ericsson.com> X-Enigmail-Version: 0.95.6 Cc: HIP Subject: Re: [Hipsec] Chartering work on HIP-based overlays 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I think it's very important and topical work. +1. Andrei Gonzalo Camarillo wrote: | Folks, | | as you know, HIP has gotten a lot of attention from people building | overlays (e.g., the P2PSIP WG folks). It seems that we are missing a set | of specifications describing how to build HIP-based overlays. With those | specifications in place, the set of people interested in HIP could grow | dramatically. As we mentioned in our last face-to-face meeting, we would | like to ask our area directors to charter us to do that work. | | In principle, we would need the following deliverables: | | o Framework to build HIP-based overlays. | o How to generate ORCHIDs from a Peer ID defined by a peer protocol. | o How to carry certificates in the base exchange. | o Lightweight messages to carry upper-layer data. | | Additionally, we may need to work on the following items at some point: | | o Something related to delegation. | o Use of SRTP to secure traffic. | | We would like to know if somebody objects to working on the deliverables | above. Additionally, we would like to get feedback on the additional | deliverables above. Is it something we want to work on right now, or | maybe our plates will be full for now and we want to tackle those | additional deliverables at a later point? | | Thanks, | | Gonzalo | HIP co-chair | _______________________________________________ | Hipsec mailing list | Hipsec@ietf.org | https://www.ietf.org/mailman/listinfo/hipsec -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH9MtvP7jp0uceFkQRAjz8AJ9EXH3FaROZNpbJaJy1efdwX7BWHgCgp3u1 Cd4AcG1w3jWA32dCx1ov8po= =g/0z -----END PGP SIGNATURE----- _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@ietf.org Wed Apr 16 23:39:14 2008 Return-Path: X-Original-To: hipsec-archive@megatron.ietf.org Delivered-To: ietfarch-hipsec-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0877628C518; Wed, 16 Apr 2008 23:39:14 -0700 (PDT) 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 5BF343A6DE3 for ; Mon, 14 Apr 2008 06:32: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 C0wMzgUW6Zq3 for ; Mon, 14 Apr 2008 06:32:28 -0700 (PDT) Received: from smtp-1.hut.fi (smtp-1.hut.fi [130.233.228.91]) by core3.amsl.com (Postfix) with ESMTP id 2D2333A6C90 for ; Mon, 14 Apr 2008 06:32:27 -0700 (PDT) Received: from localhost (katosiko.hut.fi [130.233.228.115]) by smtp-1.hut.fi (8.13.6/8.12.10) with ESMTP id m3EDWuNm006554 for ; Mon, 14 Apr 2008 16:32:56 +0300 Received: from smtp-1.hut.fi ([130.233.228.91]) by localhost (katosiko.hut.fi [130.233.228.115]) (amavisd-new, port 10024) with LMTP id 06539-53 for ; Mon, 14 Apr 2008 16:32:56 +0300 (EEST) Received: from kosh.hut.fi (kosh.hut.fi [130.233.228.10]) by smtp-1.hut.fi (8.13.6/8.12.10) with ESMTP id m3EDUe9N005181 for ; Mon, 14 Apr 2008 16:30:40 +0300 Date: Mon, 14 Apr 2008 16:30:40 +0300 (EEST) From: Lauri Silvennoinen To: hipsec@ietf.org Message-ID: MIME-Version: 1.0 X-TKK-Virus-Scanned: by amavisd-new-2.1.2-hutcc at katosiko.hut.fi X-Mailman-Approved-At: Wed, 16 Apr 2008 23:39:11 -0700 Subject: [Hipsec] HIP Registration Extension 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org Hi, I am implementing / improving the existing implementation of the HIP Registration Extension for InfraHIP project (HIPL). I have a few questions concerning draft-ietf-hip-registration-02: 1) How does a registrar announce that it is capable of providing multiple services with different lifetimes? In Section 3.1 it is said that "a registrar SHOULD include a REG_INFO parameter in the R1 packets it sends during all base exchanges." The REG_INFO parameter, however, is of the following form: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Min Lifetime | Max Lifetime | Reg Type #1 | Reg Type #2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... | ... | Reg Type #n | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Padding + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ I.e. it has single "Min Lifetime" and "Max Lifetime" values. The issue would be solved if the registrar could include multiple REG_INFO parameters in the R1 packets, but nothing is said about multiple REG_INFOs in the draft. 2) How to handle REG_REQUEST, REG_RESPONSE and REG_FAILED parameters that have redundant services? These parameters are of the following form: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Lifetime | Reg Type #1 | Reg Type #2 | Reg Type #3 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... | ... | Reg Type #n | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Padding + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Now, what happens if, say, both "Reg Type #1" and "Reg Type #2" are of type RVS? Not that it would make any sense to build such parameters, but the hosts should be ready to handle such parameters. 3) What happens if registration cancellation does not succeed? In Section 5 it is said: "A zero lifetime is reserved for canceling purposes. Requesting a zero lifetime for a registration type equals to canceling the registration of that type. A requester MAY cancel a registration before it expires by sending a REG_REQ to the registrar with a zero lifetime. A registrar SHOULD respond and grant a registration with a zero lifetime. A registrar (and an attached service) MAY cancel a registration before it expires, at its own discretion. However, if it does so, it SHOULD send a REG_RESPONSE with a zero lifetime to all registered requesters." Thus if the requester wants to cancel a service it sends a REG_REQUEST parameter with zero lifetime to which the registrar should answer with a REG_RESPONSE with zero lifetime respectively. But what happens if the registrar is unable to cancel the registration due to transient conditions or some other reason? Does the registrar just remain silent or send a REG_FAILED? Thanks, Lauri _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@ietf.org Fri Apr 18 16:03:15 2008 Return-Path: X-Original-To: hipsec-archive@megatron.ietf.org Delivered-To: ietfarch-hipsec-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 91ECC28C1AC; Fri, 18 Apr 2008 16:03:15 -0700 (PDT) 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 CBCF03A6966; Fri, 18 Apr 2008 16:03:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.599 X-Spam-Level: X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15] 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 f9KD3b38PkGi; Fri, 18 Apr 2008 16:03:12 -0700 (PDT) Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id E6A0E3A6804; Fri, 18 Apr 2008 16:03:11 -0700 (PDT) Received: by bosco.isi.edu (Postfix, from userid 70) id A39A8124F65; Fri, 18 Apr 2008 16:03:14 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20080418230314.A39A8124F65@bosco.isi.edu> Date: Fri, 18 Apr 2008 16:03:14 -0700 (PDT) Cc: hipsec@ietf.org, rfc-editor@rfc-editor.org Subject: [Hipsec] RFC 5201 on Host Identity Protocol 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: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 5201 Title: Host Identity Protocol Author: R. Moskowitz, P. Nikander, P. Jokela, Ed., T. Henderson Status: Experimental Date: April 2008 Mailbox: rgm@icsalabs.com, pekka.nikander@nomadiclab.com, petri.jokela@nomadiclab.com, thomas.r.henderson@boeing.com Pages: 104 Characters: 240492 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-hip-base-10.txt URL: http://www.rfc-editor.org/rfc/rfc5201.txt This memo specifies the details of the Host Identity Protocol (HIP). HIP allows consenting hosts to securely establish and maintain shared IP-layer state, allowing separation of the identifier and locator roles of IP addresses, thereby enabling continuity of communications across IP address changes. HIP is based on a Sigma-compliant Diffie- Hellman key exchange, using public key identifiers from a new Host Identity namespace for mutual peer authentication. The protocol is designed to be resistant to denial-of-service (DoS) and man-in-the- middle (MitM) attacks. When used together with another suitable security protocol, such as the Encapsulated Security Payload (ESP), it provides integrity protection and optional encryption for upper- layer protocols, such as TCP and UDP. This memo defines an Experimental Protocol for the Internet community. This document is a product of the Host Identity Protocol Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@ietf.org Fri Apr 18 16:03:30 2008 Return-Path: X-Original-To: hipsec-archive@megatron.ietf.org Delivered-To: ietfarch-hipsec-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C021128C174; Fri, 18 Apr 2008 16:03:30 -0700 (PDT) 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 B605A3A6B23; Fri, 18 Apr 2008 16:03:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.599 X-Spam-Level: X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15] 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 A2HvmjvV8oCT; Fri, 18 Apr 2008 16:03:28 -0700 (PDT) Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 8FA473A6AC6; Fri, 18 Apr 2008 16:03:28 -0700 (PDT) Received: by bosco.isi.edu (Postfix, from userid 70) id B2840124F67; Fri, 18 Apr 2008 16:03:28 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20080418230328.B2840124F67@bosco.isi.edu> Date: Fri, 18 Apr 2008 16:03:28 -0700 (PDT) Cc: hipsec@ietf.org, rfc-editor@rfc-editor.org Subject: [Hipsec] RFC 5202 on Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP) 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: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 5202 Title: Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP) Author: P. Jokela, R. Moskowitz, P. Nikander Status: Experimental Date: April 2008 Mailbox: petri.jokela@nomadiclab.com, rgm@icsalabs.com, pekka.nikander@nomadiclab.com Pages: 30 Characters: 68195 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-hip-esp-06.txt URL: http://www.rfc-editor.org/rfc/rfc5202.txt This memo specifies an Encapsulated Security Payload (ESP) based mechanism for transmission of user data packets, to be used with the Host Identity Protocol (HIP). This memo defines an Experimental Protocol for the Internet community. This document is a product of the Host Identity Protocol Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@ietf.org Fri Apr 18 16:03:39 2008 Return-Path: X-Original-To: hipsec-archive@megatron.ietf.org Delivered-To: ietfarch-hipsec-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ACC2828C20C; Fri, 18 Apr 2008 16:03:39 -0700 (PDT) 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 7289D28C1CD; Fri, 18 Apr 2008 16:03:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.599 X-Spam-Level: X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15] 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 yBia2UHhSaIr; Fri, 18 Apr 2008 16:03:37 -0700 (PDT) Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 04AF228C20C; Fri, 18 Apr 2008 16:03:35 -0700 (PDT) Received: by bosco.isi.edu (Postfix, from userid 70) id B5FB0124F69; Fri, 18 Apr 2008 16:03:37 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20080418230337.B5FB0124F69@bosco.isi.edu> Date: Fri, 18 Apr 2008 16:03:37 -0700 (PDT) Cc: hipsec@ietf.org, rfc-editor@rfc-editor.org Subject: [Hipsec] RFC 5203 on Host Identity Protocol (HIP) Registration Extension 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: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 5203 Title: Host Identity Protocol (HIP) Registration Extension Author: J. Laganier, T. Koponen, L. Eggert Status: Experimental Date: April 2008 Mailbox: julien.ietf@laposte.net, teemu.koponen@iki.fi, lars.eggert@nokia.com Pages: 13 Characters: 26620 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-hip-registration-02.txt URL: http://www.rfc-editor.org/rfc/rfc5203.txt This document specifies a registration mechanism for the Host Identity Protocol (HIP) that allows hosts to register with services, such as HIP rendezvous servers or middleboxes. This memo defines an Experimental Protocol for the Internet community. This document is a product of the Host Identity Protocol Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@ietf.org Fri Apr 18 16:03:44 2008 Return-Path: X-Original-To: hipsec-archive@megatron.ietf.org Delivered-To: ietfarch-hipsec-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5F08D28C28C; Fri, 18 Apr 2008 16:03:44 -0700 (PDT) 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 E6A8E28C28F; Fri, 18 Apr 2008 16:03:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.599 X-Spam-Level: X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15] 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 YWu74tGqqZAi; Fri, 18 Apr 2008 16:03:42 -0700 (PDT) Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 77D0128C28C; Fri, 18 Apr 2008 16:03:41 -0700 (PDT) Received: by bosco.isi.edu (Postfix, from userid 70) id 0E15E124F6B; Fri, 18 Apr 2008 16:03:44 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20080418230344.0E15E124F6B@bosco.isi.edu> Date: Fri, 18 Apr 2008 16:03:44 -0700 (PDT) Cc: hipsec@ietf.org, rfc-editor@rfc-editor.org Subject: [Hipsec] RFC 5204 on Host Identity Protocol (HIP) Rendezvous Extension 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: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 5204 Title: Host Identity Protocol (HIP) Rendezvous Extension Author: J. Laganier, L. Eggert Status: Experimental Date: April 2008 Mailbox: julien.ietf@laposte.net, lars.eggert@nokia.com Pages: 15 Characters: 30233 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-hip-rvs-05.txt URL: http://www.rfc-editor.org/rfc/rfc5204.txt This document defines a rendezvous extension for the Host Identity Protocol (HIP). The rendezvous extension extends HIP and the HIP registration extension for initiating communication between HIP nodes via HIP rendezvous servers. Rendezvous servers improve reachability and operation when HIP nodes are multi-homed or mobile. This memo defines an Experimental Protocol for the Internet community. This document is a product of the Host Identity Protocol Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@ietf.org Fri Apr 18 16:03:50 2008 Return-Path: X-Original-To: hipsec-archive@megatron.ietf.org Delivered-To: ietfarch-hipsec-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2666C28C2BD; Fri, 18 Apr 2008 16:03:50 -0700 (PDT) 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 E106328C2A3; Fri, 18 Apr 2008 16:03:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.599 X-Spam-Level: X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15] 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 lpo5F6kF5Qru; Fri, 18 Apr 2008 16:03:48 -0700 (PDT) Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 009BF28C2C4; Fri, 18 Apr 2008 16:03:47 -0700 (PDT) Received: by bosco.isi.edu (Postfix, from userid 70) id B18C7124F6D; Fri, 18 Apr 2008 16:03:49 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20080418230349.B18C7124F6D@bosco.isi.edu> Date: Fri, 18 Apr 2008 16:03:49 -0700 (PDT) Cc: hipsec@ietf.org, rfc-editor@rfc-editor.org Subject: [Hipsec] RFC 5205 on Host Identity Protocol (HIP) Domain Name System (DNS) Extensions 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: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 5205 Title: Host Identity Protocol (HIP) Domain Name System (DNS) Extensions Author: P. Nikander, J. Laganier Status: Experimental Date: April 2008 Mailbox: pekka.nikander@nomadiclab.com, julien.ietf@laposte.net Pages: 17 Characters: 34799 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-hip-dns-09.txt URL: http://www.rfc-editor.org/rfc/rfc5205.txt This document specifies a new resource record (RR) for the Domain Name System (DNS), and how to use it with the Host Identity Protocol (HIP). This RR allows a HIP node to store in the DNS its Host Identity (HI, the public component of the node public-private key pair), Host Identity Tag (HIT, a truncated hash of its public key), and the Domain Names of its rendezvous servers (RVSs). This memo defines an Experimental Protocol for the Internet community. This document is a product of the Host Identity Protocol Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@ietf.org Fri Apr 18 16:04:05 2008 Return-Path: X-Original-To: hipsec-archive@megatron.ietf.org Delivered-To: ietfarch-hipsec-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DAF6328C2DD; Fri, 18 Apr 2008 16:04:05 -0700 (PDT) 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 2356F3A6932; Fri, 18 Apr 2008 16:04:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.599 X-Spam-Level: X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15] 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 YVwSMOwY2tRg; Fri, 18 Apr 2008 16:03:57 -0700 (PDT) Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 2F5903A6929; Fri, 18 Apr 2008 16:03:54 -0700 (PDT) Received: by bosco.isi.edu (Postfix, from userid 70) id E069B124F6F; Fri, 18 Apr 2008 16:03:56 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20080418230356.E069B124F6F@bosco.isi.edu> Date: Fri, 18 Apr 2008 16:03:56 -0700 (PDT) Cc: hipsec@ietf.org, rfc-editor@rfc-editor.org Subject: [Hipsec] RFC 5206 on End-Host Mobility and Multihoming with the Host Identity Protocol 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: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 5206 Title: End-Host Mobility and Multihoming with the Host Identity Protocol Author: P. Nikander, T. Henderson, Ed., C. Vogt, J. Arkko Status: Experimental Date: April 2008 Mailbox: pekka.nikander@nomadiclab.com, thomas.r.henderson@boeing.com, christian.vogt@ericsson.com, jari.arkko@ericsson.com Pages: 40 Characters: 99430 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-hip-mm-05.txt URL: http://www.rfc-editor.org/rfc/rfc5206.txt This document defines mobility and multihoming extensions to the Host Identity Protocol (HIP). Specifically, this document defines a general "LOCATOR" parameter for HIP messages that allows for a HIP host to notify peers about alternate addresses at which it may be reached. This document also defines elements of procedure for mobility of a HIP host -- the process by which a host dynamically changes the primary locator that it uses to receive packets. While the same LOCATOR parameter can also be used to support end-host multihoming, detailed procedures are left for further study. This memo defines an Experimental Protocol for the Internet community. This document is a product of the Host Identity Protocol Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@ietf.org Thu Apr 24 03:27:14 2008 Return-Path: X-Original-To: hipsec-archive@megatron.ietf.org Delivered-To: ietfarch-hipsec-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A8FE3A6A5D; Thu, 24 Apr 2008 03:27:14 -0700 (PDT) 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 D6D2F3A6A5D for ; Thu, 24 Apr 2008 03:27:13 -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 mgILRCyQ7izg for ; Thu, 24 Apr 2008 03:27:10 -0700 (PDT) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id ED8923A68DF for ; Thu, 24 Apr 2008 03:27:09 -0700 (PDT) Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 18C4220970; Thu, 24 Apr 2008 12:27:14 +0200 (CEST) X-AuditID: c1b4fb3c-ae89cbb00000193b-1b-48106082555d Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 0977F206AA; Thu, 24 Apr 2008 12:27:14 +0200 (CEST) Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 24 Apr 2008 12:27:14 +0200 Received: from [153.88.12.211] ([153.88.12.211]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 24 Apr 2008 12:27:13 +0200 Message-ID: <4810607E.2070409@ericsson.com> Date: Thu, 24 Apr 2008 13:27:10 +0300 From: Gonzalo Camarillo User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: HIP X-OriginalArrivalTime: 24 Apr 2008 10:27:13.0986 (UTC) FILETIME=[C328CA20:01C8A5F5] X-Brightmail-Tracker: AAAAAA== Subject: [Hipsec] Six RFCs published 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org Hi, as you can see from the RFC Editor's notes, we have just published six new RFCs (RFC5201 through 5206). This is an important milestone for the working group! It took a while, but we finally got there. At this point, the chairs will work with the ADs to update our charter so that it reflects the current status of HIP and includes work on HIP-based overlays per our discussions on the list. We will keep the list updated. Also, we will update the target dates for our current charter items, which have been somewhat delayed for a number of reasons. Cheers, Gonzalo _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec