Embedding IP information in an IPv6 address (OMNI)

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Fri, 09 October 2020 17:46 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 1A1BE3A0D5D; Fri, 9 Oct 2020 10:46:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 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, RCVD_IN_DNSWL_BLOCKED=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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id EQkiw2J3XT3A; Fri, 9 Oct 2020 10:46:00 -0700 (PDT)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net []) (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 3DD673A0D5A; Fri, 9 Oct 2020 10:45:56 -0700 (PDT)
Received: from localhost (localhost []) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 099Hjru5031909; Fri, 9 Oct 2020 13:45:54 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1602265554; bh=qEyDPUpJMCkGc8UC1eKOl9A58J0cz27M++3zYa1RaA0=; h=From:To:Subject:Date:From; b=YZY5GXxi+DkDsAspSWAm+ejK8w05qCwnVE0GBsxCAP/AZCmHVFIod6vHTM53fHp8v kvVijirIaiMfZB2KIJ8ezexYjwTlokUBl9AljSt5hG12CsHvGnzTCN038ug/0pKOMW z0k9+2qBHHAOw6TYbOvPoH+PkCL1RJCNEyy9ZeHH/C8g6kSd31AWuB3xh2Oti0hCtb MMjJ56QsTAq0pHOBgMNRqp3KLSCkdjco1cYRwcYbAsBT8OH96xMx71UBPMdHBq0hWU SM84XGg2j71uIIGZbO8UNQA+yKLDN04NRHiLvD3TiQBoE7Dv3EaQxwYI/tsKsGQ1WS zlnBUl7Si4QgA==
Received: from XCH16-07-10.nos.boeing.com (xch16-07-10.nos.boeing.com []) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 099HjqJN031895 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Fri, 9 Oct 2020 13:45:52 -0400
Received: from XCH16-07-10.nos.boeing.com ( by XCH16-07-10.nos.boeing.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Fri, 9 Oct 2020 10:45:51 -0700
Received: from XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8]) by XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8%2]) with mapi id 15.01.2044.004; Fri, 9 Oct 2020 10:45:51 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: 6man <ipv6@ietf.org>, "atn@ietf.org" <atn@ietf.org>
Subject: Embedding IP information in an IPv6 address (OMNI)
Thread-Topic: Embedding IP information in an IPv6 address (OMNI)
Thread-Index: AdaeYhXTsIxJjBX3TKG3GOD4Nt9lNg==
Date: Fri, 9 Oct 2020 17:45:51 +0000
Message-ID: <c068f71229404b3693b977ca7cde828f@boeing.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
x-tm-snts-smtp: 774A4B955CAE296BA21A5DD39517DC2FF371B60AFBF2681400C5E49A24984C902000:8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/pw4EtjSXskNPLK4bXG_9k7LO8NI>
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, 09 Oct 2020 17:46:02 -0000

Hi, the OMNI spec defines an IPv6 link-local address format that embeds another
IP address/prefix inside the least significant bits:


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

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