Re: [regext] WG LAST CALL: draft-ietf-regext-epp-registry-maintenance-03

Hi all,

I have a couple of comments about this document:

1) Don't understand which maintenance notifications should be returned  
by an info command including the <maint:list/> element. I mean, only 
those about both ongoing and future events or also about past events? In 
the latter case,  could it be helpful to add optional attributes to the 
<maint:list/> element which allow clients to specifiy a preferred time 
interval?  For example, "createdAfter" and "createdBefore".

2) The document makes no assumption on which <maint:maint> child 
elements should be presented in the response to an info request 
including the <maint:list/> element. However, the example in section 
3.1.3 seems to suggest that servers should return a subset of the full 
information. Should the document define the minimum information which 
servers are required to provide and clients could expect?

Best,

Mario

Il 02/10/2020 22:57, James Galvin ha scritto:
> The following working group document is believed to be ready for 
> submission to the IESG for publication as a standards track document:
>
> https://datatracker.ietf.org/doc/draft-ietf-regext-epp-registry-maintenance/ 
>
>
> This WG last call will end at close of business, Friday, 16 October 2020.
>
> Please review this document and indicate your support (a simple “+1” 
> is sufficient) or concerns with the publication of this document by 
> replying to this message on the list.
>
> The document shepherd for this document is James Galvin.
>
> Regards,
>
> Antoin and Jim
>
> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext

-- 
Dr. Mario Loffredo
Systems and Technological Development Unit
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Mobile: +39.3462122240
Web: http://www.iit.cnr.it/mario.loffredo