IETF Logo Mail Archive

Re: [Hipsec] HIP parameters critical flag

"Ahrenholz, Jeffrey M" <jeffrey.m.ahrenholz@boeing.com> Tue, 12 January 2010 19:56 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 883AE3A68DF for <hipsec@core3.amsl.com>; Tue, 12 Jan 2010 11:56:46 -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 sw4RMnjSG8+R for <hipsec@core3.amsl.com>; Tue, 12 Jan 2010 11:56:45 -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 BC7203A68AE for <hipsec@ietf.org>; Tue, 12 Jan 2010 11:56:45 -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 o0CJubRA010231 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 12 Jan 2010 11:56:40 -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 o0CJubG8010181; Tue, 12 Jan 2010 13:56:37 -0600 (CST)
Received: from XCH-NWHT-01.nw.nos.boeing.com (xch-nwht-01.nw.nos.boeing.com [130.247.70.222]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id o0CJuaGq010169 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 12 Jan 2010 13:56:36 -0600 (CST)
Received: from XCH-NW-12V.nw.nos.boeing.com ([130.247.25.248]) by XCH-NWHT-01.nw.nos.boeing.com ([130.247.70.222]) with mapi; Tue, 12 Jan 2010 11:56:36 -0800
From: "Ahrenholz, Jeffrey M" <jeffrey.m.ahrenholz@boeing.com>
To: "Ahrenholz, Jeffrey M" <jeffrey.m.ahrenholz@boeing.com>, 'Robert Moskowitz' <rgm@htt-consult.com>
Date: Tue, 12 Jan 2010 11:56:35 -0800
Thread-Topic: [Hipsec] HIP parameters critical flag
Thread-Index: AcqTt9xRjdUgwuaSQH2crUXcxDj4bAABp36QAACREvA=
Message-ID: <FD98F9C3CBABA74E89B5D4B5DE0263B937813030CE@XCH-NW-12V.nw.nos.boeing.com>
References: <4B4C9C1F.7050309@htt-consult.com><AC120305-F2D2-428D-BFCB-CB12A 4114598@cs.rwth-aachen.de><FD98F9C3CBABA74E89B5D4B5DE0263B937813030C9@XCH-N W-12V.nw.nos.boeing.com><4B4CB807.5090707@htt-consult.com><FD98F9C3CBABA74E 89B5D4B5DE0263B937813030CA@XCH-NW-12V.nw.nos.boeing.com><4B4CC351.9010804@htt-consult.com> <FD98F9C3CBABA74E89B5D4B5DE0263B937813030CD@XCH-NW-12V.nw.nos.boeing.com>
In-Reply-To: <FD98F9C3CBABA74E89B5D4B5DE0263B937813030CD@XCH-NW-12V.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
x-tm-as-product-ver: SMEX-8.0.0.1181-6.000.1038-17126.005
x-tm-as-result: No--45.487900-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
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 19:56:46 -0000

> Again, I'd say make the value 715 if you plan to include it 
> in ENCRYPTED, otherwise you may want to leave that value open 
> for future parameters to be included in ENCRYPTED.

looking more carefully at that previous message, I guess there is no ENCRYPTED in the I1 packet that will include this info:

  "I1 packet has to be modified to include the hash, public keys and
  diffie-hellman algorithms supported by the Initiator in a new "algo"
  parameter.  The parameter should indicate which hash and public key
  algorithm the Initiator used to generate its HIT."

-Jeff

v2.23.0 | Report a Bug | By Email