From nobody Tue Jan 19 06:19:57 2016 Return-Path: X-Original-To: hipsec@ietf.org Delivered-To: hipsec@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B4C2E1B2F4C; Tue, 19 Jan 2016 06:19:55 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.12.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160119141955.27478.94834.idtracker@ietfa.amsl.com> Date: Tue, 19 Jan 2016 06:19:55 -0800 Archived-At: Cc: hipsec@ietf.org Subject: [Hipsec] I-D Action: draft-ietf-hip-native-nat-traversal-10.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.15 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, 19 Jan 2016 14:19:55 -0000 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 : Native NAT Traversal Mode for the Host Identity Protocol Authors : Ari Keranen Jan Melen Filename : draft-ietf-hip-native-nat-traversal-10.txt Pages : 13 Date : 2016-01-19 Abstract: This document specifies a new Network Address Translator (NAT) traversal mode for the Host Identity Protocol (HIP). The new mode is based on the Interactive Connectivity Establishment (ICE) methodology and UDP encapsulation of data and signaling traffic. The main difference from the previously specified modes is the use of HIP messages for all NAT traversal procedures. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-hip-native-nat-traversal/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-hip-native-nat-traversal-10 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-hip-native-nat-traversal-10 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Jan 19 06:25:36 2016 Return-Path: X-Original-To: hipsec@ietfa.amsl.com Delivered-To: hipsec@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD70F1B2F6A for ; Tue, 19 Jan 2016 06:25:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.9 X-Spam-Level: X-Spam-Status: No, score=-3.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LgOVuniYRRqY for ; Tue, 19 Jan 2016 06:25:33 -0800 (PST) Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAC541B2F41 for ; Tue, 19 Jan 2016 06:25:32 -0800 (PST) X-AuditID: c1b4fb25-f797e6d000007600-4c-569e475a74bf Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.183.51]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 89.8D.30208.A574E965; Tue, 19 Jan 2016 15:25:30 +0100 (CET) Received: from m46.nomadiclab.com (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.53) with Microsoft SMTP Server id 14.3.248.2; Tue, 19 Jan 2016 15:25:30 +0100 To: References: <20160119141955.27478.94834.idtracker@ietfa.amsl.com> From: =?UTF-8?Q?Ari_Ker=c3=a4nen?= Message-ID: <569E4759.2030108@ericsson.com> Date: Tue, 19 Jan 2016 16:25:29 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <20160119141955.27478.94834.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKLMWRmVeSWpSXmKPExsUyM2K7sW6U+7wwgwl/zS2mLprM7MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujPUNO5kLbvNX3D69k7GBcRZPFyMnh4SAicSE52vZIWwxiQv3 1rN1MXJxCAkcZpT4OGcjlLOOUeLMj5esIFXCAj4Sz9qXMILYIgKiElM+nGYGsYUEHCX6F60C s5kFzCRO3z8OZrMJ2Er8bt/DBGLzCmhLLH51nA3EZhFQleh9f5cFxBYVSJPof3GfGaJGUOLk zCdgcU4BJ4m1PVeBruMAmmkv8WBrGcR4eYntb+dArVWVuPrvFeMERsFZSLpnIXTMQtKxgJF5 FaNocWpxUm66kbFealFmcnFxfp5eXmrJJkZgYB7c8lt1B+PlN46HGAU4GJV4eAvy5oYJsSaW FVfmHmKU4GBWEuG1cZkXJsSbklhZlVqUH19UmpNafIhRmoNFSZw3SaYxTEggPbEkNTs1tSC1 CCbLxMEp1cAYXrXu2Im+PW7Bv2Lfi0dfmX0s+qGzkdCerxHsin0852+xFYgvDIyZe/XP16fx oqmG/0z3qP5bw7gu+Nu/aT738swWi5VNXKdhe8aQx642XSY2fk4De1JNSYxaJIfSwklznnJd +RY0fdVTzYiEhoWrFtvfPh4fcjI03q/Sln2e+6+rWvktzqJKLMUZiYZazEXFiQDtjp1KSAIA AA== Archived-At: Subject: Re: [Hipsec] I-D Action: draft-ietf-hip-native-nat-traversal-10.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.15 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, 19 Jan 2016 14:25:34 -0000 Hi, This update clarifies that also the controlled host needs to nominate a candidate pair with ESP packet and removes the "roughly" part from the relay permission refresh. With this, the authors think the draft is ready for WGLC. Cheers, Ari On 19/01/16 16:19, 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 : Native NAT Traversal Mode for the Host Identity Protocol > Authors : Ari Keranen > Jan Melen > Filename : draft-ietf-hip-native-nat-traversal-10.txt > Pages : 13 > Date : 2016-01-19 > > Abstract: > This document specifies a new Network Address Translator (NAT) > traversal mode for the Host Identity Protocol (HIP). The new mode is > based on the Interactive Connectivity Establishment (ICE) methodology > and UDP encapsulation of data and signaling traffic. The main > difference from the previously specified modes is the use of HIP > messages for all NAT traversal procedures. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-hip-native-nat-traversal/ > > There's also a htmlized version available at: > https://tools.ietf.org/html/draft-ietf-hip-native-nat-traversal-10 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-hip-native-nat-traversal-10 > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > Hipsec mailing list > Hipsec@ietf.org > https://www.ietf.org/mailman/listinfo/hipsec > From nobody Wed Jan 20 06:00:04 2016 Return-Path: X-Original-To: hipsec@ietfa.amsl.com Delivered-To: hipsec@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83BFF1A8942 for ; Wed, 20 Jan 2016 06:00:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.502 X-Spam-Level: X-Spam-Status: No, score=-1.502 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id loFWPInOYDvX for ; Wed, 20 Jan 2016 06:00:00 -0800 (PST) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [50.253.254.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E0111A8932 for ; Wed, 20 Jan 2016 06:00:00 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 82C7260945 for ; Wed, 20 Jan 2016 08:59:59 -0500 (EST) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id WqZucGS9CdGj for ; Wed, 20 Jan 2016 08:59:53 -0500 (EST) Received: from lx120e.htt-consult.com (50-205-36-242-static.hfc.comcastbusiness.net [50.205.36.242]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 97CDE60944 for ; Wed, 20 Jan 2016 08:59:53 -0500 (EST) To: hipsec@ietf.org From: Robert Moskowitz Message-ID: <569F92D7.1070806@htt-consult.com> Date: Wed, 20 Jan 2016 08:59:51 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: [Hipsec] Status of HIP DEX X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.15 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, 20 Jan 2016 14:00:03 -0000 Although draft-moskowitz-hip-dex-04 expired yesterday, I have been active with it as follows: IEEE 802.15.9 references both HIP BEX and DEX. This Recommended Standard will be starting IEEE Sponsor Ballot recirculation #2 Jan 21 on a 10 day voting cycle. We anticipate our one NO voter to switch to YES (as he contributed to the editorial changes and said they satisfied his concerns) and no new NO votes. That is it is done balloting. It is tightly timed, but this will get it on RevCom Feb 2 to be approved for publication. But,,, No Internet Drafts in an IEEE document. So HIP DEX would hold up the publication. For those not familiar with DEX, it is a reduction on BEXv2 and the text is closely aligned, thanks to Rene's editing. I plan on reving DEX-04 as DEX-05 as soon as possible. Like this week still. The question is where does this go to be moved forward. ISE submission is not good, as then it could only be Informational or Experimental. So either this workgroup does a last call and moves it forward, or I go the AD submission route. I have been discussing this with Stephen Farrell as Security AD, and regardless, he would be reviewing it. The question is what route to IESG. This wg, this wg AD, or security AD? Please help me out here. HIP DEX is also referenced in: draft-ohba-6lo-mle-hip-dex-01.txt as used by Zigbee and a further reduction of DEX (because even it was too many bytes over the air) is in a product I cannot name. I look forward to your assistance. On a personal note: I am being funded by Huawei to work on DOTS/I2NSF/MILE/SACM. Look for a number of IDs coming from me (or my joining others) in those areas. Look for HIP being referenced in a place or two. Along with SSE. I plan on attending the next IETF, but will not be arriving until Mon noon. My youngest son is engaged and the wedding is the week prior and thus I cannot split for IETF until Sunday. I am working on another contract that I soon hope to share with you here. From nobody Wed Jan 20 07:18:27 2016 Return-Path: X-Original-To: hipsec@ietfa.amsl.com Delivered-To: hipsec@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18A271A8AC0 for ; Wed, 20 Jan 2016 07:18:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.802 X-Spam-Level: X-Spam-Status: No, score=-2.802 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2gVI_o1fRiRt for ; Wed, 20 Jan 2016 07:18:23 -0800 (PST) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [50.253.254.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B58671A8AB8 for ; Wed, 20 Jan 2016 07:18:23 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 72F7460D1B for ; Wed, 20 Jan 2016 10:18:22 -0500 (EST) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 9iboeS+WeMdc for ; Wed, 20 Jan 2016 10:18:19 -0500 (EST) Received: from lx120e.htt-consult.com (50-205-36-242-static.hfc.comcastbusiness.net [50.205.36.242]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 9308D60971 for ; Wed, 20 Jan 2016 10:18:18 -0500 (EST) To: hipsec@ietf.org References: <569F92D7.1070806@htt-consult.com> From: Robert Moskowitz Message-ID: <569FA538.3010106@htt-consult.com> Date: Wed, 20 Jan 2016 10:18:16 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <569F92D7.1070806@htt-consult.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Hipsec] Status of HIP DEX X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.15 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, 20 Jan 2016 15:18:26 -0000 I just posted ver 05. I only reved the dates. I am seriously considering adding Curve25519 as it 'works' much better in constrained systems than p256. But I would need a published reference for it. On 01/20/2016 08:59 AM, Robert Moskowitz wrote: > Although draft-moskowitz-hip-dex-04 expired yesterday, I have been > active with it as follows: > > IEEE 802.15.9 references both HIP BEX and DEX. This Recommended > Standard will be starting IEEE Sponsor Ballot recirculation #2 Jan 21 > on a 10 day voting cycle. We anticipate our one NO voter to switch to > YES (as he contributed to the editorial changes and said they > satisfied his concerns) and no new NO votes. That is it is done > balloting. It is tightly timed, but this will get it on RevCom Feb 2 > to be approved for publication. But,,, > > No Internet Drafts in an IEEE document. So HIP DEX would hold up the > publication. > > For those not familiar with DEX, it is a reduction on BEXv2 and the > text is closely aligned, thanks to Rene's editing. > > I plan on reving DEX-04 as DEX-05 as soon as possible. Like this week > still. The question is where does this go to be moved forward. ISE > submission is not good, as then it could only be Informational or > Experimental. So either this workgroup does a last call and moves it > forward, or I go the AD submission route. I have been discussing this > with Stephen Farrell as Security AD, and regardless, he would be > reviewing it. The question is what route to IESG. This wg, this wg > AD, or security AD? > > Please help me out here. > > HIP DEX is also referenced in: > > draft-ohba-6lo-mle-hip-dex-01.txt > > as used by Zigbee and a further reduction of DEX (because even it was > too many bytes over the air) is in a product I cannot name. > > I look forward to your assistance. > > On a personal note: > > I am being funded by Huawei to work on DOTS/I2NSF/MILE/SACM. Look for > a number of IDs coming from me (or my joining others) in those areas. > Look for HIP being referenced in a place or two. Along with SSE. I > plan on attending the next IETF, but will not be arriving until Mon > noon. My youngest son is engaged and the wedding is the week prior > and thus I cannot split for IETF until Sunday. > > I am working on another contract that I soon hope to share with you here. > > _______________________________________________ > Hipsec mailing list > Hipsec@ietf.org > https://www.ietf.org/mailman/listinfo/hipsec > From nobody Sat Jan 23 16:48:30 2016 Return-Path: X-Original-To: hipsec@ietf.org Delivered-To: hipsec@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C1F61B2CE3; Sat, 23 Jan 2016 16:48:27 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.13.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160124004827.12718.4101.idtracker@ietfa.amsl.com> Date: Sat, 23 Jan 2016 16:48:27 -0800 Archived-At: Cc: hipsec@ietf.org Subject: [Hipsec] I-D Action: draft-ietf-hip-rfc5206-bis-10.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.15 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: Sun, 24 Jan 2016 00:48:27 -0000 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 : Host Mobility with the Host Identity Protocol Authors : Thomas R. Henderson Christian Vogt Jari Arkko Filename : draft-ietf-hip-rfc5206-bis-10.txt Pages : 33 Date : 2016-01-23 Abstract: This document defines mobility extensions to the Host Identity Protocol (HIP). Specifically, this document defines a general "LOCATOR_SET" 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_SET parameter can also be used to support end-host multihoming, detailed procedures are out of scope for this document. This document obsoletes RFC 5206. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-hip-rfc5206-bis/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-hip-rfc5206-bis-10 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-hip-rfc5206-bis-10 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Mon Jan 25 12:05:35 2016 Return-Path: X-Original-To: hipsec@ietfa.amsl.com Delivered-To: hipsec@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 371981A00CA for ; Mon, 25 Jan 2016 12:05:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.502 X-Spam-Level: X-Spam-Status: No, score=-1.502 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AP1ry1E8kQyF for ; Mon, 25 Jan 2016 12:05:31 -0800 (PST) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [50.253.254.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E92D51A00A4 for ; Mon, 25 Jan 2016 12:05:30 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id D80856218A for ; Mon, 25 Jan 2016 15:05:28 -0500 (EST) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id oSBeArsepHyK for ; Mon, 25 Jan 2016 15:05:22 -0500 (EST) Received: from lx120e.htt-consult.com (unknown [192.168.160.20]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id A026B62183 for ; Mon, 25 Jan 2016 15:05:21 -0500 (EST) To: hipsec@ietf.org From: Robert Moskowitz Message-ID: <56A67FFE.30502@htt-consult.com> Date: Mon, 25 Jan 2016 15:05:18 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: [Hipsec] HIP and Curve25519 - RFC 7748 X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.15 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, 25 Jan 2016 20:05:33 -0000 We have an RFC now for Curve25519 and it behooves us to start looking at it and what it means to HIP. I definitely need to look at it for DEX as I don't have to wait for Ed25519 which is moving along as well. I believe an important part that impacts HIP in RFC 7748 is: Designers using these curves should be aware that for each public key, there are several publicly computable public keys that are equivalent to it, i.e., they produce the same shared secrets. Thus using a public key as an identifier and knowledge of a shared secret as proof of ownership (without including the public keys in the key derivation) might lead to subtle vulnerabilities. Ouch! That is us, I believe. So this points to KEYMAT changes. If you look elsewhere in 7748 you see in 6.1: Both now share K = X25519(a, X25519(b, 9)) = X25519(b, X25519(a, 9)) as a shared secret. Both MAY check, without leaking extra information about the value of K, whether K is the all-zero value and abort if so (see below). Alice and Bob can then use a key-derivation function that includes K, K_A, and K_B to derive a symmetric key. So this is a bit different requirement for KEYMAT. Again, it definitely impacts DEX, but also BEX. I believe. One item not mentioned that is very important in DEX is ephemeral vs static key usage. What concerns are there with static key usage? Any comments on working to include this curve work? Also be on the watch for BLAKE2 as the hash to use over SHA256. From nobody Fri Jan 29 04:33:05 2016 Return-Path: X-Original-To: hipsec@ietfa.amsl.com Delivered-To: hipsec@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6060E1A8824 for ; Fri, 29 Jan 2016 04:33:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.2 X-Spam-Level: X-Spam-Status: No, score=-104.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DYqMgSa9ez0Z for ; Fri, 29 Jan 2016 04:33:03 -0800 (PST) Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6BD21A8775 for ; Fri, 29 Jan 2016 04:33:02 -0800 (PST) X-AuditID: c1b4fb2d-f78fe6d00000163a-d6-56ab5bfc7c6d Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id D5.12.05690.CFB5BA65; Fri, 29 Jan 2016 13:33:00 +0100 (CET) Received: from [148.135.149.101] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.68) with Microsoft SMTP Server id 14.3.248.2; Fri, 29 Jan 2016 13:32:13 +0100 From: Gonzalo Camarillo To: HIP Message-ID: <56AB5BCD.7060803@ericsson.com> Date: Fri, 29 Jan 2016 14:32:13 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprILMWRmVeSWpSXmKPExsUyM2K7k+6f6NVhBv/WmVhMXTSZ2YHRY8mS n0wBjFFcNimpOZllqUX6dglcGV2T2pgL3jFWTNn+grGB8QBjFyMnh4SAiURbN4wtJnHh3no2 EFtI4DCjRMNtbwh7LaNE33mwOJuAhcSWW/dZQGxhASOJWb/6weIiApISPXeXgsV5BbQlDs5f BzaTRUBVou3mQTBbVCBGYtvyxUwQNYISJ2c+AatnFjCQOLJoDiuELS+x/e0cZoi92hLLn7Ww TGDkm4WkZRaSlllIWhYwMq9iFC1OLS7OTTcy1kstykwuLs7P08tLLdnECAyog1t+6+5gXP3a 8RCjAAejEg9vwdxVYUKsiWXFlbmHGCU4mJVEeOu0VocJ8aYkVlalFuXHF5XmpBYfYpTmYFES 5z3IvyhMSCA9sSQ1OzW1ILUIJsvEwSnVwOh50vr8EvYc/ltKpyqsjK+96fPcc0dt5/3rF7t+ cvs8OKfw7tLGMKFFwr3LGlsCD7pczUjrzVT0FNvNvPih2z7FlM+Lt2mm2XI7cDjc5pR8/K6w dmKYgPlmwRiX1gPL+VVUJn+q8L1Va3jv1ooUFYPt+6acOTo74U1b8VZpN7fCm0Welxo3n1Vi Kc5INNRiLipOBADkOJSUJAIAAA== Archived-At: Subject: [Hipsec] WGLC: draft-ietf-hip-native-nat-traversal X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.15 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, 29 Jan 2016 12:33:04 -0000 Hi, I would like to start a WGLC on the following draft. This WGLC will end on February 12th: https://datatracker.ietf.org/doc/draft-ietf-hip-native-nat-traversal/ Please, send your comments to this list. Thanks, Gonzalo From nobody Sun Jan 31 12:25:24 2016 Return-Path: X-Original-To: hipsec@ietf.org Delivered-To: hipsec@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 56CF21B2CB0; Sun, 31 Jan 2016 12:25:21 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.13.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160131202521.13396.7824.idtracker@ietfa.amsl.com> Date: Sun, 31 Jan 2016 12:25:21 -0800 Archived-At: Cc: hipsec@ietf.org Subject: [Hipsec] I-D Action: draft-ietf-hip-rfc5203-bis-10.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.15 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: Sun, 31 Jan 2016 20:25:21 -0000 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 : Host Identity Protocol (HIP) Registration Extension Authors : Julien Laganier Lars Eggert Filename : draft-ietf-hip-rfc5203-bis-10.txt Pages : 15 Date : 2016-01-31 Abstract: 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 document obsoletes RFC5203. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-hip-rfc5203-bis/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-hip-rfc5203-bis-10 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-hip-rfc5203-bis-10 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Sun Jan 31 17:24:51 2016 Return-Path: X-Original-To: hipsec@ietf.org Delivered-To: hipsec@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B9B91A8787; Sun, 31 Jan 2016 17:24:50 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.13.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160201012450.29966.46628.idtracker@ietfa.amsl.com> Date: Sun, 31 Jan 2016 17:24:50 -0800 Archived-At: Cc: hipsec@ietf.org Subject: [Hipsec] I-D Action: draft-ietf-hip-rfc5205-bis-09.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.15 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, 01 Feb 2016 01:24:50 -0000 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 : Host Identity Protocol (HIP) Domain Name System (DNS) Extension Author : Julien Laganier Filename : draft-ietf-hip-rfc5205-bis-09.txt Pages : 17 Date : 2016-01-31 Abstract: 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 document obsoletes RFC5205. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-hip-rfc5205-bis/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-hip-rfc5205-bis-09 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-hip-rfc5205-bis-09 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Sun Jan 31 21:11:17 2016 Return-Path: X-Original-To: hipsec@ietf.org Delivered-To: hipsec@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A9B51AC44B; Sun, 31 Jan 2016 21:11:16 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.13.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160201051116.29360.97550.idtracker@ietfa.amsl.com> Date: Sun, 31 Jan 2016 21:11:16 -0800 Archived-At: Cc: hipsec@ietf.org Subject: [Hipsec] I-D Action: draft-ietf-hip-multihoming-07.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.15 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, 01 Feb 2016 05:11:16 -0000 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 : Host Multihoming with the Host Identity Protocol Authors : Thomas R. Henderson Christian Vogt Jari Arkko Filename : draft-ietf-hip-multihoming-07.txt Pages : 20 Date : 2016-01-31 Abstract: This document defines host multihoming extensions to the Host Identity Protocol (HIP), by leveraging protocol components defined for host mobility. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-hip-multihoming/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-hip-multihoming-07 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-hip-multihoming-07 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Sun Jan 31 21:59:50 2016 Return-Path: X-Original-To: hipsec@ietfa.amsl.com Delivered-To: hipsec@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 660241ACDD0 for ; Sun, 31 Jan 2016 21:59:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.301 X-Spam-Level: X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LpJ7Mn-p1JIG for ; Sun, 31 Jan 2016 21:59:47 -0800 (PST) Received: from mxout25.s.uw.edu (mxout25.s.uw.edu [140.142.234.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 095541ACDCF for ; Sun, 31 Jan 2016 21:59:46 -0800 (PST) Received: from hymn02.u.washington.edu (hymn02.u.washington.edu [140.142.8.71]) by mxout25.s.uw.edu (8.14.4+UW14.03/8.14.4+UW15.02) with ESMTP id u115xDSL026366 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 31 Jan 2016 21:59:13 -0800 Received: from hymn02.u.washington.edu (localhost [127.0.0.1]) by hymn02.u.washington.edu (8.14.4+UW14.03/8.14.4+UW14.04) with ESMTP id u115xBME027209; Sun, 31 Jan 2016 21:59:11 -0800 Received: from localhost (Unknown UID 17750@localhost) by hymn02.u.washington.edu (8.14.4+UW14.03/8.14.4+Submit-local) with ESMTP id u115xBPc027203; Sun, 31 Jan 2016 21:59:11 -0800 X-Auth-Received: from [73.239.169.224] by hymn02.u.washington.edu via HTTP; Sun, 31 Jan 2016 21:59:11 PST Date: Sun, 31 Jan 2016 21:59:11 -0800 (PST) From: Tom Henderson To: Gonzalo Camarillo Message-ID: User-Agent: Web Alpine 2.01 (LRH 1302 2010-07-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8BIT X-PMX-Version: 6.2.1.2493963, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.2.1.55416 X-PMX-Server: mxout25.s.uw.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report=' HTML_00_01 0.05, HTML_00_10 0.05, SUPERLONG_LINE 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1700_1799 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, DATE_TZ_NA 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG 0, __HAS_FROM 0, __HAS_MSGID 0, __HTTPS_URI 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MULTIPLE_URI_TEXT 0, __SANE_MSGID 0, __SUBJ_ALPHA_END 0, __SUBJ_ALPHA_NEGATE 0, __TO_MALFORMED_2 0, __URI_IN_BODY 0, __URI_NO_MAILTO 0, __URI_NS , __USER_AGENT 0' Archived-At: Cc: HIP Subject: Re: [Hipsec] Status of our next batch X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.15 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, 01 Feb 2016 05:59:48 -0000 On 11/17/2015 11:52 PM, Gonzalo Camarillo wrote: > Authors of the following drafts, > > could you please let the WG know their status and what needs to happen > next for each of them in order to be able to WGLC them at some point in > the future? > > https://datatracker.ietf.org/doc/draft-ietf-hip-multihoming/ > https://datatracker.ietf.org/doc/draft-ietf-hip-native-nat-traversal/ > https://datatracker.ietf.org/doc/draft-ietf-hip-rfc4423-bis/ > http://datatracker.ietf.org/doc/draft-ietf-hip-rfc5206-bis/ > > Thanks, > > Gonzalo Gonzalo and all, Here is a brief update on the mobility and multihoming drafts. I posted a revision 10 of RFC5206-bis last week: https://www.ietf.org/id/draft-ietf-hip-rfc5206-bis-10.txt I believe that we could close all the remaining open issues as either resolved or wontfix (editorial); the changes that appear in draft-10 are as follows: - issue 21: clarified that HI MAY be included in UPDATE for benefit of middleboxes - changed one informative reference from RFC 4423-bis to RFC 7401 - removed discussion about possible multiple LOCATOR_SET and ESP_INFO parameters in an UPDATE (per previous mailing list discussion) - removed discussion about handling LOCATOR_SET parameters in packets other than UPDATE (per previous mailing list discussion) I had hoped to post a revision of the multihoming draft with all of the open issues resolved by now, but there is still some work for me to do, so I just refreshed the previous version for the time being: https://www.ietf.org/id/draft-ietf-hip-multihoming-07.txt I will work on publishing -08 shortly and then I think we could consider a WGLC on the pair of drafts. - Tom