[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: Remaining HTTPS Issues and Pull Requests
IC-SC Members,If I exclude the issues associated with commonality of Section 1 content, there are only a few unresolved issues on the HTTPS Specification:Lacking any input through on-line fora (GH, email, or Slack), I propose that these changes are the agenda for next Wednesday's IC-SC meeting (6 Feb) so that we can wrap up the resolution of public review #1 comments.ÂÂ
- HTTPS-2 and -16, both of which relate to aligning requirements for the Date: field in the header to the relevant RFC. Pull requests exist for both of these (30 and 27, respectively)
- HTTPS-22, which relates to the command_id / request_id issue that was resolve at the F2F. I have a comment in the #implementation channel on Slack regarding properly implementing the resolution of that in the HTTPS spec
https://openc2-community.slack.com/archives/C5RF00U9Z/p1548971394058600- HTTPS-23 to remove the polling model. I created a pull request to implement this (#61). As this is a major change to the specification I'd appreciate other eyes on that PR to verify that I've gotten it right.
- HTTPS-26 and -27, which deal with authentication requirements and mechanisms. The separate PRs for these have been merged into PR #58, as discussing the changes for these independently was proving very awkward. This PR would also benefit from a sanity check from SC members.
Please look over the change and provide feedback. AÂ+1 in the GH issue or PR is sufficient. Thanks,DaveDavid 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]