Replication and Distributed Operations extensions to provide an Internet Directory using X.500
RFC 1276

Document Type RFC - Historic (November 1991; No errata)
Last updated 2013-03-02
Stream IETF
Formats plain text ps pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 1276 (Historic)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                            S.E. Hardcastle-Kille
Requests for Comments 1276                   University College London
                                                         November 1991

          Replication and Distributed Operations extensions
             to provide an Internet Directory using X.500

Status of this Memo
    This RFC specifies an IAB standards track protocol for the
    Internet community, and requests discussion and suggestions for
    improvements.  Please refer to the current edition of the ``IAB
    Official Protocol Standards'' for the standardization state and
    status of this protocol.  Distribution of this memo is unlimited.

Abstract
    Some requirements on extensions to X.500 are described in the
    RFC[HK91b], in order to build an Internet Directory using
    X.500(1988).  This document specifies a set of solutions to the
    problems raised.  These solutions are based on some work done for
    the QUIPU implementation, and demonstrated to be effective in a
    number of directory pilots.  By documenting a de facto standard,
    rapid progress can be made towards a full-scale pilot.  These
    procedures are an INTERIM approach.  There are known
    deficiencies, both in terms of manageability and scalability.
    Transition to standard approaches are planned when appropriate
    standards are available.  This RFCwill be obsoleted at this
    point.



RFC 1276         Internet Directory Replication          November 1991

Contents

1   Approach                                                         2

2   Extensions to Distributed Operations                             3

3   Alternative DSAs                                                 4

4   Data Model                                                       5

5   DSA Naming                                                       6

6   Knowledge Representation                                         6

7   Replication Protocol                                             9

8   New Application Context                                         12

9   Policy on Replication Procedures                                12

10  Use of the Directory by Applications                            12

11  Migration and Scaling                                           12

12  Security Considerations                                         13

13  Author's Address                                                13

A   ASN.1 Summary and Object Identifier Allocation                  14

List of Figures

    1      Knowledge Attributes  .   .   .   .   .   .   .   .       8

    2      Replication Protocol  .   .   .   .   .   .   .   .      10
    3      Summary of the ASN.1  .   .   .   .   .   .   .   .      17

Hardcastle-Kille                                                Page 1



RFC 1276         Internet Directory Replication          November 1991

1  Approach

There are a number of non-negotiable requirements which must be met
before a directory can be deployed on the Internet [HK91b].  These
problems are being tackled in the standards arena, but there is
currently no stable solution.  One approach would be to attempt to
intercept the standard.  Difficulties with this would be:

 o  Defining a coherent intercept would be awkward, and the effort
    would probably be better devoted to working on the standard.  It
    is not even clear that such an intercept could be defined.

 o  The target is moving, and it is always tempting to track it, thus
    causing more delay.

 o  There would be a delay involved with this approach.  It would be
    too late to be useful for a rapid start, and sufficiently close to
    the timing of the final standard that many would choose not to
    implement it.

Therefore, we choose to take a simple approach.  This is a good deal
simpler than the full X.500 approach, and is based on operational
experience.  The advantages of this approach are:

 o  It is proven in operation.  This RFCis simply documenting what is
    being done already.

 o  There will be a minimum of delay in starting to use the approach.

 o  The approach is simpler, and so the cost of implementation is much
    less.  It will therefore be much more attractive to add into an
    implementation, as it is less effort, and can be further ahead of
    the standard.

These procedures are an INTERIM approach.  There are known
deficiencies, both in terms of manageability and scalability.
Transition to standard approaches are planned when appropriate
standards are available.  This RFCwill be obsoleted at this point.

Hardcastle-Kille                                                Page 2



RFC 1276         Internet Directory Replication          November 1991

2  Extensions to Distributed Operations

The distributed operations of X.500 assume that all DUAs and DSAs are
fully interconnected with a global network service.  For the Internet
Pilot, this assumption is invalid.  DSAs may be operated over TCP/IP,
Show full document text