> -----Original Message----- > From: regext [mailto:regext-boun...@ietf.org] On Behalf Of Andrew Newton > Sent: Thursday, March 23, 2017 11:39 AM > To: Bernhard Reutner-Fischer <rep.dot....@gmail.com> > Cc: Andy Newton <a...@arin.net>; regext@ietf.org; Gustavo Lozano > <gustavo.loz...@icann.org> > Subject: [EXTERNAL] Re: [regext] RDAP questions > > On Tue, Mar 21, 2017 at 3:47 PM, Bernhard Reutner-Fischer > <rep.dot....@gmail.com> wrote: > >>> 2) entity handles > >>> > >>> At least for DNRs the mixture of registrars and contacts seems to be > >>a > >>> bit unfortunate at first glance. > >>> For handles (in the DNR / RFC5733 sense) could conflict between > >>> registrars and contacts. Furthermore there is no (apparent) way to > >>> output a ROID which would make it easier to distinguish these two, > >>> disregarding the role of course. > >>> I could work around this by requiring a -ROIDSFX for contacts and > >>none > >>> for registrars, for example. > >>> > >>> So i think my question is how to respond to a non-search query for > >>> an ambiguous entity? > >> > >>I'm not sure I understand this. You have two entities with the same > >>handle? > > > > Yes. I think in EPP they are unambiguous. > > > > thanks, > > So my reading of RFC 5730 doesn't say if ROIDs are unique within a > registry or unique within a namespace. I do have to admit I don't > understand how section 2.8 fits into it. Hopefully somebody more > authoritative can shed some light (I'm looking at you, Scott :) ).
Repository identifiers are intended to be unique within a registry/repository. That may not be very clear in the text, but if you read through RFCs 5731, 5732, and 5733 you'll see that ROIDs are assigned to domain, host, and contact objects, too - and they can be associated with objects across namespaces. Scott _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
