Thanks, Jim.

Please see my comments inline.

The updates are done on GitHub for your review.

Tobias

> On 6. Apr 2021, at 18:58, Gould, James <jgo...@verisign.com> wrote:
> 
> Tobias,
>  
> In reviewing the version of the draft in GitHub, I have the following 
> feedback:
>  
> Nit – There is an extra line in the second paragraph of section 4.1.3.1 “Info 
> Maintenance Item” that looks like it needs to be removed.  
> a.  When an <info> command has been processed successfully, the EPP
> b.   
> c.  <resData>

TS: Thanks! Fixed.

> Nit – It may be useful to adjust the dates in the draft to be in the future.  
> For example:
> Section 4.1.3.1 Info Maintenance Info example
>                                                               i.      
> 2020-12-30T06:00:00Z to 2021-12-30T06:00:00Z
>                                                             ii.      
> 2020-12-30T14:25:57Z to 2021-12-30T14:25:57Z
>                                                           iii.      
> 2020-10-08T22:10:00Z to 2021-10-08T22:10:00Z
> Section 4.1.3.2 Info Maintenance List example
>                                                                i.      
> 2020-12-30T06:00:00Z to 2021-12-30T06:00:00Z
>                                                              ii.      
> 2020-12-30T07:00:00Z to 2021-12-30T07:00:00Z
>                                                            iii.      
> 2020-09-08T22:10:00Z to 2021-09-08T22:10:00Z
>                                                            iv.      
> 2021-02-15T04:30:00Z to 2022-02-15T04:30:00Z
>                                                              v.      
> 2021-02-15T05:30:00Z to 2022-02-15T05:30:00Z
>                                                            vi.      
> 2020-09-08T22:11:00Z to 2021-09-08T22:11:00Z
>                                                           vii.      
> 2020-10-17T15:00:00Z to 2021-10-17T15:00:00Z
> Section 4.1.4 “EPP <poll> Command” example
>                                                               i.      
> 2020-12-30T06:00:00Z to 2021-12-30T06:00:00Z
>                                                             ii.      
> 2020-12-30T14:25:57Z to 2021-12-30T14:25:57Z
>                                                           iii.      
> 2020-10-08T22:10:00Z to 2021-10-08T22:10:00Z

TS: I’ve added another year to each timestamp.

> Once the draft passes WGLC, my recommendation is to change the XML namespace 
> from urn:ietf:params:xml:ns:epp:maintenance-0.3 to 
> urn:ietf:params:xml:ns:epp:maintenance-1.0
>  

TS: Will keep that in mind and do the update after WGLC.

