IETF Logo Mail Archive

Re: Extending a /64

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 18 November 2020 23:08 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 889F93A0DDB for <ipv6@ietfa.amsl.com>; Wed, 18 Nov 2020 15:08:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 B4Pim-2Wg0G9 for <ipv6@ietfa.amsl.com>; Wed, 18 Nov 2020 15:08:52 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27CE93A0DD8 for <ipv6@ietf.org>; Wed, 18 Nov 2020 15:08:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 7FE4D389CE; Wed, 18 Nov 2020 18:09:48 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Y2NLdT4-qvY5; Wed, 18 Nov 2020 18:09:47 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 6D17C389CD; Wed, 18 Nov 2020 18:09:47 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 250E918B; Wed, 18 Nov 2020 18:08:50 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
cc: Tony Whyman <tony.whyman@mccallumwhyman.com>, ipv6@ietf.org
Subject: Re: Extending a /64
In-Reply-To: <f18f1e55-6c8f-2963-7e3a-f22a89dda46d@joelhalpern.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> <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>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 18 Nov 2020 18:08:50 -0500
Message-ID: <27091.1605740930@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/1CAJQBsT6hIus465AfDLtSII7JM>
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: Wed, 18 Nov 2020 23:08:55 -0000

Joel M. Halpern <jmh@joelhalpern.com> wrote:
    > Tony, why are you embedding the 39 bit airplane ID into the IPv6
    > address.

Tony wrote:
> 6. Legacy Issues
>
> We have a very significant legacy issue in the existing ATN/OSI which is in
> wide-spread use in Europe. In order to avoid having to upgrade every ATC
> Centre before the ATN/IPS can be introduced into Europe, the strategy is to
> develop protocol gateways that protocol convert between the ATN/IPS and the
> ATN/OSI. For these gateways to work, there has to be semantic equivalence
> between the address spaces. That is, the ATN/IPS MNP must include the ICAO
> 24-bit and an airline identifier (15 bits seems to be the minimum here).

My reading of this is that he needs the information in each packet so that he
can do stateless translation between different technologies.   It needs
to be stateless so that it can scale horizontally (inverse multiplexing), and
so that it can be n+1 redundant.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email