Some experiences from implementing the Extensible Provisioning Protocol
draft-sullivan-epp-experience-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Andrew Sullivan | ||
| Last updated | 2005-08-12 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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-sullivan-epp-experience-00.txt
https://www.ietf.org/archive/id/draft-sullivan-epp-experience-00.txt
Abstract
This memo presents some experiences of a registry operator using the Extensible Provisioning Protocol (EPP). Some limitations of the protocol definition and associated documents are identified, and some alterations are suggested.
Authors
Andrew Sullivan (andrew@ca.afilias.info)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)