IETF Logo Mail Archive

RE: [EXTERNAL] Re: Extending a /64 (ATN/IPS worked example)

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Tue, 17 November 2020 23:06 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 7DA783A0EA2 for <ipv6@ietfa.amsl.com>; Tue, 17 Nov 2020 15:06:20 -0800 (PST)
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 Iod4wHH2Tq-I for <ipv6@ietfa.amsl.com>; Tue, 17 Nov 2020 15:06:19 -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 0DBAF3A0E9F for <ipv6@ietf.org>; Tue, 17 Nov 2020 15:06:18 -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 0AHN6Fwo010120; Tue, 17 Nov 2020 18:06:15 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1605654376; bh=/PMy11AB3M40v/irgpWhnJeLjPatGa0o9dgDAlvU6n0=; h=From:To:Subject:Date:References:In-Reply-To:From; b=MZcUJtlKFdRiReIQAnjbTzDcTFtK+ATCWqibOMvCPk7HpS9Yya0aGtGrSMsIWGEIQ 8OQ5Bcwu4eqt7FdQ8VLJUpMGqAkAaBzMbh5Rh9/Odn0Al8HXRgN5sxMAGCkJ2QL/3u e61UFWvA+JYIf2D5biTFKBVVbqz4kP8YMDBCbBDB3MiV26CjQBgXvOjQoApqy8GJm4 W56MTuWrw4tL80TW93+izVYku5LsVk0b6h4arx2HOldxca7X9g4184H1okLYdICcue 94uaVKgqNXJ6yAFsDGvftpGAX5anOXilOIEwUHHHbInuwtfdt7DejG6VCiQhmiseVM vHUTY8R7iGW6w==
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 0AHN6767010054 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Tue, 17 Nov 2020 18:06:07 -0500
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; Tue, 17 Nov 2020 15:06:06 -0800
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; Tue, 17 Nov 2020 15:06:06 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: [EXTERNAL] Re: Extending a /64 (ATN/IPS worked example)
Thread-Topic: [EXTERNAL] Re: Extending a /64 (ATN/IPS worked example)
Thread-Index: Ada9K5ZwsZCWyCeZQpmVScf8+sAtLQARIIcAABCa9uD//4ObgIAAgthA//7/MMH///9ZAA==
Date: Tue, 17 Nov 2020 23:06:06 +0000
Message-ID: <189c54bf75e2451eb5c713c6d3c97664@boeing.com>
References: <6728075c39884f40b49836e5e0061c76@boeing.com> <47e33c69-8ad9-b03e-872e-80b132af4906@gmail.com> <3ba4ac13fa304d09b7c3c6a1f0f50a9c@boeing.com> <79b67dece97044df9a15223154d15545@boeing.com> <255a5c37a1724b22a5aeac937d8a3bc3@boeing.com> <m1kf9wc-0000MnC@stereo.hq.phicoh.net>
In-Reply-To: <m1kf9wc-0000MnC@stereo.hq.phicoh.net>
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: 0D2728FF856EABB3EB77638CD99756E01C3B4555A0325357A2921C21F00E0E752000:8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/qEhq0sEjfwHEbsvkNar7mbPtpY8>
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: Tue, 17 Nov 2020 23:06:21 -0000


> -----Original Message-----
> From: pch-b9D3CB0F5@u-1.phicoh.com [mailto:pch-b9D3CB0F5@u-1.phicoh.com] On Behalf Of Philip Homburg
> Sent: Tuesday, November 17, 2020 2:59 PM
> To: ipv6@ietf.org
> Cc: Templin (US), Fred L <Fred.L.Templin@boeing.com>
> Subject: Re: Extending a /64 (ATN/IPS worked example)
> 
> >Plus, the aircraft ID is the moral equivalent of a VIN;
> 
> One way to look at this discussion is that to make aircraft ID part of an IPv6
> address is like making the VIN part of a car's license plate number.

That's why I said "moral" equivalent, and not "exact" equivalent; car VINs
are these big, long things that are far too long to embed in conventionally
sized containers. Aircraft IDs are only 24-bits - a much more workable size.

> For cars it is obvious why we don't do that. For IPv4 it is clear why we
> would not do that. It seems that IPv6 enough bits to promote 'creativity'.

If by "creativity" you mean "usefulness" then I agree. IPv6 packets are
going to tote around 128bit addresses, so we might as well pack them
with useful information.

Fred

> Same as putting IID generation types in link-local addresses. Clearly
> the link local prefix has too many bits and should have been a /64.

v2.23.0 | Report a Bug | By Email