
From internet-drafts@ietf.org  Thu Nov  7 13:13:03 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CA4821E816E; Thu,  7 Nov 2013 13:13:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level: 
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EYAXWf7tpRsS; Thu,  7 Nov 2013 13:13:02 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9698621E80FE; Thu,  7 Nov 2013 13:13:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.83
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131107211302.21885.51558.idtracker@ietfa.amsl.com>
Date: Thu, 07 Nov 2013 13:13:02 -0800
Cc: hipsec@ietf.org
Subject: [Hipsec] I-D Action: draft-ietf-hip-rfc4423-bis-06.txt
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.12
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Nov 2013 21:13:03 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Host Identity Protocol Working Group of t=
he IETF.

	Title           : Host Identity Protocol Architecture
	Author(s)       : Robert Moskowitz
                          Miika Komu
	Filename        : draft-ietf-hip-rfc4423-bis-06.txt
	Pages           : 40
	Date            : 2013-11-07

Abstract:
   This memo describes a new namespace, the Host Identity namespace, and
   a new protocol layer, the Host Identity Protocol, between the
   internetworking and transport layers.  Herein are presented the
   basics of the current namespaces, their strengths and weaknesses, and
   how a new namespace will add completeness to them.  The roles of this
   new namespace in the protocols are defined.

   This document obsoletes RFC 4423 and addresses the concerns raised by
   the IESG, particularly that of crypto agility.  It incorporates
   lessons learned from the implementations of RFC 5201 and goes further
   to explain how HIP works as a secure signaling channel.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-hip-rfc4423-bis

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-hip-rfc4423-bis-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-hip-rfc4423-bis-06


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 mkomu@cs.hut.fi  Thu Nov  7 22:45:53 2013
Return-Path: <mkomu@cs.hut.fi>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CB2421E8203 for <hipsec@ietfa.amsl.com>; Thu,  7 Nov 2013 22:45:53 -0800 (PST)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fpb-tAamdTld for <hipsec@ietfa.amsl.com>; Thu,  7 Nov 2013 22:45:47 -0800 (PST)
Received: from mail.cs.hut.fi (mail.cs.hut.fi [130.233.192.7]) by ietfa.amsl.com (Postfix) with ESMTP id 5C7D221E805D for <hipsec@ietf.org>; Thu,  7 Nov 2013 22:45:47 -0800 (PST)
Received: from [127.0.0.1] (hutcs.cs.hut.fi [130.233.192.10]) by mail.cs.hut.fi (Postfix) with ESMTP id B6A4E308199 for <hipsec@ietf.org>; Fri,  8 Nov 2013 08:45:22 +0200 (EET)
Message-ID: <527C8882.4090201@cs.hut.fi>
Date: Fri, 08 Nov 2013 08:45:22 +0200
From: Miika Komu <mkomu@cs.hut.fi>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: hipsec@ietf.org
References: <502A164E-8CCA-459B-A404-4E668150A684@helsinki.fi>	<508076EE.1050700@cs.hut.fi> <508412FD.2010606@cs.hut.fi> <50898059.503@cs.hut.fi>
In-Reply-To: <50898059.503@cs.hut.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Hipsec] Feedback for 4423bis
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Nov 2013 06:45:53 -0000

Hi,

On 10/25/2012 09:09 PM, Miika Komu wrote:
> Hi,
>
> On 10/21/2012 06:21 PM, Miika Komu wrote:
>> Hi,
>>
>> On 10/19/2012 12:38 AM, Miika Komu wrote:
>>> Hi,
>>>
>>> On 10/10/2012 10:05 PM, Sasu Tarkoma wrote:
>>>> Hi all,
>>>>
>>>> I read the latest HIP architecture draft (4423bis-05) and it looks
>>>> very good. Below you will find some observations that I made
>>>> when reading the draft.
>>>
>>> looks good to me too but I have also some suggestions for improvement.
>>> Here's the first batch of comments, I'll send the remaining ones later.
>>
>> the second batch is here, I'll send the third and final later.
>
> the third and final batch is now here. Sorry for the delay.

I fixed my own suggestions in the new version since there were no 
objections.

http://tools.ietf.org/html/draft-ietf-hip-rfc4423-bis-06

