[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: Dan Kirkdorffer <dan.kirkdorffer@enom.com>
cc: "'Daniel Manley'" <dmanley@tucows.com>, "Hollenbeck, Scott" <shollenbeck@verisign.com>, "Damaraju, Ayesha" <ayesha.damaraju@neustar.com>, "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>, epp-rtk-devel <epp-rtk-devel@lists.sourceforge.net>
From: Rick H Wesson <wessorh@ar.com>
Date: Thu, 14 Jun 2001 14:50:36 -0700 (PDT)
In-Reply-To: <935533C14F67D411B333009027DC5F6A0137ECAB@YEW>
Sender: owner-ietf-provreg@cafax.se
Subject: RE: [Epp-rtk-devel] RE: ROID Placement



On Thu, 14 Jun 2001, Dan Kirkdorffer wrote:

> Any change made now will impact any registrar coding to the API.
> Eliminating roids will break code.

yes, expect more as EPP revises itself within the IETF.

> When is the RTK planned to go 1.0 anyway?

I hope not before the RFC comes out, but release numbers are arbitrary, we
could just go to release 10 but what would that mean...

-rick

> Dan
> eNom
>
> > -----Original Message-----
> > From: Daniel Manley [mailto:dmanley@tucows.com]
> > Sent: Thursday, June 14, 2001 1:06 PM
> > To: Hollenbeck, Scott
> > Cc: 'Rick H Wesson'; Damaraju, Ayesha; 'ietf-provreg@cafax.se';
> > epp-rtk-devel
> > Subject: Re: [Epp-rtk-devel] RE: ROID Placement
> >
> >
> > I'm fine with getting rid of ROIDs from the protocol.
> >
> > With the re-introduction of the contact id, ROIDs are mostly
> > useless for
> > registrars now because it's an extra piece of data that can't
> > be used in
> > any EPP requests.  At this point, they only seem to be of
> > benifit to the
> > registry (in reports?) and possibly to Whois service.
> >
> > As for the impact on the RTKs, we would just remove the ROIDs
> > from the
> > IDL and removing their parsing from the EPP responses.  Very
> > little impact.
> >
> > Dan
> >
> > Hollenbeck, Scott wrote:
> >
> > >>-----Original Message-----
> > >>From: Rick H Wesson [mailto:wessorh@ar.com]
> > >>Sent: Thursday, June 14, 2001 2:31 PM
> > >>To: Damaraju, Ayesha
> > >>Cc: 'ietf-provreg@cafax.se'; epp-rtk-devel
> > >>Subject: Re: your mail
> > >>
> > >>
> > >>
> > >>Ayesha,
> > >>
> > >>I agree with your analysis but, i woud also like to
> > understand what any
> > >>other object besides a contact needs a roid. Objects such
> > as hosts and
> > >>domains are unique within a registry, maybe we should only
> > have a ROID for
> > >>contacts?
> > >>
> > >
> > >This all goes back to a lengthy requirements discussion
> > about ROIDs and a
> > >decision that they were required for all objects.
> > Personally I wouldn't
> > >complain if we agreed to get rid of them completely ;-), but if a new
> > >decision is made to associate them only with contacts we'd
> > need to go back
> > >and change the requirements draft (no big deal), and then it
> > would make
> > >perfect sense to put the ROID-specific stuff in the contact
> > object mapping.
> > >
> > ><Scott/>
> > >
> > >_______________________________________________
> > >Epp-rtk-devel mailing list
> > >Epp-rtk-devel@lists.sourceforge.net
> > >http://lists.sourceforge.net/lists/listinfo/epp-rtk-devel
> > >
> >
> >
> >
> >
> > _______________________________________________
> > Epp-rtk-devel mailing list
> > Epp-rtk-devel@lists.sourceforge.net
> > http://lists.sourceforge.net/lists/listinfo/epp-rtk-devel
> >
>


Home | Date list | Subject list