Verification Code Extension for the Extensible Provisioning Protocol (EPP)
draft-gould-eppext-verificationcode-04

Document Type Replaced Internet-Draft (individual)
Last updated 2016-09-29
Replaced by draft-ietf-regext-verificationcode
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-regext-verificationcode
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-gould-eppext-verificationcode-04.txt

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.

Authors

James Gould (jgould@verisign.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)