DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type:content-transfer-encoding;
 b=ovvCze3Q/aFJgOMwSjgIWiBOvizCwFUgSpQci+BnQaoryZYzuGJQkoaiHsd2j7XVOZ
 9cbMeNZvR6EPzyYTuuOYlyXpMghpfX6FqiJH++gGbw3sw6j0rHjmYSEFRWXj1em6wh4N
 tLpV/oEIjzVQCYwgEUWvDunSPSZYouNL27xNU=
MIME-Version: 1.0
In-Reply-To: <BANLkTimAOQQ5n0nOKfs0Of7-L=dPBdr_FA@mail.gmail.com>
References: <4D94D7E4.5010701@htt-consult.com>
 <BANLkTimAOQQ5n0nOKfs0Of7-L=dPBdr_FA@mail.gmail.com>
Date: Fri, 15 Apr 2011 03:39:55 -0700
Message-ID: <BANLkTimMTTMA52-j-RJkJG2yrkqCVsiDxw@mail.gmail.com>
From: Julien Laganier <julien.ietf@gmail.com>
To: Robert Moskowitz <rgm@htt-consult.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: HIP <hipsec@ietf.org>
Subject: Re: [Hipsec] Need to clarify HIT prefix
Precedence: list

and FWIW 2001:10::/28 and 2001:0000::/32 are disjoint.

On Fri, Apr 15, 2011 at 3:36 AM, Julien Laganier <julien.ietf@gmail.com> wr=
ote:
> http://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-spec=
ial-registry.xml
>
> On Thu, Mar 31, 2011 at 12:37 PM, Robert Moskowitz <rgm@htt-consult.com> =
wrote:
>> WHAT is the prefix used in HIPv1 (RFC 5201)?
>>
>> RFC 4843 states:
>>
>> =A0 Prefix =A0 =A0 =A0 =A0 =A0: A constant 28-bit-long bitstring value
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 (2001:10::/28).
>>
>>
>> But 4843-bis states:
>>
>> =A0 IANA allocated a temporary non-routable 28-bit prefix from the IPv6
>> =A0 address space. =A0By default, the prefix will be returned to IANA in
>> =A0 2014, continued use requiring IETF consensus. =A0As per [RFC4773], t=
he
>> =A0 28-bit prefix was drawn out of the IANA Special Purpose Address
>> =A0 Block, namely 2001:0000::/23, in support of the experimental usage
>> =A0 described in this document. =A0IANA has updated the IPv6 Special
>> =A0 Purpose Address Registry.
>>
>> There is NOTHING in the IANA registry about any assignment. =A0But as I =
plowed
>> through the iana assignment information, I found:
>>
>> http://www.iana.org/assignments/ipv6-unicast-address-assignments/ipv6-un=
icast-address-assignments.xml
>>
>> [9] =A0 =A03FFE:831F::/32 was used for Teredo in some old but widely
>> =A0 =A0 =A0 =A0distributed networking stacks. This usage is deprecated i=
n favour of
>> 2001::/32,
>> =A0 =A0 =A0 =A0which was allocated for the purpose in [RFC4380]
>>
>> And sure enough in 4380:
>>
>> 2.6. Global Teredo IPv6 Service Prefix
>>
>> =A0 An IPv6 addressing prefix whose value is 2001:0000:/32.
>>
>> From this I MIGHT infer that Teredo is stepping within HIP's ORCHID
>> allocation!
>>
>> Obviously this needs some clarification (at least for me!)
>>
>> AND
>>
>> IANA needs to put in the registry what HIPv1 is using, and then make sur=
e
>> that the HIPv2 prefix is publicized.
>>
>>
>> _______________________________________________
>> Hipsec mailing list
>> Hipsec@ietf.org
>> https://www.ietf.org/mailman/listinfo/hipsec
>>
>