Re: [hiprg] draft-zhang-hip-hierarchical-parameter-00:Includinghieararchy in HIT generation

"Henderson, Thomas R" <thomas.r.henderson@boeing.com> Mon, 10 August 2009 17:34 UTC

Return-Path: <thomas.r.henderson@boeing.com>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E143928C114 for <hiprg@core3.amsl.com>; Mon, 10 Aug 2009 10:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.86
X-Spam-Level:
X-Spam-Status: No, score=-5.86 tagged_above=-999 required=5 tests=[AWL=0.739, 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 ZzSSyngg5amr for <hiprg@core3.amsl.com>; Mon, 10 Aug 2009 10:34:44 -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 D094B3A6EBF for <hiprg@irtf.org>; Mon, 10 Aug 2009 10:33:48 -0700 (PDT)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n7AHXhTU021319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Aug 2009 10:33:44 -0700 (PDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n7AHXhlp027182; Mon, 10 Aug 2009 10:33:43 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n7AHXc5I026810; Mon, 10 Aug 2009 10:33:43 -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.3959); Mon, 10 Aug 2009 10:33:42 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 10 Aug 2009 10:33:41 -0700
Message-ID: <77F357662F8BFA4CA7074B0410171B6D0A8B7220@XCH-NW-5V1.nw.nos.boeing.com>
In-Reply-To: <A49729CD-84AF-49AF-93CE-2B5210E0C21D@cs.rwth-aachen.de>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [hiprg] draft-zhang-hip-hierarchical-parameter-00:Includinghieararchy in HIT generation
Thread-Index: AcoZ2p6iOojCPsdERVKxqnpDdUbAzwAA+FqA
References: <C1CCBFC6-D133-4CCE-8ABF-3B7A88EC9B0B@cs.rwth-aachen.de><77F357662F8BFA4CA7074B0410171B6D0A8B7219@XCH-NW-5V1.nw.nos.boeing.com> <A49729CD-84AF-49AF-93CE-2B5210E0C21D@cs.rwth-aachen.de>
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: Tobias Heer <heer@cs.rwth-aachen.de>
X-OriginalArrivalTime: 10 Aug 2009 17:33:42.0100 (UTC) FILETIME=[B440E140:01CA19E0]
Cc: hiprg@irtf.org
Subject: Re: [hiprg] draft-zhang-hip-hierarchical-parameter-00:Includinghieararchy in HIT generation
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Aug 2009 17:34:45 -0000

> Hence, the  
> hierarchy information would be self certifying in the sense 
> that if I  
> give a HIT to someone, the hierarchy would be bound to it and 
> it would  
> stay like that unless I changed my HIT. 

...

> The proposed solution was not meant to replace the hierarchy  
> information in an additional parameter it was only intended 
> to have a  
> stronger binding between hierarchy information and HIT. 

Maybe this is a terminology issue but I don't think of this as a binding
or as self-certifying, in the same way that a certificate binds a name
to a principal, or in the way that current HITs are self-certifying,
because there is no authorization to use the hierarchy bits.

- Tom