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

Fernando Gont <fgont@si6networks.com> Wed, 14 October 2020 14:47 UTC

Return-Path: <fgont@si6networks.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 5667E3A0FA2; Wed, 14 Oct 2020 07:47:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.112
X-Spam-Level:
X-Spam-Status: No, score=-2.112 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.213, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 0vRgo4aVqZuR; Wed, 14 Oct 2020 07:47:20 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50C1D3A0F18; Wed, 14 Oct 2020 07:47:05 -0700 (PDT)
Received: from [IPv6:2800:810:464:b9c:4d77:be33:d267:ab18] (unknown [IPv6:2800:810:464:b9c:4d77:be33:d267:ab18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id B9CC8283B7F; Wed, 14 Oct 2020 14:47:01 +0000 (UTC)
Subject: Re: Embedding IP information in an IPv6 address (OMNI)
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>, 6man <ipv6@ietf.org>, "atn@ietf.org" <atn@ietf.org>
References: <c068f71229404b3693b977ca7cde828f@boeing.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <739bc23a-c48d-4791-be06-4f972b4699d8@si6networks.com>
Date: Wed, 14 Oct 2020 10:40:33 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <c068f71229404b3693b977ca7cde828f@boeing.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/g5efizrloq2kRArmGayXr5Mv9Nw>
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: Wed, 14 Oct 2020 14:47:29 -0000

Hi, Fred,

On 9/10/20 14:45, Templin (US), Fred L wrote:
[...]
> 
> 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.

It would seem to me that such work would have to involve an update of 
RFC4291 if you want to play with the prefix bits, and of RFC7136 if you 
want to play with the IID bits.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492