Re: Embedding IP information in an IPv6 address (OMNI)

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Fri, 16 October 2020 16:05 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDCF33A0FB9; Fri, 16 Oct 2020 09:05:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=boeing.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8XTo_HNqil38; Fri, 16 Oct 2020 09:05:20 -0700 (PDT)
Received: from clt-mbsout-01.mbs.boeing.net (clt-mbsout-01.mbs.boeing.net [130.76.144.162]) (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 AAAB73A0FBA; Fri, 16 Oct 2020 09:05:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 09GG5GQq006863; Fri, 16 Oct 2020 12:05:16 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1602864316; bh=VTyNu6LV0jpmcaiv5J6Q+T5GbUJc6NFNe6M+GmHnuOs=; h=From:To:CC:Subject:Date:From; b=G1Cgzu4ljmxdw9NWHvxV4GBt6j4jxmPMSDSA3qI/rWd6CcwzsP1j4mVGHgTOpJmXw 3qCHpGicNnHHtgZB8VeI5mhh0DgL945y8nAHx+YgaVFxG3c778bjeA5nRYVLnwXVF3 IiYPs+qpmOLQq4EhizaaiCmKq/3i746dHrMTS/O5DTkE+PZzf6k1IripFZmBMhrWBN +Goj6VOwX+dQcILDjZnR8tfjxyB11PtF0iy8Li9+8/MA0re9OyQK/YNzUnMgV8RHG+ O5sfsAk/MN470pHzy4XJt6ytu/4SkSU7JsphgS8MY28gjBRfynPP+/EBLut32feBIW slD/+0Os21gsw==
Received: from XCH16-07-11.nos.boeing.com (xch16-07-11.nos.boeing.com [144.115.66.113]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 09GG5CIq006431 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Fri, 16 Oct 2020 12:05:12 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-11.nos.boeing.com (144.115.66.113) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Fri, 16 Oct 2020 09:05:11 -0700
Received: from XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5]) by XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.2044.004; Fri, 16 Oct 2020 09:05:11 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "sarikaya@ieee.org" <sarikaya@ieee.org>
CC: 6man <ipv6@ietf.org>, "atn@ietf.org" <atn@ietf.org>
Subject: Re: Embedding IP information in an IPv6 address (OMNI)
Thread-Topic: Embedding IP information in an IPv6 address (OMNI)
Thread-Index: Adaj1fucxD3hGdlTThaXSslc4Lj72w==
Date: Fri, 16 Oct 2020 16:05:10 +0000
Message-ID: <c5dc340f820546ae8510de6dc422d07c@boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: D22AC97ED0DDC97CB8B169F8BF48DFB62CF2157308299CEFEDFB7EA1A7CAD6332000:8
Content-Type: multipart/alternative; boundary="_000_c5dc340f820546ae8510de6dc422d07cboeingcom_"
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/yPJtGRjj_JeX0-ZnEnTUahQntg8>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Oct 2020 16:05:22 -0000

Behcet, OMNI would most certainly be a good fit for StarLink. But, StarLink is just
one example of a data link that OMNI nodes would include in their multilink profiles.

Thanks - Fred

From: Behcet Sarikaya [mailto:sarikaya2012@gmail.com]
Sent: Friday, October 16, 2020 7:40 AM
To: Templin (US), Fred L <Fred.L.Templin@boeing.com>
Cc: 6man <ipv6@ietf.org>rg>; atn@ietf.org
Subject: Re: Embedding IP information in an IPv6 address (OMNI)

Hi Fred,

I am curious whether OMNI is designed with LEO satellite links like StarLink which is being deployed worldwide and
operational partially in North America in mind?

Behcet

On Fri, Oct 9, 2020 at 12:46 PM Templin (US), Fred L <Fred.L.Templin@boeing.com<mailto:Fred.L.Templin@boeing.com>> wrote:
Hi, the OMNI spec defines an IPv6 link-local address format that embeds another
IP address/prefix inside the least significant bits:

https://datatracker.ietf.org/doc/draft-templin-6man-omni-interface/

The idea behind embedding IP information inside an IPv6 address was first published
 in RFC1884 (December 1995) where the "IPv4-compatible" and "IPv4-mapped" IPv6
addresses were defined. (This was the first edition of the IPv6 addressing architecture,
with the latest edition now as RFC4291.) Later, RFC4214 and RFC5214 put a more formal
structuring around embedded IP addresses and RFC5969 even went further to move
the embedded information up into the upper 64 bits of the IPv6 address.

The genesis of the OMNI concept of embedding additional IP information in the IPv6
address was introduced in the "AERO(bis)" draft following the publication of RFC6706.
This format was later cited in RFC7421. Now in the present OMNI draft, we have an
IPv6 link-local address format where embedded IP information begins immediately
after the fe80::/10 prefix thereby utilizing up to 112 available bits for encoding useful
information.

It has come to my attention that some are skeptical about embedded IP information
inside an IPv6 address. But, the OMNI draft shows clear benefits for making use of
these otherwise-wasted bits and follows on from decades-old examples that are
still in use today. Would love to hear everyone's thoughts on this.

Thanks - Fred


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org<mailto:ipv6@ietf.org>
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------