iMichaela
commented
3 weeks ago @Telos-sa - This is an OSCAL schema issue not OSCAL content. Can you please move the issue to the https://github.com/usnistgov/OSCAL repo? . I could do it myself, but it would not preserve the issue ownership. With the said - is the capitalization of the allowed values TCP and UDP such a difficult issue that it cannot be addressed programmatically and requires a schema change? Maybe there is more background info related to this issue that we could benefit from better understanding it?
Also important to note that oscal-cli supports the OSCAL schemas so the change is NOT in oscal-cli Thank you.
Telos-sa
User Story:
As an OSCAL {stakeholder}, I want to pass a token styled data, and it still validate as long as the token format is met.
Goals:
Adjust the requirements and validations for transport token, to allow either TCP/tcp UDP/udp as either format would be an accepted token format
Dependencies:
Updating the SSP model reference on the Nist Site. Updating metaschema to support all token formats for each token, updating validation.
Acceptance Criteria
{The items above are general acceptance criteria for all User Stories. Please describe anything else that must be completed for this issue to be considered resolved.}