On 20/12/18 1:01 AM, Gould, James wrote: > > Your proposed Privacy Considerations section and much of your proposed Human > Rights Considerations section focuses on the interface of the VSP, which is > out-of-scope for draft-ietf-regext-verificationcode. The scope of > draft-ietf-regext-verificationcode is on the structure of the digitally > signed verification code, that represents proof of verification, and the > interface between the client (registrar) and the server (registry) to pass > the verification code. The role of the VSP is defined, but the VSP interface > and the concrete verifications is by design left out of > draft-ietf-regext-verificationcode, and therefore is out-of-scope. >
I think the previous thread with Andrew Newton clarifies why the Privacy Considerations are applicable. Could you be specific as to which HR consideration is out of scope? As you have already noted, the role of the VSP is defined and (therefore presumably) in the scope of the document. Since most HR considerations relate to the VSP's role, they are also in the scope of draft-ietf-regext-verificationcode. Thank you. Gurshabad
signature.asc
Description: OpenPGP digital signature
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
