OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

openc2-imple message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Draft Agenda for IC-SC portion of Face to Face


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/ 




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]