> Thanks,
>  
> -- 
>  
> JG
> 
> <image001.png>
> 
> James Gould
> Fellow Engineer
> jgo...@verisign.com 
> <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgo...@verisign.com>
> 
> 703-948-3271
> 12061 Bluemont Way
> Reston, VA 20190
> 
> Verisign.com <http://verisigninc.com/>
>  
> From: Tobias Sattler <satt...@united-domains.de 
> <mailto:satt...@united-domains.de>>
> Date: Tuesday, April 6, 2021 at 12:29 PM
> To: James Gould <jgo...@verisign.com <mailto:jgo...@verisign.com>>, 
> "michael.baul...@knipp.de <mailto:michael.baul...@knipp.de>" 
> <michael.baul...@knipp.de <mailto:michael.baul...@knipp.de>>
> Cc: "regext@ietf.org <mailto:regext@ietf.org>" <regext@ietf.org 
> <mailto:regext@ietf.org>>
> Subject: [EXTERNAL] Re: [regext] I-D Action: 
> draft-ietf-regext-epp-registry-maintenance-12.txt
>  
> Thanks Michael and Jim. 
>  
> I’ve made the adjustment on GitHub for your review.
> https://github.com/seitsu/registry-epp-maintenance/blob/master/draft-ietf-regext-epp-registry-maintenance.txt
>  
> <https://secure-web.cisco.com/1qHhn9m_n0q1Aop-LvX59fsy8JV04r9d-NS_iCDZ5x8vZ_ZXeJt2CO7oDXK27hsU8Mr8S_41nsjRPFrjYDAiFveBRZ3ZkF5Nw_uo2v2SnNYXN7rkMl6JYfcd0O3CGnC0_kwrvWmTkqx6cPzh6l4_7icShqr4GYvhj7rqXvmaccBz2M5PDzZm--ziQiAUKihBIGtyIJkMdPi33ApZBYhIAqUSMx1C5YFQyxN622sUqjir77szIdHyTOIdQrMiPLsb6/https%3A%2F%2Fgithub.com%2Fseitsu%2Fregistry-epp-maintenance%2Fblob%2Fmaster%2Fdraft-ietf-regext-epp-registry-maintenance.txt>
>  
> Tobias
> 
> 
>> On 6. Apr 2021, at 14:21, Gould, James <jgould=40verisign....@dmarc.ietf.org 
>> <mailto:jgould=40verisign....@dmarc.ietf.org>> wrote:
>>  
>> If the intent is to support a list of description elements, then my 
>> recommendation is to update the schema, as previously noted with 
>> maxOccurs="unbounded", and update the description of the element with 
>> something similar to:
>> 
>> Zero or more OPTIONAL free-form descriptions of the maintenance...
>> 
>> -- 
>> 
>> JG
>> 
>> 
>> 
>> James Gould
>> Fellow Engineer
>> jgo...@verisign.com <mailto:jgo...@verisign.com> 
>> <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgo...@verisign.com 
>> <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgo...@verisign.com>>
>> 
>> 703-948-3271
>> 12061 Bluemont Way
>> Reston, VA 20190
>> 
>> Verisign.com <http://verisign.com/> <http://verisigninc.com/ 
>> <http://secure-web.cisco.com/1q-u3_Fr2541unEM2O8NdJxYqFh-WP_FpSuHAnIlW4rGpTehTzsSVd_qpsRWqNaHhOnOwxg6faxqvKocTCBIu91LoZVv_J_kw1nC2UsaEML6NrC3QKXRfXGhRa2bpkKVVR6rxisAdEeCN5_wuXAs58cVUua-wGK4zjIMlgZpfeSCqA4JTmRfBdUhBQcg1jYXcsyK5sZXzT7K2BFB0_DUbc1h4YT-Vd5yi8GGR6IdM3hqyirKu_MwDUGUBUVo6E2R_/http%3A%2F%2Fverisigninc.com%2F>>
>> 
>> On 4/6/21, 5:50 AM, "regext on behalf of Michael Bauland" 
>> <regext-boun...@ietf.org <mailto:regext-boun...@ietf.org> on behalf 
>> ofmichael.baul...@knipp.de <mailto:michael.baul...@knipp.de>> wrote:
>> 
>> 
>>    Hi Jody,
>> 
>>    thanks for your answer.
>> 
>>    I agree with your comments, but there is still an issue with the
>>    descriptions in multiple languages. You said:
>> 
>> 
>>> << JWK
>>> The maint:description element is unbounded.  If descriptions in different 
>>> languages are needed, they can be sent on the same poll message.
>>> 
>>>>>  
>> 
>>    I think this is not the case according to the schema:
>> 
>>         <complexType name="maintDataType">
>>           <sequence>
>>             <element name="id" type="maint:idType"/>
>>             <element name="type" type="maint:typeType" minOccurs="0"/>
>>             <element name="pollType" type="maint:pollType" minOccurs="0"/>
>>             <element name="systems" type="maint:systemsType"/>
>>             <element name="environment" type="maint:envType"/>
>>             <element name="start" type="dateTime"/>
>>             <element name="end" type="dateTime"/>
>>             <element name="reason" type="maint:reasonEnum"/>
>>             <element name="detail" type="anyURI" minOccurs="0"/>
>>             <element name="description" type="maint:descriptionType"
>>              minOccurs="0"/>
>>             <element name="tlds" type="maint:tldsType" minOccurs="0"/>
>>             <element name="intervention" type="maint:interventionType"
>>              minOccurs="0"/>
>>             <element name="crDate" type="dateTime"/>
>>             <element name="upDate" type="dateTime" minOccurs="0"/>
>>           </sequence>
>>         </complexType>
>> 
>>    There is no maxOccurs element and the default is maxOccurs="1".
>>    My suggestion is to update the schema and allow unbounded occurrences to
>>    support multiple languages in one notification.
>> 
>>    Best regards,
>> 
>>    Michael
>> 
>>    -- 
>>    ____________________________________________________________________
>>         |       |
>>         | knipp |            Knipp  Medien und Kommunikation GmbH
>>          -------                    Technologiepark
>>                                     Martin-Schmeisser-Weg 9
>>                                     44227 Dortmund
>>                                     Germany
>> 
>>         Dipl.-Informatiker          Fon:    +49 231 9703-0
>>                                     Fax:    +49 231 9703-200
>>         Dr. Michael Bauland         SIP:    michael.baul...@knipp.de 
>> <mailto:michael.baul...@knipp.de>
>>         Software Development        E-mail: michael.baul...@knipp.de 
>> <mailto:michael.baul...@knipp.de>
>> 
>>                                     Register Court:
>>                                     Amtsgericht Dortmund, HRB 13728
>> 
>>                                     Chief Executive Officers:
>>                                     Dietmar Knipp, Elmar Knipp
>> 
>>    _______________________________________________
>>    regext mailing list
>>    regext@ietf.org <mailto:regext@ietf.org>
>>    
>> https://secure-web.cisco.com/15k4MSsRmzO-vHkCwzCFTssa7wd6ube1TSVU9nPxSO0AvM5DSo-tqeF_QM-BOhHtQTCvYiN1Vu5caHJVGataZX93gVy4Td_WfFf5P69l-KZVWCTZeL63FrxS3j4izOnCXW-UkcYj9gZZxKHR8n7ECnYRg01JPweXW12kVqhxtE6z8By7KHJXHqSb4Grl_-1b_WDL_WAddOkE8Unkkb_601jo0hsbojViwdeVAB0mLY90OJBdLKj7DeW6hTQwwrxZQ/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext
>>  
>> <https://secure-web.cisco.com/15k4MSsRmzO-vHkCwzCFTssa7wd6ube1TSVU9nPxSO0AvM5DSo-tqeF_QM-BOhHtQTCvYiN1Vu5caHJVGataZX93gVy4Td_WfFf5P69l-KZVWCTZeL63FrxS3j4izOnCXW-UkcYj9gZZxKHR8n7ECnYRg01JPweXW12kVqhxtE6z8By7KHJXHqSb4Grl_-1b_WDL_WAddOkE8Unkkb_601jo0hsbojViwdeVAB0mLY90OJBdLKj7DeW6hTQwwrxZQ/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext>
>> 
>> 
>> _______________________________________________
>> regext mailing list
>> regext@ietf.org <mailto:regext@ietf.org>
>> https://www.ietf.org/mailman/listinfo/regext 
>> <https://www.ietf.org/mailman/listinfo/regext>
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

Reply via email to