To:
"Edmon Chung" <edmon@neteka.com>
cc:
"Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>, ietf-provreg@cafax.se, brunner@nic-naa.net
From:
Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Date:
Fri, 06 Sep 2002 21:11:52 -0400
In-Reply-To:
Your message of "Fri, 06 Sep 2002 18:18:54 EDT." <004101c255f3$640f1880$0f01a8c0@neteka.inc>
Sender:
owner-ietf-provreg@cafax.se
Subject:
Re: epp via smtp
> It is honestly, fairly simple. Reason being ease of implementation for the > registry as well as the registrar. ... Good. > ... SMTP as a transport mechanism and then parse out the body portion and > dump it back into the regular EPP gateway ... Fine. > One SMTP message may contain multiple EPP messages. Transaction IDs are > used. OK. >> Content-Type > ... headers are not used as identifiers ... How about text/xml; charset=utf-8? >> Content-Transfer-Encoding > 8bit How about base64? > None Mime-version: 1.0 > Only PGP is used. OK. Now an implementation question or two. What bits are you using? What email address(es) I can send the following (with a useful test fqdn): <?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> <check> <domain:check 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>example1.tld</domain:name> <domain:name>example2.tld</domain:name> <domain:name>example3.tld</domain:name> </domain:check> </check> <clTRID>ABC-12345</clTRID> </command> </epp> What should I expect in return? Eric