Title:

Description: Section 3.3 of the attachment spec contains notmative text that appears on the surface as non-normative guidance (a MUST that hides behind a "Note that ...").

Also, the text seems to be limited to use of the PolicyURIs attribute, however, I don't believe that was the intent. I believe that it was intended to place a constraint on policy attachment authors, that they MUST define the policy scope of the attachment.

Justification: See above. Normative text should not begin with "Note" as it seems to suggest editorial commentary.

Type: editorial

Proposal:

Change:

Note that the policy scope of the attachment is specific to the policy attachment Mechanism using it; accordingly, any policy attachment mechanism using this attribute MUST define the policy scope of the attachment.

To:

The policy scope of an attachment is specific to the policy attachment Mechanism using it. Accordingly, any policy attachment mechanism MUST define the policy scope of the attachment.

and, relocate the paragraph from section 3.3 to section 3.2