Re: [openc2] Groups - Explanation for Liaison uploaded

[Bret Jordan <bret.jordan@broadcom.com>]

For what it's worth, I fully support moving OpenC2, if we feel it is done and ready for prime time, to the ITU and for that matter even to ETSI. I know some are always concerned about change control and what that will mean if we submit to another standards body. But I am not worried about that. If we can step aside and look at the broader picture and the chance for broader adoption (think international treaties and national regulations), then sometimes we need to be willing to let go a bit. I highly doubt the ITU or ETSI will make or suggest any major changes. And honestly, if they did, we should probably listen.ÂÂ

So regardless, I support this and will be there in person.

Thanks,

Bret

PGP Fingerprint:Â63B4 FC53 680A 6B7D 1447 ÂF2C0 74F8 ACAE 7415 0050

"Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg."

On Mon, Feb 17, 2020 at 2:37 PM Duncan Sparrell <duncan@sfractal.com> wrote:

Submitter's message
I am proposing the TC vote to send a liaison to ITU SG17 on our recent specifications. The ITU 2017-2020 study period is coming to a close and it behooves us to get into their queue at their upcoming March meeting. This document has some explanation forthe proposed text which is in a companion document
-- Mr. Duncan Sparrell

Document Name: Explanation for Liaison

---

Description
I am proposing the TC vote to send a liaison to ITU SG17 on our recent
specifications. The ITU 2017-2020 study period is coming to a close and it
behooves us to get into their queue at their upcoming March meeting. This
document has some explanatio forthe proposed text which is in a companion
document
Download Latest Revision
Public Download Link

---

Submitter: Mr. Duncan Sparrell
Group: OASIS Open Command and Control (OpenC2) TC
Folder: Documents
Date submitted: 2020-02-17 13:36:58