IETF Logo Mail Archive

[regext] Signaling BCP support in EPP for draft-ietf-regext-secure-authinfo-transfer and draft-ietf-regext-unhandled-namespaces

"Gould, James" <jgould@verisign.com> Mon, 16 March 2020 14:28 UTC

Return-Path: <jgould@verisign.com>
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 DB2CB3A091D for <regext@ietfa.amsl.com>; Mon, 16 Mar 2020 07:28:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verisign.com
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 sAl6BZPv4_rg for <regext@ietfa.amsl.com>; Mon, 16 Mar 2020 07:28:51 -0700 (PDT)
Received: from mail6.verisign.com (mail6.verisign.com [69.58.187.32]) (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 098873A091B for <regext@ietf.org>; Mon, 16 Mar 2020 07:28:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=20714; q=dns/txt; s=VRSN; t=1584368931; h=from:to:subject:date:message-id:mime-version; bh=78No8uy0hgeezmh0fGC4G+bQd6R78w4ObcVxdK057RI=; b=doGig/JgyoFVR1EM101EqrS3rSdLfl4Hg11b2Do1XsO/YKgVG/s1uJsi Z+E45pxUea2LLEL8uzgs44FaUDmjBBWA+pS72zQyMOy/0w9EhRLvUdyov YfGY4C0iFWVgiUkJT/M/yzO8Rl1ZA2sk8SC5hCmVZn7vgiB+OkaWjhgiF eoeSsNFwFnDU+j//OH5iD1fqExVK/64F0idVJBCNh4jI+c9I56S8KmdHz 6zd4h1A7HlZ4YSPTzy+EVzyizWmnUUHyrxpHM8ryjUOOlCmEJd+NhLM80 S3e8kWJofLeWvDA0Jhw0qpotaKiMlHBpc2QctdgQlOhqSTUYjwAh+jyJf g==;
IronPort-SDR: 58S0B+BOQ61quHHXCBsDy3Q712laqCozP26iQoC6jFPFNLIboVlIU2P4T4juinWboRVVFDGGva kevx4End7AqjvmuFwzUD2KcnIDkNXavkyLX0CT0UNnso5Ml0RmC9BH/c0iiMK0G/YXM9k9cPV/ hW0ghkhXQbjRtPZ8zM5aCd+ewILxY+XGba28xBSU61KmYKVH20dHHaT10mndSpzcobNY9J6bs2 P11sBsUlEsjYFGlw0QG96p1RXQ1eVJGxCL6cCTqGALGIAXkhXbgU28I9f9bT3YmHoDoRW4czyC 0l0=
X-IronPort-AV: E=Sophos;i="5.70,560,1574139600"; d="png'150?scan'150,208,217,150";a="887124"
IronPort-PHdr: 9a23:C70oahbkeXPiv3gHx4m+TiT/LSx+4OfEezUN459isYplN5qZr8S5bnLW6fgltlLVR4KTs6sC17OK9fm7Aidevd6oizMrTt9lb1c9k8IYnggtUoauKHbQC7rUVRE8B9lIT1R//nu2YgB/Ecf6YEDO8DXptWZBUhrwOhBoKevrB4Xck9q41/yo+53Ufg5EmCexbal9IRmrogjdrNQajIVsJ6o+yxbErWZDdvhLy29vOV+ckBHw69uq8pV+6SpQofUh98BBUaX+Yas1SKFTASolPW4o+sDlrAHPQgST6HQSVGUWiQdIDBPe7B7mRJfxszD1ufR71SKHIMD5V7E0WTCl76d2VB/ljToMOjAl/G3LjMF7kaRWqw+jqRNi2Y7ZeIGbOuRjcKPBc90URmROXsdNWCNOGY68dZcDD+8bMOpEtYTwpV0Dpga+Cwm2A+PvzydFinH30609zuQhFRzJ0BQ9FNwKqnvUqcv6NLwcXeuoy6TIzzrDb/RL2Tf59YfFaQ4hru+WXbJxasrRyEYvFwXfglqMrozlOiqY2+IQuGaV6OpgUPigi28hqwxpvDig2N0siojShoIUxVDE8yR5wIApKtGiVEF7ZtukHZ1NvC+ZL4t7Wt4uT31ytConyLALt4S3cDUKxZkp3RLSZP+Kf5CV7h7/TuqdPDV1iG5/dL6iiBu/8lKsxvD/W8Ws3lZFsClInsXJu30IzRPe6cyKReB480qvxzqAygHe5+RfLk0wlKfWKZssz7A+m5cRrEvOGDL9ll/sg6+MbEok//Cl6+HgYrr7uJCRL5R0igTiMqQ2ncy/HPg4PhAOX2eF/eS806Xu8FDlTrtSk/E5krHXvp/bKsgHu6K1GRFV3Zok6xalFzeqys4XkmQdIFJbYhKHlI7pN0vSL/D/CPezm1WskDF1yPDaJrDtH4nBImLenLrjc7tx8VNQxQo9wNxF6J9ZCakNIPfpVU/wsNzYAAU5Mwuxw+v/CtV92YQeWX+LAqCEK67Sr0GH5vguI+mXZY8VtzD9J+I56P7piH81gUUdcrWx3ZsLdHC4GexrI1+HbnrjnNgAHnsKsxE/TOP0lF2CXyRfZ3GoX6IztXkHD9fsF4rMS5CxqL2MwCn9GYdZLCgSEF2DHGf0X4SJR/lKbziddJxPiDsBAPKOTJIl2VXmlgb/xqEtZr7W9SoFsZ7LytVv5vbSmhd0/jtxWZfOm1qRRn15yztbDwQ927py9BRw
X-IPAS-Result: A2GOBQDZi29e/zCZrQpiA4NmU4EdgTEKhAyOT4ImgzRflxc8AgcBAQEBAQEBAQEDAQMBEwwQBAEBAoRBGYIvOBMCAwEBCwEBAQUBAQEBAQUDAQEBAoY/AQuCOyJ2Lwk5AQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBBQIIB00HRysBHQIIAUAdASUBAQEOAQwHAgQFEAEODCcECggBBgiDGAGvZYEyhDUBhh4QgTiDCoQqhRSBQj6BEScMFIIfhR8vCiYBAoJHMoIsBJBshXeBG44pgnGHJQMHgjyGLgKBJoFiiAiFToJKgQGHJ5BRiniCTIFAh2WBHJJaAgQCBAUCFYFpgXtwFTsqAYJBCUcYDY4pFxWDO4pVdA4kjCUPgSKBEAEB
Received: from BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) by BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Mon, 16 Mar 2020 10:28:15 -0400
Received: from BRN1WNEX01.vcorp.ad.vrsn.com ([fe80::a89b:32d6:b967:337d]) by BRN1WNEX01.vcorp.ad.vrsn.com ([fe80::a89b:32d6:b967:337d%5]) with mapi id 15.01.1913.005; Mon, 16 Mar 2020 10:28:15 -0400
From: "Gould, James" <jgould@verisign.com>
To: "regext@ietf.org" <regext@ietf.org>
Thread-Topic: Signaling BCP support in EPP for draft-ietf-regext-secure-authinfo-transfer and draft-ietf-regext-unhandled-namespaces
Thread-Index: AQHV+58hRG8AlO5yZ0KlqGlUvJObkQ==
Date: Mon, 16 Mar 2020 14:28:15 +0000
Message-ID: <05FCD17E-1868-4B58-B873-276013142D3C@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.13.200210
x-originating-ip: [10.170.148.18]
Content-Type: multipart/related; boundary="_004_05FCD17E18684B58B873276013142D3Cverisigncom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/kjTGIfkm5ednf2l0rSe-FltYLzQ>
Subject: [regext] Signaling BCP support in EPP for draft-ietf-regext-secure-authinfo-transfer and draft-ietf-regext-unhandled-namespaces
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: Mon, 16 Mar 2020 14:28:53 -0000

