Re: [regext] REGEXT Interim Meeting 2018OCT16

Patrick, I like how you have broken down the problem into discrete registry implementation cases that can be applied to any EPP extension. To make the core object-extension (draft-gould-carney-regext-registry) workable, we need to target case 1 (fully RFC-compliant registry implementers) and

Re: [regext] REGEXT Interim Meeting 2018OCT16

On Tue, Nov 27, 2018, at 11:28, Gould, James wrote: > > * Ensure that the hostAddr model of RFC 5731 is supported > > * > > *Discussion* > > * In the case of a zone that supports domain:hostAddr instead of >

Re: [regext] REGEXT Interim Meeting 2018OCT16

Patrick, Please review the latest version of draft-gould-carney-regext-registry, since I believe it has changes that are applicable to your feedback (e.g., batch schedule, host attribute support). I provide my responses to your feedback below. — JG James Gould Distinguished Engineer

Re: [regext] REGEXT Interim Meeting 2018OCT16

On Mon, Nov 26, 2018, at 13:58, Roger D Carney wrote: > * I still don’t like the use of the elements as a > “flexible mechanism to share data between the client and the server”. There are many registries going this route, and it is very sad, even if easy to understand why. It voids any usefuln

Re: [regext] REGEXT Interim Meeting (2018OCT16)

I will attend this meeting. Thanks Roger. Jim On 1 Oct 2018, at 12:57, Roger D Carney wrote: Good Morning, I would like to invite everyone to an interim meeting Tuesday October 16th at 16:00 UTC for 60 minutes. We plan to focus the discussion around two topics: Agenda 1. Vali