RE: Issues on 3.4.9 Object Information Query

["Hollenbeck, Scott" <shollenbeck@verisign.com>]

>-----Original Message-----
>From: Klaus Malorny [mailto:Klaus.Malorny@knipp.de]
>Sent: Wednesday, April 11, 2001 4:03 AM
>To: Jordyn A. Buchanan
>Cc: Hollenbeck, Scott; ietf-provreg@cafax.se
>Subject: Re: Issues on 3.4.9 Object Information Query
>
>
>"Jordyn A. Buchanan" wrote:
>> 
>> At 9:24 AM +0200 4/10/01, Klaus Malorny wrote:
>>
>> >>[...]
>
>> >I think it does.
>> 
>> Why?  These are fairly separate functions.  The set of capabilities
>> currently defined within provreg are all basically required for
>> object registration and provisioning.  The capability you're talking
>> about is more useful for "maintenance, database synchronisation,
>> error detection etc." as you mention below.  It seems like we could
>> handle the separate functions and purposes through separate
>> mechanisms.
>> 
>
>Just think of the following "conversation":
>
>  Client: delete domain blabla.tld
>  Server: deletion denied. Object still in use.
>
>and now? What are you doing now in the case that *you* think that the
domain
>is *not* in use? Do you want to pay for the domain until you get a database
>dump end of next month or quarter revealing the problem?

Ahh, but the problem will be immediately obvious given the requirement to
explicitly identify the *.blabla.tld name servers in the response to a
general object information query.  The client who wants to delete the domain
can determine exactly which other objects are involved by doing an info
query on the domain object.

<Scott/>