I posted draft-ietf-regext-verificationcode-05 that incorporates the feedback received thus far from the IETF-103 REGEXT meeting. Please review and provide any additional feedback.
Thanks, — JG James Gould Distinguished Engineer [email protected] 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com <http://verisigninc.com/> On 11/21/18, 9:13 AM, "[email protected]" <[email protected]> wrote: A new version of I-D, draft-ietf-regext-verificationcode-05.txt has been successfully submitted by James Gould and posted to the IETF repository. Name: draft-ietf-regext-verificationcode Revision: 05 Title: Verification Code Extension for the Extensible Provisioning Protocol (EPP) Document date: 2018-11-21 Group: regext Pages: 38 URL: https://www.ietf.org/internet-drafts/draft-ietf-regext-verificationcode-05.txt Status: https://datatracker.ietf.org/doc/draft-ietf-regext-verificationcode/ Htmlized: https://tools.ietf.org/html/draft-ietf-regext-verificationcode-05 Htmlized: https://datatracker.ietf.org/doc/html/draft-ietf-regext-verificationcode Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-regext-verificationcode-05 Abstract: This document describes an Extensible Provisioning Protocol (EPP) extension for including a verification code for marking the data for a transform command as being verified by a 3rd party, which is referred to as the Verification Service Provider (VSP). The verification code is digitally signed by the VSP using XML Signature and is "base64" encoded. The XML Signature includes the VSP signer certificate, so the server can verify that the verification code originated from the VSP. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat _______________________________________________ regext mailing list [email protected] https://www.ietf.org/mailman/listinfo/regext
