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

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Wed, 14 October 2020 15:26 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 7E8963A0F4C; Wed, 14 Oct 2020 08:26:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_H4=0.001, RCVD_IN_MSPIKE_WL=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 adGg7eLwOf4u; Wed, 14 Oct 2020 08:25:34 -0700 (PDT)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (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 A8B793A0F3C; Wed, 14 Oct 2020 08:25:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 09EFPTu7024657; Wed, 14 Oct 2020 11:25:30 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1602689130; bh=zenTT2++2QNFCGPyWFSr9urgMkVL1Fjha6/NvgDo59M=; h=From:To:Subject:Date:References:In-Reply-To:From; b=Zs7jPCYoY0zpbA/SLZm5H0+5jMPwBzunxMUNnWWiPBU6CGHiKpmyN1Wv6+o7exjWL EvPXKX+2hDAoZCLa1MTyJa27bW2tlrKrvdM68IwkDaIyvmRiKbKzcaBbTHzZ/eNVNj leLTJhVhXyffIDEcMuxQ4NBKEfu+WL/cYCp6qluPl8jk2sisrZdlEX6XpXtRmUePVa 4iJv6pHPhr1wQhF4gb7fz+yZ6QK6tYvsAKpjYPj7Fb9uvZf+yYbHrcTvHScdGwHW8s HgU+kAihWMeHWazug+/NXPntrvxRy7oowm76zVuTrPnU+UgIofQ8mtcWcNhaf1lzJB zgz/wWCSCxglQ==
Received: from XCH16-07-09.nos.boeing.com (xch16-07-09.nos.boeing.com [144.115.66.111]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 09EFPPjm024333 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Wed, 14 Oct 2020 11:25:26 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-09.nos.boeing.com (144.115.66.111) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Wed, 14 Oct 2020 08:25:24 -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; Wed, 14 Oct 2020 08:25:24 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fgont@si6networks.com>, 6man <ipv6@ietf.org>, "atn@ietf.org" <atn@ietf.org>
Subject: RE: [EXTERNAL] Re: Embedding IP information in an IPv6 address (OMNI)
Thread-Topic: [EXTERNAL] Re: Embedding IP information in an IPv6 address (OMNI)
Thread-Index: AdaeYhXTsIxJjBX3TKG3GOD4Nt9lNgECC1GAAAsux4A=
Date: Wed, 14 Oct 2020 15:25:24 +0000
Message-ID: <5ae440c047db4b51811a00fd5dd15e3a@boeing.com>
References: <c068f71229404b3693b977ca7cde828f@boeing.com> <739bc23a-c48d-4791-be06-4f972b4699d8@si6networks.com>
In-Reply-To: <739bc23a-c48d-4791-be06-4f972b4699d8@si6networks.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: 8AB7E6B1E7CFB6FF33B159F3860CB47981BB5622740483B05927EC8A70BFC6402000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/J_5WtbTu_TfztPXt1scYmwBi7Ro>
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 15:26:07 -0000

Fernando,

We really do want to define the link-local address format for OMNI interfaces.
Too many things depend on every IPv6 interface configuring a unique link-local
address. The address format and the means by which it is assured unique is what
we want to specify for OMNI in an "IPv6-over-foo"-specifc document.

Thanks - Fred

> -----Original Message-----
> From: Fernando Gont [mailto:fgont@si6networks.com]
> Sent: Wednesday, October 14, 2020 6:41 AM
> To: Templin (US), Fred L <Fred.L.Templin@boeing.com>om>; 6man <ipv6@ietf.org>rg>; atn@ietf.org
> Subject: [EXTERNAL] Re: Embedding IP information in an IPv6 address (OMNI)
> 
> This message was sent from outside of Boeing. Please do not click links or open attachments unless you recognize the sender and
> know that the content is safe.
> 
> 
> 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
> 
> 
>