IETF Logo Mail Archive

Re: [regext] Comments to the feedback about epp-over-http

Alexander Mayrhofer <alexander.mayrhofer@nic.at> Wed, 30 March 2022 07:02 UTC

Return-Path: <alexander.mayrhofer@nic.at>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC30D3A0D1C for <regext@ietfa.amsl.com>; Wed, 30 Mar 2022 00:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nic.at
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id odo40jcjJZJG for <regext@ietfa.amsl.com>; Wed, 30 Mar 2022 00:02:14 -0700 (PDT)
Received: from mail.sbg.nic.at (mail.sbg.nic.at [83.136.33.227]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21B943A0CF0 for <regext@ietf.org>; Wed, 30 Mar 2022 00:02:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nic.at; s=it2019; h=From:From:To:CC:Subject:Date:Message-Id:Content-Type:Received:Received:Received; bh=aWrmTK7u5ywyZqWHI7Bu5E7noEhZKgZUqXCWj57aJX8=; b=QlcdRj/mdtNCtbiK7ZCB3jd/wa8Qpn5o5I1DlW16kB5fWRRDTuKXsxaOGyXkkqAbu/BqHU5NCYnU9B9Lh1+3tsLUERX2ytoh3iPAmTrt6S0P+5zHcwsAE9bERq/KbX0Gu8JxJM25zSkHtzcGv9t1Rb6/0eF8ilppvlBXLS4h2VtmOiqYNkIZxHGEleFvctvUTTVs6QUhXy3T0t4lfZ2rI3b4PYS7pfw247tJuojCP0x0MKg3jAtUaETA7LkoD1BUMGP343vkVHezhhFwcXqNztWEV9bAEZw5dTe2auJM2F5/lcrCWlsy0x/NoynkynxKVtdHvSL5bvnulO5qAi148Q==;
Received: from nics-exch3.sbg.nic.at ([10.17.175.2]) by mail.sbg.nic.at over TLS secured channel (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) with XWall v3.56 ; Wed, 30 Mar 2022 09:02:08 +0200
Received: from nics-exch3.sbg.nic.at (10.17.175.2) by nics-exch3.sbg.nic.at (10.17.175.2) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.12; Wed, 30 Mar 2022 09:02:08 +0200
Received: from nics-exch3.sbg.nic.at ([fe80::3079:e311:a6d4:792b]) by nics-exch3.sbg.nic.at ([fe80::3079:e311:a6d4:792b%2]) with mapi id 15.01.2375.012; Wed, 30 Mar 2022 09:02:08 +0200
Thread-Topic: Re: [regext] Comments to the feedback about epp-over-http
Thread-Index: AQHYQ2HusCiygyjR1UKSIh4+FqxVv6zWeGeQ
References: <BF7ADD0A-6C30-4A36-B96D-38E3C1455D01@verisign.com>
In-Reply-To: <BF7ADD0A-6C30-4A36-B96D-38E3C1455D01@verisign.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.22.2.6]
From: Alexander Mayrhofer <alexander.mayrhofer@nic.at>
To: "Gould, James" <jgould=40verisign.com@dmarc.ietf.org> , "mario.loffredo@iit.cnr.it" <mario.loffredo@iit.cnr.it> , "regext@ietf.org" <regext@ietf.org>
Date: Wed, 30 Mar 2022 09:02:08 +0200
X-Assembled-By: XWall v3.56
Message-ID: <940b3020cee7496096ba394023f077d9@nic.at>
X-XWALL-BCKS: auto
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="_NextPart_1_5tmes6y4gqXSlrAaABjFzFVDVlR"
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/AfxYfRJA7r_8FSvUCFrX4pvnPjY>
Subject: Re: [regext] Comments to the feedback about epp-over-http
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2022 07:02:19 -0000

Guys,

i’ve yet to read up on the latest version of the document (and I will do so). However, as a quick comment:


  1.  Establish TCP connection
  2.  Establish TLS session via TLS-handshake
  3.  Establish HTTP session via setup of the HTTP session cookie (e.g., JSESSIONID)
  4.  Return EPP Greeting in framed HTTP response with the session cookie (e.g., JSESSIONID)
  5.  Support HTTP requests in the form of framed EPP commands that are returned in HTTP responses in the form of framed EPP responses.

[AM] Please please let’s not assume that HTTP is TCP. The protocol (imho MUST) also work over HTTP/3, which uses QUIC, which in turn uses UDP. However, the approach of using a session ID for identifying the equivalent of a TCP connection in “plain” EPP is still valid, and I support that design choice.



More feedback to come once I manage to squeeze in time to read through the draft more carefully.



Best,

Alex

v2.8.7 | Report a Bug | By Email