Chuck Lever <chuck.lever@xxxxxxxxxx> writes: >> I think you want s/must/MUST/. There's also an unstated requirement >> that the RPC consumers have some way of accessing this information. > > IMHO the non-normative form of "must" is appropriate in this case. > > - The text is not specific enough to be part of an enforceable normative > compliance statement. > > - The remark here is about an internal RPC consumer API, as you note. > Such APIs are not something on which this document can place hard > requirements. > > However, I'm open to further comments and discussion. Hmmm, I think I'll leave that to the Security Directorate. Dale -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
