Technical Summary
This document describes the mapping of the Extensible Provisioning
Protocol (EPP) statuses with the statuses registered for use in the
Registration Data Access Protocol (RDAP). This document identifies
gaps in the mapping, and registers RDAP statuses to fill the gaps to
ensure that all of the EPP RFC statuses are supported in RDAP
Working Group Summary
draft-ietf-regext-epp-rdap-status-mapping is on standards track. This
document proposes new RDAP status values, motivated by EPP status
values, to be added to the original set of RDAP status values defined
in RFC7483, which is a proposed standard.
The working group agreed that some EPP statuses were missing in the
RDAP status list and after discussion there is broad agreement in the
WG for this document.
Document Quality
ICANN technical staff were a part of the discussions and review of
this document. They will seek to get these new RDAP statuses to
become part of the implementation requirements for the ICANN gTLD
program.
Verisign, SIDN and NIC.AT are currently working on implementations.
Personnel
Document shepherd is Ulrich Wisser, ulrich@wisser.se
Area Director is Alexey Melnikov, aamelnikov@fastmail.fm
Shepherd Comments
As document shepherd I have verified that all EPP statuses from RFC5731, RFC5732,
RFC5733 and RFC3915 have been included in this list. And the IANA considerations
sections fulfills the requirements for inscription mentioned in RFC7483 section 10.2.
As document shepherd I believe this document is ready for publication.
The author has confirmed following BCP78 and BCP79 in the document header.
No IPR disclosures have been submitted for this document.
After carefully reviewing the mailings lists of the regext, eppext and provreg working
groups I have found no objections to this document. From IETF meetings I recall
broad consensus that this document is ready for publication.
There are no informative references. All normative references have been verified.