Welcome to the NIST IR 8112 Public Draft! We’re excited to share this publication and collaboratively enhance it openly with our stakeholder community.
Click here to access the document.
Feedback on any part of this publication is welcomed and encouraged. We opted to publish this document as a NISTIR in an effort to treat it as an implementers’ draft, an approach common in the development lifecycle of many private sector standards and specifications. This allows the developer and policy community, in both the public and private sectors, to apply some or all of the metadata in this NISTIR on a volunteer basis, and provide us with practical feedback gained through implementation experience.
A formal 60-day (01 August 2016 - 30 September 2016) comment period was previously held to gain initial feedback on the document. Further development of the NISTIR relies upon the application of the NISTIR’s schema in actual solutions and implementations, so we are finalizing this NISTIR in order for the community to start implementing this guidance. Though this is a finalized NISTIR, this is considered an initial attempt at a schema that will require implementation feedback before being developed more fully. As such, we will be maintaining this public page beyond the initial 60-day comment period and the NISTIR’s finalization to continually receive input and iteratively improve the document in anticipation of a second revision. Some specific questions we are interested in answering both in the short and long term include:
Commenters are STRONGLY encouraged to publically collaborate with the team and other participants via GitHub—see this page for details on how to submit a comment. In order to maintain a lean approach we would prefer to receive comments through GitHub rather than via email, Excel, or other file types. However, we will accept comments in these formats—they can be sent to email@example.com. In instances where comments come to us outside of GitHub, we will post them to GitHub, preserving commenter anonymity, so that we can continue to manage and track edits using “issues” native to GitHub. We thank you in advance for your efforts to keep this process streamlined for the editors.
Information from the workshop held in January 2016 can be found here.