Re: [regext] list of documents to consider for working group adoption

["Gould, James" <[e-mail]>]

Jim,

Thanks for putting the list together and I look forward to the Doodle poll.  

You can remove the following drafts from the list for now until we address the IPR with draft-gould-carney-regext-registry:

    Registry Mapping
    https://www.ietf.org/internet-drafts/draft-gould-carney-regext-registry/

    Launch Phase Policy (Extension of Registry Mapping)
    https://datatracker.ietf.org/doc/draft-gould-regext-launch-policy/

I would add the data escrow drafts to the list:

    Registry Data Escrow Specification
    https://datatracker.ietf.org/doc/draft-arias-noguchi-registry-data-escrow/

    Domain Name Registration Data (DNRD) Objects Mapping
    https://datatracker.ietf.org/doc/ draft-arias-noguchi-dnrd-objects-mapping/


I'm in the process of updating the Data Set File Format draft https://datatracker.ietf.org/doc/draft-gould-regext-dataset/ to support a report file definition, in addition to the existing bulk operation file defintion.  The draft will support an extensible set of file definitions, so if new file definitions are needed the draft can be used.  The definition can be in a separate file from the data, which is similar to the CSV approach in the data escrow drafts, or may be combined in the same file as the data, as currently defined in the existing version of draft-gould-regext-dataset.  The field definitions (domain, host, contact, registrar) can be reused across many types of definition files.  The meta-data about the files can be extensible - the meta-data for a bulk operation (i.e., bulk command and sub-command, client identifier, creation date) is different from the meta-data for a report (i.e., report type and sub-type, date or date-range, frequency, tld or tlds, account).  Support for a standard report definition file would help in formally defining the meta-data and format of any report.  This would help the registrars to automate the consumption of any report.  An IANA registry could be setup to register report identifiers and the associated format definitions for both custom and standardized reports.  This draft represents an opportunity for the working group to create a more generic solution for handling reports and bulk operations.  

—
 
JG



James Gould
Distinguished Engineer
[e-mail]

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

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

On 12/7/18, 9:38 AM, "regext on behalf of James Galvin" <[e-mail] on behalf of [e-mail]> wrote:

    Included below is the list of potential documents and topics this 
    working group could adopt.  The first step in moving forward is to make 
    sure we have a complete list.  We are asking folks to review this list 
    and make sure we have not missed anything.  We are allowing one week for 
    this review, until Friday 14 December 2018.  During this time please do 
    ask questions about documents or topics.
    
    The next step will be for the working group members to indicate their 
    top 5 choices of documents to move forward.  Recall that 5 is the 
    maximum number of milestones suggested for us to have open at a time.  
    If there is discussion to be had about this number please start a new 
    email thread and we will see where it goes.
    
    We will do this with a Doodle poll.  Hopefully you are familiar with 
    this.  We will setup each document as a choice and you’ll be asked to 
    select up to 5 documents.  In Doodle, you can select Yes, No, or 
    IfNeedBe.  You can use the IfNeedBe option to indicate documents that 
    you support but not as your top 5.  We will open this Doodle poll before 
    the Christmas holiday and leave it open through Friday, 11 January.  
    That should be plenty of time to get past holiday and vacation time that 
    many folks will have during this time.
    
    Once we have an ordered list of documents we will announce working group 
    adoption requests and we will move forward with our work.  It’s going 
    to be a busy year, 2019!
    
    Registry Mapping
    https://www.ietf.org/internet-drafts/draft-gould-carney-regext-registry/
    
    Registry Reporting Repository
    https://datatracker.ietf.org/doc/draft-mcpherson-sattler-registry-reporting-repo/
    
    Registry Reporting Structure
    https://datatracker.ietf.org/doc/draft-mcpherson-sattler-registry-report-structure/
    
    Domain Fee Report
    https://datatracker.ietf.org/doc/draft-sattler-registry-domain-fee-report/
    
    Registry Transaction Report
    https://datatracker.ietf.org/doc/draft-mcpherson-sattler-ry-transaction-report/
    
    Registry Domain Inventory Report
    https://datatracker.ietf.org/doc/draft-sattler-registry-domain-inventory-report/
    
    Registry Domain Drop Report
    https://datatracker.ietf.org/doc/draft-sattler-registry-domain-drop-report
    
    Registry Maintenance Notifications
    https://datatracker.ietf.org/doc/draft-sattler-epp-registry-maintenance/
    
    Unhandled Namespaces
    https://tools.ietf.org/html/draft-gould-casanova-regext-unhandled-namespaces
    
    Change Poll
    https://tools.ietf.org/html/draft-ietf-regext-change-poll
    
    RDAP Search
    https://datatracker.ietf.org/doc/draft-fregly-regext-rdap-search-regex/
    
    Data Set File Format
    https://datatracker.ietf.org/doc/draft-gould-regext-dataset/
    
    Launch Phase Policy
    https://datatracker.ietf.org/doc/draft-gould-regext-launch-policy/
    
    Login Security
    https://datatracker.ietf.org/doc/draft-gould-regext-login-security/
    
    Antoin and Jim
    
    _______________________________________________
    regext mailing list
    [e-mail]
    https://www.ietf.org/mailman/listinfo/regext