Re: [Hipsec] Need to clarify HIT prefix
Julien Laganier <julien.ietf@gmail.com> Fri, 15 April 2011 10:40 UTC
Return-Path: <julien.ietf@gmail.com>
X-Original-To: hipsec@ietfc.amsl.com
Delivered-To: hipsec@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id D072AE06AD for <hipsec@ietfc.amsl.com>; Fri, 15 Apr 2011 03:40:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iDQ94o3vDNoq for <hipsec@ietfc.amsl.com>; Fri, 15 Apr 2011 03:39:59 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfc.amsl.com (Postfix) with ESMTP id 458D3E0689 for <hipsec@ietf.org>; Fri, 15 Apr 2011 03:39:59 -0700 (PDT)
Received: by fxm15 with SMTP id 15so2001873fxm.31 for <hipsec@ietf.org>; Fri, 15 Apr 2011 03:39:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=xl2vBmKswUwH4+KFVtEBKD2CG0q6Mm34UP69X8oyKN8=; b=hx3OmAtny4PmwqrW1HWlM9dFXdEwKOI8Jt6NChSaASxWT4ZdfLsLO5d6I1lxzV/GN3 nFlrp5lQg4TgECJ0cHEm8kQWxUqM4NgpRXh09KvEXDg/RfYZlRPIxFlYrVx8Scld8Yf5 Q60uHZdUAKSimx4TfcrHVpRs70+GuExVOpk6c=
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
Received: by 10.223.97.142 with SMTP id l14mr1945520fan.111.1302863995655; Fri, 15 Apr 2011 03:39:55 -0700 (PDT)
Received: by 10.223.87.1 with HTTP; Fri, 15 Apr 2011 03:39:55 -0700 (PDT)
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
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.12
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/options/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, 15 Apr 2011 10:40:01 -0000
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> wrote: > http://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-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: >> >> 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! >> >> 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] Need to clarify HIT prefix Robert Moskowitz
- Re: [Hipsec] Need to clarify HIT prefix Samu Varjonen
- Re: [Hipsec] Need to clarify HIT prefix Samu Varjonen
- Re: [Hipsec] Need to clarify HIT prefix Gonzalo Camarillo
- Re: [Hipsec] Need to clarify HIT prefix Julien Laganier
- Re: [Hipsec] Need to clarify HIT prefix Julien Laganier
- Re: [Hipsec] Need to clarify HIT prefix Robert Moskowitz
- Re: [Hipsec] Need to clarify HIT prefix Robert Moskowitz