Anthony,

I reviewed your draft.  We implemented EPP over HTTP a while back, where HTTP 
was treated as transport in line with EPP over TCP (RFC 5734).  It was shut 
down when it became clear that EPP over TCP was the preferred option.  The 
difference with your draft and our implementation is that the draft defines a 
stateless transport and our implementation was a stateful transport.  We simply 
framed the EPP packets using HTTP, with HTTP keep-alive, and with full support 
for the EPP login and logout commands.   Changing from stateful to stateless 
would really not allow easily replacing the transport on the client-side or the 
server-side.  We used the following HTTP properties:


  1.  Content length is explicitly specified
  2.  Chunked transfer encoding of HTTP 1.1
  3.  Content-type set to “text/xml”

The 2-way HTTPS connection would be established, the client packet is framed as 
an HTTP packet and sent to the server, where the server processed the HTTP 
packet as it would a framed packet with EPP over TCP.  All of the EPP over HTTP 
commands and responses would behave consistently with EPP over TCP.

—

JG

[cid:image001.png@01D255E2.EB933A30]

James Gould
Distinguished Engineer
jgo...@verisign.com

703-948-3271
12061 Bluemont Way
Reston, VA 20190

Verisign.com<http://verisigninc.com/>

From: regext <regext-boun...@ietf.org> on behalf of Anthony Eden 
<anthony.eden=40dnsimple....@dmarc.ietf.org>
Date: Tuesday, May 22, 2018 at 12:09 PM
To: "regext@ietf.org" <regext@ietf.org>
Subject: [EXTERNAL] [regext] Interest in collaborating on an EPP over HTTP 
draft?

Greetings folks!

I've thrown together a repo over at GitHub to work on an EPP over HTTP draft 
(https://github.com/aeden/epp-over-http). I'd love to know if there are others 
from the community who are interested on collaborating. As a registrar, we'd 
love to be able to work with registries using HTTP as the transport protocol in 
the future.

Note that the current version of this draft deals solely with EPP over HTTP 
1.1, it does not consider HTTP 2 at this time.

Feedback is welcome. Thanks!

Sincerely,
Anthony Eden

--
DNSimple.com
http://dnsimple.com/
Twitter: @dnsimple
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

Reply via email to