Re: CVE Pilot Approach

• To: "Sain, Joe" <jas@mitre.org>, cve-editorial-board-list <cve-editorial-board-list@lists.mitre.org>
• Subject: Re: CVE Pilot Approach
• From: "Landfield, Kent B" <kent.b.landfield@intel.com>
• Date: Fri, 18 Mar 2016 15:01:22 +0000
• Accept-language: en-US
• Authentication-results: spf=none (sender IP is 129.83.29.3) smtp.mailfrom=LISTS.MITRE.ORG; mitre.mail.onmicrosoft.com; dkim=none (message not signed) header.d=none;mitre.mail.onmicrosoft.com; dmarc=none action=none header.from=intel.com;
• Delivery-date: Mon Mar 21 08:28:24 2016
• In-reply-to: <SN1PR09MB10388E8577FA8D374F67C5BCB18C0@SN1PR09MB1038.namprd09.prod.outlook.com>
• List-help: <mailto:LISTSERV@LISTS.MITRE.ORG?body=INFO%20CVE-EDITORIAL-BOARD-LIST>
• List-owner: <mailto:CVE-EDITORIAL-BOARD-LIST-request@LISTS.MITRE.ORG>
• List-subscribe: <mailto:CVE-EDITORIAL-BOARD-LIST-subscribe-request@LISTS.MITRE.ORG>
• List-unsubscribe: <mailto:CVE-EDITORIAL-BOARD-LIST-unsubscribe-request@LISTS.MITRE.ORG>
• References: <SN1PR09MB10388E8577FA8D374F67C5BCB18C0@SN1PR09MB1038.namprd09.prod.outlook.com>
• Sender: <owner-cve-editorial-board-list@lists.mitre.org>
• Spamdiagnosticmetadata: 43da9c421be74aed97248473db21fd15
• Spamdiagnosticoutput: 1:2
• Thread-index: AdGBJEOfo2i4ZLWYR/2qDMpuK8UH9QAE4iYA
• Thread-topic: CVE Pilot Approach
• User-agent: Microsoft-MacOutlook/0.0.0.160212

Thank you.

As for a meeting next week….  I am totally booked Monday thru Wednesday 
and only available Thursday morning and all day Friday.
---
Kent Landfield
+1.817.637.8026

From: 
<owner-cve-editorial-board-list@lists.mitre.org<mailto:owner-cve-editorial-board-list@lists.mitre.org>>
 on behalf of "Sain, Joe" <jas@mitre.org<mailto:jas@mitre.org>>
Date: Friday, March 18, 2016 at 9:50 AM
To: cve-editorial-board-list 
<cve-editorial-board-list@lists.mitre.org<mailto:cve-editorial-board-list@lists.mitre.org>>
Subject: CVE Pilot Approach

Yesterday, we described to you a plan to test a pilot approach that 
addresses the rapid-response security researcher use case. A number of 
concerns with the proposed syntax were raised, and we heard them 
clearly. As a result of your feedback, we will not move forward with a 
public announcement of the pilot plan, which we are putting on 
indefinite hold.

The pilot described yesterday was designed to run in parallel and to be 
completely separate from the production CVE stream, but we certainly 
understand the importance of not perturbing any operating aspect of 
CVE. Our goal is to be responsive to the critical need for the 
no-description use case, but we must also ensure that we have the 
correct operating model.

We would like to hold an Editorial Board meeting next week to discuss 
approaches to addressing the security researcher use case as well as 
any other issues or concerns that the Board may have. We want to be 
certain that every Board member has the opportunity to voice their 
opinions, concerns, and ideas. An agenda will be forthcoming.

We truly appreciate your feedback, and we are looking forward to 
developing an operating model that enables CVE to move forward and that 
preserves the foundational work that the community has put into the 
effort.

Regards,

Joe Sain
CVE Communications and Adoption Lead
The MITRE Corporation

• References:
  • CVE Pilot Approach
    • From: "Sain, Joe" <jas@mitre.org>

• Prev by Date: CVE Pilot Approach
• Next by Date: Scheduling a Board Discussion Telecon
• Previous by thread: CVE Pilot Approach
• Next by thread: Scheduling a Board Discussion Telecon
• Index(es):
  • Date
  • Thread