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

"Templin (US), Fred L" <> Thu, 15 October 2020 21:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E6BB33A082F; Thu, 15 Oct 2020 14:25:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Status: No, score=-2.1 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_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id zX2fMI9G6A3W; Thu, 15 Oct 2020 14:25:14 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EF8583A07F9; Thu, 15 Oct 2020 14:25:13 -0700 (PDT)
Received: from localhost (localhost []) by (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 09FLPBV9030303; Thu, 15 Oct 2020 17:25:11 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=boeing-s1912; t=1602797111; bh=nM6cqr1CgIFiUix80XBgLSzzX+lYH8ifrlDti1ZK7eU=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=Pt/1pIRL+4KIgvLKBTXW6HCNOOiZ6CgSdxT2FsXBXNKaB6KFoIZXCCqYPwAx7vmsn JxDZl6zkpKuVAayMe4OP56/cylMlUyMrT+2uDCm1xyNnv5AL+D2QZ2v0Q2ndFRykKS 9P4PBMXmh619vugDTpoJ5B8/axy11DBsd/C/DlLheCu739Lm4iZ8MeLvW38jryEDfY PWtJwJiBTMlPevUCdCKnlrl72aiQ9FkhFTtoBdbEExCJu+99fAkRRVatH3wtK1hXAy SUZvZWSWYcg8PSyDcj3/0Bi5tZBMqquDgVjqMu7TlP3xv2Roq1m3slEnJkEpie2Wq7 5e0DzfXRjaRKg==
Received: from ( []) by (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 09FLOxag028568 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 15 Oct 2020 17:24:59 -0400
Received: from ( by ( 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 14:24:58 -0700
Received: from ([fe80::1522:f068:5766:53b5]) by ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.2044.004; Thu, 15 Oct 2020 14:24:58 -0700
From: "Templin (US), Fred L" <>
To: Bob Hinden <>
CC: =?utf-8?B?T2xlIFRyw7hhbg==?= <>, IPv6 List <>, "" <>
Subject: RE: Embedding IP information in an IPv6 address (OMNI)
Thread-Topic: Embedding IP information in an IPv6 address (OMNI)
Thread-Index: AdajMsD1xD3hGdlTThaXSslc4Lj72wABksWA
Date: Thu, 15 Oct 2020 21:24:58 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
x-tm-snts-smtp: 39CC56B5031305B7EC519F9667523A4A7CB4EC2840B4095970C2972D371717E82000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 15 Oct 2020 21:25:16 -0000

A bit more to this:

> I think that may be due to the fact that we have only examined a few fundamental
> aspects of the architecture, and there is more to it than what has been discussed
> so far - a *lot* more.  For instance, the reason for wanting both LLAs and SLAs is so
> that we can use overlay "L2 bridging" to join disjoint Internetworks together as
> though they were one big bridged campus LAN. For example, in civil aviation there
> are many network service providers including ARINC, SITA, Inmarsat and others and
> each runs their own networks as an independent entity. But, an aircraft connected
> to ARINC may need to communicate with an air traffic controller in SITA. OMNI then
> views each of the providers as a link *segment* and bridges the segments using
> RFC2473 encapsulation with SLAs and BGP router peerings between the providers.
> The IPv6 layer then sees this bridged arrangement as a single, connected IPv6 link
> and the aircraft and ATC can communicate as peers on the link even though they
> are located in different provider networks in the underlay.

It is important to understand that the RFC2473 encapsulation I am referring to is
a "mid-layer" encapsulation and not the outermost encapsulation. When joining
multiple providers as I have said above, the SLAs are not routable in the public
Internet; only public IP addresses are routable within that realm. The OMNI
approach fully understands this, and therefore the RFC2473 encapsulation I am
referring to occurs as a *mid-layer* encapsulation and not the outermost
encapsulation. The outer encapsulation would use public IP addresses and some
form of security like IPsec or Wiregurad. So what we would end up with is:

  1) an inner IPv6 packet with GUA or LLA addresses
  2) a mid-layer RFC2473 encapsulation IPv6 header with SLA addresses
  3) an outer encapsulation IP header with public addresses plus any security codes