IETF Logo Mail Archive

Re: [dhcwg] Reminder: Call for Adoption - draft-bvtm-dhc-mac-assign - Respond by April 16, 2019

"Bernie Volz (volz)" <volz@cisco.com> Tue, 16 April 2019 15:58 UTC

Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6FD61207C6 for <dhcwg@ietfa.amsl.com>; Tue, 16 Apr 2019 08:58:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=N+OVeOJH; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=dRSwLjkk
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 gqy-s4R2SuwV for <dhcwg@ietfa.amsl.com>; Tue, 16 Apr 2019 08:58:55 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65E431207C7 for <dhcwg@ietf.org>; Tue, 16 Apr 2019 08:03:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=26487; q=dns/txt; s=iport; t=1555427021; x=1556636621; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=vMqLSuuxXpUNT/qH3tsymLEQPdoMcxpjHOQfoY5N77M=; b=N+OVeOJH4FDQJ2hLOn8f5nX19wxqbzwuR2NmL7XKdlhBaXK4quEPFOCo yP0bHuBjrVuWjPjzyqoVTgZt80179a+XCL1BBnDbGy04zCXulxyE/gMgX 6UtjsKjRcpMmytO19ibDcTXiTMP+o8l6W5IFnU8oqC1NrKXQk3aJYzvGc 0=;
IronPort-PHdr: 9a23:C6LfwhFlIf+j7aPAOgLw7p1GYnJ96bzpIg4Y7IYmgLtSc6Oluo7vJ1Hb+e4w0Q3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0ETBoZkYMTlg0kDtSCDBjlK/r4Ryc7B89FElRi+iLzPA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AIAACA7rVc/5tdJa1mDgwBAQEBAQIBAQEBBwIBAQEBgVEFAQEBAQsBgQ4vUANoVSAECyiEDoNHA4RSikeCV5cbgS6Bew4BARgBDgaEQAIXhXAjNAkOAQMBAQoBAgECbRwMhUoBAQECAgEBGwYdAQEsCwEPAgEIEQMBAQEhBwMCAgIlCxQJCAEBBA4FgyIBgR1MAxwBAgyeOwKKFHGBL4J5AQEFgTIBAwICDw+DKBiCDQmBMgGLSReBf4E4H4JMPoEEgTglAQEBAoFINg0JCIJMMYImjSqEOodjjHIJAoIGhguMDhQHgghdhT6MU4NdhzcJhniNcQIEAgQFAg4BAQWBTziBVnAVOyoBgkEJggEYH4M4hRSFBDtyAYEoj0kBAQ
X-IronPort-AV: E=Sophos;i="5.60,358,1549929600"; d="scan'208,217";a="548071580"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 16 Apr 2019 15:03:20 +0000
Received: from XCH-ALN-019.cisco.com (xch-aln-019.cisco.com [173.36.7.29]) by rcdn-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id x3GF3KfT004001 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 16 Apr 2019 15:03:20 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-ALN-019.cisco.com (173.36.7.29) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 16 Apr 2019 10:03:19 -0500
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 16 Apr 2019 10:03:19 -0500
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 16 Apr 2019 10:03:19 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vMqLSuuxXpUNT/qH3tsymLEQPdoMcxpjHOQfoY5N77M=; b=dRSwLjkkeH6cPH4r0RVLDCgWTntCZwTitMh43HVQqoRwiU9dptUBJrk4cfQFDekOUZtnvrR5lDC6fsabYbgANEpIPSToaKFWNXc7GaO1Ci8WZ3Ve0KcUCjyixitbTfoANYckmG9hpgiWtnGTAjQRryMfwsTGuhb9Od5cLrTW9Tg=
Received: from BN8PR11MB3601.namprd11.prod.outlook.com (20.178.219.23) by BN8PR11MB3713.namprd11.prod.outlook.com (20.178.220.155) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1792.19; Tue, 16 Apr 2019 15:03:17 +0000
Received: from BN8PR11MB3601.namprd11.prod.outlook.com ([fe80::8c78:bc80:a926:7111]) by BN8PR11MB3601.namprd11.prod.outlook.com ([fe80::8c78:bc80:a926:7111%4]) with mapi id 15.20.1792.018; Tue, 16 Apr 2019 15:03:17 +0000
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Tim Chown <Tim.Chown@jisc.ac.uk>
CC: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] Reminder: Call for Adoption - draft-bvtm-dhc-mac-assign - Respond by April 16, 2019
Thread-Index: AdTvpvkfFejm0yNeScSuZcNL7Y5QUAElyRUAAAF3qYA=
Date: Tue, 16 Apr 2019 15:03:17 +0000
Message-ID: <ED8065BD-322F-414B-ABAA-A6274194C3DE@cisco.com>
References: <BN8PR11MB360181ED5E398DC994FD81D5CF2E0@BN8PR11MB3601.namprd11.prod.outlook.com> <D68FA680-2DBC-49B6-8370-ADB0A29AEA8F@jisc.ac.uk>
In-Reply-To: <D68FA680-2DBC-49B6-8370-ADB0A29AEA8F@jisc.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.17.1.190326
authentication-results: spf=none (sender IP is ) smtp.mailfrom=volz@cisco.com;
x-originating-ip: [2001:420:2c51:1321:60dd:42a4:fc13:80fb]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f7ac7fb5-71b4-4add-0ad9-08d6c27ca876
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600140)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:BN8PR11MB3713;
x-ms-traffictypediagnostic: BN8PR11MB3713:
x-ms-exchange-purlcount: 7
x-microsoft-antispam-prvs: <BN8PR11MB37135F14E4F6BB4BAF13BDCDCF240@BN8PR11MB3713.namprd11.prod.outlook.com>
x-forefront-prvs: 000947967F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(136003)(376002)(39860400002)(396003)(346002)(12213003)(189003)(199004)(83716004)(105586002)(46003)(6916009)(71200400001)(106356001)(5660300002)(2616005)(14454004)(8936002)(71190400001)(99286004)(6506007)(2906002)(11346002)(229853002)(6246003)(53546011)(486006)(7736002)(102836004)(97736004)(476003)(86362001)(36756003)(76176011)(316002)(53936002)(606006)(58126008)(8676002)(68736007)(256004)(33656002)(966005)(236005)(14444005)(4326008)(54896002)(6486002)(81166006)(186003)(81156014)(6512007)(478600001)(82746002)(6306002)(6436002)(6116002)(25786009)(446003); DIR:OUT; SFP:1101; SCL:1; SRVR:BN8PR11MB3713; H:BN8PR11MB3601.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: qDNZCKYyYla21aRw06n2k2WiDlyCzfxrddLCZrke6sDQcX3Pyp7xCyFfWU2tQj19oJsCkxvb867VubNDBq/7oM6KI5JWrOljABKEFShKn7cx/Ulb00KhjjcFVK7Y/gFIcKK5eSEWP7DJDo1cGYOsnciv0w6N2C+XHJJLhH0JelsJizLuicauoBIFr8t+FtNHN6lTceZWkXwwl1fgn7ch4xpe15BgGRxiukGqbn5nn1Ms/1bQQgZuBy8t8dTmRvE6WBmzWVhMg4+qIyc+cc63ddDL6iHjRBVkolT2eA9QbHNm0GBp55/VelXYCkE/WE8PnigFtZrkD6y07lrascQz4delB+zhktpwYkpS/fOshE4oB843sYrEzNrzQW00a6guTeHCWhWBQzFDrKCGRag20FEY70gbHad+QYhmvdCil10=
Content-Type: multipart/alternative; boundary="_000_ED8065BD322F414BABAAA6274194C3DEciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: f7ac7fb5-71b4-4add-0ad9-08d6c27ca876
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Apr 2019 15:03:17.5754 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN8PR11MB3713
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.29, xch-aln-019.cisco.com
X-Outbound-Node: rcdn-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/yWdpAijtY46qxr-dRHlvaoijoAY>
Subject: Re: [dhcwg] Reminder: Call for Adoption - draft-bvtm-dhc-mac-assign - Respond by April 16, 2019
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Apr 2019 15:58:59 -0000

