RE: [EXTERNAL] Re: [atn] Embedding IP information in an IPv6 address (OMNI)

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Fri, 09 October 2020 21:35 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 D7BC13A156E; Fri, 9 Oct 2020 14:35:00 -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 hVJl3aJqSncS; Fri, 9 Oct 2020 14:34:59 -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 5AF3C3A0D4F; Fri, 9 Oct 2020 14:34:59 -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 099LYvA7027479; Fri, 9 Oct 2020 17:34:57 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1602279298; bh=jVr7LxWhd7dj/ukPnCAsabjY8hJhy1pZYdKTd1uVuaE=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=LEsTLGZpgzOJpE3/m3nTzkf7xx9JtFniANBu73GfddU1CwVEhidKiJw01CWLPegjd mwV6jjefwLPk9xq2DajjzSEy9GPry9upv4Ks+0r95oD+QpbCPhsGYgn4YGD4fFruqE MbX01ZvGk3G4IevxY6A1mTssqhGZ+1wJeYUGKjBeA+LB+q/pq1qxIeBs7BGMqe/+g2 /mXdTUNbLb4R6t/aKLFZQmiNoqYHn6NWrtA+1Njn+4C+w0+51IguE2MoMJk63FQBPy Gp/1RJIYACVHDPDeSSe82L3SPn6p1v/asqbjpZVhumRw8D1si8wp7k8q/5VDljxVXM oBJvESZM/AJBg==
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 099LYkpe026430 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Fri, 9 Oct 2020 17:34:46 -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; Fri, 9 Oct 2020 14:34:45 -0700
Received: from XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8]) by XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8%2]) with mapi id 15.01.2044.004; Fri, 9 Oct 2020 14:34:45 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Fred Baker <fredbaker.ietf@gmail.com>, Robert Moskowitz <rgm@labs.htt-consult.com>
CC: 6man <ipv6@ietf.org>, "atn@ietf.org" <atn@ietf.org>
Subject: RE: [EXTERNAL] Re: [atn] Embedding IP information in an IPv6 address (OMNI)
Thread-Topic: [EXTERNAL] Re: [atn] Embedding IP information in an IPv6 address (OMNI)
Thread-Index: AQHWnoMLTQ3goFZI8k6V0haOyYZmuamPyXtg
Date: Fri, 9 Oct 2020 21:34:45 +0000
Message-ID: <026e1f94f9d646f38e6912174998b929@boeing.com>
References: <7af0ab36-4a6b-cb44-609c-6e81b364a01c@labs.htt-consult.com> <8009C8E3-E654-4623-BDC8-F794346C33B1@gmail.com>
In-Reply-To: <8009C8E3-E654-4623-BDC8-F794346C33B1@gmail.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: 78DFFA8A9295EC794E7C279E76240EBA59B79FDAE3FB40EC2D363B030423F8A12000: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/Gw0-r5ibH5c7AKGv9l1E2XK0amg>
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: Fri, 09 Oct 2020 21:35:01 -0000

Fred,

> The concept of embedding information in the 54 “must be zero” bits of the link local address is enticing, but may not prove 
> interoperable, given the “must be zero” definition of a link local address.

Also good input, but given that these link-local addresses are defined and intended
for the exclusive use of a specific IPv6-over-(foo) interface type, only interfaces that
understand the address format will process the addresses and they will understand
the usage of the 54 bits.

Thanks - Fred