Skip to content

Incorrect use of normative text (MAY NOT) in 6.12 #338

@cmschmidt

Description

@cmschmidt

The second sentence of 6.12 (Network Traffic Object) contains the phrase "The network traffic MAY or MAY NOT constitute a valid unicast, multicast, or broadcast network connection.". MAY NOT is not a valid normative marker (see RFC 2119) and is ambiguous. ("You may not do X" is generally understood to be a prohibition against doing X, rather than simply noting that one "might not" do X.)

The sentence should be changed to "The network traffic MAY constitute a valid unicast, multicast, or broadcast network connection." Alternately, if the point is to emphasize the potential of capturing invalid connections, the sentence could be changed to "The network traffic might not constitute a valid unicast, multicast, or broadcast network connection."

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions