To:
ietf-provreg@cafax.se
From:
Andrew Sullivan <andrew@ca.afilias.info>
Date:
Thu, 13 Apr 2006 10:11:26 -0400
Content-Disposition:
inline
In-Reply-To:
<443E51AE.3070805@nic.at>
Mail-Followup-To:
Andrew Sullivan <andrew@ca.afilias.info>,ietf-provreg@cafax.se
Reply-To:
Andrew Sullivan <andrew@ca.afilias.info>
Sender:
owner-ietf-provreg@cafax.se
User-Agent:
Mutt/1.5.11
Subject:
Re: [ietf-provreg] RFC3731: domain:roid in <info> response
On Thu, Apr 13, 2006 at 03:27:10PM +0200, Alexander Mayrhofer wrote: > Hi, > > i just noticed that the "roid" element in the response to a <domain:info> > request is a mandatory element. However, it seems that the "roid" is not > required in any other requests on domain objects, because all other > transactions use the <domain:name> to identify a certain object instance. It might be useful to clients over time, though: a domain name need not be unique over time (whereas the roid is defined in such a way that it ought to be). When the record is current, of course, the sponsor could know what the roid is (because they had it originally, and the object hasn't been removed from the repository). But it is undoubtedly extremely useful for retrospective co-ordination for client and server operators to be able to refer to different objects of the same name by unique ids. Of course, that's not a terribly strong reason for a mandatory requirement. A -- ---- Andrew Sullivan 204-4141 Yonge Street Afilias Canada Toronto, Ontario Canada <andrew@ca.afilias.info> M2P 2A8 +1 416 646 3304 x4110