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


To: Alexander Mayrhofer <axelm@nic.at>
CC: ietf-provreg@cafax.se
From: janusz <janusz@ca.afilias.info>
Date: Thu, 13 Apr 2006 10:34:41 -0400
In-Reply-To: <443E51AE.3070805@nic.at>
Sender: owner-ietf-provreg@cafax.se
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040413 Debian/1.6-5
Subject: Re: [ietf-provreg] RFC3731: domain:roid in <info> response

Alex,
making the element OPTIONAL could create some problems for EPP clients. 
A domain object with the same name can be deleted and later recreated. I 
don't see anything else than <domain:roid> in domain info response that 
would allow EPP clients detection of such situations.

cheers,

Janusz Sienkiewicz




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.
>
>So, is there a reason why the "roid" is not optional in the <info> response?
>And, any chance to change that in 3731bis? As it seems to me, we'd need to
>"leak" the internal id of a domain object to the client for just this single
>info-response - without any further use.
>
>any insight appreciated.
>
>cheers
>
>Alex Mayrhofer
>nic.at
>  
>


Home | Date list | Subject list