IETF Logo Mail Archive

Re: encoding link ID in link-local addrs (Re: about violation of standards)

"Mudric, Dusan (Dusan)" <dmudric@avaya.com> Thu, 25 April 2019 14:32 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 7D9D01200B7 for <ipv6@ietfa.amsl.com>; Thu, 25 Apr 2019 07:32:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.121
X-Spam-Level:
X-Spam-Status: No, score=-6.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_NEUTRAL=0.779] 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 43vcEi-7nNg5 for <ipv6@ietfa.amsl.com>; Thu, 25 Apr 2019 07:32:28 -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 17550120043 for <ipv6@ietf.org>; Thu, 25 Apr 2019 07:32:27 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2FmAABcxMFc/yYyC4dmHQEBBQEHBQGBUQgBCwGBPVADgT0gBDMKh0wDhFKKOIJXmEuBJAMYPA8BLQKEPgKGMSM0CQ4BAwEBAQQBAQEBAgICaRwMg0U5MgEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQUCODkBAQECARIoBgEBNwEEDQEIDSlCJgEEAQ0NEweEagMNDwECAp8XAoEGL4hfgiAaAoJdAQEFhQUYgg0JCQGBKAGLSBeBQT6BEUaCTD6ERAKDOYImimmbcQkCggiHRYsAjAkDiQiMBJQ7AgICAgQFAg4BAQWBTzmBVnAVgyeCDwwXg0yKU3KBKY4oAYEgAQE
X-IPAS-Result: A2FmAABcxMFc/yYyC4dmHQEBBQEHBQGBUQgBCwGBPVADgT0gBDMKh0wDhFKKOIJXmEuBJAMYPA8BLQKEPgKGMSM0CQ4BAwEBAQQBAQEBAgICaRwMg0U5MgEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQUCODkBAQECARIoBgEBNwEEDQEIDSlCJgEEAQ0NEweEagMNDwECAp8XAoEGL4hfgiAaAoJdAQEFhQUYgg0JCQGBKAGLSBeBQT6BEUaCTD6ERAKDOYImimmbcQkCggiHRYsAjAkDiQiMBJQ7AgICAgQFAg4BAQWBTzmBVnAVgyeCDwwXg0yKU3KBKY4oAYEgAQE
X-IronPort-AV: E=Sophos;i="5.60,394,1549947600"; d="scan'208";a="337585623"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 25 Apr 2019 10:32:12 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-US1EXHC02.global.avaya.com) ([135.11.85.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Apr 2019 10:32:12 -0400
Received: from PW365VMAP01.avaya.com (135.11.29.21) by az-us1exhc02.global.avaya.com (135.11.85.13) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 25 Apr 2019 10:32:12 -0400
Received: from NAM05-BY2-obe.outbound.protection.outlook.com (104.47.50.54) by PW365VMAP01.avaya.com (135.11.29.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1531.3; Thu, 25 Apr 2019 09:32:12 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Avaya365.onmicrosoft.com; s=selector1-avaya-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NMhDIAd7O+skztNfHXqoCXGNPwOdCyVD4mYwODtdHA0=; b=ZmkoXKzO5G4vC/gXHzAazIntL1YVHilkzq6SlIZgMCjWlM3jtNiSRF4MUlX5UBgtVXOcg2ERWpVhJvOHlfMVxFDbTPsdgrvmqBcAcGMW/sI94WqF6JigWwN9Hpe0PW1NxFQzmjCaw0hJ4kPt1iISq5KFGS/2wmpoBHSNxrhqfmw=
Received: from DM6PR15MB2506.namprd15.prod.outlook.com (20.176.71.32) by DM6PR15MB3180.namprd15.prod.outlook.com (20.179.51.77) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1813.14; Thu, 25 Apr 2019 14:32:10 +0000
Received: from DM6PR15MB2506.namprd15.prod.outlook.com ([fe80::f9bf:a95a:e7db:2480]) by DM6PR15MB2506.namprd15.prod.outlook.com ([fe80::f9bf:a95a:e7db:2480%5]) with mapi id 15.20.1835.010; Thu, 25 Apr 2019 14:32:10 +0000
From: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>, Alexandre Petrescu <alexandre.petrescu@gmail.com>, Ole Troan <otroan@employees.org>, "," <jinmei@wide.ad.jp>
CC: "Pascal Thubert (pthubert" <pthubert@cisco.com>
Subject: Re: encoding link ID in link-local addrs (Re: about violation of standards)
Thread-Topic: encoding link ID in link-local addrs (Re: about violation of standards)
Thread-Index: AdT7c6lZK6PR6hcAS8aF47MFgzNtEg==
Date: Thu, 25 Apr 2019 14:32:10 +0000
Message-ID: <DM6PR15MB25060A2397F2949C08B4A896BB3D0@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.170]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: a87ef27f-dfd1-4177-460c-08d6c98acd36
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(7168020)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:DM6PR15MB3180;
x-ms-traffictypediagnostic: DM6PR15MB3180:
x-microsoft-antispam-prvs: <DM6PR15MB3180E429927ED4269DC7B75ABB3D0@DM6PR15MB3180.namprd15.prod.outlook.com>
x-forefront-prvs: 0018A2705B
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(136003)(366004)(396003)(376002)(39860400002)(189003)(199004)(86362001)(71200400001)(71190400001)(256004)(99286004)(73956011)(66446008)(66476007)(476003)(66556008)(64756008)(6116002)(7696005)(74316002)(76116006)(3846002)(55016002)(9686003)(66946007)(229853002)(7736002)(6246003)(305945005)(2906002)(81166006)(81156014)(8676002)(4326008)(53936002)(6436002)(25786009)(8936002)(97736004)(55236004)(68736007)(2501003)(110136005)(102836004)(66066001)(186003)(52536014)(14454004)(316002)(6506007)(478600001)(5660300002)(26005)(33656002)(486006); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6PR15MB3180; 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: 0RPHxTIg4FPU/Ov5U9qxY+b1qC7Wbxs3OkpdDd1CpIymw9PUDQrbewecMimKiiVnDGVRxaVm7O61/smHD/HMdLtzg/WeUrKcQ5kPSWktikf8zGANK4nPB2YFLsVQY1Kl7BtYUZCqFw3zMHkiu1zlnGcpyVp4BYB2z0JsPT9v7zTv1jSfSBsCaBbRwy4RpRmexDxY3/QNIPi5Atr1OxvDfwfiUlz3YZVpq327qqJfYY1lW9wbUZJA9EDSooJ/m/HWonR5pWwj3mVCZpfeSIv3y3GlIhzV4UP0KMVaY9Lz0cLvHsbmqisYmKEdvS60htsnKVjshSD0V/8V5R4rmUIqhAtYgcCbPJpSolPirsds7Ueo++widYqymC+Eern8QokL46ndsoaz/xkMeCMCJoHcLALs6590PYGfkhvlZzgpPKM=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: a87ef27f-dfd1-4177-460c-08d6c98acd36
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Apr 2019 14:32:10.3458 (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-Transport-CrossTenantHeadersStamped: DM6PR15MB3180
X-OriginatorOrg: avaya.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/U1ManXIiP6TTm5d_EDsRcKxMDhQ>
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: Thu, 25 Apr 2019 14:32:31 -0000

> 2 IPv6 link-local addresses are typically self-configured according to 4
>    RFCs and relying on the fe80::/10 IANA allocation, RFC 54 0 bits, and
>    RFC MAC-based 64bit Interface IDs.  In some cases, it is advantageous
>    to manually configure link-local addresses.  This is useful for easy
>    remembering by humans, and for parameter resilience during
>    network interface replacement.
> 
>    Manual configuration of an LL may use short IID and Subnet ID
>    The Subnet ID presence in the link-local address is useful in some
>    wireless settings where the subnet structure parameters depend on the
>    link locality.  Other settings may also benefit.
> 
>    When manually setting the link-local address it is necessary to know
>    the length of the prefix of the subnet on which this link-local
>    address is present.  This length is necessary for on-link
>    determination.
> 
[Dusan] Is the Subnet ID unique per host? Is it possible that all hosts on the link share the same Subnet ID? Can somebody provide more details about the problem and how this solution will solve the problem?

v2.23.0 | Report a Bug | By Email