[Ietf-not43] -02 requirements draft

[Peter Gietz]

Hi,

I would like to second Ted in this thread. The Domain Registrant Search=20
is doable by means of an indexing system.
We in an European working Group on Directory deployment (TERENA Task=20
Forc LDAP Service Deployment, http://www.terena.nl/task-forces/tf-lsd)=20
have gained some experience with LDAP and CIP. The single service manager=

wouldn't even have to provide an index object, but could also allow its=20
service to be crawled by a known, registered and
authenticated crawler that can produce such an index object. So its=20
either delivering the index objects yourself or let a trusted
crawler do that job. And: yes there has to be someone who is willing to=20
maintain the index service.

I also second Ted in another respect: requirements documents should not=20
too much be concerned with the architecture that fullfills the specified =

requirements. It is more something like "what to we want, what do we=20
need" and it is the problem of the authors of the architecture documents =

to specify the architecture accordingly.

A distributed architecture with one or more central index services (in=20
analogy to www and google)  is in any case a good choice, which provides =

flexibility, scalability, and reliability (by redundancy).  I am happy=20
to contribute to the LDAP documents to include such an architecture.

Cheers,

Peter


Rick Wesson wrote:

>Ted,
> =20
>
>>discussion is a requirements discussion.  The requirement provides
>>functionality: "Tell me all the domains administered by Example DNS
>>/Tell me all the domains owned by Joe Example".  There are
>>clear reasons to want this functionality.
>>   =20
>>
>
>no, I've asked for the requirement to be removed. only you and the draft=

>author have said no. There has been almost no discussion on this list on=

>or about the points in the requirements draft. I am stating that these
>requirements are not fully baked and are not nearly cooked enough for
>passing them off to the IESG.
>
>none of the other requirements have conditions that require all members =
of
>the mesh to participate in a query. this type of query does deserve
>special attention because of the negative impact it could bring to those=

>who provide crip resolution service.
>
>for these reasons I request that 3.2.3 be removed as a requirement,
>otherwise please enumerate the clear reasons you have eluded to for
>retaining this functionality.
>
>-rick
>
>
>
>
>
>_______________________________________________
>Ietf-not43 mailing list
>Ietf-not43@lists.verisignlabs.com
>http://lists.verisignlabs.com/mailman/listinfo/ietf-not43
> =20
>


--=20
_______________________________________________________________________
=20
Peter Gietz (CEO)
DAASI International GmbH                phone: +49 7071 2970336
Wilhelmstr. 106                         Fax:   +49 7071 295114 =20
D-72074 T=FCbingen                        email: peter.gietz@daasi.de
Germany                                 Web:   www.daasi.de

Directory Applications for Advanced Security and Information Management
_______________________________________________________________________