Re: [EXT] Re: [cti] New version of the Extension Definition Policy docum

Its available from our “cover page” - https://docs.google.com/document/d/1yvqWaPPnPW-2NiVCLqzRszcx91ffMowfT5MmE9Nsy_w

I thought everything on that page was available to anyone on the CTI TC.

Emily, can you confirm this??

From: Jamie Clark <jamie.clark@oasis-open.org>
Date: Friday, January 20, 2023 at 7:59 PM
To: Rich Piazza <rpiazza@mitre.org>
Cc: Chet Ensign <chet.ensign@oasis-open.org>, OASIS CTI TC Discussion List <cti@lists.oasis-open.org>
Subject: [EXT] Re: [cti] New version of the Extension Definition Policy document

Sorry, is this a private Google Doc? Not visible to me. I assume that manually loading the name of every member of CTI TC, into the perms for each one-off doc of this type, also would be a bit burdensome?

Regards and happy weekend all Jamie

James Bryce Clark, General Counsel, OASIS Open, setting the standard for open collaboration

On Fri, Jan 20, 2023 at 12:46 PM Rich Piazza <rpiazza@mitre.org> wrote:

Hi All,

Version 1.1 of the policy document is available for review. Much has been added since version 1.0 and the document has been reorganized.

The major additions are:

An additional level of extension definitions, called “External”. This is for extension content that is developed and managed independent of the CTI TC (e.g., TLP 2.0). It was suggested that such content not be part of the specification, because its release schedule is unrelated to STIX’s.
Best Practices for creating an Extension Definition, including the related JSON schema
How to incorporate an approved Extension Definition into a future specification

Please read the document for more details.

The document will be reviewed starting at the 24 January WG meeting.

This document was originally written as a Committee Note, but it contains normative language, so it cannot be officially published as such because normative language is not permitted. The TC could publish it as a Committee Specification Draft, or the normative words can be made informative, and it can remain a Committee Note. The TC needs to decide which format will be used.

All the best,

Rich

--

Rich Piazza

Lead Cyber Security Engineer

The MITRE Corporation

781-271-3760

––––––––––––––––––––––––––––––––––––

MITRE - Solving Problems for a Safer World™

cti message