RFC 8399 is a Proposed Standard RFC that updates RFC 5280, another Proposed Standard. RFCs 5730 – 5733 are Internet Standards (RFC 2026 describes the difference in maturity levels), and as such the barrier for updates tends to be higher. The EPP RFCs are aging, and yes, we’re finding things that need to be updated. However, this is precisely why we can extend the protocol without having to modify the core XML schemas. You may disagree, but I think you’ll find that an extension will be an easier path forward from both implementation interest and process perspectives.
Scott From: Dmitry Belyavsky <[email protected]> Sent: Thursday, October 8, 2020 10:21 AM To: Hollenbeck, Scott <[email protected]> Cc: [email protected]; [email protected] Subject: [EXTERNAL] Re: [regext] Fwd: New Version Notification for draft-belyavskiy-epp-eai-00.txt Dear Scott, Many thanks for your response! I'm sorry, I don't feel the difference between this case and a similar update of X.509 profile by RFC 8399. And, as the email field is mandatory on creating the contact, I don't think that the extension is the best way. On Thu, Oct 8, 2020 at 5:13 PM Hollenbeck, Scott <[email protected] <mailto:[email protected]> > wrote: Thanks for the note, Dmitry. I get what you’re trying to do, but I don’t think we can update Standard 69 (the set of EPP RFCs) this way. I’m not aware of any RFCs that expressly prohibit such things, but it’s a topic that the IESG has debated multiple times over the years and there might not be support for doing it his way now. A safer path would be to develop an extension using one of the techniques described in RFC 3735, “Guidelines for Extending the Extensible Provisioning Protocol”. Scott From: regext <[email protected] <mailto:[email protected]> > On Behalf Of Dmitry Belyavsky Sent: Wednesday, October 7, 2020 9:28 AM To: [email protected] <mailto:[email protected]> Cc: marabox <[email protected] <mailto:[email protected]> > Subject: [EXTERNAL] [regext] Fwd: New Version Notification for draft-belyavskiy-epp-eai-00.txt Dear colleagues, This is an initial version of the IETF draft allowing usage of Internationalized Email Addresses in the EPP protocol. ---------- Forwarded message --------- From: <[email protected] <mailto:[email protected]> > Date: Wed, Oct 7, 2020 at 4:25 PM Subject: New Version Notification for draft-belyavskiy-epp-eai-00.txt To: Dmitry Belyavskiy <[email protected] <mailto:[email protected]> > A new version of I-D, draft-belyavskiy-epp-eai-00.txt has been successfully submitted by Dmitry Belyavskiy and posted to the IETF repository. Name: draft-belyavskiy-epp-eai Revision: 00 Title: Use of Internationalized Email Addresses in EPP protocol Document date: 2020-10-07 Group: Individual Submission Pages: 4 URL: https://www.ietf.org/id/draft-belyavskiy-epp-eai-00.txt <https://secure-web.cisco.com/1LkyicX_gPmVOFcqhopUmVBWNTNu8kNZjDBEJQvuOubNy547f4jeqX_rzGbyYv6ETENBk4XhC6Pf1HYfuQdaDUGDzadgReCVZHuAE3qDlDJ-ztd4b8LLqBg3K_QCXVYdim6g241oyclQbCWdzjcjdB0qsqZhAj7W3T-uShNPnveo9pis0PgzAehHj4M_Pa1E2SJthPbd5fydZFjMvT1MZ7uJOuf11g-OM7uxR0y4HKXBBcQmHQeYPly9f0fMNpUmxbzdghKVzx472b1k082jKppl8gS440Z2FgZc1DYcPwzw/https%3A%2F%2Fwww.ietf.org%2Fid%2Fdraft-belyavskiy-epp-eai-00.txt> Status: https://datatracker.ietf.org/doc/draft-belyavskiy-epp-eai/ <https://secure-web.cisco.com/1iH-jWELClftnGP8aH6xLx2NYPu3jsbvha_VBM_4gIYI_a8gCvX2XYik-58d-Us1TIPSkJ-7MhuKX4fkdG4KZTg6OnUZ-zO05p4r4nD5I65TQfgse3foF4wNxX8RmIRAC7QJJZfmvtRF40KsstlpsRnvYB6kI9UZHGMck8TJxG4ie2i_kJkLDrxEG4bX4IwyU_uaYJ6NcQKwea85dIKFVXK7crG9xK8yBLnaj7wswNB70e2H_7SYNN1Iye6vp1u3iq54v8LaLW08h06WUNV5rxQ/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-belyavskiy-epp-eai%2F> Htmlized: https://datatracker.ietf.org/doc/html/draft-belyavskiy-epp-eai <https://secure-web.cisco.com/1R1veyqLSTSFJHBa1BOcXLht2lZlaD_b-6Bcn_diis5-1NVr8a1BzS7TR8Hx0DncgMGnCAxrF7tXkKyNq8gqWnEUxjk2pAF9gfoOnpD39Aa3C81DT4CHwuBnuZx9GisUlHkmqsxp2MkhJKm-1oyTZGF9pTmhivYFGZdBjn9pRiTMFYfCDrvh6aE1Q1_ZBmI3o6O5Y68lqVSGq23CffeKWDO6wXDh-43gZ9Uri_2xEmQbOzBdfrrvfdLy7dRo0XEaaG_Ixs6XMLnC9OQSoppMSbw/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-belyavskiy-epp-eai> Htmlized: https://tools.ietf.org/html/draft-belyavskiy-epp-eai-00 <https://secure-web.cisco.com/1aPLpPIJlvKOGrv9LEQTzgEaIIt-akmzF6wRR_zggj-AfW5Y1tzou50A5DCNMH-Fdh2GPXgvVE2JvtV-6esKg-9tT0f-1iQykAZFrmwEYBLzRgmzI7XbCUcbjoMuV7BsJlwNBzH4j50M5pdZJa0HXNlXozZxgd9oeWyq-yPwoq-mg4mGEDYXJ_aS8sTyd0VPYw1_jJV0RlvffC9RLZ1t6WSpFIlP1IW3dEqhkFF0Lj3CEhPPJAYe47DoLsUCcnbcz-Gc-1tv63IN6ljQrXIXITIYo_HnS9RwKFZQ8lcQ9XDc/https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-belyavskiy-epp-eai-00> Abstract: This document permits usage of Internationalized Email Addresses in the EPP protocol. TO BE REMOVED on turning to RFC: The document is edited in the dedicated github repo [1]. Please send your submissions via GitHub. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org <http://secure-web.cisco.com/1Uf4zmBFe46PVm16LpIWeYo6zFDeCMc2krmNCh3enAUGvptve1fyz-b7Ajy5sgY3pxCRTvrr8PSkB8TxBU26-mOuzr751etNgYOdmrmv7bGGtkDxLWyYJufulJaqZILFmfGSMMkAWh07W_JGwcxgQ-FwE5tyXQ_H3Ka6VoeG8BUjpzT77mFSpvxlgcu4il6bYriCZWRrgvLZTH87sUfS2zQ2qIuM-6BHE6xtTxk0J7nbjI8KZUUu9vTJAvq6YnoTNsdf8qPm9KHQ3I-MktA3ikpnptxlzHINmJAIJJPD5L2E/http%3A%2F%2Ftools.ietf.org> . The IETF Secretariat -- SY, Dmitry Belyavsky -- SY, Dmitry Belyavsky
_______________________________________________ regext mailing list [email protected] https://www.ietf.org/mailman/listinfo/regext
