IETF Logo Mail Archive

Re: [Hipsec] HIP parameters critical flag

"Ahrenholz, Jeffrey M" <jeffrey.m.ahrenholz@boeing.com> Tue, 12 January 2010 18:27 UTC

Return-Path: <jeffrey.m.ahrenholz@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 5988028C119 for <hipsec@core3.amsl.com>; Tue, 12 Jan 2010 10:27:17 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AzrFrX8jLTkQ for <hipsec@core3.amsl.com>; Tue, 12 Jan 2010 10:27:16 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id B3DA628C106 for <hipsec@ietf.org>; Tue, 12 Jan 2010 10:27:16 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id o0CIR26Y016218 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 12 Jan 2010 10:27:04 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id o0CIR1HV001310; Tue, 12 Jan 2010 12:27:01 -0600 (CST)
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id o0CIR13b001295 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 12 Jan 2010 12:27:01 -0600 (CST)
Received: from XCH-NW-12V.nw.nos.boeing.com ([130.247.25.248]) by XCH-NWHT-11.nw.nos.boeing.com ([130.247.25.114]) with mapi; Tue, 12 Jan 2010 10:27:01 -0800
From: "Ahrenholz, Jeffrey M" <jeffrey.m.ahrenholz@boeing.com>
To: 'Robert Moskowitz' <rgm@htt-consult.com>
Date: Tue, 12 Jan 2010 10:27:00 -0800
Thread-Topic: [Hipsec] HIP parameters critical flag
Thread-Index: AcqTsoZnxlx1fcdaQ0O4n0mnPe8wkwAAW2xg
Message-ID: <FD98F9C3CBABA74E89B5D4B5DE0263B937813030CA@XCH-NW-12V.nw.nos.boeing.com>
References: <4B4C9C1F.7050309@htt-consult.com> <AC120305-F2D2-428D-BFCB-CB12A4114598@cs.rwth-aachen.de> <FD98F9C3CBABA74E89B5D4B5DE0263B937813030C9@XCH-NW-12V.nw.nos.boeing.com> <4B4CB807.5090707@htt-consult.com>
In-Reply-To: <4B4CB807.5090707@htt-consult.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
Cc: "hipsec@ietf.org" <hipsec@ietf.org>
Subject: Re: [Hipsec] HIP parameters critical flag
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: Tue, 12 Jan 2010 18:27:17 -0000

> > Have you considered extending the HOST_ID TLV by one field 
> to include HIH (rather than using a separate parameter)?
> > (for example the HI hi_hdr already indicates the RSA/DSA 
> key type, the HIP_SIGNATURE contains SIG algorithm, etc.)
> >    
> 
> I envision multiple HIH per HI.  With a possible ranking of 
> HIH for the HI.

It seems hard to rank or negotiate the HIH since the HITs chosen in the HIP header are already derived using a particular HIH. If you chose a different HIH then you would start a new association using different HITs? Maybe I don't fully understand HIH yet...

-Jeff

v2.23.0 | Report a Bug | By Email