From mkomu@cs.hut.fi  Thu Nov  7 22:58:50 2013
Return-Path: <mkomu@cs.hut.fi>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76DDE21E80E0 for <hipsec@ietfa.amsl.com>; Thu,  7 Nov 2013 22:58:50 -0800 (PST)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fBsboQcpTi7h for <hipsec@ietfa.amsl.com>; Thu,  7 Nov 2013 22:58:45 -0800 (PST)
Received: from mail.cs.hut.fi (mail.cs.hut.fi [130.233.192.7]) by ietfa.amsl.com (Postfix) with ESMTP id B730721E80A8 for <hipsec@ietf.org>; Thu,  7 Nov 2013 22:58:40 -0800 (PST)
Received: from [127.0.0.1] (hutcs.cs.hut.fi [130.233.192.10]) by mail.cs.hut.fi (Postfix) with ESMTP id 84F9C3081BA for <hipsec@ietf.org>; Fri,  8 Nov 2013 08:58:38 +0200 (EET)
Message-ID: <527C8B9E.4090404@cs.hut.fi>
Date: Fri, 08 Nov 2013 08:58:38 +0200
From: Miika Komu <mkomu@cs.hut.fi>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: hipsec@ietf.org
References: <502A164E-8CCA-459B-A404-4E668150A684@helsinki.fi>
In-Reply-To: <502A164E-8CCA-459B-A404-4E668150A684@helsinki.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Hipsec] Feedback for 4423bis
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Nov 2013 06:58:50 -0000

Hi Sasu,

On 10/10/2012 10:05 PM, Sasu Tarkoma wrote:
> Hi all,
>
> I read the latest HIP architecture draft (4423bis-05) and it looks
> very good. Below you will find some observations that I made
> when reading the draft.

thanks for the comments!

> - Architecture and implementation details are partly
>   intertwined here. Perhaps the generic model can
> be summarised first and then the implementation
> specific details. Theory of HI is mentioned in the
> beginning, but I think it is not clear for all readers what
> is meant by this.
>
> - It is stated that the model is general and it does not require
> public key crypto; however, this is not really elaborated. Also
> it is stated that the model can be applied at any
> layer, but this is not explained. The description assumes
> that Host Identity decouples internetworking and
> transport layers.

I have tried to improve the text in general.

> - The draft does not discuss architecture and protocol
> deployment issues. This is one practical requirement given
> the momentum of the current solutions.

Done.

> - The description of the HIP protocol is quite light in this
> draft. The introductory part to section 5 could briefly state the
> key components of HIP including BEX, mobility/multihoming support,
> and rendezvous that are covered by the following subsections.

Done.

> - In section 5, it is stated that:
> "Similarly, if it is possible to distribute the processing of a single
>     Host Identity over several physical computers, HIP provides for
>     cluster based services without any changes at the client end-point."
>
> I think the base specification and implementation do not directly
> support this, but additional management extensions are needed.

Agreed, I have modified the text.

> - Computational puzzle does not appear to be mentioned.

Now they are.

> - Extensions (new hash functions) are not elaborated. This is
> related to a general requirement that a protocol should be evolvable.
>
> - p. 17 section 10 needs a reference
>
> - p. 21 the downgrade attack should be elaborated.
>
> - Typo: p. 5 Identfier

Fixed.

The new version includes a number of references, including peer-reviewed 
papers and a few citations to the most relevant work-in-progress drafts 
(I hope citing drafts is ok). The ideas did not arrive from thin air, so 
I felt compelled to cite the original work and point out an interested 
reader to the right direction for more details.

http://tools.ietf.org/html/draft-ietf-hip-rfc4423-bis-06

