Last Call Review of draft-ietf-regext-epp-rdap-status-mapping-01
review-ietf-regext-epp-rdap-status-mapping-01-secdir-lc-murphy-2016-10-20-00

Request Review of draft-ietf-regext-epp-rdap-status-mapping
Requested revision No specific revision (document currently at 04)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2016-10-10
Requested 2016-09-29
Authors James Gould
I-D last updated 2016-10-20
Completed reviews Genart Last Call review of -01 by Robert Sparks (diff)
Secdir Last Call review of -01 by Sandra L. Murphy (diff)
Opsdir Last Call review of -01 by Mehmet Ersue (diff)
Assignment Reviewer Sandra L. Murphy
State Completed
Request Last Call review on draft-ietf-regext-epp-rdap-status-mapping by Security Area Directorate Assigned
Reviewed revision 01 (document currently at 04)
Result Ready
Completed 2016-10-20
review-ietf-regext-epp-rdap-status-mapping-01-secdir-lc-murphy-2016-10-20-00
I have reviewed this document as part of the security directorate’s ongoing
effort to review all IETF documents being processed by the IESG. These comments
were written primarily for the benefit of the security area directors. 
Document editors and WG chairs should treat these comments just like any other
last call comments.

The draft draft-ietf-regext-epp-rdap-status-mapping identifies gaps in the
mapping of EPP statuses to RDAP statuses that are registered in the IANA RDAP
JSON Values Registry.  The draft provides entries in the RDAP JSON Values
Registry to fill those gaps.

I see no security issues with this draft.

—Sandy

Attachment:

signature.asc

Description:

 Message signed with OpenPGP using GPGMail