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

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Thu, 15 October 2020 18:14 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 88A193A0E7D; Thu, 15 Oct 2020 11:14:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.397
X-Spam-Level:
X-Spam-Status: No, score=-4.397 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_DNSWL_MED=-2.3, 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 WgJQ77bjKp9U; Thu, 15 Oct 2020 11:14:17 -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 EF6753A0E7A; Thu, 15 Oct 2020 11:14:16 -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 09FIEBDY020231; Thu, 15 Oct 2020 14:14:13 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1602785654; bh=EQjid1IDtGCRkXviHo+RKTSbwHDhtrff5a5O6Nbc7fs=; h=From:To:CC:Subject:Date:From; b=T/5Fl5IVbw7faMn+ZxhHN+bb8MgNWAtXnNsrupxtGTGR4bnS1EtrA0Nu0MyVTOj5T l63DzYWP1pfVm9SgCv6cKTGpW2YZl2wwSLrmEFuszwGeyRECVVsL3JqAgWDRpHy13r yRjNbQlxVg6MUX7ppShrVpf9qeqWAvdYAorvLydW8RJD322u8ccGV1dsQJSsAqqASD iATJBr4fZN61Oq+y1uy6g4Ua3bugAoZT+WCeQeXtIkVOYLepkVQtkTNUZ1/Zve+PfT IrLLH0oit4fkhxGJzMewgWvfQteAFgLfK2aIq5ZlyZXTP829ahnX2HEwNV2/KtA2LW z/2P0I8Uv1s/Q==
Received: from XCH16-07-07.nos.boeing.com (xch16-07-07.nos.boeing.com [144.115.66.109]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 09FIE7P1019377 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 15 Oct 2020 14:14:07 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-07.nos.boeing.com (144.115.66.109) 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 11:14:06 -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 11:14:06 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "otroan@employees.org" <otroan@employees.org>
CC: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>, 6man WG <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: AdajHr2v6kRDBKobS0SrVaj++JwD+A==
Date: Thu, 15 Oct 2020 18:14:06 +0000
Message-ID: <3452a374e8df4fa197eda4940cd52c35@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: 31532DE6C3DCD3BDCCF55DE29B0BC208C6C3A30588FFB8E2508C29BA8CF1C50C2000: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/QV9OzfWq__myqb9MzDA1BDNNcr8>
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 18:14:20 -0000

Hi Ole,

> -----Original Message-----
> From: otroan@employees.org [mailto:otroan@employees.org]
> Sent: Thursday, October 15, 2020 10:40 AM
> To: Templin (US), Fred L <Fred.L.Templin@boeing.com>
> Cc: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>om>; 6man WG <ipv6@ietf.org>rg>; atn@ietf.org
> Subject: Re: [atn] [EXTERNAL] Re: Embedding IP information in an IPv6 address (OMNI)
> Fred,
> 
> > There are many reasons why I like what we have already, but one that I will point out
> > is the ease of constructing a routable OMNI site-local address (SLA) from a non-routable
> > OMNI link-local address (LLA). For an OMNI LLA such as fe80:2001:db8:1:2:: all that is
> > needed to turn it into an OMNI SLA is to set bit #9 to yield fec0:2001:db8:1:2::. That is
> > computationally very simple and allows a single-bit translation between LLAs and SLAs
> > (to get an LLA, clear bit #9 and to get an SLA se bit #9). If instead the LLA had the
> > embedded prefix in bits 64 thru 127, the translation between SLAs and LLAs would
> > be much more expensive.
> 
> 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.

Thanks - Fred

> Cheers,
> Ole=