From mkomu@cs.hut.fi  Sat Nov  9 02:53:13 2013
Return-Path: <mkomu@cs.hut.fi>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D33D11E810A for <hipsec@ietfa.amsl.com>; Sat,  9 Nov 2013 02:53:13 -0800 (PST)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WLph9gjcQK6L for <hipsec@ietfa.amsl.com>; Sat,  9 Nov 2013 02:53:09 -0800 (PST)
Received: from mail.cs.hut.fi (mail.cs.hut.fi [130.233.192.7]) by ietfa.amsl.com (Postfix) with ESMTP id DA5BC11E80FA for <hipsec@ietf.org>; Sat,  9 Nov 2013 02:53:08 -0800 (PST)
Received: from [127.0.0.1] (hutcs.cs.hut.fi [130.233.192.10]) by mail.cs.hut.fi (Postfix) with ESMTP id 06A373084C0 for <hipsec@ietf.org>; Sat,  9 Nov 2013 12:53:05 +0200 (EET)
Message-ID: <527E1410.7090001@cs.hut.fi>
Date: Sat, 09 Nov 2013 12:53:04 +0200
From: Miika Komu <mkomu@cs.hut.fi>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: hipsec@ietf.org
References: <C018CAF7B620E64D87620E581C4E6BB9020D80@XCH-BLV-104.nw.nos.boeing.com> <C018CAF7B620E64D87620E581C4E6BB902C00A@XCH-BLV-104.nw.nos.boeing.com>
In-Reply-To: <C018CAF7B620E64D87620E581C4E6BB902C00A@XCH-BLV-104.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Hipsec] additional comments on latest RFC5201-bis draft
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Nov 2013 10:53:13 -0000

FYI,

On 09/26/2013 11:45 PM, Henderson, Thomas R wrote:
> I'll try to wrap up the inputs and post a revision over the weekend, if no further comments.  Please see inline below.

Xin Gu implemented HIPv2 (sponsored by Aalto university) and the code is 
now available in the HIPL trunk:

https://launchpad.net/hipl

Documentation of the HIPv2 efforts are published in his master thesis 
(as announced earlier in this mailing list):

http://nordsecmob.aalto.fi/en/publications/theses_2012/gu-xin_thesis.pdf

Binary images for Linux platforms are also available here:

http://hipl.hiit.fi/index.php?index=download

We haven't done interoperability tests because I believe HIPL is 
currently the only implementation with v2 support.

