Re: Is 1111 1110 10 equal to 0xfe80 or 0x3fa?

Yucel Guven <yucel.guven@gmail.com> Mon, 10 June 2019 15:26 UTC

Return-Path: <yucel.guven@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 3BAF0120116 for <ipv6@ietfa.amsl.com>; Mon, 10 Jun 2019 08:26:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 aWPKwcCLwSqF for <ipv6@ietfa.amsl.com>; Mon, 10 Jun 2019 08:26:04 -0700 (PDT)
Received: from mail-oi1-x230.google.com (mail-oi1-x230.google.com [IPv6:2607:f8b0:4864:20::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94FFE12013E for <ipv6@ietf.org>; Mon, 10 Jun 2019 08:26:04 -0700 (PDT)
Received: by mail-oi1-x230.google.com with SMTP id q186so6546756oia.0 for <ipv6@ietf.org>; Mon, 10 Jun 2019 08:26:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Y4DnFfwRSTpWh11Djy3bLLPh3s2fYvWPqiiXtq62gP4=; b=pR6b7cFjoUQLrCT84dMWEe+yeVXQKQicWSHCiizy1i6cxz8TFqGpx5Vjkv6ByIg6S4 fbx222GoWwkQIwVbwxLiCLyXKjPQm+MtXMxxLmjjOlW8EwLv5IfOueVCqlaMiYJ9+wiO MuqFA+jxNp7O/9TuaqtA1eW4nbjjj/4WTYLojwNaP/mDyA15kxrLF9TjRxW+hFRmUUJ2 bZKytHDpVxbpDMM9KuRF4ZPfnBlxU9iPy4X5lZrLWlTiF+ip5cw5OhUIzPlF+gkp73Fd nTGCRQrZyVNias19coAlelUQ7p8+pgK5P4C2azIoEzdwqMv3v98QLhWjxDpZy9xI9thH jSfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Y4DnFfwRSTpWh11Djy3bLLPh3s2fYvWPqiiXtq62gP4=; b=WLbL/q0iBgL12PkVuVQ5ykOAXRUSv99DamHnlceG2LVunOGwRSmTFKaJYIKQ91SSSi PooIaAWhuXpnzcvsw9Dy6D4oXDgH6bUMNCY2Yf1m5Q6GC9t1JT3/Ih/1IcdyTykwFFdU /9jE9wYLFpXoOUciB9ZWu8k9uAmVuEPDuvXg4m9sju9UFwVGkHgUDk6B4KIzBQoccqrw w1WVz6LtB4lDAKIWsYybfgdKcEs5fUj4lqkQfTCTte12i/Dvy925JpTNoO9uDjwBGra7 42IEeIqtKT3yGD6c6bA/I2K/NeQD9SrawaJJtzs9IuuUh1HvzGg1/ccsPDL14jepZAXX otDw==
X-Gm-Message-State: APjAAAW1/nTJgwfzf4JPs2UNI7javvlShVW6FmShq3wEq5Ye3DrVWsQL W4y9J6trBJ3uI9KV6B9t7yvhhTBJxEPYQly7IMZAWMBRjEc=
X-Google-Smtp-Source: APXvYqyvuIBh3DjVycxe6ZWJk/GZIsxwNfYBO4OaWf2w3oHmWaGdo04gPqpDfqwdxcve8TDiGcICVMUu2PZJBuLNhnI=
X-Received: by 2002:aca:318c:: with SMTP id x134mr11888274oix.125.1560180363885; Mon, 10 Jun 2019 08:26:03 -0700 (PDT)
MIME-Version: 1.0
References: <DM6PR15MB2506E62560613C85F74A1FF8BB100@DM6PR15MB2506.namprd15.prod.outlook.com> <CALx6S36vVpD9bAPSBQmhV+daR0Yr4heQ-LaiB4hABAs8ofVfNQ@mail.gmail.com> <DM6PR15MB25063BAF058C1825E2B63E30BB130@DM6PR15MB2506.namprd15.prod.outlook.com> <CALx6S37HsHyGwvXfWEjWHUrbnepLGbwp1Z64dbNK43kv4L33EQ@mail.gmail.com>
In-Reply-To: <CALx6S37HsHyGwvXfWEjWHUrbnepLGbwp1Z64dbNK43kv4L33EQ@mail.gmail.com>
From: Yucel Guven <yucel.guven@gmail.com>
Date: Mon, 10 Jun 2019 18:25:48 +0200
Message-ID: <CAKQ4NaWy3+tJnGw2HeifXvr2oMCTuMFZNmfGb5=khBTEB+dh3A@mail.gmail.com>
Subject: Re: Is 1111 1110 10 equal to 0xfe80 or 0x3fa?
To: Tom Herbert <tom@herbertland.com>
Cc: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006001c8058af9cc8e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/hil-bXPbAR-2vn6ZFaKppcmTqAU>
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: Mon, 10 Jun 2019 15:26:07 -0000

Tom,
FE8::/10 == 0FE8::/10  up to here OK, but
If prefix-lengh is 10 bits, then it should be:   FE8::/10 == 0FE8::/10 ==
0FC0::/10 == FC0::/10

Right?

On Mon, Jun 10, 2019 at 5:04 PM Tom Herbert <tom@herbertland.com> wrote:

> On Mon, Jun 10, 2019 at 6:58 AM Mudric, Dusan (Dusan) <dmudric@avaya.com>
> wrote:
> >
> > > On Friday, June 7, 2019 at 3:48 PM Tom Herbert
> > > <tom@herbertland.com> wrote
> > > >
> > > > >
> > > > > 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. In
> this
> > > notation, FE80::/10 = FEBF::/10,  because the first 10 bits are equal
> and other
> > > 6 should be ignored. 111 1111010 can be defined as FE80::/10 only if
> every
> > > time it is also mentioned that the trailing 6 bits are all zero.
> > >
> > > By that logic, we'd have to mention that the trailing 118 bits are
> zero.  E.g.
> > > FE80::/10 == FEBD:F676:BBBB:C654:FEBD:F676:BBBB:C654/10
> > > also. It's obviously convenient canonical notication to express all
> the trailing
> > > bits as zeroes for a prefix, but not required. For instance, ifconfig
> shows my
> > > host address as fe80::ac2f:ea58:94a:438/64 which in one string
> indicates both
> > > a fully qualified address and it's prefix bits.
> > [Dusan] In this example fe80::ac2f:ea58:94a:438/64 is LL address with
> 0xfe80 0x0000 0x0000 0x0000 prefix. Based on LL prefix definition, this LL
> address can have a value of feab::ac2f:ea58:94a:438/64 and still have the
> binary 10 bit prefix 1111111010
> >
> > May be LL address can be defined in hex notation as a range FE8::/10 -
> FEB::/10? This range always has the same well know LL identifier, the
> binary 10 bit prefix 1111111010.
>
> FE8::/10 - FEB::/10, only three digits in IPv6 notation? So wouldn't
> FE8::/10 == 0FE8::/10 == 0FE0::/10 == FE0::/10. I don't think that's
> right.
>
> Tom
>
> >
> > >
> > > Tom
> > >
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>