[Hipsec] Need to clarify HIT prefix

Robert Moskowitz <rgm@htt-consult.com> Thu, 31 March 2011 19:36 UTC

Return-Path: <rgm@htt-consult.com>
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 A225C3A6BAB for <hipsec@core3.amsl.com>; Thu, 31 Mar 2011 12:36:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id tUj8n2F7HdW6 for <hipsec@core3.amsl.com>; Thu, 31 Mar 2011 12:36:18 -0700 (PDT)
Received: from klovia.htt-consult.com (klovia.htt-consult.com []) by core3.amsl.com (Postfix) with ESMTP id 6295F3A6B94 for <hipsec@ietf.org>; Thu, 31 Mar 2011 12:36:18 -0700 (PDT)
Received: from localhost (unknown []) by klovia.htt-consult.com (Postfix) with ESMTP id 4D35262AB0 for <hipsec@ietf.org>; Thu, 31 Mar 2011 19:37:32 +0000 (UTC)
X-Virus-Scanned: amavisd-new at localhost
Received: from klovia.htt-consult.com ([]) by localhost (klovia.htt-consult.com []) (amavisd-new, port 10024) with ESMTP id Wf-eI2rydsxR for <hipsec@ietf.org>; Thu, 31 Mar 2011 15:37:11 -0400 (EDT)
Received: from nc2400.htt-consult.com (unknown []) (Authenticated sender: rgm@htt-consult.com) by klovia.htt-consult.com (Postfix) with ESMTPSA id F045D62A78 for <hipsec@ietf.org>; Thu, 31 Mar 2011 15:37:10 -0400 (EDT)
Message-ID: <4D94D7E4.5010701@htt-consult.com>
Date: Thu, 31 Mar 2011 21:37:08 +0200
From: Robert Moskowitz <rgm@htt-consult.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Thunderbird/3.1.9
MIME-Version: 1.0
To: HIP <hipsec@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [Hipsec] Need to clarify HIT prefix
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, 31 Mar 2011 19:36:19 -0000

WHAT is the prefix used in HIPv1 (RFC 5201)?

RFC 4843 states:

    Prefix          : A constant 28-bit-long bitstring value

But 4843-bis states:

    IANA allocated a temporary non-routable 28-bit prefix from the IPv6
    address space.  By default, the prefix will be returned to IANA in
    2014, continued use requiring IETF consensus.  As per [RFC4773], the
    28-bit prefix was drawn out of the IANA Special Purpose Address
    Block, namely 2001:0000::/23, in support of the experimental usage
    described in this document.  IANA has updated the IPv6 Special
    Purpose Address Registry.

There is NOTHING in the IANA registry about any assignment.  But as I 
plowed through the iana assignment information, I found:


[9]    3FFE:831F::/32 was used for Teredo in some old but widely
         distributed networking stacks. This usage is deprecated in 
favour of 2001::/32,
         which was allocated for the purpose in [RFC4380]

And sure enough in 4380:

2.6. Global Teredo IPv6 Service Prefix

    An IPv6 addressing prefix whose value is 2001:0000:/32.

 From this I MIGHT infer that Teredo is stepping within HIP's ORCHID 

Obviously this needs some clarification (at least for me!)


IANA needs to put in the registry what HIPv1 is using, and then make 
sure that the HIPv2 prefix is publicized.