RE: Implementation Report Findings

"Hollenbeck, Scott" <[email protected]>
Newsgroups gmane.ietf.provreg
Message-ID <046F43A8D79C794FA4733814869CDF070172A69B@dul1wnexmb01.vcorp.ad.vrsn.com>
Excellent -- thanks for confirming!

-Scott-

> -----Original Message-----
> From: Asbjorn S. Mikkelsen [mailto:[email protected]] 
> Sent: Tuesday, August 22, 2006 10:09 AM
> To: Hollenbeck, Scott
> Cc: [email protected]
> Subject: Re: [ietf-provreg] Implementation Report Findings
> 
> Scott,
> 
> Using a slightly modified version of the code from the c++ version of
> the SourceForge epp-rtk project against the .name OT&E:
> 
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
>      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>      xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
>      epp-1.0.xsd">
>   <command>
>     <transfer op="request">
>       <domain:transfer
>            xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
>            xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
>            domain-1.0.xsd">
>         <domain:name>asm.name</domain:name>
>         <domain:authInfo>
>           <domain:pw roid="1529404CONTACT-NAME">as8n59f</domain:pw>
>         </domain:authInfo>
>       </domain:transfer>
>     </transfer>
>     <clTRID>ABC-12345</clTRID>
>   </command>
> </epp>
> 
> Where "as8n59f" is the password for the contact object, not the domain
> object.
> 
> Returned:
> 
> <?xml version="1.0"?>
> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
>      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>      xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
>      epp-1.0.xsd">
>   <response>
>     <result code="1000">
>       <msg>Command completed successfully</msg>
>     </result>
>     <resData>
>       <domain:trnData
>            xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
>            xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
>            domain-1.0.xsd">
>         <domain:name>ASM.NAME</domain:name>
>         <domain:trStatus>pending</domain:trStatus>
>         <domain:reID>XXXXXXX1</domain:reID>
>         <domain:reDate>2006-08-22T13:53:21.0000Z</domain:reDate>
>         <domain:acID>XXXXXXX2</domain:acID>
>         <domain:acDate>2006-08-27T13:53:21.0210Z</domain:acDate>
>         <domain:exDate>2007-02-11T12:07:44.0000Z</domain:exDate>
>       </domain:trnData>
>     </resData>
>     <trID>
>       <clTRID>ABC-12345</clTRID>
>       <svTRID>3196766-1156254801065</svTRID>
>     </trID>
>   </response>
> </epp>
> 
> 
> Please let me know if this is sufficient. If not, I can liaise with
> Patrick to test the same with his client against the .name production
> system.
> 
> 
> Cheers,
> 
> Asbjorn
> 
> 
> On Tue, 2006-08-22 at 08:23 -0400, James Gould wrote:
> > Scott,
> > 
> > The VeriSign EPP SDK supports passing of the roid with 
> transfer requests
> > which was used for testing the feature against the NAME Registry.
> 
> 
> -- 
> Asbjorn Steira Mikkelsen <[email protected]>
> CTO
> The Global Name Registry, Limited
> _____________________________________________________
> 
> Information contained herein is Global Name Registry Proprietary
> Information and/or Registry Sensitive Information and is made 
> available
> to you because of your interest in or affiliation with our 
> company. This
> information is submitted in confidence and its disclosure to 
> you is not
> intended to constitute public disclosure or authorization for 
> disclosure
> to other parties. Should you have received this email and are not an
> intended recipient, please delete this email in its entirety. Global
> Name Registry is registered with the Office of the UK Information
> Commissioner.
> 
> 
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.