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


To: "Stephane Bortzmeyer" <bortzmeyer@nic.fr>, <ietf-provreg@cafax.se>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
Date: Thu, 20 Oct 2005 10:05:53 -0400
Content-class: urn:content-classes:message
Sender: owner-ietf-provreg@cafax.se
Thread-Index: AcXVd5KF3Nwuce65QZGdOwcT/aLFmgAANMFw
Thread-Topic: [ietf-provreg] Re: EPP domain:transfer
Subject: RE: [ietf-provreg] Re: EPP domain:transfer

> -----Original Message-----
> From: owner-ietf-provreg@cafax.se 
> [mailto:owner-ietf-provreg@cafax.se] On Behalf Of Stephane Bortzmeyer
> Sent: Thursday, October 20, 2005 8:46 AM
> To: ietf-provreg@cafax.se
> Subject: [ietf-provreg] Re: EPP domain:transfer
> 
> On Wed, Oct 19, 2005 at 03:16:40PM +0200,
>  Gerhard Winkler <gerhard.winkler@univie.ac.at> wrote 
>  a message of 130 lines which said:
> 
> > Are there any ideas how this transfer problem could be solved still
> > using the EPP RFCs?
> 
> What's the purpose of this? Intellectual exercice? Standards are
> supposed to make life *simpler*. If you need a lot of work to fit your
> business rules into the standard, then it is not worth it.

As I said yesterday, one potential solution is quite easy to specify.

> EPP is a bad standard because it is not possible, giving the variety
> of registration rules, to have a standard which is both standard
> (meaning reuse of software) and sufficient.

Given that there is no standard set of registration rules, the first
part of the statement above is disingenuous at best.  The complete
problem is unsolvable by definition because there is no standard set of
registration rules; only parts of the problem can be solved.  What's bad
is asserting that solutions to smaller parts of the problem are
something more than they were designed to be.

-Scott-


Home | Date list | Subject list