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

Robert Moskowitz <rgm@labs.htt-consult.com> Fri, 09 October 2020 19:53 UTC

Return-Path: <rgm@labs.htt-consult.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 4D9EE3A151E; Fri, 9 Oct 2020 12:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.111
X-Spam-Level:
X-Spam-Status: No, score=-2.111 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 pJS52uWzQE2h; Fri, 9 Oct 2020 12:53:17 -0700 (PDT)
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 9C89E3A151C; Fri, 9 Oct 2020 12:53:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 65F87625F7; Fri, 9 Oct 2020 15:53:15 -0400 (EDT)
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 akQiMQcZ22F9; Fri, 9 Oct 2020 15:53:07 -0400 (EDT)
Received: from lx140e.htt-consult.com (unknown [192.168.160.29]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 99A2A622FA; Fri, 9 Oct 2020 15:53:05 -0400 (EDT)
Subject: Re: [atn] 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> <79e05326796e4775bfd7f074671ba325@boeing.com>
From: Robert Moskowitz <rgm@labs.htt-consult.com>
Message-ID: <7af0ab36-4a6b-cb44-609c-6e81b364a01c@labs.htt-consult.com>
Date: Fri, 9 Oct 2020 15:52:56 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0
MIME-Version: 1.0
In-Reply-To: <79e05326796e4775bfd7f074671ba325@boeing.com>
Content-Type: multipart/alternative; boundary="------------7084D7479C12440D02FEBF36"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/bNrZAnUUu8LImxEyrXpisSRff2M>
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:53:20 -0000

RFC 8064 updates all recommendations on content of the 64 bit Interface 
portion of IPv6.

Lots of old bad practices in old RFCs.

On 10/9/20 3:10 PM, Templin (US), Fred L wrote:
> 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

-- 
Standard Robert Moskowitz
Owner
HTT Consulting
C:248-219-2059
F:248-968-2824
E:rgm@labs.htt-consult.com

There's no limit to what can be accomplished if it doesn't matter who 
gets the credit