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

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Thu, 15 October 2020 19:10 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 B97F33A1183; Thu, 15 Oct 2020 12:10:53 -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 qyUIVnErwR0s; Thu, 15 Oct 2020 12:10:52 -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 27DF33A1181; Thu, 15 Oct 2020 12:10:52 -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 09FJAlKf002088; Thu, 15 Oct 2020 15:10:49 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1602789050; bh=USNDsGnT1eSfZ1vEjwX3qgriHyik1nkyrisXs2k/J6U=; h=From:To:CC:Subject:Date:From; b=fDVLy4EKskuOaeyk4ludPwQAX06Vc/UIc8vHDgEicABSImHjRipfX3/ne0NaGFUai gDm5LGdwvtyKVLt3meXwsxO7odZCVBIgCCdgs6IDtepTifYFzffxBItNb1jFEoaFdo nO2Our7+yO+LUfZDc5zhDFfjqSFxRaeUtpNzY6mfIWenHmKuLNgYGNQ46JmgGg0f1t 9T28ED7JJSdNyVwamQDyByL780Mj/kglxYEpgovVK/Z+/p+Qb5N5grqN4Nm9gelNcP AUNQAqYnc7V5Y9KnG17vuT6oGaU5nR5svgWhhCXXpsHCj9Gwd7cXAWboNDLCDkBsa5 cABru541FnPxQ==
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 09FJAiVF002078 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 15 Oct 2020 15:10:44 -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; Thu, 15 Oct 2020 12:10:43 -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; Thu, 15 Oct 2020 12:10:43 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Bob Hinden <bob.hinden@gmail.com>
CC: =?utf-8?B?T2xlIFRyw7hhbg==?= <otroan@employees.org>, IPv6 List <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: AdajJf5j6kRDBKobS0SrVaj++JwD+A==
Date: Thu, 15 Oct 2020 19:10:43 +0000
Message-ID: <95763ccac7f64f0fa61bfe72c5bfd926@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: 2B59001D553BA3B4101720E8FAE35EB6B241EAA371751D2AB84FC027B18005F62000: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/Htb2tgz-06D-USrG4AgRd569Juo>
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: Thu, 15 Oct 2020 19:10:54 -0000

Bob,

> -----Original Message-----
> From: Bob Hinden [mailto:bob.hinden@gmail.com]
> Sent: Thursday, October 15, 2020 11:43 AM
> To: Templin (US), Fred L <Fred.L.Templin@boeing.com>
> Cc: Bob Hinden <bob.hinden@gmail.com>om>; Ole Trøan <otroan@employees.org>rg>; IPv6 List <ipv6@ietf.org>rg>; atn@ietf.org
> Subject: Re: Embedding IP information in an IPv6 address (OMNI)
> 
> Fred,
> 
> > On Oct 15, 2020, at 11:40 AM, Templin (US), Fred L <Fred.L.Templin@boeing.com> wrote:
> >
> >>>>>
> >>>>
> >>>> The use of site locals also sets limitations of addressing/routing in the underlay.
> >>>
> >>> This is rather about addressing/routing in the *overlay*.
> >>>
> >>>> With regards to performance. Is the conversion between SLA/LLA something you do per packet?
> >>>> If not, I'm unsure I see why optimising that is beneficial.
> >>>
> >>> Per-packet - a simple bit-flip changes the address from SLA to LLA or vice-versa.
> >>
> >> Umm, that would break the transport protocol checksum.
> >
> > Good point, and that brings into focus the need for RFC2473 encapsulation.
> > If you want a packet with IPv6 link-local addresses (LLAs) to go more than
> > one hop, encapsulate it in an IPv6 header with the same LLAs and then
> > flip the bit to turn them into SLAs. Then, present the (encapsulated) packet
> > to the IPv6 overlay routing system.
> 
> If you want the packets to go more than one hop, then don’t use link-local addresses.

That circles us right back to the subject of how RFC4861 is intrinsically tied to
the use of link-local address and the fact that all IPv6 interfaces are required
to configure a unique link-local address. It would be a bear to try to change
that, so OMNI employs RFC2473 encapsulation instead of trying to override
the bedrock IPv6 standards. The use of RFC2473 encapsulation also brings
other important benefits.

Fred

> Bob
>