Subject: [eppext] EPPEXT IETF Meeting

From: "Gould, James" <[email-masked]>
Date: Tue, 8 Jul 2014 13:13:25 +0000

Since we’re not going to be meeting in Toronto I’d like to try to bring a couple of topics up for discussion again.  I’ve shared feedback on draft-ietf-eppext-idnmap, draft-ietf-eppext-keyrelay, and draft-ietf-eppext-reg.  The authors of draft-ietf-eppext-reg and draft-ietf-eppext-launchphase have incorporated mine and others feedback, but I think there are still some unresolved issues with draft-ietf-eppext-keyrelay and draft-ietf-eppext-idnmap as highlighted below:

  1.  draft-ietf-eppext-keyrelay – Marc Groeneweg responded that draft-ietf-eppext-keyrelay as drafted could be registered as a custom extension for SIDN and the desire to progress draft-ietf-eppext-keyrelay with changes based on the list feedback.  The authors are considering the feedback for a new version of the draft that I’m assuming would be worked on by the EPPEXT WG.  Discussion at an IETF meeting would have been useful to further discuss the options and the preferences of the authors.
  2.  draft-ietf-eppext-idnmap – Francisco and I have been going back and forth on support for both a language and the existing table model.  We have a custom IDN Language Tag extension that takes language as input, so it’s important to me that language is explicitly supported.  Discussion at an IETF meeting would have been useful to discuss the various models and approaches to use draft-ietf-eppext-idnmap for the registration of IDN domain names across the registries.

I noticed that there was no on-list call for meeting agenda items. It might be helpful to meet if we don’t make on-list progress in the near future.

--

JG

James Gould
Principal Software Engineer
[email-masked]<mailto:[email-masked]>

703-948-3271 (Office)
12061 Bluemont Way
Reston, VA 20190
VerisignInc.com
“This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is non-public, proprietary, privileged, confidential and exempt from disclosure under applicable law or may be constituted as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this message in error, notify sender immediately and delete this message immediately.”