John, The 2119 words MUST and MAY are used to signify requirements; although that does imply interoperability as well. This statement is associated with making the verification code functional, since the verification code represents a signed and typed verification pointer, it must point to something. The VSP is required, by the normative MUST, to store the proof of verification and the generated verification code, and can optionally, by the normative MAY, store the verified data. The "; and MAY store the verified data" can be removed, since the proof of verification is the only requirement for the verification code to be a functional pointer.
Do you agree that the "; and MAY store the verified data" text should be removed? The statement would then read: "The VSP MUST store the proof of verification and the generated verification code." Thanks, — JG James Gould Distinguished Engineer jgo...@verisign.com 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com <http://verisigninc.com/> On 12/28/18, 2:45 PM, "regext on behalf of John Levine" <regext-boun...@ietf.org on behalf of jo...@taugh.com> wrote: In article <41f72627-faf2-1fd4-b356-065b3cb98...@cis-india.org> you write: >"The VSP MUST store the proof of verification and the generated >verification code; and MAY store the verified data." The 2119 words MUST and MAY are about interoperation. Now that you point it out, this has nothing to do with interoperation unless compliance somehow affects interop. I would suggest removing that part, or at least making it non-normative since business practices are generally way out of scope for IETF specs. R's, John _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
