Pieter,

A reserved domain name may be held in the live domain table and sponsored by an 
internal server account, where the allocation token on a transfer request may 
be used to allocate the domain name to the client.  The allocation token is an 
explicit credential for allocation authorization and it does not replace the 
authInfo value.  

Thanks,
  
—
 
JG



James Gould
Distinguished Engineer
[email protected]

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

Verisign.com <http://verisigninc.com/> 
On 4/13/18, 5:05 AM, "Pieter Vandepitte" <[email protected]> 
wrote:

    Hi,
    
    Short question: what's the purpose of an allocation token within a transfer 
command (and what's the difference with authInfo code)? I understand the 
purpose in case of create and I can imagine some use cases for update, but even 
for update, I have my doubts.
    
    I'm sorry if this question has been asked in the past, but Google doesn't 
appear to be my friend today ;-)
    
    Pieter
    
    > On 29 Jan 2018, at 20:32, Gould, James <[email protected]> wrote:
    > 
    > Hi,
    > 
    > I published the revised draft-ietf-regext-allocation-token based on the 
feedback received during the WGLC.  Please provide any additional feedback on 
the list.
    > 
    > Thanks,
    > 
    > —
    > 
    > JG
    > 
    > 
    > 
    > James Gould
    > Distinguished Engineer
    > [email protected]
    > 
    > 703-948-3271
    > 12061 Bluemont Way
    > Reston, VA 20190
    > 
    > Verisign.com <http://verisigninc.com/>
    > On 1/29/18, 2:30 PM, "regext on behalf of [email protected]" 
<[email protected] on behalf of [email protected]> 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           : Allocation Token Extension for the 
Extensible Provisioning Protocol (EPP)
    >            Authors         : James Gould
    >                              Kal Feher
    >           Filename        : draft-ietf-regext-allocation-token-06.txt
    >           Pages           : 22
    >           Date            : 2018-01-29
    > 
    >    Abstract:
    >       This document describes an Extensible Provisioning Protocol (EPP)
    >       extension for including an Allocation Token in query and transform
    >       commands.  The Allocation Token is used as a credential that
    >       authorizes a client to request the allocation of a specific object
    >       from the server, using one of the EPP transform commands including
    >       create and transfer.
    > 
    > 
    >    The IETF datatracker status page for this draft is:
    >    https://datatracker.ietf.org/doc/draft-ietf-regext-allocation-token/
    > 
    >    There are also htmlized versions available at:
    >    https://tools.ietf.org/html/draft-ietf-regext-allocation-token-06
    >    
https://datatracker.ietf.org/doc/html/draft-ietf-regext-allocation-token-06
    > 
    >    A diff from the previous version is available at:
    >    https://www.ietf.org/rfcdiff?url2=draft-ietf-regext-allocation-token-06
    > 
    > 
    >    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
    >    [email protected]
    >    https://www.ietf.org/mailman/listinfo/regext
    > 
    > 
    > _______________________________________________
    > regext mailing list
    > [email protected]
    > https://www.ietf.org/mailman/listinfo/regext
    
    

_______________________________________________
regext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/regext

Reply via email to