[Last-Call] Opsdir telechat review of draft-ietf-regext-epp-registry-maintenance-17

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Reviewer: Joe Clarke
Review result: Has Nits

I have been tasked to review this document on behalf of the OPS Area
Directorate.  This document describes an EPP extension for conveying
maintenance events to EPP clients.  Overall, I find the document mostly ready,
but I do have a few questions, and I found a few typos.

===

Section 3.3

What is the use case for having <maint:start> be equal to <maint:end>?  I would
think you'd always want the end time to be in the future to be a relevant
maintenance event.

===

Section 3.3

s/negotiated value is something other then the/negotiated value is something
other than the/

===

Section 3.3

If one of the intervention elements is true, how does one find out the details
of the connection or implementation-related intervention?  I imagine the URI
would provide that, but I was expecting to see it stated in this document in
the description of these elements.

===

Section 4.1.4

s/command and response is defined/command and response are defined/


-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call



[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux