Re: [v6ops] IPv6 addressing: Gaps? (draft-gont-v6ops-ipv6-addressing-considerations)

Fernando Gont <fgont@si6networks.com> Thu, 18 February 2021 21:32 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 3CC003A18C0 for <v6ops@ietfa.amsl.com>; Thu, 18 Feb 2021 13:32:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, 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 KVxWkeMACJPX for <v6ops@ietfa.amsl.com>; Thu, 18 Feb 2021 13:32:43 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::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 6D4193A18B9 for <v6ops@ietf.org>; Thu, 18 Feb 2021 13:32:36 -0800 (PST)
Received: from [IPv6:2800:810:464:2b9:d092:11d0:9223:9b8f] (unknown [IPv6:2800:810:464:2b9:d092:11d0:9223:9b8f]) (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 47644280260; Thu, 18 Feb 2021 21:32:34 +0000 (UTC)
To: Ted Lemon <mellon@fugue.com>
Cc: IPv6 Operations <v6ops@ietf.org>
References: <36ba7456-210c-0626-5ec6-147538e49e5d@si6networks.com> <37012643-4F63-4FB6-979E-7C3BDD13DCD0@fugue.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <fbfd05eb-3a22-8e4d-4b82-44f70f6121b2@si6networks.com>
Date: Thu, 18 Feb 2021 18:32:19 -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: <37012643-4F63-4FB6-979E-7C3BDD13DCD0@fugue.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/2fOyTjbOlw3VvQP37eiw35FGQdo>
Subject: Re: [v6ops] IPv6 addressing: Gaps? (draft-gont-v6ops-ipv6-addressing-considerations)
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: Thu, 18 Feb 2021 21:32:47 -0000

Ted,

On 18/2/21 18:16, Ted Lemon wrote:
> This is wrong:
> 
>     Therefore, ULAs are not globally meaningful and thus, for most (if
>     not all) practical purposes, ULAs can be considered to have non-
>     global scope.  For this reason, ULAs are treated as non-global scope
>     addresses, even when from a specifications point of view they have
>     global scope.
> 
> 
> ULAs are explicitly global in scope. Please don’t try to change this in 
> an informational document. The other text in this section is fine.

FWIW, the intent in this Section wasn't to change that.  The text was 
meant that, when discussing how "scope" affects other properties of IPv6 
addresses, for all practical purposes ULAs have limited scope.

This text predates draft-gont-6man-ipv6-ula-scope which effectively does 
try to formally update the scope of ULAs.

P.S.: I will update the text before the cut-off.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492