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

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Thu, 15 October 2020 18:40 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 554BA3A12CF; Thu, 15 Oct 2020 11:40:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
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: 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 elFOIv-ukmA1; Thu, 15 Oct 2020 11:40:41 -0700 (PDT)
Received: from clt-mbsout-01.mbs.boeing.net (clt-mbsout-01.mbs.boeing.net [130.76.144.162]) (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 41C853A12D4; Thu, 15 Oct 2020 11:40:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 09FIebQo027389; Thu, 15 Oct 2020 14:40:38 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1602787238; bh=s9nmbjSzkVl0tFlc6zHhE3yIBVqvfkzE7OrNWWxsuEI=; h=From:To:CC:Subject:Date:From; b=VJBv44yfUaY7mRqV+FCPpVv4rC6DskN6khqW90hgP2h75PjOsN6vLSTy9mHn9TTMd VtvynZQOMV4u3nich/CWlMpyd70K7mnNIOfHYqKPdS3LIanG56oXs4LvAeDaUuJJVO sXNldoraY671sItm+hAnnilPQZ69jvxRL6OGS6sf0+f9XlJ2qJcVZixfsJbLET4z6x FwLXYqtJb4Tu7qBUvjjhQm8l3rpQGPjqd3nPJZ+t44zK96tFrbbF8UD42Lkvik0c+5 7BQQCNk7Vbpci0rYp1f82ps6wlgzmQAmbhiB0638IkqwtmJA4JibgDi1OCXuuCqvwV QUdBpJeVW/G9w==
Received: from XCH16-07-08.nos.boeing.com (xch16-07-08.nos.boeing.com [144.115.66.110]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 09FIeQf3026268 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 15 Oct 2020 14:40:26 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-08.nos.boeing.com (144.115.66.110) 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:40:25 -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:40:25 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Bob Hinden <bob.hinden@gmail.com>
CC: =?iso-8859-1?Q?Ole_Tr=F8an?= <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: AdajIgm96kRDBKobS0SrVaj++JwD+A==
Date: Thu, 15 Oct 2020 18:40:25 +0000
Message-ID: <0191a92c5eb24aa3b74fd988852d1056@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: 526C64BC748F09552B147BFEBF328CCB09440C1D77076D84A7BF4C7C5903CC2B2000:8
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/bqOVnQwQP3BuLjS1lWn1lDDkLeo>
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:40:43 -0000

Hi Bob,

> -----Original Message-----
> From: Bob Hinden [mailto:bob.hinden@gmail.com]
> Sent: Thursday, October 15, 2020 11:33 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)
> 
> > On Oct 15, 2020, at 11:14 AM, Templin (US), Fred L <Fred.L.Templin@boeing.com> wrote:
> >
> > 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.
> 
> 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.

Thanks - Fred

> Bob
> 
> 
> >
> > Thanks - Fred
> >
> >> Cheers,
> >> Ole=
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------