From thomas.r.henderson@boeing.com  Tue Nov 12 09:57:31 2013
Return-Path: <thomas.r.henderson@boeing.com>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4FC611E811B for <hipsec@ietfa.amsl.com>; Tue, 12 Nov 2013 09:57:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GjvQzYOZ0zA6 for <hipsec@ietfa.amsl.com>; Tue, 12 Nov 2013 09:57:14 -0800 (PST)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) by ietfa.amsl.com (Postfix) with ESMTP id C193711E80E4 for <hipsec@ietf.org>; Tue, 12 Nov 2013 09:57:14 -0800 (PST)
Received: from stl-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id rACHvD2h013070 for <hipsec@ietf.org>; Tue, 12 Nov 2013 11:57:13 -0600
Received: from XCH-PHX-409.sw.nos.boeing.com (xch-phx-409.sw.nos.boeing.com [10.57.37.40]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id rACHvCIj013023 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 12 Nov 2013 11:57:12 -0600
Received: from XCH-BLV-104.nw.nos.boeing.com ([169.254.4.229]) by XCH-PHX-409.sw.nos.boeing.com ([169.254.9.131]) with mapi id 14.03.0158.001; Tue, 12 Nov 2013 09:57:11 -0800
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "'Robert Moskowitz'" <rgm@htt-consult.com>, HIP <hipsec@ietf.org>
Thread-Topic: [Hipsec] Adding CMAC and GMAC to 5202-bis
Thread-Index: AQHO1XtvMmTWCSl/eUS/dlcSoxsK55oh9OyA
Date: Tue, 12 Nov 2013 17:57:11 +0000
Message-ID: <C018CAF7B620E64D87620E581C4E6BB905BAFB@XCH-BLV-104.nw.nos.boeing.com>
References: <527115EC.4060608@htt-consult.com>
In-Reply-To: <527115EC.4060608@htt-consult.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Subject: Re: [Hipsec] Adding CMAC and GMAC to 5202-bis
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Nov 2013 17:57:31 -0000

> -----Original Message-----
> From: hipsec-bounces@ietf.org [mailto:hipsec-bounces@ietf.org] On
> Behalf Of Robert Moskowitz
> Sent: Wednesday, October 30, 2013 7:22 AM
> To: HIP
> Subject: [Hipsec] Adding CMAC and GMAC to 5202-bis
>=20
> We added the 'modern' modes:  CCM and GCM to 5202-bis, but left out the
> authentication only modes.  Thus I propose adding to sec 5.1.2:
>=20
>   AES-CMAC-96         14              [RFC4493], [RFC4494]
>   AES-GMAC              15              [RFC4543]
>=20
> If you have CCM in your implementation, it makes sense to offer CMAC,
> and likewise GCM/GMAC.
>=20
> If there is no down votes on this, Tom said he would add them.

I will plan to add these on Friday if there are no further comments.

>=20
>=20
> There is JUST one MINOR point about manditory to implement, also in sec
> 5.1.2.
>=20
> Keep it as is, or change it two either CCM or GCM?  I can argue this
> all ways around.  I suspect that sensor implementations may well ignore
> the manditory and just do CCM.
>=20

I will keep as is in the next revision, unless there is support voiced for =
changing it.  Current statement is:

   Mandatory implementations: AES-128-CBC with HMAC-SHA-256 and NULL
   with HMAC-SHA-256.

Rene also pointed out in his reviews that the current spec set may need to =
be slightly modified to accommodate sensor requirements, but I believe that=
 we decided to leave those for further study/specification.

- Tom

From internet-drafts@ietf.org  Mon Nov 18 23:31:41 2013
Return-Path: <internet-drafts@ietf.org>
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 158FD1AC4A3; Mon, 18 Nov 2013 23:31:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 iJR9zZZqi-jO; Mon, 18 Nov 2013 23:31:40 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E79231AC404; Mon, 18 Nov 2013 23:31:39 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.83.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131119073139.12901.56223.idtracker@ietfa.amsl.com>
Date: Mon, 18 Nov 2013 23:31:39 -0800
Cc: hipsec@ietf.org
Subject: [Hipsec] I-D Action: draft-ietf-hip-rfc5202-bis-05.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." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec/>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 07:31:41 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Host Identity Protocol Working Group of t=
he IETF.

	Title           : Using the Encapsulating Security Payload (ESP) Transport=
 Format with the Host Identity Protocol (HIP)
	Author(s)       : Petri Jokela
                          Robert Moskowitz
                          Jan Melen
	Filename        : draft-ietf-hip-rfc5202-bis-05.txt
	Pages           : 37
	Date            : 2013-11-18

Abstract:
   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 document obsoletes RFC 5202.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-hip-rfc5202-bis

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-hip-rfc5202-bis-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-hip-rfc5202-bis-05


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 mkomu@cs.hut.fi  Mon Nov 25 06:21:45 2013
Return-Path: <mkomu@cs.hut.fi>
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 9B1491ADBCB for <hipsec@ietfa.amsl.com>; Mon, 25 Nov 2013 06:21:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.302
X-Spam-Level: 
X-Spam-Status: No, score=-2.302 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 cNvd9BVynlYn for <hipsec@ietfa.amsl.com>; Mon, 25 Nov 2013 06:21:42 -0800 (PST)
Received: from mail.cs.hut.fi (mail.cs.hut.fi [130.233.192.7]) by ietfa.amsl.com (Postfix) with ESMTP id A99071AD9AC for <hipsec@ietf.org>; Mon, 25 Nov 2013 06:21:42 -0800 (PST)
Received: from [127.0.0.1] (hutcs.cs.hut.fi [130.233.192.10]) by mail.cs.hut.fi (Postfix) with ESMTP id 24CF9308DD2 for <hipsec@ietf.org>; Mon, 25 Nov 2013 16:21:42 +0200 (EET)
Message-ID: <52935CF5.2040504@cs.hut.fi>
Date: Mon, 25 Nov 2013 16:21:41 +0200
From: Miika Komu <mkomu@cs.hut.fi>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: hip WG <hipsec@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Hipsec] Android support for HIP
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." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec/>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Nov 2013 14:21:45 -0000

FYI,

HIP for Linux has now experimental support for Android:

http://hipl.hiit.fi/hipl/manual/HOWTO.html#android

The source code is available here:

https://launchpad.net/hipl

If you're interested in asking further questions, please join the HIPL 
developers mailing list:

http://www.freelists.org/list/hipl-dev

