Re: [Hipsec] Need to clarify HIT prefix

Samu Varjonen <samu.varjonen@hiit.fi> Fri, 01 April 2011 07:11 UTC

Return-Path: <samu.varjonen@hiit.fi>
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 A065C3A6BF7 for <hipsec@core3.amsl.com>; Fri, 1 Apr 2011 00:11:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 so68uZv7uuav for <hipsec@core3.amsl.com>; Fri, 1 Apr 2011 00:11:29 -0700 (PDT)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by core3.amsl.com (Postfix) with ESMTP id 722A03A6BF3 for <hipsec@ietf.org>; Fri, 1 Apr 2011 00:11:29 -0700 (PDT)
Received: from [192.168.0.10] (cs181123051.pp.htv.fi [82.181.123.51]) by argo.otaverkko.fi (Postfix) with ESMTP id 8E66925EEBE; Fri, 1 Apr 2011 10:13:08 +0300 (EEST)
Message-ID: <4D957AFF.70304@hiit.fi>
Date: Fri, 01 Apr 2011 10:13:03 +0300
From: Samu Varjonen <samu.varjonen@hiit.fi>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; fi; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Robert Moskowitz <rgm@htt-consult.com>
References: <4D94D7E4.5010701@htt-consult.com> <4D95538C.30303@hiit.fi>
In-Reply-To: <4D95538C.30303@hiit.fi>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: HIP <hipsec@ietf.org>
Subject: Re: [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: Fri, 01 Apr 2011 07:11:32 -0000

1.4.2011 7:24, Samu Varjonen kirjoitti:
> 31.3.2011 22:37, Robert Moskowitz kirjoitti:
>> WHAT is the prefix used in HIPv1 (RFC 5201)?
>>
>> RFC 4843 states:
>>
>> Prefix : A constant 28-bit-long bitstring value
>> (2001:10::/28).
>>
>>
>> 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:
>>
>> http://www.iana.org/assignments/ipv6-unicast-address-assignments/ipv6-unicast-address-assignments.xml
>>
>>
>>
>> [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
>> allocation!
>>
>
> There is something similar going on with RFC 3849. The Nit-checker
> complained the following:
>
> "
> == There are 2 instances of lines with non-RFC3849-compliant IPv6 addresses
> in the document. If these are example addresses, they should be changed.
> "
>

Forgot to mention that this happened when the IETF Nit-checker tried to 
check HITs from a draft.

>
>> Obviously this needs some clarification (at least for me!)
>>
>> AND
>>
>> IANA needs to put in the registry what HIPv1 is using, and then make
>> sure that the HIPv2 prefix is publicized.
>>
>>
>> _______________________________________________
>> Hipsec mailing list
>> Hipsec@ietf.org
>> https://www.ietf.org/mailman/listinfo/hipsec
>
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec