Erroneous warnings raised for not providing a start or end for components>protocols>port-ranges

[Telos-sa]

Describe the bug

When validating an SSP with the oscal-cli, a warning is raised saying that a start port exists but an end doesn't and vice versa, when both start and end are present in the OSCAL being validated.

Warning:

OSCAL SSP section being flagged:

Who is the bug affecting

Any user looking to validate their OSCAL SSP with port-ranges provided.

What is affected by this bug

OSCAL Content

How do we replicate this issue

1. Create an OSCAL SSP with a component>protocol>port-ranges element (with start and end provided).
2. Validate the OSCAL SSP with the oscal-cli

Expected behavior (i.e. solution)

No warning should be raised (clutters the error log) when there is no actual issue with the port-ranges structure.

Other comments

No response

Revisions

No response

[iMichaela]

This is fixed by the commit 751e2d7 in develop branch and will be released with all other fixies in develop as soon as we address the camelCase data type issue which was removed but it is being requested back by GSA.