Re: 1111 1110 10 equals 0xfe80 to 0xfebf

Simon Hobson <linux@thehobsons.co.uk> Sat, 15 June 2019 21:22 UTC

Return-Path: <linux@thehobsons.co.uk>
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 023EE120131 for <ipv6@ietfa.amsl.com>; Sat, 15 Jun 2019 14:22:05 -0700 (PDT)
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, SPF_HELO_NONE=0.001, SPF_NONE=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 U2AZ_I14BW92 for <ipv6@ietfa.amsl.com>; Sat, 15 Jun 2019 14:22:02 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [80.229.10.150]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9D3F12012E for <ipv6@ietf.org>; Sat, 15 Jun 2019 14:22:02 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from simons-macbookpro.thehobsons.co.uk (Simons-MacBookPro.thehobsons.co.uk [192.168.137.111]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id D23FF1BC37 for <ipv6@ietf.org>; Sat, 15 Jun 2019 21:21:56 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: 1111 1110 10 equals 0xfe80 to 0xfebf
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <2a8b3f2a-d0de-f2e3-ae25-17f2234cb18a@gmail.com>
Date: Sat, 15 Jun 2019 22:21:54 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C85BDEE1-FD85-47F1-8A87-3BDEDA313D2F@thehobsons.co.uk>
References: <DM6PR15MB2506E62560613C85F74A1FF8BB100@DM6PR15MB2506.namprd15.prod.outlook.com> <2a8b3f2a-d0de-f2e3-ae25-17f2234cb18a@gmail.com>
To: 6man WG <ipv6@ietf.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/VQ3ZbVOcvixjfCM3AFkQ4hHCjUg>
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: Sat, 15 Jun 2019 21:22:05 -0000

Alexandre Petrescu <alexandre.petrescu@gmail.com> wrote:

>>> If I have prefix fe80::/10, as described in RFC 4291, the next bit is bit 11. Doing
>>> the same subdivision of the prefix is fe80::/11 and fea0::/11.
>> [Dusan] The hexadecimal definition for LL address is not syntactically correct. The binary 10 bit prefix 1111111010 cannot be presented as hexadecimal FE80::/10. It is rather a range FE80::/10 - FEBF::/10. In this notation, FE80::/10 = FEBF::/10, 
> 
> I agree.  The IPv6 link-local prefix is not one hextet, but a range of hextets: FE80::/10 to FEBF::/10.
> 
> Maybe one can come up with a base in which that range of hextets is represented as just one number.

We don't need any new representation.
As others have already said, this thread has gone on far too long, and is really starting to seem like trolling. It is hard to understand how someone involved in networking does not understand CIDR, and someone involved in an IPv6 working group doesn't understand standard IPv6 CIDR notation. I'm sorry if that sounds like an insult, but these are pretty basic concepts.

There is no problem, there is no ambiguity.

Consider the IPv4 notation where someone says "subnet 123.123.252.0/22". That's unambiguous, meaning a subnet 0111 1011 0111 1011 1111 11 expanded to 32 bits with 00 0000 0000 0000, or in hex, FB FB FC 00/22. The fact that the subnet encompasses addresses from 123.123.252.0 through to 123.123.255.255 doesn't alter that, and we don't insist on saying it's subnet 123.123.(252 to 255).(0 to 255). Everyone knows exactly what is meant - if they understand CIDR, which sadly too many networking people don't (you wouldn't believe the number of people who don't understand anything but a /24 !)

In IPv6 notation, the rules are equally clear. FE80::/10 means exactly one thing - the TEN bits 1111 1110 10 followed by 118 zeros. As a prefix (analogous to a subnet in IPv4) that is clear, unambiguous, and understandable by anyone who understands the basics of IPv6 notation. The fact that the prefix can encompass addresses from FE80:: through to FEBF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF does not change the fact that the PREFIX is still FE80/10. So no, it is not necessary to say FE(80 through BF):<stuff>/10 and it would be very confusing to try and do so.

And all that is completely irrelevant to whether any address is link local or not. For example, an address FE81:1:<something> is still within the prefix FE80::/10. So if you wish to take the view that a link local address is allowed to use all 118 bits then the prefix is still FE80/10 and it is still valid to say that a link local address is in the FE80/10 subnet. So whether 54 bits are all zero or can be non-zero (and thus the hex representation can be anything from FE80:stuff to FEBF:stuff) doesn't change that basic notation.

> What is a nub?

It's a manner of speech in some areas, roughly translated it means "the essential point of the issue".