Michaela Iorga

Changed label from bug to enhancement since discrepancies between latest OSCAL and the oscal-cli modified and used by FedRAMP do not identify bugs in current OSCAL. Any oscal-cli is meant...

@aj-stein-gsa - **I find some of your comments above insulting.** The `oscal-cli` v1.1.2 you released is using `metaschema-java` code that implements Metaschema 0.9.0 and not 0.10.0 (the latest released by...

I asked the community for input on this issue and no preference on how to address it was provided from the community. Since a patch v1.1.3 is being prepared and...

> [THIS](https://github.com/usnistgov/OSCAL/blob/v1.1.2/src/metaschema/oscal_assessment-common_metaschema.xml#L64-L75) is incorrect: > > ``` > > > **(deprecated)** Use 'assessment-objective' instead. > **(deprecated)** Use 'assessment-method' instead. > The part defines an assessment objective. > The part defines...

I agree with @david-waltermire, and as long as FedRAMP is aware of the bug, I can release 1.1.3 without it, BUT this bug has been raised to us (NIST) several...

> We have developed a solid test harness for testing external constraints at FedRAMP. We would be glad to offer tuning up the OSCAL repo CI/CD with some of these...

@aj-stein-nist and @Telos-sa -- All comments above are addressing more than what the issue is calling for: "_**how information is flowing throughout the accreditation boundary and how these ports and...

> An Internet Protocol Version 6 interconnection address I believe there is an error in the description for 'direction" in the enumeration above. And the value fro the "direction" should...

> @iMichaela currently, "direction" as a property name is only in the allowed values list for component type "interconnection". I am suggesting that it belongs anyplace `protocol` belongs, and that...

Per @aj-stein-gsa's note in the PR #2063, this initial issue should have addressed by that PR. Are we saying it si not because there are additional findings, or because the...