IETF Logo Mail Archive

RE: [EXTERNAL] Re: Extending a /64

"Manfredi (US), Albert E" <albert.e.manfredi@boeing.com> Mon, 16 November 2020 23:22 UTC

Return-Path: <albert.e.manfredi@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 6B12D3A166D for <ipv6@ietfa.amsl.com>; Mon, 16 Nov 2020 15:22:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_BLOCKED=0.001, 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 UtDxuB0lqEbf for <ipv6@ietfa.amsl.com>; Mon, 16 Nov 2020 15:22:04 -0800 (PST)
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 3DF953A166B for <ipv6@ietf.org>; Mon, 16 Nov 2020 15:22:04 -0800 (PST)
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 0AGNLxLB027916; Mon, 16 Nov 2020 18:22:01 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1605568921; bh=FVAPGZfvqigK3RUqKiSaXVOwWVZ8mxHFL2wGT307QX8=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=X8xvdVrnnLmC5KYTtZGo/JLJo8foBqPlrLAnCrLQm0iQV7PHz81v7SUB/LCBMiDi0 To5SO+m7c5Qg59doZbvZEE+ozNf8G2zdViqtGYxbf4d3vz90gKW0KBkyEMz7HEKSsV /0MlTJzTRBqJS+0EVEfjZTY1VXBnvqK6ojqCWAOBXFb8HM8Dz7wJKDMN9JVeRFwGgI 8SNAVeI11/0/g/LXCoALkXMGRQ4IS6WGIRH/hMFDSYQdT9yWeGAobzADAQ+kGrNrYa SZEc1Ie1z7ilXr/7/1W/u9ycOHxcdtMO05lUUfj/jgWYqbazpFGb8Cb90eM9TGOwzp VqfNe7C9ZJC8Q==
Received: from XCH16-01-09.nos.boeing.com (xch16-01-09.nos.boeing.com [144.115.65.234]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 0AGNLwkT027910 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Mon, 16 Nov 2020 18:21:58 -0500
Received: from XCH16-01-11.nos.boeing.com (144.115.66.39) by XCH16-01-09.nos.boeing.com (144.115.65.234) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Mon, 16 Nov 2020 15:21:57 -0800
Received: from XCH16-01-11.nos.boeing.com ([fe80::c57c:39bc:4c0a:384b]) by XCH16-01-11.nos.boeing.com ([fe80::c57c:39bc:4c0a:384b%4]) with mapi id 15.01.2044.004; Mon, 16 Nov 2020 15:21:57 -0800
From: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
To: Mark Smith <markzzzsmith@gmail.com>
CC: 6man WG <ipv6@ietf.org>
Subject: RE: [EXTERNAL] Re: Extending a /64
Thread-Topic: [EXTERNAL] Re: Extending a /64
Thread-Index: AQHWu18TSAPYQn9dKU+Kr3IaOFR/aKnKGBIAgAAIXQD//4H0LIAAkFcAgAAS5ICAAWPdAP//utvg
Date: Mon, 16 Nov 2020 23:21:57 +0000
Message-ID: <e78954ba3a384ce697da2812a45ee3af@boeing.com>
References: <202011151920.0AFJKN9U003337@mail2.mwassocs.co.uk> <3d26bffe-b6c9-4ed7-6135-a515f9902fd7@gmail.com> <m1keOTi-0000EGC@stereo.hq.phicoh.net> <CAO42Z2wZkXryhw1u5WAFdtCvXHyyz1zeM22FP_gRxjurjsG-Jw@mail.gmail.com> <29299.1605477799@localhost> <CAO42Z2yS9gL9wQcfPb7Bes+ao=an2Lp2r5eJo97kcb4y2si=gg@mail.gmail.com>
In-Reply-To: <CAO42Z2yS9gL9wQcfPb7Bes+ao=an2Lp2r5eJo97kcb4y2si=gg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [144.115.204.6]
x-tm-snts-smtp: 110FCB8FF1B7C9B8C9BC8E55B2A281CFB344393D39CC6643477B466A236EE71A2000: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/rwHuVJ2PFBKOiOkGiLbLySwCJFc>
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, 16 Nov 2020 23:22:06 -0000

From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Mark Smith

> A management platform or system that controls and aggregates data from ULA addressed devices is perfectly compliant with the IPv6 architecture, because the management system is built with hosts. No NAT, no ALGs, the transport connections are end host to end host within the distinct network.
>
> Outside access to that would be via multi-homing one or more of the hosts in the management system. Specifically, forwarding between the hosts' interfaces is not enabled. The multihomed host(s) are relaying data between these two networks **at the application layer and as part of the application architecture**.
>
> This is how the IPv6 smart meter network I've seen works - and actually, were IPv6 only on the meter side, and only IPv4 on the outside.

Indeed. This is a practical approach, and it separates and reduces the mobility problem, to many fewer nodes. With no reason to assume that the mobility aspect must use statically assigned IP addresses, with semantics which trivially identify the platform. Plus, no problem with having to redefine address architectures, or anything else.

Bert

v2.23.0 | Report a Bug | By Email