Re: [openc2-imple] Draft Agenda for IC-SC portion of Face to Face

[Dave Lemire <dave.lemire@g2-inc.com>]

I'd like to thank Joe for chairing the 2 JanuaryÂmeeting while I was on vacation, and for going above and beyond to produce this proposal for IC-SC discussions at the F2F meeting.

Dave

David P. Lemire, CISSP
 OpenC2 Technical Committee Secretary
 OpenC2 Implementation Considerations SC Co-chair
 Contractor support to NSA
Email: dave.lemire@g2-inc.com
Office: 301-575-5190 / Mobile: 240-938-9350

On Thu, Jan 3, 2019 at 8:40 AM Brule, Joseph M <jmbrule@radium.ncsc.mil> wrote:

Implementation Considerations Subcommittee,

At the last monthly meeting, the Technical Committee tasked the editors of the specifications to assist in planning the agenda for the Face to Face. ÂThe scope of the tasking is to provide a listing of the comments to be resolved and approximate time required for discussion.Â

REQUEST: Please comment on the topics and time estimates for the Face to Face agenda. It would be especially beneficial if you could look at the CRM spreadsheet and github issues and provide comments in advance.Â

PROPOSED Implementation Considerations Agenda:Â (Bottom Line Up Front: )

Public Review Comments:
*Â Â Â ÂRecommendations from the IC-SC (45 minutes)
*Â Â Â ÂSerialization and Conformance Section (30 minutes)
*Â Â Â ÂRefer to Language Specification Discussions (45 minutes)
*Â Â Â ÂMechanical/ non-material (15 minutes)

Here are some additional details that helped us estimate the time required:

A spreadsheet was created ( https://docs.google.com/spreadsheets/d/15RUBgNRoSZzuxhCt5TPX46qU5m9uPYbWkOHUbjNwH54/edit#gid=0 ) that lists issues and provides a link to the email that generated the issue, a link to an issue on github and a pull request that attempts to resolve the issue. Please put the pull request in perspective, the pull requests are simply a suggestion or an attempt to resolve the comment and not necessarily a final resolution.Â

The following issues are 'mechanical' in nature. That is to say, they involve typos, wording, cross checking references etc. I estimate that the following issues will take less than 15 minutes
*Â Â Â ÂMessage examples should use example dates rather than template (HTTPS-3)
*   ÂEnsure consistency in the front matter (aka boilerplate in section 1) (HTTPS-4, HTTPS-8, HTTPS-9, HTTPS-10, HTTPS-11 HTTPS-14, HTTPS-16)
*Â Â Â ÂTypographical errors and minor wordsmithing (HTTPS-6, HTTPS-7, HTTPS-12, HTTPS-13, HTTPS-17)
*Â Â Â ÂAdd hyperlinks where appropriate (HTTPS-15)
*Â Â Â ÂSet and use language to distinguish between normative and nonnormative (HTTPS-25)

The following issues are interrelated with the Language Specification. We will need some time to determine the best way to incorporate, but much of this will be influenced by the language spec discussions.
*   ÂCommand_id: This will be discussed at the language spec, however we need to discuss it in the context of a transfer spec. Suggest 45 minutes. (HTTPS-22, HTTPS-20)

The IC-SC did reach a consensus on the following issues, but we want to spend some time discussing during the F2F. Suggest 30 minutes.
*Â Â Â ÂSerialization and conformance (HTTPS-1)
*Â Â Â ÂPolling Scenario (HTTPS-23)
*Â Â Â ÂRemove 'notification' (HTTPS-20)
*Â Â Â ÂMutual Authentication and TLS Version 1.3 (HTTPS-27, HTTPS-24)


Thank you



Joe Brule
Engineering (Y2D122)
FNX-3, B4A335
410.854.4045
'Adnius ad retinedam puritem noster peciosus corporalis fluidorum...'
I welcome VSRE emails. Learn more at http://vsre.info/



---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php