IETF Logo Mail Archive

RE: [EXTERNAL] Re: Happy St Nicholas Day: Re-Launching the IPv6 ULA registry

"Manfredi (US), Albert E" <albert.e.manfredi@boeing.com> Wed, 09 December 2020 21:33 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 303A43A10F2 for <ipv6@ietfa.amsl.com>; Wed, 9 Dec 2020 13:33:34 -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 QNEMCKQgg-EK for <ipv6@ietfa.amsl.com>; Wed, 9 Dec 2020 13:33:32 -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 B6F373A0855 for <ipv6@ietf.org>; Wed, 9 Dec 2020 13:33:32 -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 0B9LXSVt023826; Wed, 9 Dec 2020 16:33:30 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1607549610; bh=I2m5TmGLzO+9hCgxIZI2amKSA8YmZIu07RcFpEfRmaw=; h=From:To:Subject:Date:References:In-Reply-To:From; b=KtYctzdnsJqrKe3P9BGaTDTmBYme+/NLI8Rou82lCqKm+ExEP10L8HlAYuhAQUh3v P3fYUMN491yEeab4zeOO6oBfHJNOg6ILAQ4jbCcTmM/HU+TIoauAuutsjJzSgpG8o5 bSMM17zdAgXMzNTyFQgWB43R9ZZzNu6vYtfwDqe8/nsmM/bHua3s9KgHKazf1oELZi 1ev8Lh80QpVCo1b+m+UvfVO+RcZ5H09GB4/T3+KuTVg+robJ2qJhW1pClXyWj36KLo bsJc2OXHpNyXfBOI2zilaMDkIO74UsGuJZ6C2Y34JowfuL1LOJbz46mZ2OUslA7UqB ZCnimyfjkv56Q==
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 0B9LXMLh023780 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Wed, 9 Dec 2020 16:33:22 -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; Wed, 9 Dec 2020 13:33:21 -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; Wed, 9 Dec 2020 13:33:21 -0800
From: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: [EXTERNAL] Re: Happy St Nicholas Day: Re-Launching the IPv6 ULA registry
Thread-Topic: [EXTERNAL] Re: Happy St Nicholas Day: Re-Launching the IPv6 ULA registry
Thread-Index: AQHWzOiky1BpiA7mk0iPfNJbLUF5mKnthZIAgAADnoCAANDcgIAAwkwA//+d+LmAAOpeAP//ovzg
Date: Wed, 09 Dec 2020 21:33:21 +0000
Message-ID: <728139b40ee445cf9bde32735565dc45@boeing.com>
References: <87r1o3deni.fsf@ungleich.ch> <CAKD1Yr3ptRjewThToEgERUOKwehTwdqNUAq14acc_nHLFqf3bg@mail.gmail.com> <87im9ds0z9.fsf@ungleich.ch> <fc637d64-a763-e5cf-fb93-002babe5f9ae@foobar.org> <87v9dcr37w.fsf@ungleich.ch> <CA+9kkMCb9fJQFJaP5ZaiwkQ2nRS7Fsn+q=C5OCPqdmMZRLSBKg@mail.gmail.com> <87sg8fp8ez.fsf@ungleich.ch> <m1kmyvz-00007rC@stereo.hq.phicoh.net> <fdaa0bad-a808-264a-e98b-9fa37ba198d6@gmail.com>
In-Reply-To: <fdaa0bad-a808-264a-e98b-9fa37ba198d6@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: 874C500BF9893D33C2B44A346787973161DABE342F7ACAA046BBAF7A9E618CB22000: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/UKfflZzK0oHNeLOGmXASG1kswkc>
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, 09 Dec 2020 21:33:34 -0000

-----Original Message-----
From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Brian E Carpenter
> On 10-Dec-20 01:51, Philip Homburg wrote:
fc00::/8 prefix that has been discussed before as centrally managed.
>> 
>> Deciding on how to set up a registry is more something for the RIR
>> communities.
>
> That's only true for address space that IANA has released to the RIRs.
That is not the case for fc00::/7, which remains under IETF control.

Yes, but in complete fairness, in principle, this could happen, and would be in compliance with RFC 4193:

----------------
3.1.  Format

   The Local IPv6 addresses are created using a pseudo-randomly
   allocated global ID.  They have the following format:

      | 7 bits |1|  40 bits   |  16 bits  |          64 bits           |
      +--------+-+------------+-----------+----------------------------+
      | Prefix |L| Global ID  | Subnet ID |        Interface ID        |
      +--------+-+------------+-----------+----------------------------+

   Where:

      Prefix            FC00::/7 prefix to identify Local IPv6 unicast
                        addresses.

      L                 Set to 1 if the prefix is locally assigned.
                        Set to 0 may be defined in the future.  See
                        Section 3.2 for additional information.
------------------

What most people, myself included, have been talking about is ULAs in which the L bit is set to 1. Which is, fd00::/8. Aside from Fernando's admission of having set the L bit to 0 (tsk tsk), Nico and Ungleich are talking about this "future use" of not-locally-assigned ULAs, fc00::/8. Presumably, not-locally-assigned would mean, globally assigned?

Are we saying that RFC 4193 needs an update, and that the meaning of the L bit has changed?

Bert

v2.23.0 | Report a Bug | By Email