RFC 2969 on Wide Area Directory Deployment

RFC Editor <rfc-ed@ISI.EDU> Fri, 13 October 2000 02:02 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12131; Thu, 12 Oct 2000 22:02:32 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id VAA08701 for ietf-123-outbound.10@ietf.org; Thu, 12 Oct 2000 21:55:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id TAA07681 for <all-ietf@loki.ietf.org>; Thu, 12 Oct 2000 19:54:46 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA08177 for <all-ietf@ietf.org>; Thu, 12 Oct 2000 19:54:44 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id QAA13016; Thu, 12 Oct 2000 16:54:43 -0700 (PDT)
Message-Id: <200010122354.QAA13016@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2969 on Wide Area Directory Deployment
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 12 Oct 2000 16:54:43 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        RFC 2969

        Title:	    Wide Area Directory Deployment - Experiences from
                    TISDAG 
        Author(s):  T. Eklof, L. Daigle
        Status:     Informational
	Date:       October 2000
        Mailbox:    thommy.eklof@hotsip.com, leslie@thinkingcat.com
        Pages:      19
        Characters: 43002
        Updates/Obsoletes/SeeAlso:    none

        I-D Tag:    draft-eklof-dag-experiences-04.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2969.txt


The TISDAG (Technical Infrastructure for Swedish Directory Access
Gateway) project provided valuable insight into the current reality
of deploying a wide-scale directory service.  This document
catalogues some of the experiences gained in developing the necessary
infrastructure for a national (i.e., multi-organizational) directory
service and pilot deployment of the service in an environment with
off-the-shelf directory service products.  A perspective on the
project's relationship to other directory deployment projects is
provided, along with some proposals for future extensions of the work
(larger scale deployment, other application areas).
 
These are our own observations, based on work done and general
project discussions.  No doubt, other project participants have their
own list of project experiences; we don't claim this document is
exhaustive!

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ftp.isi.edu/in-notes/rfc2969.txt"><ftp://ftp.isi.edu/in-notes/rfc2969.txt>