All,

I have read the draft and think it is good to go +1 for that

I do have one clarification question with respect to the reseller drafts. When 
reading https://tools.ietf.org/html/draft-ietf-regext-reseller-00#section-3.3 
there are 2 statuses defined that are not known statuses (readonly and 
terminated).

I expect that one day the reseller data will also be available as a RDAP 
entity. At that point in time these two fields could be simply registered with 
IANA in the "RDAP JSON Values Registry” right? Is it something to consider to 
do it right away in the reseller drafts while we are working on them or 
can/should this be done later.

Gr,
Rik


On 05 Jul 2016, at 18:38, Andrew Newton <a...@hxr.us<mailto:a...@hxr.us>> wrote:

I have reviewed this draft and think it is good to go.

-andy

On Tue, Jul 5, 2016 at 11:41 AM, Gould, James 
<jgo...@verisign.com<mailto:jgo...@verisign.com>> wrote:
I posted the 01 draft that incorporates the feedback received during the WG 
last call.  Let me know if I missed anything.

Thanks,

—

JG


<BF09FAA4-32D8-46E0-BED0-CD72F43BD6E0[81].png>

James Gould
Distinguished Engineer
jgo...@verisign.com<http://jgo...@verisign.com/>

703-948-3271<tel:703-948-3271>
12061 Bluemont Way
Reston, VA 20190

VerisignInc.com<http://verisigninc.com/>

On Jul 5, 2016, at 8:27 AM, 
internet-dra...@ietf.org<mailto:internet-dra...@ietf.org> wrote:


A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Registration Protocols Extensions of the IETF.

       Title           : Extensible Provisioning Protocol (EPP) and 
Registration Data Access Protocol (RDAP) Status Mapping
       Author          : James Gould
Filename        : draft-ietf-regext-epp-rdap-status-mapping-01.txt
Pages           : 11
Date            : 2016-07-05

Abstract:
  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.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-regext-epp-rdap-status-mapping/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-regext-epp-rdap-status-mapping-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-regext-epp-rdap-status-mapping-01


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<http://tools.ietf.org/>.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
regext mailing list
regext@ietf.org<mailto:regext@ietf.org>
https://www.ietf.org/mailman/listinfo/regext


_______________________________________________
regext mailing list
regext@ietf.org<mailto:regext@ietf.org>
https://www.ietf.org/mailman/listinfo/regext


_______________________________________________
regext mailing list
regext@ietf.org<mailto:regext@ietf.org>
https://www.ietf.org/mailman/listinfo/regext

_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

Reply via email to