[regext] FW: I-D Action: draft-ietf-regext-secure-authinfo-transfer-04.txt

The WGLC for draft-ietf-regext-secure-authinfo-transfer ended on Friday, October 16th.  The following are the changes included in draft-ietf-regext-secure-authinfo-transfer-04:

  1.  Converted from xml2rfc v2 to v3.
  2.  Updated Acknowledgements to match the approach taken by the RFC Editor with draft-ietf-regext-login-security.
  3.  Changed from Best Current Practice (BCP) to Standards Track based on mailing list discussion.

Please review and provide feedback on anything missed.

Thanks,

--

JG

James Gould

Fellow 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/>

On 10/21/20, 3:29 PM, "regext on behalf of internet-drafts@ietf.org" <regext-bounces@ietf.org on behalf of internet-drafts@ietf.org> wrote:

    A New Internet-Draft is available from the on-line Internet-Drafts directories.

    This draft is a work item of the Registration Protocols Extensions WG of the IETF.

            Title           : Extensible Provisioning Protocol (EPP) Secure Authorization Information for Transfer

            Authors         : James Gould

                              Richard Wilhelm

                Filename        : draft-ietf-regext-secure-authinfo-transfer-04.txt

                Pages           : 28

                Date            : 2020-10-21

    Abstract:

       The Extensible Provisioning Protocol (EPP), in RFC 5730, defines the

       use of authorization information to authorize a transfer.  The

       authorization information is object-specific and has been defined in

       the EPP Domain Name Mapping, in RFC 5731, and the EPP Contact

       Mapping, in RFC 5733, as password-based authorization information.

       Other authorization mechanisms can be used, but in practice the

       password-based authorization information has been used at the time of

       object create, managed with the object update, and used to authorize

       an object transfer request.  What has not been fully considered is

       the security of the authorization information that includes the

       complexity of the authorization information, the time-to-live (TTL)

       of the authorization information, and where and how the authorization

       information is stored.  This document defines an operational

       practice, using the EPP RFCs, that leverages the use of strong random

       authorization information values that are short-lived, that are not

       stored by the client, and that are stored using a cryptographic hash

       by the server to provide for secure authorization information used

       for transfers.

    The IETF datatracker status page for this draft is:

    https://secure-web.cisco.com/1EgRjgku8x3Km5JfhgQuWfmGV6lwNhSwZOtZ2lDscdUkSS52HJ3sTfBo7_cMRE7DUiv_QgMaeIkQdUfaACitDc5RyhnI93rUeCJB2tFkZy_nWr-PfZAYj5vwXUNQh718p_1Pt5qyDX0hbDYTRl-yPzyhRPYGDCKPurQ-9eNdDWNl3n3yZLljD-qJTRlSDDCiWeCmd1DDJL-Nuy4RgUmhMfAJ4f016F6eVVugCeu2x-ywUMssOKMTinUQ3Z_2D6Wy39RKS3s0JJvNGgDuqkkHfvA/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-regext-secure-authinfo-transfer%2F

    There is also an HTML version available at:

    https://secure-web.cisco.com/1g-oFG2Rb0q9OudOZLHcWqayl3iWcDsYYYKy_6mZX5TsIDTEMFbpB8B8L4mb9TWJ-vFrG2RHBB7bsYZ2z_-XKj-6BddfRt9vXlGSTzJx474CwTJvAVoCwjlVA8jxti_HkcFOeSzwKetNXaIhmsJZ2aPEe3VyhHqJJZGabO40l1olRshbuxP_OHRZbmpOqQ5xw55XgLktAb2HU4e2cnkdpaDV_OU13sILJk3y7ygn1ketFtPURul2FndhvLi5xlp8yfh4qF3tJkGnzZjyquShCwkLTcqXHIhpBByxMjXKAWvw/https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-ietf-regext-secure-authinfo-transfer-04.html

    A diff from the previous version is available at:

    https://secure-web.cisco.com/1HzsdHG6E7e8J9WSPH21O9ZCeVdqvKbyoCVxIuh_fnzuTDUjS0XmsEJ1q1BmFd_kpxgEjtGnAGIV55-i56OxtBOQV6XvwaYkP-g6ThI4FE9vJToZ_G0_kQLQz3kof8i7NRmB6Qzd0nXBM61logPXuDrs20JR9HIOd4vf7aGyHF73BgclQZi2X8pRvaBc-KiZeps-bPXnjE3g3B_5e70EUOiFOBOFlHdwAtuUCwHF93nB6lmkNqxi_pWcDNMpfDxVlclRNn3L8-vgt7P1TXHC_Yle0wx2fbGTSUx6JO2rnfu4/https%3A%2F%2Fwww.ietf.org%2Frfcdiff%3Furl2%3Ddraft-ietf-regext-secure-authinfo-transfer-04

    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.

    Internet-Drafts are also available by anonymous FTP at:

    ftp://ftp.ietf.org/internet-drafts/

    _______________________________________________

    regext mailing list

    regext@ietf.org

    https://secure-web.cisco.com/17C2eFpLRJfccIq47DXAl5UQJCNzM_o4m5jyYP_s06DJOGkItUWrzLbgT9LA8u1ANCu2TUWFe73Vrrey46g4bls0KvUQpstLcHWLZA8iaFc1iibb18LEYLg2-QiVXpbGqvf1_s4TJXy8FMCpRpVFM2gZ_xJmXUuVt7_rsMX30M7kJTo-3THwoYhypnSxpHF1GhIV92GlKFED3WfXO50NDzyeNAukn5Bf6amWblGqyhPAzIEDB1PhHPTcCWI_NAm-ePr9DZbr3nsZhA-g2SiIi1yvh4EwL1_qsiWX3Y2Juiio/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext