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

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Mon, 19 October 2020 16:41 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 6EFC03A0C82; Mon, 19 Oct 2020 09:41:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level:
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[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 XnfC9JRjTtbU; Mon, 19 Oct 2020 09:41:07 -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 DBA443A0C7E; Mon, 19 Oct 2020 09:41:06 -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 09JGf2R7021525; Mon, 19 Oct 2020 12:41:04 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1603125665; bh=C1N6uvTjx73NVJI6lQKwBbp0yhrDH2YwdIqM85eP0eU=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=mnrpGpZG/iVM87lMD+729rp60MKX08tYgEwLUwHgsU+uhsgekAkTn9dxMkSjQtEPN S+1qI9D8RENdvqBcEFtecohtxgMsTOIRAYPdRbyElFHT0/wBvlFzJW5yhmNga0n5Gt VF17g+E/9cDISUrymCJCF5Xz32AXAnhSSqzfHCraOgHePl8AOFWJjUuXB7ATGdFLAy GuAAAUZgECTFsWs1yUiOo9OerxPoH4vQvQmAoEk5s7pDAVz1WmUaJ01K5N3qJDNWDA HT/1VKqyRCy3G77Ns7PbvP4K6e+91hWuCNZR0UTis5h4aMyoHvinMl1p5b1TeC8EEf SfUf2kXBjWHAg==
Received: from XCH16-01-11.nos.boeing.com (xch16-01-11.nos.boeing.com [144.115.66.39]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 09JGes6S020314 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Mon, 19 Oct 2020 12:40:54 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-01-11.nos.boeing.com (144.115.66.39) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Mon, 19 Oct 2020 09:40:53 -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; Mon, 19 Oct 2020 09:40:53 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Bob Hinden <bob.hinden@gmail.com>
CC: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>, =?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: AdamGxsTxD3hGdlTThaXSslc4Lj72wAGYdDg
Date: Mon, 19 Oct 2020 16:40:53 +0000
Message-ID: <d4d270dfac7d4f8f8296582e4fd54fbc@boeing.com>
References: <093fce506718470bb147e2eefbf02b42@boeing.com>
In-Reply-To: <093fce506718470bb147e2eefbf02b42@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: 5704DE2A82D3B71CD7E100C1F5EC46C5F48D810A701A4D090467101FF800BA4E2000: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/ETU5Y9ijeBDPbELJcMhXNt6lo60>
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: Mon, 19 Oct 2020 16:41:12 -0000

Bob,

> > There are very good reasons why SLA were deprecated, I don’t see a reason to change that.  ULAs are intended to replace the use
> of
> > SLAs.
> 
> OMNI Is a good reason to re-instate SLAs. OMNI will also want to use ULAs, but for
> other and non-overlapping purposes.

Before this discussion goes too much further, I want to point out that the term "SLA"
has never been used in association with "Site Local Address" prior to the use in OMNI
and these current list discussions; the term was introduced by me, but I would not like
for it to retroactively refer to "site" because it never has before in the past. So, I would
like to propose that we break that connection starting now.

What OMNI needs is an address range that is unique within the scope of a layer-2
spanning tree manifested by a service that joins together the segments of a
(segmented) link. So, I propose we rename fec0::/10 for its use in OMNI as one
of the following:

"Spanning-tree Local Addresses (SLA)"
"Service Local Addresses (SLA)"
"Segment Local Addresses (SLA)"

The term "site" is not relevant to OMNI and would no longer be used in that
context (once we submit a document update, that is). Would that address
the concern?

Thanks - Fred