To:
"Damaraju, Ayesha" <ayesha.damaraju@neustar.com>
cc:
"'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>, epp-rtk-devel <epp-rtk-devel@lists.sourceforge.net>
From:
Rick H Wesson <wessorh@ar.com>
Date:
Thu, 14 Jun 2001 11:30:45 -0700 (PDT)
In-Reply-To:
<FD6332B64829D5119CB8001083FCDD562FE806@VA02>
Sender:
owner-ietf-provreg@cafax.se
Subject:
Re: your mail
Ayesha, I agree with your analysis but, i woud also like to understand what any other object besides a contact needs a roid. Objects such as hosts and domains are unique within a registry, maybe we should only have a ROID for contacts? It does look like this change will effect the Liberty RTK, does anyone from liberty want to comment on the impact of this change? -rick On Thu, 14 Jun 2001, Damaraju, Ayesha wrote: > > 1. Moved the <roid> element out of the response data for > > <create> and <info> > > command, and now is in the <response> element as an > > optional element. > > > > --My litmus test for this move was the answer to the question "is the ROID > --concept common to all objects, or is it required of specific objects". As > --discussed on this list, it's common to all objects, so I though it should > be > --in the base protocol instead of in the object mappings. That's why it was > --moved. > > > > It is common to all objects, but not to all responses. For example doesn't > apply to a <check> response. > And logically, <roid> is part of <resData>, as --- > > " An OPTIONAL <resData> (response data) element that contains child > elements specific to the command and associated object." > > Well I like to hear how the people working on implementing EPP feel about > this, as this > migration of <roid> in to base protocol changes the model, as XML generation > is not straight > forward anymore. > > Example domain_create_result.xml file from EPP-01 > > <?xml version="1.0" standalone="no"?> > <epp xmlns="urn:iana:xml:ns:epp" > xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" > xsi:schemaLocation="urn:iana:xml:ns:epp epp.xsd"> > <response> > <result code="1000"> > <msg>Command completed successfully</msg> > </result> > <resData> > <domain:creData xmlns:domain="urn:iana:xml:ns:domain" > xsi:schemaLocation="urn:iana:xml:ns:domain domain.xsd"> > <domain:name>example.com</domain:name> > <domain:roid>EXAMPLE1-VRSN</domain:roid> > <domain:exDate>2002-06-08T22:00:00.0Z</domain:exDate> > </domain:creData> > </resData> > <unspec/> > <trID> > <clTRID>ABC-12345</clTRID> > <svTRID>54321-XYZ</svTRID> > </trID> > </response> > </epp> > > > Example domain_create_result.xml file from EPP-02 > <?xml version="1.0" encoding="UTF-8" standalone="no"?> > <epp xmlns="urn:iana:xml:ns:epp" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="urn:iana:xml:ns:epp epp.xsd"> > <response> > <result code="1000"> > <msg>Command completed successfully</msg> > </result> > <resData> > <domain:creData xmlns:domain="urn:iana:xml:ns:domain" > xsi:schemaLocation="urn:iana:xml:ns:domain domain.xsd"> > <domain:name>example.com</domain:name> > <domain:exDate>2002-06-08T22:00:00.0Z</domain:exDate> > </domain:creData> > </resData> > <unspec/> > <roid>EXAMPLE1-VRSN</roid> > <trID> > <clTRID>ABC-12345</clTRID> > <svTRID>54321-XYZ</svTRID> > </trID> > </response> > </epp> > > > > -Ayesha >