One question that was raised by Patrick Mevzek on the mailing list was associated with signaling the implementation of a BCP by the server that I believe would also apply to the client.  This question applies to the two REGEXT BCP drafts draft-ietf-regext-secure-authinfo-transfer and draft-ietf-regext-unhandled-namespaces.  The only existing signaling mechanism in EPP is the use of the greeting and login services.  A namespace URI could be assigned for each BCP draft that is included as an <objURI> or an <extURI> in the greeting to inform the client of the support of the BCP by the server, and in the login command to inform the server of the support of the BCP by the client.  Between the two options, I prefer the use of the <extURI>.  The questions for the working group include:


  1.  Is signaling needed in EPP for the implementation of BCPs?
  2.  If signaling is needed:
     *   Will the existing signaling mechanism in EPP with the greeting and login services meet the purpose?
     *   Of the two service URIs <objURI> and <extURI>, which is the preferred URI to use?
     *   What URI scheme should be used?

                                                  i.      One proposal is to include bcp in the namespace, such as “urn:ietf:params:xml:ns:epp:bcp:secure-authinfo-transfer-<version>” and “urn:ietf:params:xml:ns:epp:bcp:unhandled-namespaces-<version>”.  The <version> would be updated based on material updates to the BCP draft and bumped to 1.0 after WGLC.

Please reply to the list with your feedback.

Thanks,
--

JG

[cid:image001.png@01D255E2.EB933A30]

James Gould
Distinguished Engineer
jgould@Verisign.com<applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgould@Verisign.com>

703-948-3271
12061 Bluemont Way
Reston, VA 20190

Verisign.com<http://verisigninc.com/>

v2.23.0 | Report a Bug | By Email