Re: [ire] New versions of data escrow drafts

[Francisco Obispo <[e-mail]>]

I just went over the new drafts and found something interesting:

The example XML documents in the draft reference the rdeDomain namespace:

   <rdeDom:domain>
     <rdeDom:name>example1.test</rdeDom:name>
     <rdeDom:roid>Dexample1-TEST</rdeDom:roid>
     <rdeDom:status s="ok"/>
     <rdeDom:registrant>jd1234</rdeDom:registrant>
     <rdeDom:contact type="admin">sh8013</rdeDom:contact>
     <rdeDom:contact type="tech">sh8013</rdeDom:contact>
     <rdeDom:ns>
       <domain:hostObj>ns1.example.com</domain:hostObj>
       <domain:hostObj>ns1.example1.test</domain:hostObj>
     </rdeDom:ns>
     <rdeDom:clID>RegistrarX</rdeDom:clID>
     <rdeDom:crRr client="jdoe">RegistrarX</rdeDom:crRr>
     <rdeDom:crDate>1999-04-03T22:00:00.0Z</rdeDom:crDate>
     <rdeDom:exDate>2015-04-03T22:00:00.0Z</rdeDom:exDate>
   </rdeDom:domain>


but the XML schema is referencing the EPP (Domain) namespace for validation:

(example validation of one of my escrow dump)

[][][][]_2013-03-20_full_S1_R0.ryde:1: element pw: Schemas validity error : Element '{urn:ietf:params:xml:ns:rdeDomain-1.0}pw': This element is not expected. Expected is one of ( {urn:ietf:params:xml:ns:domain-1.0}pw, {urn:ietf:params:xml:ns:domain-1.0}ext ).


So it seems like the schema will need to be modified to include the elements from the EPP schema, (or re-define them), otherwise the schema validation will fail.

Or should I be using the EPP Domain NS instead?

This is part of my escrow dump:


      <rdeDomain:domain>
        <rdeDomain:name>deleteme.[][][][]</rdeDomain:name>
        <rdeDomain:roid>DO_c13a4e438c6471d8ead63a8031d41698-ISC</rdeDomain:roid>
        <rdeDomain:status s="inactive"/>
        <rdeDomain:rgpStatus s="ok"/>
        <rdeDomain:registrant>updateme03</rdeDomain:registrant>
        <rdeDomain:clID>foobar</rdeDomain:clID>
        <rdeDomain:crID>foobar</rdeDomain:crID>
        <rdeDomain:crDate>2013-03-19T16:36:31.961Z</rdeDomain:crDate>
        <rdeDomain:exDate>2014-03-19T16:36:31.961Z</rdeDomain:exDate>
        <rdeDomain:authInfo>
          <rdeDomain:pw>OhXahpatahriomi6</rdeDomain:pw>
        </rdeDomain:authInfo>
      </rdeDomain:domain>


Francisco


On Mar 12, 2013, at 7:54 AM, Gustavo Lozano <[e-mail]> wrote:

> Colleagues,
> 
> 
> Two new versions of the data escrow drafts have been
> published:
> * http://www.ietf.org/id/draft-arias-noguchi-dnrd-objects-mapping-02.txt
> * http://www.ietf.org/id/draft-arias-noguchi-registry-data-escrow-05.txt
> 
> 
> These drafts incorporate feedback received in this list and
> private emails.
> 
> 
> The authors of draft-arias-noguchi-dnrd-objects-mapping and
> draft-gould-thippeswamy-dnrd-csv-mapping agreed to merge both drafts to
> create
> a single specification that supports XML only and XML+CSV.
> 
> 
> The data elements/objects in both drafts have been
> normalized.
> 
> 
> The authors of draft-gould-thippeswamy-dnrd-csv-mapping will
> publish a new version of the CSV draft before the merge of both drafts.
> 
> 
> The new version (03) of the draft draft-arias-noguchi-dnrd-objects-mapping
> is going to include both models (XML only and XML+CSV).
> 
> 
> Version 03 should include only minor changes to the data
> escrow specification.
> 
> 
> If you are attending the IETF 86 meeting and want to talk
> about data escrow, please send me an email and we can arrange an informal
> meeting.
> 
> 
> Regards,
> Gustavo Lozano
> 
> _______________________________________________
> ire mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/ire

Francisco Obispo 
Director of Applications and Services - ISC
email: [e-mail]
Phone: [phone] || INOC-DBA *3557* NOC
PGP KeyID = B38DB1BE