From gonzalo.camarillo@ericsson.com  Tue Nov 26 01:03:04 2013
Return-Path: <gonzalo.camarillo@ericsson.com>
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 834471AE076 for <hipsec@ietfa.amsl.com>; Tue, 26 Nov 2013 01:03:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.851
X-Spam-Level: 
X-Spam-Status: No, score=-103.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 Y58ZXomBB8D5 for <hipsec@ietfa.amsl.com>; Tue, 26 Nov 2013 01:03:02 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 551CB1AC863 for <hipsec@ietf.org>; Tue, 26 Nov 2013 01:03:02 -0800 (PST)
X-AuditID: c1b4fb2d-b7f1c8e000005ceb-1d-529463c5e813
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id B2.98.23787.5C364925; Tue, 26 Nov 2013 10:03:01 +0100 (CET)
Received: from [147.214.22.133] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.35) with Microsoft SMTP Server id 14.2.328.9; Tue, 26 Nov 2013 10:03:01 +0100
Message-ID: <529463C4.7050405@ericsson.com>
Date: Tue, 26 Nov 2013 10:03:00 +0100
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: HIP <hipsec@ietf.org>
References: <5270EC63.6070101@ericsson.com>
In-Reply-To: <5270EC63.6070101@ericsson.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrJJMWRmVeSWpSXmKPExsUyM+Jvre7R5ClBBp3d2hZTF01mdmD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxueT5xgLbvBXTDi3mqmBcT9PFyMnh4SAicS6x91sELaYxIV7 64FsLg4hgUOMEise/GCGcNYwSlz5/48RpIpXQFti1so3YDaLgKrEi6ZrTCA2m4CFxJZb91lA bFGBKInz514yQdQLSpyc+QQsLiIgKdFzdymQzcEhLJAq8WkZP0hYCGhk34MpYCM5BXQktvzY zQ5SIiEgLtHTGAQSZhbQk5hytYURwpaX2P52DjNM6/JnLSwTGAVnIVk2C0nLLCQtCxiZVzGy 5yZm5qSXG25iBAbfwS2/dXcwnjoncohRmoNFSZz3w1vnICGB9MSS1OzU1ILUovii0pzU4kOM TBycUg2MnRJ2PrkzLv+q39ijq/k8MEJl9Y3te/IDJ6wXXRRcfmFPku/Cl0IpT3J+aatOCwwT sjZtK2RqrenYxdk5ba1ZzfHTZT8WeyfNfDghpeKA9MJ5HvaPr4kJSB53Pyki+V68TVTte/nm 2DseLVyecbypjhG1jbYv/rbnFMz+5dnakCF809Fvxx0lluKMREMt5qLiRABtfGRiDAIAAA==
Subject: Re: [Hipsec] Status update on the four core drafts: 4423bis, 4843bis, 5201bis, and 5202bis
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." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec/>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Nov 2013 09:03:04 -0000

Hi,

5201bis and 5202bis seem to be ready for publication request at this
point... but 4843bis has expired and thus is not even on the official
archives any longer.

Cheers,

Gonzalo

On 30/10/2013 12:24 PM, Gonzalo Camarillo wrote:
> Folks,
> 
> here you have a status update on the four core drafts. Note that at this
> point only one of them is ready for publication request. Authors and
> editors, please put some energy into this so that we can send them to
> our AD shortly.
> 
> 
> https://datatracker.ietf.org/doc/draft-ietf-hip-rfc4423-bis/
> 
> This draft needs to be revised. The last version expired in April:
> 
> http://tools.ietf.org/id/draft-ietf-hip-rfc4423-bis-05.txt
> 
> We agreed that this draft will be Informational (the current version
> still says PS).
> 
> Given the slow progress of this draft, we will not be blocking the other
> three drafts on this one. Nevertheless, we need to make some progress
> with this one as well.
> 
> 
> https://datatracker.ietf.org/doc/draft-ietf-hip-rfc4843-bis/
> 
> This draft, which expires in a week, needs to be revised to fix a few
> nits. I am hoping that a new revision of this draft will be ready for
> publication request.
> 
> 
> https://datatracker.ietf.org/doc/draft-ietf-hip-rfc5201-bis/
> 
> This revision seems to be ready for publication request. We will request
> the publication of the three drafts (4843bis, 5201bis, and 5202bis)
> together, though.
> 
> 
> https://datatracker.ietf.org/doc/draft-ietf-hip-rfc5202-bis/
> 
> We need to add CMAC and GMAC to 5202-bis to provide a modern null
> cipher. We are waiting for text from Bob.
> 
> Also, I still have not received a confirmation from all authors that
> they do not know any additional IPR on the draft. I hope to get it shortly.
> 
> 
> Cheers,
> 
> Gonzalo
> 
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec
> 
> 

