RFC 2970 on Architecture for IDS - Result from TISDAG
RFC Editor <rfc-ed@ISI.EDU> Fri, 13 October 2000 02:13 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12392; Thu, 12 Oct 2000 22:13:12 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id WAA08793 for ietf-123-outbound.10@ietf.org; Thu, 12 Oct 2000 22:05: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 TAA07730 for <all-ietf@loki.ietf.org>; Thu, 12 Oct 2000 19:56:17 -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 TAA08226 for <all-ietf@ietf.org>; Thu, 12 Oct 2000 19:56:14 -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 QAA13251; Thu, 12 Oct 2000 16:56:15 -0700 (PDT)
Message-Id: <200010122356.QAA13251@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2970 on Architecture for IDS - Result from TISDAG
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 12 Oct 2000 16:56:14 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries.
RFC 2970
Title: Architecture for Integrated Directory Services -
Result from TISDAG
Author(s): L. Daigle, T. Eklof
Status: Informational
Date: October 2000
Mailbox: leslie@thinkingcat.com, thommy.eklof@hotsip.com
Pages: 18
Characters: 40448
Updates/Obsoletes/SeeAlso: none
I-D Tag: draft-daigle-arch-ids-05.txt
URL: ftp://ftp.isi.edu/in-notes/rfc2970.txt
A single, unified, global whitepages directory service remains
elusive. Nonetheless, there is increasing call for participation of
widely-dispersed directory servers (i.e., across multiple
organizations) in large-scale directory services. These services
range from national whitepages services, to multi-national indexes of
WWW resources, and beyond. Drawing from experiences with the TISDAG
(Technical Infrastructure for Swedish Directory Access Gateways)
([TISDAG]) project, this document outlines an approach to providing
the necessary infrastructure for integrating such widely-scattered
servers into a single service, rather than attempting to mandate a
single protocol and schema set for all participating servers to use.
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.