Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 27 February 2017 10:00 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48E12129CEB for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2017 02:00:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.332
X-Spam-Level:
X-Spam-Status: No, score=-0.332 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 CmR2bfhLPigU for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2017 02:00:49 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 807E9129CE7 for <ietf@ietf.org>; Mon, 27 Feb 2017 02:00:49 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v1RA0lRT042763 for <ietf@ietf.org>; Mon, 27 Feb 2017 11:00:47 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 4133A207ABF for <ietf@ietf.org>; Mon, 27 Feb 2017 11:00:47 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 38214200E98 for <ietf@ietf.org>; Mon, 27 Feb 2017 11:00:47 +0100 (CET)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v1RA0k4V028667 for <ietf@ietf.org>; Mon, 27 Feb 2017 11:00:46 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: ietf@ietf.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <6dbbbf7d-b3b8-0fbc-c2a3-546472925893@si6networks.com> <9B712605-E180-4F33-806F-9DC5CBAD2E31@steffann.nl> <456cf6e5-a57b-8198-4261-1ff2c0dc1e1c@si6networks.com> <86D1EAA4-237B-46E0-A766-E2D181250695@steffann.nl>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <fffefb38-476f-8b02-d814-60597b7d2bdd@gmail.com>
Date: Mon, 27 Feb 2017 11:00:33 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <86D1EAA4-237B-46E0-A766-E2D181250695@steffann.nl>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kXB3q9rPcCAxo3bbk7yWYdhQugY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 10:00:51 -0000


Le 26/02/2017 à 14:24, Sander Steffann a écrit :
>
>> Op 26 feb. 2017, om 14:05 heeft Fernando Gont <fgont@si6networks.com> het volgende geschreven:
>>
>> On 02/26/2017 09:55 AM, Sander Steffann wrote:
>>> Hi,
>>>
>>>> 2.3.  Address Type Identification
>>>>
>>>>  The type of an IPv6 address is identified by the high-order bits of
>>>>  the address, as follows:
>>>>
>>>>     Address type         Binary prefix        IPv6 notation   Section
>>>>     ------------         -------------        -------------   -------
>>>>     Unspecified          00...0  (128 bits)   ::/128          2.4.2
>>>>     Loopback             00...1  (128 bits)   ::1/128         2.4.3
>>>>     Multicast            11111111             ff00::/8        2.6
>>>>     Link-Local unicast   1111111010           fe80::/10       2.4.6
>>>>     Global Unicast       (everything else)
>>>>
>>>>
>>>> I wonder if this table should explicitly call out ULAs, and provide a
>>>> reference to the corresponding section.
>>>
>>> ULAs are not an address type, they are Global Unicast. Adding them here might confuse people. And if we include ULAs then there is lots more that we should include as well. So while I understand your question, I think it would be better not to.
>>
>> The "confusing" part is that, while globally unique, their scope is not
>> really global -- i.e., they are not meant to be globally routable.
>
> Indeed, globally unique vs globally routable. But if you go into this then it's more complicated than it seems. Whether something is routable and where are an operational choice. Companies choosing to interconnect might route each other's ULA space, while some of my RIPE NCC allocated space is not routed anywhere public. It's difficult to give a fixed definition that doesn't take operational stuff into account.
>
> Of course the intention of how to use ULA should be mentioned somewhere, but probably not in this table.
>
>> Wasn't there at some point an I-D aiming to clarify what "global" meant?
>> -- IIRC, authored by Brian et al.
>
> Sorry, I don't remember.

It was something to correct at IANA about this 'global'.

Alex

>
> Cheers,
> Sander
>