Re: Is 1111 1110 10 equal to 0xfe80 or...

Alexandre Petrescu <alexandre.petrescu@gmail.com> Sun, 09 June 2019 15:50 UTC

Return-Path: <alexandre.petrescu@gmail.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 88132120047 for <ipv6@ietfa.amsl.com>; Sun, 9 Jun 2019 08:50:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 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, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] 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 YWpBQr1cC2w5 for <ipv6@ietfa.amsl.com>; Sun, 9 Jun 2019 08:50:52 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 7850B12003E for <ipv6@ietf.org>; Sun, 9 Jun 2019 08:50:52 -0700 (PDT)
Received: from nephilia.intra.cea.fr (nephilia.intra.cea.fr [132.166.88.33]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x59FolEY073109; Sun, 9 Jun 2019 17:50:47 +0200
Received: from nephilia.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id BFA641C1970; Sun, 9 Jun 2019 17:50:47 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by nephilia.intra.cea.fr (Postfix) with ESMTP id B113D1C14EE; Sun, 9 Jun 2019 17:50:47 +0200 (CEST)
Received: from [132.166.86.26] ([132.166.86.26]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x59FoeKT003169; Sun, 9 Jun 2019 17:50:43 +0200
Subject: Re: Is 1111 1110 10 equal to 0xfe80 or...
To: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>, "ipv6@ietf.org" <ipv6@ietf.org>
References: <DM6PR15MB2506E62560613C85F74A1FF8BB100@DM6PR15MB2506.namprd15.prod.outlook.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <cb14591f-3abe-55e6-5bf8-f55afb68cae0@gmail.com>
Date: Sun, 09 Jun 2019 17:50:38 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <DM6PR15MB2506E62560613C85F74A1FF8BB100@DM6PR15MB2506.namprd15.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/PlTF6mTnWlRmHRjQlmAMolG1R0I>
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: Sun, 09 Jun 2019 15:50:55 -0000


Le 07/06/2019 à 21:29, Mudric, Dusan (Dusan) a écrit :
>> 
>> Message: 3 Date: Fri, 7 Jun 2019 10:53:28 -0700 From: Fred Baker
>> <fredbaker.ietf@gmail.com> To: Alexandre Petrescu
>> <alexandre.petrescu@gmail.com> Cc: IPv6 <ipv6@ietf.org> Subject:
>> Re: Is 1111 1110 10 equal to 0xfe80 or 0x3fa? Message-ID:
>> <A722E202-7671-4111-BA92-8A67B3D3B924@gmail.com> Content-Type:
>> text/plain; charset="us-ascii"
>> 
>> 
>> 
>> 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.

I fully agree.  That is what we should be talking about: a range.  The 
fe80::/10 to febf::/10 is the prefix of link local addresses.

The difficulty (not able to say just one hextet fe80, but a range from 
one hextet to another) is due  to the IPv6 notation, the textual 
representation of IPv6 addresses.

It is still strange to say that the bit pattern 1111 1110 10 can not be 
represented in hexa.  Or maybe there is a need of a new base.

> In this notation, FE80::/10 = FEBF::/10,  because the
> first 10 bits are equal and other 6 should be ignored.

I agree.

> 111 1111010
> can be defined as FE80::/10 only if every time it is also mentioned
> that the trailing 6 bits are all zero.

I agree.  And the trailing 6 bits are not all zero.  RFC 4291 makes them 
to be 0, but IANA allocation does not make them to be 0.

> But, it is very common to say
> FE80::/10 is LL prefix, without mentioning the 6 trailing bits to be
> zeros.

I agree.  Whoever I spoke to about LL was saying they are FE80.

On another hand, there is a similar difficulty with fc and fd in ULA 
addresses.  In the v6ops WG, and in the ULA RFC, there seems to be a 
clearer idea about the ULA notation.

In private I am also told to get mind around around CIDR notation.

Alex

> 
> -------------------------------------------------------------------- 
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6 
> --------------------------------------------------------------------
>