Re: [EXTERNAL] Why this is broken [was Re: Extending a /64]

Matthew Petach <mpetach@netflight.com> Mon, 16 November 2020 20:58 UTC

Return-Path: <mpetach@gmail.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 AA1783A1430 for <ipv6@ietfa.amsl.com>; Mon, 16 Nov 2020 12:58:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.398
X-Spam-Level:
X-Spam-Status: No, score=-1.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 X3jOF3HYBpHL for <ipv6@ietfa.amsl.com>; Mon, 16 Nov 2020 12:58:17 -0800 (PST)
Received: from mail-io1-f41.google.com (mail-io1-f41.google.com [209.85.166.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 485233A0E5D for <ipv6@ietf.org>; Mon, 16 Nov 2020 12:58:17 -0800 (PST)
Received: by mail-io1-f41.google.com with SMTP id j12so18925314iow.0 for <ipv6@ietf.org>; Mon, 16 Nov 2020 12:58:17 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5/Ambx0wiVn95Y0sZUHKrVIAEkaUlHDw1Ec56JVtSBA=; b=HQc57fmOuS8ZrQE5uHTS0JUZKMQLEPhSAtEwVbgzqwH1B1pHxkpv6bpmAQSaoH7CXY iyKfsjgiZpZDX70OVuwLo0ihoLaRBcE5DUBQz+3OpF6jczUetDszTkfE63e0pDICnA3j 3bLjS1exVXu08MdGv69HaomtTcAGcM5s/w+ekYIIbc+qd0ioPtmbXVJlqAWdh57EnJJ+ g3p3WItIgXAhUItC7ObshQTX+vNkG1NqaWAKa28KKJ78hzdfPQEjrjVFTSegW+eNL8yj hEzzjd1GeVsPm/7nplBubC++oV0YtX6Zx+kPthR+Qlia8pLZvP8cHwNdYJrRlFucbjl/ QgjA==
X-Gm-Message-State: AOAM533kiaPuGz2wAPWzVxg7E+wNJhayXGfUVSEz3/tgPCibjGlD1Mi0 LRWi8kck/SHitShoGuXmNbvTmw2wAWD7Z3jFN40=
X-Google-Smtp-Source: ABdhPJwtEqagB1jC38WxwvChU0s2fThv0I/jWAIWjUhGC43IYiDrSwjzAPLhDcJSw1GlOBx11HC787DQWTZ2d8O5xzI=
X-Received: by 2002:a05:6638:24c8:: with SMTP id y8mr1150487jat.63.1605560296349; Mon, 16 Nov 2020 12:58:16 -0800 (PST)
MIME-Version: 1.0
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> <5f505585-1328-d942-2ec2-a2d96b7b4779@foobar.org> <m1kePdR-0000I6C@stereo.hq.phicoh.net> <b022d11f-b55d-07ef-307d-949ff57cd562@foobar.org> <m1keS7i-0000E0C@stereo.hq.phicoh.net> <f06db586-15ed-6dd3-d09f-06a4e3759275@mccallumwhyman.com> <m1kecJm-0000EOC@stereo.hq.phicoh.net> <5101F72E-4197-4E58-8DEF-9EB9D5541482@thehobsons.co.uk> <m1kefWI-0000ETC@stereo.hq.phicoh.net> <845e43f9-4534-a125-3105-9d345b85029f@mccallumwhyman.com> <f18f1e55-6c8f-2963-7e3a-f22a89dda46d@joelhalpern.com> <0443de45-931d-fbda-20ab-2931383a3a8d@mccallumwhyman.com> <61f8e6f7-1bfd-4c17-9e42-dc5fc10a19b5@gmail.com> <e0fe6742451d418e98c25039c8a45a21@boeing.com>
In-Reply-To: <e0fe6742451d418e98c25039c8a45a21@boeing.com>
From: Matthew Petach <mpetach@netflight.com>
Date: Mon, 16 Nov 2020 12:58:05 -0800
Message-ID: <CAEmG1=qJg8Gp0SrF93Hw+4Wd1JFSNnRbmLSgx4ABxYQykFvVJg@mail.gmail.com>
Subject: Re: [EXTERNAL] Why this is broken [was Re: Extending a /64]
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, Tony Whyman <tony.whyman@mccallumwhyman.com>, "Joel M. Halpern" <jmh@joelhalpern.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002126d205b43fa354"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/xuN3P8NDmcj64duJRYVLFJ-Kn0c>
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 20:58:19 -0000

On Mon, Nov 16, 2020 at 12:43 PM Templin (US), Fred L <
Fred.L.Templin@boeing.com> wrote:

> Brian,
>

[...]


> The ATN/IPS will be a secured network with no connections to the Internet
> and open only to authorized users. An enterprise network for civil
> aviation,
> if you will. Unauthorized users will not have access to the network, and
> even
> for authorized users the multi-layered security services will ensure
> secured
> communications.
>
> Fred
>

If it is truly an isolated network, with no connections to the Internet,
can't you define your addressing within it as freely as you want?
Surely you don't need IETF approval to do strange and unusual
addressing schemes within your own internal networks that never
connect to the rest of the Internet.  Lord knows I never asked the
IETF for approval before performing unusual acts of discontiguous
addressing within my lab networks.   ;)

If it really is completely isolated and can never connect to the
wider Internet, you can define your addressing and your
protocols in any way you like; and in fact, making them
not entirely compatible with the rest of the Internet may
help ensure there's no accidental leakage, by making the
two schemes dissimilar enough that they can't cross-communicate
accidentally.

Matt