IETF Logo Mail Archive

Re: [6gip] IP Address Mobility project

Robert Moskowitz <rgm@htt-consult.com> Wed, 08 February 2023 20:19 UTC

Return-Path: <rgm@htt-consult.com>
X-Original-To: 6gip@ietfa.amsl.com
Delivered-To: 6gip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3C1CC151544 for <6gip@ietfa.amsl.com>; Wed, 8 Feb 2023 12:19:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4pz1WqIDncQP for <6gip@ietfa.amsl.com>; Wed, 8 Feb 2023 12:19:51 -0800 (PST)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29495C14CF18 for <6gip@ietf.org>; Wed, 8 Feb 2023 12:19:50 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id D21D662434; Wed, 8 Feb 2023 15:19:18 -0500 (EST)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id friMG0OJ860b; Wed, 8 Feb 2023 15:19:13 -0500 (EST)
Received: from [172.20.1.178] (unknown [12.52.57.66]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 4A667625FC; Wed, 8 Feb 2023 15:19:11 -0500 (EST)
Content-Type: multipart/alternative; boundary="------------QZ3mLinTRI3QiSXGXLCoB5ul"
Message-ID: <086bc17a-dcdd-77dd-be6b-77c2f50985a5@htt-consult.com>
Date: Wed, 08 Feb 2023 15:19:39 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0
Content-Language: en-US
To: Hesham ElBakoury <helbakoury@gmail.com>, sarikaya@ieee.org
Cc: Luigi Iannone <ggx@gigix.net>, Dino Farinacci <farinacci@gmail.com>, Ca By <cb.list6@gmail.com>, 6gip@ietf.org, rgm@labs.htt-consult.com
References: <DBAPR06MB68551330133B1A3C347A2D9BB5C19@DBAPR06MB6855.eurprd06.prod.outlook.com> <8d85fba9-9c96-93a5-6602-bd816605a9db@gmail.com> <CAC8QAcfQYKQRDBme-kBe9gwMrmzY3w9TUjHoWgAU6yevuLwMiA@mail.gmail.com> <0a1a500a-1b83-d546-fb0d-902e0037368e@gmail.com> <CAC8QAceGR-NFH77hopfU7CKdwj5qjKnifOstazEo6z3VEkeL4Q@mail.gmail.com> <9EFAD01C-DB5F-48FA-807D-AA184CEF9BCE@gmail.com> <f6f0ce45-969a-a2bc-e4bf-1485559c3661@gmail.com> <CAC8QAcfrgDzsb3P5OuatQLULkFnTv34RdMs-ZHUB_g1oHRxFhQ@mail.gmail.com> <CAC8QAcfPeevi8Gd8f1iizgxDBTHeARWbNhfkEMeb1dd9+qkZ9g@mail.gmail.com> <CD62FB99-9EBF-4954-8D17-FB453ADCA660@gigix.net> <CAD6AjGSfkmw_64do8fgDfeZC_upu6ncP_WAgLbQytU0mj4ip-g@mail.gmail.com> <3D62C7B3-C2C4-431C-9A84-68FF197822E4@gigix.net> <DC506A2B-B89C-4B4E-A6B6-2A2935D9AF4F@gmail.com> <939C9FC6-3E4E-4446-BB4E-39C20114B0C2@gigix.net> <CAC8QAcdvjjOxKC=MYrHBAR7235iaA0qLp8VeZ9SrBCM3Zpk5BA@mail.gmail.com> <CAFvDQ9qBeGzRxyj_4G12dwh1U+zK_PqTmgR_qxciNvymY5aRbA@mail.gmail.com>
From: Robert Moskowitz <rgm@htt-consult.com>
In-Reply-To: <CAFvDQ9qBeGzRxyj_4G12dwh1U+zK_PqTmgR_qxciNvymY5aRbA@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/6gip/6sYZSFTkuxn90YvZ3pcHX8avlQ4>
Subject: Re: [6gip] IP Address Mobility project
X-BeenThere: 6gip@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IP Issues in 6th Generation Mobile Network System \(6gip\)" <6gip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6gip>, <mailto:6gip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6gip/>
List-Post: <mailto:6gip@ietf.org>
List-Help: <mailto:6gip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6gip>, <mailto:6gip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2023 20:19:54 -0000

I have not been following this thread.  I am over committed in 
aviation.  The DRIP work is just a small piece of what I am doing.

That said, I have a strong future for HIP in aviation in a lot of use 
cases as we get the DRIP Device Entity Tag (DET) into use, not just for 
unmanned, but also general aviation via the ICAO Trust Framework Panel 
(why I will not be at IETF116).

DETs are in https://datatracker.ietf.org/doc/draft-ietf-drip-rid/ which 
is now in the RFC editor queue for publication.

IANA has assigned an IPv6 prefix for DETs.

As DETs add the hierarchy of registration into HITs, as I originally 
wanted for HIP, it scales nicely and DETs can be used in HIP or DTLS, 
and probably QUIC.

So HIP is there.  HHITs, as defined in DRIP improve on HITs.  Once DETs 
are used for aircraft trusted Identifiers, it is reasonable to see them 
used more generally.

Bob

On 2/8/23 12:20, Hesham ElBakoury wrote:
> This Wikipedia article describes HIP: 
> https://en.m.wikipedia.org/wiki/Host_Identity_Protocol
>
> I added Rob to the thread to comment on the fate of HIP.
>
> Hesham
>
>
>
> On Wed, Feb 8, 2023, 9:05 AM Behcet Sarikaya <sarikaya2012@gmail.com> 
> wrote:
>
>     Hi Luigi,
>
>     On Wed, Feb 8, 2023 at 5:09 AM Luigi Iannone <ggx@gigix.net> wrote:
>
>
>
>         > On 7 Feb 2023, at 21:59, Dino Farinacci
>         <farinacci@gmail.com> wrote:
>         >
>         >> Because IP is the central point of our hourglass, if we
>         solve mobility there we solve it for everything above L3.
>         >> Is this line of thought 90s… yes ;-)
>         >
>         > But the way it was solved was problematic. The address the
>         host used would be assigned from a locator subnet. That's
>         broken because what if the subnet no longer exists. You need
>         an EID out of a block that is not in the underlying routing
>         system. Just like foobar@gmail.com.
>
>         This sounds like HIP. I am not too familiar with HIP, I assume
>         there are mobility solutions for HIP, but we end up to the
>         same question: why did not fly?
>         (Pointer welcome ;-) )
>
>
>     HIP is transport layer.
>     I am not sure if Bob (Robert Moskowitz) is in this list
>
>     Behcet
>
>
>         L.
>
>
>
>         >
>         > Dino
>         >
>
>     -- 
>     6gip mailing list
>     6gip@ietf.org
>     https://www.ietf.org/mailman/listinfo/6gip
>
>

v2.23.0 | Report a Bug | By Email