I submitted draft-ietf-regext-secure-authinfo-transfer-02 to address feedback 
from Ulrich Wisser (use of random salt) and from Patrick Mevzek (NULL dependent 
on the type of database), and I filled in the Security Considerations section.  
Please review and provide any feedback to the draft.

Thanks,

-- 
 
JG



James Gould
Fellow Engineer
jgo...@verisign.com 
<applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgo...@verisign.com>

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

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

On 6/12/20, 11:53 AM, "regext on behalf of internet-dra...@ietf.org" 
<regext-boun...@ietf.org on behalf of internet-dra...@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-02.txt
        Pages           : 27
        Date            : 2020-06-12
    
    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/1nWxSgquNYjgRAC-j7g-VX-huOMuGaRF_Adgd4ljR80nKZJgFwGQhL7V03Wm05eaxtZ2Y6H9oIEINUeA27eu-ikVIf1PaeOlnGLEW6NnNipF0lmBTQ6XMA71GtS5im3ZqmIoqZ13Sc7Z-aqQp5xKO2HJhwuanB8lVXY8ZjR1UgHMs6De8S2eVU0MfgHZFVFigyOp2GYMWkeUEakfrTcF2JaDiVhtPwQaPg-QXyVUZbJ1t-KTwIkTbrdPzugE7vADHnxb1TPm3yUrsHebay_nvbQ/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-regext-secure-authinfo-transfer%2F
    
    There are also htmlized versions available at:
    
https://secure-web.cisco.com/13almBZ8FDCQavB05zHjFUPljVtW-d0NxcKrCOkIq6A6pddCx-MpAskvn7IHnOyYkxMf16cEusKn5F85ynZbf29tXz2U_dsdqbFT7uwI-e5Y5sIT7Q3Nn-bNiZ5PSzfGQaVEfaFchkdtm_V6bHQprAKr8UWqT6R_WwgtKfCmKqxkfpHd1w2B8xKGdvpMDJkNsM0vLrgZv-K8oEqhDvWGJMt79fsw0v6mVDOP5wsn2gXsM6loz3GqdM_0m5-u8aKd-ApP3b8HIsspX7SkOXpgGzbnKqTKymwgpnoFERJRTffA/https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-regext-secure-authinfo-transfer-02
    
https://secure-web.cisco.com/1FsT0ACHPYyK5SRgcXu_v3-lLChJrUK5sOV6vfMKr_Zsplu4vEUXdy9zv7DoXXyXPdTHWJae7kjWq2pUMEAqq6enMORE3G0XZnlJE1bMMoxODEQrCJq7zhhO1HK7hG9x3pLc45jzju8iLwQaunjxsJCaL7a2NFWBff7DQvih_IkkUr1AiZaief3OuALXZXygYBn1WQVWM-mq_aL_sZ7473fWW8214ph_gDo91oajhkLCnRGZlGsm4zFFZD5kDxI1qY_I0Ehn-iNPTcCURKwgkEw/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-regext-secure-authinfo-transfer-02
    
    A diff from the previous version is available at:
    
https://secure-web.cisco.com/1lvI5BcWA72D95A13V0ng_AP5HHS4vJl-Yz71-H46OoUpa9OjZ3baZEIDUKCYNJn3BV3K4H5WsW-DbFCtbdlsOrmtlY9FIJq1TQ1UhYGmIJSm36KsZ6qathoGVmWp7j6sNDENeGVebtacUs5UsVNZnO6R65lTqEBKBTHCKxVvy-BlNtJrmwCL6-oTcW1m7mv8t-CAtfkI9qyMeNjueQpPmJQ1xgJkH4tHqhRvKoLfwWcT71LAYBhZ_agsp09Wbdihy3LlyhHy39kEMujxTN8DOw/https%3A%2F%2Fwww.ietf.org%2Frfcdiff%3Furl2%3Ddraft-ietf-regext-secure-authinfo-transfer-02
    
    
    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/1bwhJBiwIPO5mhJD-cbteJ1zChdI1AP5SedMd81C2ikzT5tG6Pw7SF67qrqDhvSi2t54tVTrlVOx5wyVgBRppEiVr9NKDH-mUArP-JgsZUIR6BvTT8GETOjI9EnoeFgVtUAx1OkL4qq0G-Sqz0EraZyyTDuW7vcXRnXc2YNNeyc7ztaIXia9dZaMwUAZqeUsEvpF82iKDn0uYTOnyYnAzGYXuji6TwIX-eFgSDsFoQsqpYDD8GFuaf8S5Y_-Y5vwWo9q0dadMNDUtYG5ePFh3lw/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext
    
    

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

Reply via email to