rfc1564.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.

    ....................................................................
    ....................................................................
    ....................................................................

   49. Does the DSA attempt to use relay DSAs (which have access to more
       than one network) in order to achieve connectivity with DSAs
       which are not on the same network?  [2] .........................

7.  Management tools

7.1  Dynamic system management

   50. Are there tools for monitoring DSA activity, using:

      (a)  DAP? [1] ....................................................

      (b)  CMIP? [1] ...................................................

      (c)  SNMP? [1] ...................................................

   51. Are there tools for controlling a run-time DSA? [2] .............






Barker & Hedberg                                               [Page 11]

RFC 1564                      DSA Metrics                   January 1994


7.2  Static system management

   52. If knowledge information is stored within the DIT, are there
       tools for knowledge management?  [2] ............................

   53. Are there tools for checking that attributes with Distinguished
       Name syntax contain values of entries in the DIT (i.e., they do
       not contain "dangling pointers")?  [1] ........................

7.3  Data management

   54. If the DSA doesn't use a general-purpose database package, what
       data management tools are available?  ...........................
    ....................................................................

   55. Are there any tools for arboriculture - the moving, copying or
       deleting of DIT subtrees?  [2] ..................................

8.  Operational Use

   The DSA may have lots of wonderful features -- on paper!  But has the
   DSA been shown to work in practice?  The following measures are
   intended to give some measure of confidence that the DSA's viability
   has been demonstrated.

   56. How many entries in the largest DSA in use in operational use?  :

   57. What is the largest set of DSAs supporting an organisation?  ....

   58. What is the estimated number of organisations using this
       implementation for service use?  [8 if more than 100
       organisations, 5 if more than 50 organisations, 3 if more than 20
       organisations, 2 if more than 5 organisations, 1 if more than 1
       organisation] ...................................................

   59. Is this DSA used commercially with an installed base of more than
       10 customers?  [2] ..............................................

9.  Interoperability

   The X.500 Directory is the OSI Directory.  OSI stands for Open
   Systems Interconnection -- DSAs have to be able to inter-operate.
   They also have to be seen to interoperate.

   60. Is this DSA in use in X.500 pilots?  ............................

      (a)  Is this DSA in use anywhere in the COSINE/Internet Pilot? [3]




Barker & Hedberg                                               [Page 12]

RFC 1564                      DSA Metrics                   January 1994


        ................................................................

      (b)  Is this DSA in use in any other major pilot?  [2] ...........

   61. Name any other systems which you believe the system to
       interoperate with.  (It is not sufficient to say "any system
       which supports the conformance clauses ...")  ..................
    ....................................................................
    ....................................................................
    ....................................................................

   62. Please name all interoperability testing applied to the
       implementation, specify test suite and what other implementation
       that was used [1 per implementation, up to maximum of 5] ........
    ....................................................................
    ....................................................................
    ....................................................................
    ....................................................................
    ....................................................................

10.  Performance

   This section should give an outline to the expected performance of
   the DSA. A number of operations are timed in order to give a feel for
   the DSA's speed and throughput.  Note that all operations should be
   resolvable within a single DSA. Chaining and referral are not
   assessed, although it should be possible to infer, albeit
   approximately, the speed of distributed operations.

   i.  The tests should be made against an organisational database of
       20000 entries.  Some tests are against subsets of this data, and
       so the database should be set up according to the following
       instructions.

       Create an organisational DSA with 20000 entries below the
       organisation node.  Sub-divide this data into a number of
       organisational units, one of which should contain 1000 entries,
       another of which should contain 100 entries, and a third which
       should contain just 10 entries.  The entries, which should
       differ, should be created with the following attributes:

       (a)  Common Name

       (b)  Surname

       (c)  Telephone number

       (d)  Postal Address (of 100 characters)



Barker & Hedberg                                               [Page 13]

RFC 1564                      DSA Metrics                   January 1994


       (e)  Object class

    ii. In all the tests, two timings should be taken.  In order to
        normalise the test results as much as possible, it is suggested
        that these tests be undertaken on an otherwise lightly loaded
        machine.

       (a)  A typical "cold start" reading should be given.  In this
            case the system will not have the advantage of any benefits
            that derive from operating system paging, or caching.

       (b)  A best possible figure should be given, which indicates the
            upper limit of DSA performance.

   iii. The timings should relate to the default set-up, and should be
        entered in Table 2.  If significant performance gains can be made
        by use of configuration options, such as building extra indexes
        to support searches, measures of the improved performance may
        also be given, and should be entered in Table 3.
        Attention should be also drawn to any optimisations, heuristic or
        otherwise, which are not evidenced in the following tests.

    iv. Please note that the tests should be made using a DUA and DSA
        with full 7-layer stacks, rather than some lightweight protocol.

10.1  Speed for various operations

   The tests are described, one subsection per operation.  The results
   should be entered in Table 2 (and Table 3 if a non-default set-up is
   also measured).

10.1.1  Bind

   The time it takes for a DUA to bind to the Directory.  This time
   should include all the initialisation time a DUA process needs before
   it can query the Directory: e.g., reading of tailor files, schema
   information, etc.  Give the bind time for each of the following
   levels of authentication.  State "n/a" if the implementation does not
   support a particular level of authentication.

   63. Anonymous

   64. Simple

   65. Simple protected

   66. Strong




Barker & Hedberg                                               [Page 14]

RFC 1564                      DSA Metrics                   January 1994


10.1.2  List

   Give the time for listing a set of organisational unit sibling
   entries.

   67. 10 entries

   68. 1000 entries

10.1.3  Search

   In this section, two sets of search operations should be performed on
   the DSA.

   i.  A single level search of 100 entries within an organisational
       unit.

   ii. An organisation subtree search, on the subtree of 20000 entries.

   The following searches should be tried.  Unless otherwise stated, the
   "XXX" or "YYY" part of the search filter should be chosen in such a
   way as to return a single result.  Unless stated otherwise the
   results should return all attributes for the entry.

   69. Exact match for a surname:

           surname=XXX

   70. Leading substring match for a common name:

           commonName=XXX*

   71. Any substring match for a common name:

           commonName=*XXX*

   72. Trailing substring match for a common name:

           commonName=*XXX

   73. Approximate match for a common name:

           commonName"=XXX

   74. More complex filter, searching by object class and two other
       attribute types:





Barker & Hedberg                                               [Page 15]

RFC 1564                      DSA Metrics                   January 1994


           objectClass=person AND
           (commonName=XXX* OR telephoneNumber=*YYY)

   75. Search returning all entries (i.e., 100 entries in the single
       level search, and all 20000 entries in the subtree search:

           objectClass=*

       In this case, no attribute values should be returned in the
       result set.

10.1.4  Read

   76. A single read operation, returning all attributes.

10.1.5  Add entry

   77. Add an entry beneath an entry which has:

      (a)  0 children

      (b)  10 children

      (c)  1000 children

10.1.6  Modify entry

   Modify an attribute value, other than an RDN value, for an entry
   which has

   1.  10 siblings

   2.  1000 siblings

   78. Modify an entry

      (a)  Add description attribute

      (b)  Remove description attribute