Proposed OpenC2 Language Spec Agenda 8/20/2019

["Considine, Toby" <Toby.Considine@unc.edu>]

OpenC2 Language Spec Agenda 8/20/2019

1.0  Welcome â

2.0  Topics â

Nominations for a new Co-Chair to replace Jason Romanoâ

This is his last LS Meetingâ

3.0 Standard JSONâ

Standard JSON Schemasâ

- Jason Romanoâ

- Brian Berlinerâ

3.0 Status Codesâ

- Other Status Codes defined by IANA (David Kempâ

- The LS defines a response as containing one of nine specific HTTP status codes, and additional codes can be added as needed.  A response containing a status code not listed in the LS, such as 201 - Created (listed by IANA https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml), or 273 (which is unassigned) is invalid in LS v1.0.   Should v1.1 allow unassigned status codes? â

4.0 Next Stepsâ

- Review of Use Casesâ

- Review Custom Actuator Profilesâ

- primary work is in Implementations SCâ

- CAPs are a potential Source of new language requirementsâ

https://github.com/oasis-tcs/openc2-capâ

Trend Micro Custom Profileâ

â

5.0 Time Permittingâ

- Other Status Codes defined by IANA (David Kempâ

The LS defines a response as containing one of nine specific HTTP status codes, and additional codes can be added as needed.  A response containing a status code not listed in the LS, such as 201 - Created (listed by IANA https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml), or 273 (which is unassigned) is invalid in LS v1.0.   Should v1.1 allow unassigned status codes? â

- Message Types other than Commandâ

6.0 Wrap-Up â

â Actionsâ

â Next Meeting Tuesday, September 3â

â Full TC, tomorrow, 8/21â