Skip to main content

Minutes IETF102: regext: Tue 13:30
minutes-102-regext-201807171330-00

Meeting Minutes Registration Protocols Extensions (regext) WG
Date and time 2018-07-17 17:30
Title Minutes IETF102: regext: Tue 13:30
State Active
Other versions plain text
Last updated 2018-07-27

minutes-102-regext-201807171330-00
Notes from Registration Protocols Extensions (REGEXT)
IETF 102, Montreal, CA, Agenda

Co-chairs: Jim Galvin, Antoin Verschuren
Mailinglist: regext@ietf.org

Session II,  Regular WG meeting session.
Tuesday, July 17th, 13:30-14:30, Centre Ville

Meeting materials:
https://datatracker.ietf.org/meeting/102/materials/agenda-102-regext-00

Slides:

Chair Slides:
https://datatracker.ietf.org/meeting/102/materials/slides-102-regext-sessb-chair-slides-01

Login Security EPP Extension
https://datatracker.ietf.org/meeting/102/materials/slides-102-regext-sessb-login-security-epp-extension-00

Meeting opened on time by Jim Galvin

1. Welcome and Introductions

Galvin handled meeting mechanics, including review of NOTE WELL and reminder
about standards of behavior

   i.   Jabber scribe
   ii.  Notes scribe
   iii. NOTE WELL
   iv. Charter update

Galvin placed latest charter (see Chair Slides) on screen
-Galvin: On the list, concerns about overly broad scope; these were noted as
 being addressed about with “in consultation with its responsible area director”
 allows scope creep to be addressed
-Adam Roach (ART AD) said that it will be reviewed shortly… and maybe on the
 next TeleChat, which is Aug 2
Proceeded, no further comments on Charter

   v. Document management

Galvin made a request for document shepherds for upcoming work

2. Existing Document Status

2.a. IETF Last call

Galvin noted that the following docs are in IETF Last Call

   i.  Registration Data Access Protocol (RDAP) Object Tagging
       https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-object-tag/

   ii. Allocation Token Extension for the Extensible Provisioning Protocol (EPP)
       https://datatracker.ietf.org/doc/draft-ietf-regext-allocation-token/

2.b.  Documents past WGLC

Galvin noted that the following docs are past WGLC (and are therefore off the
WG to-do list)

   i.  Change Poll Extension for the Extensible Provisioning Protocol (EPP)
       https://datatracker.ietf.org/doc/draft-ietf-regext-change-poll/

   ii. Extensible Provisioning Protocol (EPP) Organization Mapping
       https://datatracker.ietf.org/doc/draft-ietf-regext-org/
       Organization Extension for the Extensible Provisioning Protocol (EPP)
       https://datatracker.ietf.org/doc/draft-ietf-regext-org-ext/

Galvin noted that the I-D on Strict Bundling Registration needs a document
shepherd.  This document is: "Extensible Provisioning Protocol (EPP) Domain Name
Mapping Extension for Strict Bundling Registration"
https://datatracker.ietf.org/doc/draft-ietf-regext-bundlingregistration/

Slide 11 includes another doc that is past WGLC

"Registry Fee Extension for the Extensible Provisioning Protocol (EPP)"
– https://datatracker.ietf.org/doc/draft-ietf-regext-epp-fees/

-Galvin noted that a technical issue has come up with this
-Jim Gould:  working on discrepancy, discussed among a group that included
Afilias, Verisign, GoDaddy.  It was identified that a standard attribute was
in the wrong place.  Going to post info to the list and Roger Carney will be
posting an update.
-Scott Hollenbeck:  we need to run the document through WGLC after it’s edited
-Agreement from the Antoin (who was remote and on video chat)
-Galvin:  we were trying to figure out if this was a technical oversight or
an error.  We’re going to run this through the list.  We missed something and
now we’re going to fix it.  Regardless, we’re going to run it through the
mailing list and will document this for transparency and visibility

2.c. Other documents on our milestones list (5 minutes)

See Chair Slide 12 for exact list with URLs, etc

-Third Party DNS operator to Registrars/Registries protocol
    Galvin:  editors want to move this along… but they have some issues to
    address
-ICANN TMCH functional spec
    Galvin described as 'parked'
-Validate Mapping for the EPP
    Roger Carney:  We had a meeting… and we have some changes coming out of
    that. Should be coming in the next six weeks
-Verification code extension for the EPP
    Galvin:  has been set aside for a while)

2.d. New work items

   i. Login Security EPP Extension (James Gould)
      https://datatracker.ietf.org/doc/draft-gould-regext-login-security/

Gould reviewed provided slides and went to the mic to review them
-Stephane Bortzmeyer:  Brought up a suggestion he said he made on the mailing
list
 what about trying to not reinvent the wheel as it relates to security.
    Galvin agreed to review the email comment
-Alexander (via Jabber):  “Can I use the features independently”…
    Gould:  yes, they are independent

   ii. Data escrow drafts (Gustavo Lozano)

Gustavo provided an update, focused on Data Escrow specification document.
Described documents as stable.
-Roger Carney:  Asked about data privacy considerations.
-Scott Hollenbeck:  Are these specifications being used outside of the gTLD
community? If these were being used in the ccTLD community… then they might be
better targets for global standard. -Richard Wilhelm:  Comments that the
situation around the ICANN adoption of its Temporary Specification the GDPR
could mean that the escrow specification might be changing

3.  Work session summaries

   i. Registry Mapping (Roger Carney)
Roger:  Described as a good working session yesterday.  Group will be trying
to meet semi-regularly to progress the document.  A brief overview:  described
a large questionnaire (from a registrar, to a registry) and how the registry
mapping could help, for example, consistent naming.  It can take a long time
to onboard a registry.  The goal is to accomplish 80% of the questions quickly.

No further discussion.

   ii. Unhandled Namespaces (Jim Gould)
Jim Gould:  In the registry, there is a message queue, when the client connects,
it specifies what things it supports.  So if there are messages that the client
doesn’t support, what should the server do.  Described the options (see slides
from yesterday).  Current conclusion:  we have a problem that we think should
be fixed and we’ll create an I-D to help solve it.
Roger Carney:  Agree that it’s a problem, not sure how big it is.  I don’t know
that it’s a priority.

Jim Galvin:  I’m also not sure it’s a problem, but it certainly is a question.

No further discussion.

   iii. RDAP Search Capabilities and Authentication (Francisco Arias)
Francisco: (see slides in meeting)  Described the goal of improving search. 
Described some of the concerns brought up yesterday… weight of implementation,
tiered access, and privacy.

Galvin:  Looking forward to discussing this

No further discussion.

4. AOB

-No one came to the mic to bring up any new business.
-Galvin thanked the group and adjourned the meeting.
-Adjourned at ~2:20pm local time

*****************************************
#EOF