Re: Presentation on EPP present and future

Wil Tan <[email protected]>
Newsgroups gmane.ietf.provreg
Message-ID <[email protected]>
On Thu, Jun 24, 2010 at 9:20 AM, Michael Young <[email protected]>wrote:

> As far as I understand the process to initiate further EPP work in the IETF
> would focus on a) defining a problem and subsequent scope of work  b)
> garnering support from the relevant area director  c) following the process
> of initiating a working group - mailing list where clear efforts are
> demonstrated, BOF, etc OR another option is to file an informational RFC.
>
>
I missed Patrick's presentation at the ccNSO tech day, but did read the
draft that he circulated a while ago.

From my perspective, the main problem with how the implementations have
evolved is a loss of interoperability. IIRC, in the case of CZNIC, complete
schemas were defined to replace the standard domain and contact mappings,
reducing EPP into not much more than a framing protocol. Not sure exactly
the rationale for doing that, though I'm sure considerable thoughts have
been put into it. It does mean that registrars could not easily reuse
existing libraries or code written for one registries to talk to another
though.


> Its been said before, but I'll say it again, EPP is an Extensible protocol.
> Given its flexibility, I have yet to hear an argument as to why existing
> issues cannot be addressed using the extension system.
>
>
See above. Also, I believe there are some minor tweaks that could be done to
the existing schema that would make less inherent assumptions about the
registry data model (by making some fields optional). However, I don't any
way to handle schema changes in a backwards compatible manner.

Working along the lines of defining new mapping encompassing common use
cases would perhaps be worth pursuing and more productive than attempting to
change the core protocol. Patrick's work would certainly come in handy in
that case.

wil.

If a valid argument can be made, I am happy to support additional efforts on
> the base protocol, as of yet, I have not seen one.
>
> Best Regards,
>
> Michael Young
>
>
> -----Original Message-----
> From: Patrick Mevzek [mailto:[email protected]]
> Sent: June-23-10 9:01 PM
> To: EPP Provreg
> Subject: [ietf-provreg] Presentation on EPP present and future
>
> Hello,
>
> I've done last monday in the ICANN ccNSO
> tech day a presentation on my current view of EPP, based on the
> extensions seen in the wild, and what could be future works on EPP
> with some data on the 60+ extensions I've seen, and choices among EPP
> "options" (host as attribute or contact, contact data, etc.)
>
> You can find the presentation online here:
>
> http://www.dotandco.com/services/software/Net-DRI/docs/netdri-future-epp-ica
> nn-brussels-ccnso-techday-201006/index.html
> or if you want just the text as PDF:
>
> http://www.dotandco.com/services/software/Net-DRI/docs/netdri-future-epp-ica
>
> nn-brussels-ccnso-techday-201006/netdri-future-epp-icann-brussels-ccnso-tech
> day-201006.pdf
>
> While the attendance was high, there has not been any real feedback
> at that time on the relevance on working again on EPP or even, as
> stated in my presentation, to try at least to make people (from
> registries, registrars, and outside developers such as myself) to
> collaborate together, starting with extensions documentation and
> public announcements.
>
> Hope that helps.
>
> --
> Patrick Mevzek
> Dot and Co <http://www.dotandco.com/> <http://www.dotandco.net/>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> List run by majordomo software.  For (Un-)subscription and similar details
> send "help" to [email protected]
>
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> List run by majordomo software.  For (Un-)subscription and similar details
> send "help" to [email protected]
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.