Hi Mario,

Thanks for this draft and your feedback on the other threads.

While I understand the need for standardization (and I support that), even if 
EPP over HTTP is not widely used, I wonder if the future could not be REST API 
considering that new APIs are mostly built that way? I don’t suggest doing it 
that way, but out of curiosity and a look into the further future.

Best,
Tobias

> On 2. Mar 2022, at 12:45, Mario Loffredo <mario.loffr...@iit.cnr.it> wrote:
> 
> Hi folks,
> 
> Just posted a draft about EPP over HTTP.  It aims to define rules for the EPP 
> implementations leveraging HTTP due to its simplicity and ease of use.
> 
> The proposal preserves EPP commands semantics as HTTP is used merely for 
> transportation.
> 
> The appendix includes possible strategies about how to implement load 
> balancing in this context.
> 
> 
> 
> Even if EPP is largely implemented over TCP, some HTTP based implementations 
> exist and a standardization would be advisable.
> 
> Feedback is welcome and appreciated.
> 
> Best,
> 
> Mario
> 
> 
> 
> -------- Messaggio Inoltrato --------
> Oggetto:      New Version Notification for 
> draft-loffredo-regext-epp-over-http-00.txt
> Data: Wed, 02 Mar 2022 03:16:34 -0800
> Mittente:     internet-dra...@ietf.org <mailto:internet-dra...@ietf.org>
> A:    Jan Romanowski <jan.romanow...@nask.pl> 
> <mailto:jan.romanow...@nask.pl>, Lorenzo Luconi Trombacchi 
> <lorenzo.luc...@iit.cnr.it> <mailto:lorenzo.luc...@iit.cnr.it>, Lorenzo 
> Trombacchi <lorenzo.luc...@iit.cnr.it> <mailto:lorenzo.luc...@iit.cnr.it>, 
> Marcin Machnio <i...@dns.pl> <mailto:i...@dns.pl>, Mario Loffredo 
> <mario.loffr...@iit.cnr.it> <mailto:mario.loffr...@iit.cnr.it>, Maurizio 
> Martinelli <maurizio.martine...@iit.cnr.it> 
> <mailto:maurizio.martine...@iit.cnr.it>
> 
> 
> A new version of I-D, draft-loffredo-regext-epp-over-http-00.txt
> has been successfully submitted by Mario Loffredo and posted to the
> IETF repository.
> 
> Name: draft-loffredo-regext-epp-over-http
> Revision: 00
> Title: Extensible Provisioning Protocol (EPP) Transport over HTTP
> Document date: 2022-03-02
> Group: Individual Submission
> Pages: 15
> URL: 
> https://www.ietf.org/archive/id/draft-loffredo-regext-epp-over-http-00.txt 
> <https://www.ietf.org/archive/id/draft-loffredo-regext-epp-over-http-00.txt>
> Status: https://datatracker.ietf.org/doc/draft-loffredo-regext-epp-over-http/ 
> <https://datatracker.ietf.org/doc/draft-loffredo-regext-epp-over-http/>
> Htmlized: 
> https://datatracker.ietf.org/doc/html/draft-loffredo-regext-epp-over-http 
> <https://datatracker.ietf.org/doc/html/draft-loffredo-regext-epp-over-http>
> 
> 
> Abstract:
> This document describes how the Extensible Provisioning Protocol
> (EPP) is mapped over the Hypertext Transfer Protocol (HTTP). This
> mapping requires the use of the Transport Layer Security (TLS)
> protocol to protect information exchanged between an EPP client and
> an EPP server.
> 
> 
> 
> The IETF Secretariat
> 
> 
> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext

_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

Reply via email to