Re: [Hipsec] Status of HIP implementation
"Henderson, Thomas R" <thomas.r.henderson@boeing.com> Tue, 16 July 2013 16:14 UTC
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 2120711E80D5 for <hipsec@ietfa.amsl.com>; Tue, 16 Jul 2013 09:14:47 -0700 (PDT)
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 iW58uv+GgF22 for <hipsec@ietfa.amsl.com>; Tue, 16 Jul 2013 09:14:41 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) by ietfa.amsl.com (Postfix) with ESMTP id 9031D21E805F for <hipsec@ietf.org>; Tue, 16 Jul 2013 09:14:41 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r6GGEdNU005324 for <hipsec@ietf.org>; Tue, 16 Jul 2013 09:14:39 -0700
Received: from XCH-NWHT-01.nw.nos.boeing.com (xch-nwht-01.nw.nos.boeing.com [130.247.70.222]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r6GGEcQ5004781 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 16 Jul 2013 09:14:38 -0700
Received: from XCH-NW-16V.nw.nos.boeing.com ([130.247.25.240]) by XCH-NWHT-01.nw.nos.boeing.com ([130.247.70.222]) with mapi; Tue, 16 Jul 2013 09:14:39 -0700
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: 'Gonzalo Camarillo' <Gonzalo.Camarillo@ericsson.com>, HIP <hipsec@ietf.org>
Date: Tue, 16 Jul 2013 09:14:39 -0700
Thread-Topic: [Hipsec] Status of HIP implementation
Thread-Index: Ac6B9aG1uuhETTQyTxiM0ywk3FIzVQAScuYw
Message-ID: <758141CC3D829043A8C3164DD3D593EA2ED77F18F8@XCH-NW-16V.nw.nos.boeing.com>
References: <51E4F548.8050903@ericsson.com>
In-Reply-To: <51E4F548.8050903@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Subject: Re: [Hipsec] Status of HIP implementation
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, 16 Jul 2013 16:14:47 -0000
> -----Original Message----- > From: hipsec-bounces@ietf.org [mailto:hipsec-bounces@ietf.org] On > Behalf Of Gonzalo Camarillo > Sent: Tuesday, July 16, 2013 12:25 AM > To: HIP > Subject: [Hipsec] Status of HIP implementation > > Folks, > > one of the questions we need to answer when requesting the publication > of the bis specs is the following: > > > Are there existing implementations of the protocol? Have a > significant > > number of vendors indicated their plan to implement the > specification? > > If you could send me an update on your implementation, or third-party > implementations you are aware of, that would be great. In particular, > it would be good to know which implementers intend to update their > implementations to comply with the Standards Track bis specs (as > opposed to implementations that are no being actively maintained any > longer). OpenHIP (http://www.openhip.org) plans to support the bis specs, but work has not yet started. - Tom
- [Hipsec] Status of HIP implementation Gonzalo Camarillo
- Re: [Hipsec] Status of HIP implementation Miika Komu
- Re: [Hipsec] Status of HIP implementation Henderson, Thomas R