That is certainly a good question.

I do intend for this support to be implemented in Cisco Prime Network Registrar’s DHCP server, but I don’t have final say in exactly what gets in and when. Thus, this is just my intent to push for it being done, and not an official statement.

It will be interesting to learn if there are any client implementations planned (such as for hypervisors), as that will drive the servers and provide more data to those that do have final say.

It is always a chicken and egg issue – and the more time that goes by, people will look for alternatives (i.e., obtaining an OUI space from IEEE).

  *   Bernie
From: Tim Chown <Tim.Chown@jisc.ac.uk>
Date: Tuesday, April 16, 2019 at 6:21 AM
To: Bernie Volz <volz@cisco.com>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Reminder: Call for Adoption - draft-bvtm-dhc-mac-assign - Respond by April 16, 2019

Do we have any expression of interest from those who would implement it, and the associated other draft with the call for adoption out?

Tim

On 10 Apr 2019, at 15:09, Bernie Volz (volz) <volz@cisco.com<mailto:volz@cisco.com>> wrote:

Hi … just a friendly reminder that this call for adoption is outstanding – you have just under a week to comment.

Thanks much!


  *   Bernie

From: Bernie Volz (volz)
Sent: Wednesday, March 27, 2019 9:56 AM
To: dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Cc: draft-bvtm-dhc-mac-assign@ietf.org<mailto:draft-bvtm-dhc-mac-assign@ietf.org>
Subject: Call for Adoption - draft-bvtm-dhc-mac-assign - Respond by April 16, 2019

Hi:

As discussed at the DHC WG session at IETF-104, we are trying another call … this starts the WG Call for Adoption for the draft-bvtm-dhc-mac-assign-02 document. Please respond by end of day April 16, 2019 whether you support adoption of this work or not.

This was presented at IETF-104 (see https://datatracker.ietf.org/meeting/104/materials/slides-104-dhc-link-layer-addresses-assignment-mechanism-for-dhcpv6-refresher-01) and also IETF-101 (seehttps://datatracker.ietf.org/meeting/101/materials/slides-101-dhc-mac-addresses-assignment-for-dhcpv6-01) and discussed with our Area Director (Suresh) as acceptable work for the DHC WG to adopt. This work was also presented by Tomek and Bernie to the IEEE P802.1CQ discussions at the OmniRAN meeting in May 2018 – slides available at https://github.com/dhcwg/dhcp-mac/blob/master/ietf-dhc-mac-assign.pdf, as the IEEE is exploring allocation protocols.

If you are silent, it is not possible for us to know your support or lack therefore; so please do respond if you feel this work is something the DHC WG should (or should not) work on.

Thanks much!


  *   Tomek & Bernie

PS: We will also start a call on the extension work draft-bernardos-dhc-slap-quadrant<https://www.ietf.org/archive/id/draft-bernardos-dhc-slap-quadrant-01.txt> shortly.
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org<mailto:dhcwg@ietf.org>
https://www.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email