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

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Fri, 09 October 2020 19:11 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 289B63A1433; Fri, 9 Oct 2020 12:11:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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_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 Mj0Uem85FHpJ; Fri, 9 Oct 2020 12:11:04 -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 0694E3A142D; Fri, 9 Oct 2020 12:11:03 -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 099JAwBC011679; Fri, 9 Oct 2020 15:11:01 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1602270661; bh=h8wmQN6DXST/NJInY3jKx8PxuzrB+mrcSngS+V4DY3E=; h=From:To:Subject:Date:References:In-Reply-To:From; b=J31rD4IYjAIKjbf5GprjebT2lO+jQkraZ8XUJC5vC3Jr6w3KlUM4RJBmipk//MOM7 DB6X8TqDVOEhFTKcbeirgAozIPwhrAZL/2Qo9/JRtzcK68lCuF3bSJEeCqLyU2vutd OU/M14QSMYoBfX7Fm6alI443UAHTYEjuGaae5euqDH5DvmNCi/et7tq64JJH8kDrkN cr/kW21zfEwgC1MafiuvQq2EhrYVDjepSoxeShsaXCPo868wQSXB1m/6JQB2Cg/77Z g0AvZVn8/wKQ9VN6d+UzaV/wOQ4jhbgNdR+1b8vUonhPWpyhOak1zSQM3Fa/LKUDCl NrbQ/sE1WB3aQ==
Received: from XCH16-07-08.nos.boeing.com (xch16-07-08.nos.boeing.com [144.115.66.110]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 099JArC3011631 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Fri, 9 Oct 2020 15:10:53 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-08.nos.boeing.com (144.115.66.110) 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 12:10:52 -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 12:10:52 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: 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: AdaeYhXTsIxJjBX3TKG3GOD4Nt9lNgADYQ8Q
Date: Fri, 9 Oct 2020 19:10:52 +0000
Message-ID: <79e05326796e4775bfd7f074671ba325@boeing.com>
References: <c068f71229404b3693b977ca7cde828f@boeing.com>
In-Reply-To: <c068f71229404b3693b977ca7cde828f@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: 7AEDDB4301D136188DA85C1D0FC769D0CC2A9CBA2E78710FCE836125F4C14F7E2000:8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/r-lNQOPfmALjDKWaAlSuw5WNCng>
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 19:11:07 -0000

I forgot to mention RFC4380 which also embeds a *lot* of additional IP information
within the IPv6 address. There may be others I am also forgetting.

Fred

> -----Original Message-----
> From: atn [mailto:atn-bounces@ietf.org] On Behalf Of Templin (US), Fred L
> Sent: Friday, October 09, 2020 10:46 AM
> To: 6man <ipv6@ietf.org>rg>; atn@ietf.org
> Subject: [atn] Embedding IP information in an IPv6 address (OMNI)
> 
> 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
> 
> 
> --
> atn mailing list
> atn@ietf.org
> https://www.ietf.org/mailman/listinfo/atn