To:
Eugenio Pinto <eugenio.pinto@fccn.pt>
Cc:
ietf-provreg@cafax.se
From:
Stephane Bortzmeyer <bortzmeyer@nic.fr>
Date:
Wed, 31 Oct 2007 09:04:14 +0100
Content-Disposition:
inline
In-Reply-To:
<47281687.60607@fccn.pt>
Sender:
owner-ietf-provreg@cafax.se
User-Agent:
Mutt/1.5.13 (2006-08-11)
Subject:
[ietf-provreg] Re: EPP over HTTP or simple TCP?
On Wed, Oct 31, 2007 at 05:45:43AM +0000, Eugenio Pinto <eugenio.pinto@fccn.pt> wrote a message of 21 lines which said: > - A way is to send EPP messages in the body of HTTP requests and > manage HTTP requests with standard code. That's tempting but it violates RFC 3205 and, besides, there is no written specification on EPP-over-HTTP so it will be non-standard. > - Another solution, with less overhead, is to send EPP messages > directly in the TCP stream and add some "end-code" characters to the > end of the message in order for the server to recognize each EPP > message Why adding this end-code when RFC 4934 uses a leading length field? 4. Data Unit Format The EPP data unit contains two fields: a 32-bit header that describes the total length of the data unit, and the EPP XML instance.