[Hipsec] Parameter space layout and significant change in wording

Tobias Heer <heer@cs.rwth-aachen.de> Thu, 29 July 2010 17:28 UTC

Return-Path: <heer@informatik.rwth-aachen.de>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 062A328C1DD for <hipsec@core3.amsl.com>; Thu, 29 Jul 2010 10:28:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.476
X-Spam-Status: No, score=-4.476 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id e+kP7PcKadDa for <hipsec@core3.amsl.com>; Thu, 29 Jul 2010 10:28:40 -0700 (PDT)
Received: from mta-1.ms.rz.rwth-aachen.de (mta-1.ms.rz.RWTH-Aachen.DE []) by core3.amsl.com (Postfix) with ESMTP id 78C0A28C0DB for <hipsec@ietf.org>; Thu, 29 Jul 2010 10:28:40 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: text/plain; charset="us-ascii"
Received: from ironport-out-1.rz.rwth-aachen.de ([]) by mta-1.ms.rz.RWTH-Aachen.de (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008)) with ESMTP id <0L6B00LWVXWGXPF0@mta-1.ms.rz.RWTH-Aachen.de> for hipsec@ietf.org; Thu, 29 Jul 2010 19:29:04 +0200 (CEST)
X-IronPort-AV: E=Sophos;i="4.55,281,1278280800"; d="scan'208";a="67064981"
Received: from relay-auth-2.ms.rz.rwth-aachen.de (HELO relay-auth-2) ([]) by ironport-in-1.rz.rwth-aachen.de with ESMTP; Thu, 29 Jul 2010 19:29:03 +0200
Received: from dhcp-21dd.meeting.ietf.org ([unknown] []) by relay-auth-2.ms.rz.rwth-aachen.de (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 9 2008)) with ESMTPA id <0L6B00K22XWFHB70@relay-auth-2.ms.rz.rwth-aachen.de> for hipsec@ietf.org; Thu, 29 Jul 2010 19:29:03 +0200 (CEST)
From: Tobias Heer <heer@cs.rwth-aachen.de>
Date: Thu, 29 Jul 2010 19:29:06 +0200
Message-id: <661EB84D-5466-4893-BA7D-1A9A4B73F4CC@cs.rwth-aachen.de>
To: HIP WG <hipsec@ietf.org>
X-Mailer: Apple Mail (2.1081)
Subject: [Hipsec] Parameter space layout and significant change in wording
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: Thu, 29 Jul 2010 17:28:42 -0000


We were discussing the parameter space layout during the 5201-bis discussion session.
The result was the following. I marked the changes with "!"

  0     - 1023  Handshake
  1024  - 2047  Reserved
! 2048  - 8191  Signed parameters allocated through specification documents*
! 8192  - 61439 Reserved
! 61440 - 62463 Signatures and (signed) MACs
! 62464 - 63487 Parameters that are neither signed nor MACed*
  63488 - 64511 Rendezvous and relaying
! 64512 - 65023 Parameters that not signed*
! 65024 - 65535 Reserved

The rationale behind the changes was to have a non-BEX block and reserved blocks for future expansion in all vital spaces. The parts marked with * are the sub-spaces that are intended for extensions, etc. that do not strictly extend or modify the handshake. Any comments or objections?

There is a slight change in wording to make creating HIP derivatives without signature less complex. I changed the "Signatures and MACs" to "Signatures and (signed) MACs" and "Parameters that are not signed" to "Parameters that are neither signed nor MACed". This will not change anything in the BEX (most importantly it will stay SIGMA compliant) but it avoids redefinition of parameters with different parameter numbers for DEX and other variants without signature capabilities. This is to allow a movement towards a "family" of interoperable HIP protocols. I would appreciate discussion and comments on this step on the list.



Dipl.-Inform. Tobias Heer, Ph.D. Student
Distributed Systems Group 
RWTH Aachen University, Germany
tel: +49 241 80 207 76
web: http://ds.cs.rwth-aachen.de/members/heer
blog: http://dtobi.wordpress.com/
card: http://card.ly/dtobi