[v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)

Fernando Gont <fgont@si6networks.com> Wed, 06 January 2021 01:21 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5AD03A108E; Tue, 5 Jan 2021 17:21:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, 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 4bnZu7Xtp6RO; Tue, 5 Jan 2021 17:21:17 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A96D3A0FB3; Tue, 5 Jan 2021 17:21:13 -0800 (PST)
Received: from [10.0.0.129] (unknown [186.19.8.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id B48A8284516; Wed, 6 Jan 2021 01:21:06 +0000 (UTC)
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com>
To: "6man@ietf.org" <6man@ietf.org>, IPv6 Operations <v6ops@ietf.org>
From: Fernando Gont <fgont@si6networks.com>
X-Forwarded-Message-Id: <160989494094.6024.7402128068704112703@ietfa.amsl.com>
Message-ID: <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com>
Date: Tue, 5 Jan 2021 22:20:55 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <160989494094.6024.7402128068704112703@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Kt7dNn0ds9HOgQp9GY4-rNchS3U>
Subject: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 01:21:22 -0000

Folks,

Based on the recent discussion on the v6ops list 
(https://mailarchive.ietf.org/arch/msg/v6ops/b7r35HgOb-6dfxsDoW8c4FtGnZo//), 
I've posted this new I-D, meant to discuss the scope of ULAs:

Title: "Scope of Unique Local IPv6 Unicast Addresses"
I-D: https://tools.ietf.org/id/draft-gont-6man-ipv6-ula-scope-00.txt


Short version of the story:

ULAs are formally part of the GUA space. However, the characteristics of 
ULAs do not seem to match the definition of global scope from RFC4007 
(IPv6 Scope Addr Architecture). ULA seem to have a scope of 
scope(link-local) < scope(ULA) < scope(GUA).

This is not only a terminology thing (which I think is nevertheless 
important to get right) but also has practical implications. For 
example, there's a python library that considers ULAs as "not global", 
and "private" -- contradicting the current RFC4291/RFC4193 specs.

Prior to posting this document, we had some on-list discussion (on the 
v6ops list) and also some off-list discussion with some of you (bcc'ed).

The opinions have been in one of these camps:

1) the current specs are coherent and there's no problem

2) There's a problem with the definition of "global scope" -- so ULAs 
*are* global scope, but global scope does not really stand for the 
definition in RFC4007.

3) The definitions in RFC4007 are correct, and thus the scope of ULAs is 
not really global, but scopee(link-local) < scope(ULAs) < scope(global)


While this document does propose a way out (it assumes #3 above, and 
acts accordingly), I believe the first step is to agree on what "global 
scope" means and, subsequently, whether ULAs are really "global scope" 
or not. Since opinions on the topic have vary a lot (as noted above), 
I've posted this I-D and I'm sending this note for further input from 
the WG.

Thanks!

Regards,
Fernando




-------- Forwarded Message --------
Subject: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt
Date: Tue, 05 Jan 2021 17:02:20 -0800
From: internet-drafts@ietf.org
To: Fernando Gont <fgont@si6networks.com>


A new version of I-D, draft-gont-6man-ipv6-ula-scope-00.txt
has been successfully submitted by Fernando Gont and posted to the
IETF repository.

Name:		draft-gont-6man-ipv6-ula-scope
Revision:	00
Title:		Scope of Unique Local IPv6 Unicast Addresses
Document date:	2021-01-05
Group:		Individual Submission
Pages:		8
URL: 
https://www.ietf.org/archive/id/draft-gont-6man-ipv6-ula-scope-00.txt
Status: 
https://datatracker.ietf.org/doc/draft-gont-6man-ipv6-ula-scope/
Htmlized: 
https://datatracker.ietf.org/doc/html/draft-gont-6man-ipv6-ula-scope
Htmlized: 
https://tools.ietf.org/html/draft-gont-6man-ipv6-ula-scope-00


Abstract:
    Unique Local IPv6 Unicast Addresses (ULAs) are formally part of the
    IPv6 Global Unicast address space.  However, the semantics of ULAs
    clearly contradict the definition of "global scope".  This document
    discusses the why the terminology employed for the specification of
    ULAs is problematic, along with some practical consequences of the
    current specification of ULAs.  Finally, it formally updates RFC4291
    and RFC4193 such that the scope of ULAs is defined as "local".

 


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat