Re: [Hipsec] The HIT prefix once again (was Re: Re: Type 1 and 2 HITs)
Pekka Nikander <pekka.nikander@nomadiclab.com> Sat, 30 July 2005 19:15 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dywo1-0005i3-Eb; Sat, 30 Jul 2005 15:15:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dywnz-0005ho-JE for hipsec@megatron.ietf.org; Sat, 30 Jul 2005 15:15:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24556 for <hipsec@ietf.org>; Sat, 30 Jul 2005 15:15:29 -0400 (EDT)
Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DyxJt-0005rf-Ge for hipsec@ietf.org; Sat, 30 Jul 2005 15:48:30 -0400
Received: from n2.nomadiclab.com ([193.234.219.2]) by mx2.foretec.com with esmtp (Exim 4.24) id 1Dywns-0002LP-8J for hipsec@ietf.org; Sat, 30 Jul 2005 15:15:24 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id BB768212C72; Sat, 30 Jul 2005 22:09:45 +0300 (EEST)
In-Reply-To: <200507300838.j6U8coY7001856@givry.rennes.enst-bretagne.fr>
References: <200507300838.j6U8coY7001856@givry.rennes.enst-bretagne.fr>
Mime-Version: 1.0 (Apple Message framework v733)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <452C95C4-1813-4B6B-B394-1FCF9469D197@nomadiclab.com>
Content-Transfer-Encoding: 7bit
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: Re: [Hipsec] The HIT prefix once again (was Re: Re: Type 1 and 2 HITs)
Date: Sat, 30 Jul 2005 21:09:43 +0200
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
X-Mailer: Apple Mail (2.733)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit
Cc: hipsec@ietf.org
X-BeenThere: hipsec@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/hipsec>
List-Post: <mailto:hipsec@lists.ietf.org>
List-Help: <mailto:hipsec-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@lists.ietf.org?subject=subscribe>
Sender: hipsec-bounces@lists.ietf.org
Errors-To: hipsec-bounces@lists.ietf.org
Francis, > HIP is not the only protocol which could take avantage from > a dedicated prefix marked as not an address/not routable. > I wrote a short I-D draft-dupont-ipv6-cgpref-01.txt which could > work for at least HIP and a TMSI-like location privacy solution > for MIPv6. I consulted IANA at an IETF meeting just before writing > the first version.... > > I believe it could be better to share the prefix with other (and > with weaker requirements) usages, i.e., to win one bit (2 x) at the > cost of 1/8?... > > so you need an I-D. IMHO it will be easier with a short one than > with an "en passant" paragraph in a HIP architecture one.... > > PS: if you agree to join us, we can ask the IPv6 WG chairs to poll > the IPv6 WG about a WG item. I can't see technical concerns so it > should be easy and the discussion (in the mailing list about the > WG item) should only be about the length of the prefix. In principle, I think it would be good to join forces, and at least make the cases at the same time rather than one after another. However, what HIP needs now is an experimental prefix which, IMHO, should have a default timeout after which it is returned to IANA unless the IETF decides otherwise. I don't know what are your desires w.r.t the time frame for the prefix, i.e., whether you are trying to get a permanent prefix or just an assignment that would be returned unless the IETF decides otherwise. There also may be differences in whether the prefix is supposed to ever get out in IPv6 headers. In the HIP case it is not, i.e., it is supposed to appear only in HIP control packets in the network. IMHO those two issues may make a big difference that may also have affect to the length of the prefix that the IPv6 WG and the IETF are willing to issue. --Pekka _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec
- [Hipsec] Type 1 and 2 HITs Julien Laganier
- [Hipsec] Re: Type 1 and 2 HITs Pekka Nikander
- RE: [Hipsec] Re: Type 1 and 2 HITs Henderson, Thomas R
- [Hipsec] The HIT prefix once again (was Re: Re: T… Pekka Nikander
- Re: [Hipsec] The HIT prefix once again (was Re: R… Francis Dupont
- Re: [Hipsec] The HIT prefix once again (was Re: R… Pekka Nikander
- Re: [Hipsec] The HIT prefix once again (was Re: R… Francis Dupont
- Re: [Hipsec] The HIT prefix once again Pekka Nikander
- Re: [Hipsec] The HIT prefix once again Francis Dupont
- Re: [Hipsec] The HIT prefix once again Bob Hinden
- [Hipsec] Type 1 and 2 HITs Petri Jokela