Might not have been best one to start with. Hopefully todays rdmase has more meat in it of relevance to OpenC2. If nothing else, they should spark thoughts on what they should have had in them.
Suggestions on improving the English would be welcome. Developing more concrete use cases (especially if used OpenC2
😊 ) would also be welcome.
Back in the day most ITU recs were written in either French or English with some Japanese, but now the Chinese contribute more than everyone else combined, with Korea in second place. I consider us lucky we still meet and draft in English.
Some of the awkwardness is 2nd-language issues. Some is trying to do too much with too little effort - and therefore not doing good quality control. But some is compromised wording. I just was on a call that agreed to really
horrible awkward title as a compromise (allowed both sides to have their way â so its effectively meaningless to anyone not present. I made that point to no avail). âA camel is the compromise of a committee trying to design a horseâ. Outside eyes without baggage
help â ie comments welcome.
I talked one group today into letting me put their work on github so we could track issues and do better change control. They are letting me try as an experiment. Hopefully that will catch on and make stuff like this easier in future. Of
course that means I need to do the work to get it on github.
😊
Duncan Sparrell
sFractal Consulting LLC
iPhone, iTypo, iApologize
I welcome VSRE emails. Learn more at http://vsre.info/
From: Dave Lemire <dave.lemire@g2-inc.com>
Date: Monday, March 23, 2020 at 9:05 AM
To: "duncan@sfractal.com" <duncan@sfractal.com>
Cc: TC OpenC2 <openc2@lists.oasis-open.org>
Subject: Re: [openc2] Groups - X.fgati uploaded
I took the time to read this on Friday. It's relatively high level, so I don't see a lot of potential to extract use cases from it.
Also, based on the Chinese authors I presume this is English as a 2nd language, but it got me wondering if many ITU documents are as repetitive as this.
HII Mission Driven Innovative Solutions (HII-MDIS) â formerly G2, Inc.
Technical Solutions Division
302 Sentinel Drive | Annapolis Junction, MD 20701
Email:
dave.lemire@g2-inc.com
Email (effective 1 April 2020):
david.lemire@hii-tsd.com
Work: 301-575-5190 |
Mobile: 240-938-9350
Submitter's message
This proposed ITU recommendation X.fgati "Framework and Guidelines for Applying Threat Intelligence in Telecom Network Operation" is from ITU SG17 mtg 3/2020. OC2 members should be pleased to note that our OpenC2 specs are referenced, included in the figure
7-1 as the interface to firewalls, ids, anti-ddos, etc. Of special interest, note the wording near the end of section 7 that states "Security command and control is recommended to use OASIS OpenC2 specifications". "is recommended" is less strong than "is required"
but is still pretty good. It means OC2 is the preferred approach but you are allowed to use other interfaces. Members of OC2 TC may want to review this document for use cases we have not yet covered so we can further expand our language, actuator profiles,
and transport specs to meet all needs.
-- Mr. Duncan Sparrell
|
Document Name:
X.fgati
Description
A proposed ITU recommendation X.fgati "Framework and Guidelines for
Applying Threat Intelligence in Telecom Network Operation" from ITU SG17
mtg 3/2020
Download Latest Revision
Public Download Link
Submitter: Mr. Duncan Sparrell
Group: OASIS Open Command and Control (OpenC2) TC
Folder: Documents
Date submitted: 2020-03-20 01:33:29
|