Re: [Hipsec] WGLC: HIP-based overlays
"Henderson, Thomas R" <thomas.r.henderson@boeing.com> Mon, 22 February 2010 18:43 UTC
Return-Path: <thomas.r.henderson@boeing.com>
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 A18E828C374 for <hipsec@core3.amsl.com>; Mon, 22 Feb 2010 10:43:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 tagged_above=-999 required=5 tests=[AWL=0.217, 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 eqmciVAv2Uvn for <hipsec@core3.amsl.com>; Mon, 22 Feb 2010 10:43:33 -0800 (PST)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id AF16128C164 for <hipsec@ietf.org>; Mon, 22 Feb 2010 10:43:30 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by stl-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id o1MIjJ62028156 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 22 Feb 2010 12:45:20 -0600 (CST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id o1MIjHjd007717; Mon, 22 Feb 2010 10:45:17 -0800 (PST)
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id o1MIjGwh007679 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 22 Feb 2010 10:45:16 -0800 (PST)
Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.83]) by XCH-NWHT-11.nw.nos.boeing.com ([130.247.25.114]) with mapi; Mon, 22 Feb 2010 10:45:16 -0800
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: 'Gonzalo Camarillo' <Gonzalo.Camarillo@ericsson.com>, HIP <hipsec@ietf.org>
Date: Mon, 22 Feb 2010 10:45:15 -0800
Thread-Topic: [Hipsec] WGLC: HIP-based overlays
Thread-Index: Acqem2t7RDuopi1YTBisaKUsTpcP6AVOTsEw
Message-ID: <7CC566635CFE364D87DC5803D4712A6C4C1F48A7BD@XCH-NW-10V.nw.nos.boeing.com>
References: <4B5F07F6.7080800@ericsson.com>
In-Reply-To: <4B5F07F6.7080800@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
Subject: Re: [Hipsec] WGLC: 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." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 22 Feb 2010 18:43:34 -0000
> -----Original Message----- > From: hipsec-bounces@ietf.org > [mailto:hipsec-bounces@ietf.org] On Behalf Of Gonzalo Camarillo > Sent: Tuesday, January 26, 2010 7:19 AM > To: HIP > Subject: [Hipsec] WGLC: HIP-based overlays > > Folks, > > we would like to WGLC the set of specifications that describe how to > build HIP-based overlays. The documents under WGLC are the following: > > http://tools.ietf.org/html/draft-ietf-hip-bone-04 > http://tools.ietf.org/html/draft-ietf-hip-reload-instance-00 > http://tools.ietf.org/html/draft-ietf-hip-hiccups-01 > http://tools.ietf.org/html/draft-ietf-hip-via-00 > > This WGLC will end on February 23rd. Please, send your > comments to this > list. > Gonzalo, Below are my WGLC comments on this set of drafts. I will send some detailed comments on each draft in subsequent messages. Overall, my opinion is that this set of drafts is not yet ready to publish, because there are some missing elements in each draft (see the detailed comments) and also because I think the overall clarity of the specifications could be improved. In particular, I found several instances where I had a question of how something worked in one draft, and later found the answer somewhere else in another draft. These types of things could be probably addressed by some reorganization. Also, I did not have a clear big picture of this type of overlay until I read all of the details of all drafts. Some type of "Protocol overview" section in the framework draft, with particular attention to interface definitions or modular decomposition, would help. For example, when I read the RELOAD draft, I found a nice overview section including architectural diagrams in Section 1 of the draft. Maybe Section 7 of the hip-bone draft could be moved forward to Section 1 and expanded. I would suggest: 1) merge draft-ietf-hip-bone, draft-ietf-hip-via, and draft-ietf-hip-hiccups into one draft. Keep the reload instance as a separate draft. Keep the certificate draft as a separate draft. 2) write a protocol (or framework) overview section in the draft-ietf-hip-bone-04 and place it in Section 1, like was done for RELOAD. Note that I did not review these drafts from the perspective of whether all of the new crypto defined is correct and consistent with the rest of HIP. Regards, Tom
- [Hipsec] WGLC: HIP-based overlays Gonzalo Camarillo
- Re: [Hipsec] WGLC: HIP-based overlays Henderson, Thomas R
- Re: [Hipsec] WGLC: draft-ietf-hip-via-00 Henderson, Thomas R
- Re: [Hipsec] WGLC: draft-ietf-hip-hiccups-01 Henderson, Thomas R
- Re: [Hipsec] WGLC: draft-ietf-hip-reload-instance… Henderson, Thomas R
- Re: [Hipsec] WGLC: draft-ietf-hip-bone-04 Henderson, Thomas R
- Re: [Hipsec] WGLC: HIP-based overlays Gonzalo Camarillo
- Re: [Hipsec] WGLC: draft-ietf-hip-via-00 Ari Keranen
- Re: [Hipsec] WGLC: draft-ietf-hip-reload-instance… Ari Keranen
- Re: [Hipsec] WGLC: HIP-based overlays Henderson, Thomas R
- Re: [Hipsec] WGLC: draft-ietf-hip-via-00 Henderson, Thomas R
- Re: [Hipsec] WGLC: draft-ietf-hip-reload-instance… Henderson, Thomas R
- Re: [Hipsec] WGLC: HIP-based overlays Gonzalo Camarillo
- Re: [Hipsec] WGLC: draft-ietf-hip-via-00 Ari Keranen
- Re: [Hipsec] WGLC: draft-ietf-hip-reload-instance… Ari Keranen
- Re: [Hipsec] WGLC: draft-ietf-hip-reload-instance… Henderson, Thomas R
- Re: [Hipsec] WGLC: draft-ietf-hip-reload-instance… Ari Keranen
- Re: [Hipsec] WGLC: draft-ietf-hip-reload-instance… Henderson, Thomas R
- Re: [Hipsec] WGLC: draft-ietf-hip-bone-04 Ari Keranen
- Re: [Hipsec] WGLC: draft-ietf-hip-reload-instance… Ari Keranen
- Re: [Hipsec] WGLC: draft-ietf-hip-reload-instance… Henderson, Thomas R
- Re: [Hipsec] WGLC: draft-ietf-hip-reload-instance… Ari Keranen
- Re: [Hipsec] WGLC: draft-ietf-hip-hiccups-01 Jan Melen
- Re: [Hipsec] WGLC: draft-ietf-hip-hiccups-01 Jan Melen
- Re: [Hipsec] WGLC: draft-ietf-hip-hiccups-01 Jan Melen