Re: CVE ID Issuance Strategies Using the New ID Syntax

• To: Art Manion <amanion@cert.org>
• Subject: Re: CVE ID Issuance Strategies Using the New ID Syntax
• From: Mark J Cox <mjc@redhat.com>
• Date: Thu, 20 Jun 2013 08:25:04 +0100
• CC: <coley@mitre.org>, <cve-editorial-board-list@LISTS.MITRE.ORG>
• Delivery-Date: Thu Jun 20 03:26:16 2013
• In-Reply-To: <51C24640.3090207@cert.org>
• References: <Pine.GSO.4.64.1306181429400.15565@faron.mitre.org> <51C24640.3090207@cert.org>
• User-Agent: Unknown

> There will probably be some head scratching about why the numbers are
> skipping around.

At the moment CNAs get whole blocks of IDs that mean we already have a lot 
of ID assignment non-linearity and names at the end of CNA blocks but in 
the middle of the entire space that never got allocated.  So no one will 
really notice any difference if you avoid some protection names.  So +0 
("don't think it matters much either way, Mitre can choose").

Mark

• References:
  • CVE ID Issuance Strategies Using the New ID Syntax
    • From: "Steven M. Christey" <coley@mitre.org>
  • Re: CVE ID Issuance Strategies Using the New ID Syntax
    • From: Art Manion <amanion@cert.org>

• Prev by Date: Re: CVE ID Issuance Strategies Using the New ID Syntax
• Prev by thread: Re: CVE ID Issuance Strategies Using the New ID Syntax
• Next by thread: Re: CVE ID Issuance Strategies Using the New ID Syntax
• Index(es):
  • Date
  • Thread