Re: EPP over HTTP or simple TCP?
Stephane Bortzmeyer <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Organization | NIC France |
| Message-ID | <[email protected]> |
On Wed, Oct 31, 2007 at 05:45:43AM +0000, Eugenio Pinto <[email protected]> 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.