IETF Logo Mail Archive

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

"Mudric, Dusan (Dusan)" <dmudric@avaya.com> Fri, 07 June 2019 19:29 UTC

Return-Path: <dmudric@avaya.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 2F0C012018F for <ipv6@ietfa.amsl.com>; Fri, 7 Jun 2019 12:29:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=avaya365.onmicrosoft.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 F-mqvqZHsshf for <ipv6@ietfa.amsl.com>; Fri, 7 Jun 2019 12:29:55 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.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 6078F1200F3 for <ipv6@ietf.org>; Fri, 7 Jun 2019 12:29:55 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2F7AwCwufpc/wUHmMZmHgEfBgeBTAKBPFCBXwMEMwqHUgOOYUqCDYlDjxyBJAMYPAkBAQENAS0CAQEChD4CgmsjNAkOAQMBAQEEAQEBAQMBAgJpHAELg0U5MgEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQUCODgBAQICARIoBgEBOBEBCA0EAwECHzERHQkBBBMIGoRrAw4PAQICnQYCgQgwiF4BAYIhGgKCXQEBBYUCDQuCDwkJAYEqi1sXgUE+gRFGgh4uPoIagioCBYM1giaoaj4JAoIOj1aEBo0NA4oBjQ+IdY1BAgICAgQFAg4BAQWBTzmBWHAVgyeFf4pTcoEpjWsBgSABAQ
X-IPAS-Result: A2F7AwCwufpc/wUHmMZmHgEfBgeBTAKBPFCBXwMEMwqHUgOOYUqCDYlDjxyBJAMYPAkBAQENAS0CAQEChD4CgmsjNAkOAQMBAQEEAQEBAQMBAgJpHAELg0U5MgEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQUCODgBAQICARIoBgEBOBEBCA0EAwECHzERHQkBBBMIGoRrAw4PAQICnQYCgQgwiF4BAYIhGgKCXQEBBYUCDQuCDwkJAYEqi1sXgUE+gRFGgh4uPoIagioCBYM1giaoaj4JAoIOj1aEBo0NA4oBjQ+IdY1BAgICAgQFAg4BAQWBTzmBWHAVgyeFf4pTcoEpjWsBgSABAQ
X-IronPort-AV: E=Sophos;i="5.63,564,1557201600"; d="scan'208";a="345619528"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 07 Jun 2019 15:29:54 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-US1EXHC04.global.avaya.com) ([135.11.85.15]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Jun 2019 15:29:53 -0400
Received: from PW365VMAP02.avaya.com (135.8.98.110) by AZ-US1EXHC04.global.avaya.com (135.11.85.15) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 7 Jun 2019 15:29:52 -0400
Received: from NAM05-BY2-obe.outbound.protection.outlook.com (104.47.50.54) by PW365VMAP02.avaya.com (135.8.98.110) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1531.3; Fri, 7 Jun 2019 14:29:52 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Avaya365.onmicrosoft.com; s=selector1-Avaya365-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Dea75dHqY8E99rVHWUy2BQTT2p12nEPOhgD5TikS8Pg=; b=Ozx0sxtRBpUi+XtZJ6PJE3b1qjooW2IAWm2zIMq7mUdoz6tRz0C5eAMyP6xUYkHN8Dp23CEHncIfOBIPGftHuUf/DvhnIXqO/P1H7T4/ao4R/9BDDIU0sa3HUqtk3j+JmnkP02+PStMCYCVG1MSF6V1KStoFa84vLJD5ipGIM2o=
Received: from DM6PR15MB2506.namprd15.prod.outlook.com (20.176.71.32) by DM6PR15MB3275.namprd15.prod.outlook.com (20.179.50.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1943.22; Fri, 7 Jun 2019 19:29:50 +0000
Received: from DM6PR15MB2506.namprd15.prod.outlook.com ([fe80::fc26:4d7:b56:72ac]) by DM6PR15MB2506.namprd15.prod.outlook.com ([fe80::fc26:4d7:b56:72ac%7]) with mapi id 15.20.1965.011; Fri, 7 Jun 2019 19:29:50 +0000
From: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: Is 1111 1110 10 equal to 0xfe80 or 0x3fa?
Thread-Topic: Is 1111 1110 10 equal to 0xfe80 or 0x3fa?
Thread-Index: AdUdZ16t99pzr7IZQvSKYtdaSR9kGQ==
Date: Fri, 07 Jun 2019 19:29:50 +0000
Message-ID: <DM6PR15MB2506E62560613C85F74A1FF8BB100@DM6PR15MB2506.namprd15.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=dmudric@avaya.com;
x-originating-ip: [104.129.196.166]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: eff28cbc-1b69-44c1-bf9c-08d6eb7e8251
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(7168020)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:DM6PR15MB3275;
x-ms-traffictypediagnostic: DM6PR15MB3275:
x-microsoft-antispam-prvs: <DM6PR15MB327544F318E9B274FE3CC225BB100@DM6PR15MB3275.namprd15.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0061C35778
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(39860400002)(346002)(376002)(396003)(136003)(189003)(199004)(26005)(476003)(305945005)(7736002)(478600001)(66066001)(86362001)(81166006)(68736007)(81156014)(2501003)(8936002)(71190400001)(71200400001)(33656002)(14454004)(76116006)(73956011)(66946007)(64756008)(53936002)(186003)(8676002)(74316002)(66446008)(256004)(486006)(9686003)(4744005)(2351001)(6916009)(7696005)(52536014)(55016002)(5660300002)(25786009)(99286004)(66556008)(66476007)(6116002)(229853002)(3846002)(5640700003)(102836004)(2906002)(6436002)(6246003)(6506007)(55236004)(316002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6PR15MB3275; H:DM6PR15MB2506.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: avaya.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: QEHFQzz1u/pQrSydj97wgwydnLiStxuvRpEIF9Kpal5y6OczmOMxieEVAzD/4MvXnY0hHm3DQN9BHVnvVCnE9JmhBit+vWRVjNPzXATVTAEpLNasGNO92Aw6WjgFkrUqlYWmuniV4F/6m4aOiep/UjfOGMm0/mHd5+jfj+5Wia8/Z1aKG81sIWL6nKPLCz+o2ni0I1wOArkyV5XwMFoBhGTZReFp75aXxXFIOLq6QX5TTp9Ff+YZtBqQ6GQuO8k+Vz4e70074lWzi+djpDObsvYqBOAU9NF8UfPfrPqTwvWxv1Mvo5z4IGkTGopGd16HLGT3eYD55x8zhBJPmi16TDaCmQbsxACYjbiy+C12V09+HfRpoZ4B2pHOZSmdDfkEmhpfED4nn4trhaFyplPrahkiKibntHv7zS82Ff0MFX8=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: eff28cbc-1b69-44c1-bf9c-08d6eb7e8251
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Jun 2019 19:29:50.2966 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 04a2636c-326d-48ff-93f8-709875bd3aa9
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: dmudric@avaya.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR15MB3275
X-OriginatorOrg: avaya.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/5WsHU36vff_b_CfaCp5H5O3OZIs>
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: Fri, 07 Jun 2019 19:29:57 -0000

> 
> 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. But, it is very common to say FE80::/10 is LL prefix, without mentioning the 6 trailing bits to be zeros.

v2.23.0 | Report a Bug | By Email