rfc1249.txt

<VC++网络游戏建摸与实现>源代码


RFC 1249                         DIXIE                       August 1991


2.2.4.1 Modify Request

   The header opcode should be set to 0x02.  The data portion of the
   packet consists of the DN of the entry to modify, followed by a null
   octet, followed by a null-separated list of modify operations to
   perform.  Each modify operation is one of the following:

           type            remove attribute type
           type=value      make value the sole value for attribute type
           type+=value     add value to attribute type
           type-=value     remove value from attribute type

   The second form will see to it that existing values (if any) are
   deleted before the new ones are added.  The third form will add the
   attribute type if it does not already exist.  Note that the QUIPU EDB
   format, used to specify value, allows multiple values to be specified
   separated by the "&" character.  This operation is only allowed over
   TCP.

2.2.4.2 Modify Reply

   There is no reply data for the modify operation.  The only indication
   of success or failure is the return code in the header.

2.2.5 Modify RDN

   The DIXIE modify RDN operation corresponds to an X.500 DAP  MODIFYRDN
   operation.

2.2.5.1 Modify RDN Request

   The header opcode should be set to 0x13.  The data portion of the
   packet consists of the DN of the entry to modify, followed by a null
   octet, followed by the new RDN the entry should have, followed by a
   final null octet.  The old value of the RDN is never kept as an
   attribute of the entry.  This operation is only allowed over TCP.

2.2.5.2 Modify RDN Reply

   There is no reply data to the modify RDN operation.  The only
   indication of success or failure is the return code in the header.

2.2.6 Add

   The DIXIE add operation corresponds to an X.500 DAP ADD operation.






Howes, Smith, & Beecher                                         [Page 6]

RFC 1249                         DIXIE                       August 1991


2.2.6.1 Add Request

   The header opcode should be set to 0x11.  The data portion of the
   packet consists of the DN of the entry to add, followed by a null
   octet, followed by a null-separated list of the entry's attributes.
   Each attribute in this list has the form:

           type=value

   where value can consist of a single value, or multiple values
   separated by the "&" character.  The request is terminated by two
   null octets in a row.  This operation is only allowed over TCP.

2.2.6.2 Add Reply

   There is no reply data to the add operation.  The only indication of
   success or failure is the return code in the header.

2.2.7 Remove

   The DIXIE remove operation corresponds to an X.500 DAP REMOVE
   operation.

2.2.7.1 Remove Request

   The header opcode should be set to 0x12.  The data portion of the
   packet consists of the DN of the entry to remove, followed by a null
   octet.  This operation is only allowed over TCP.

2.2.7.2 Remove Reply

   There is no reply data for the remove operation.  The only indication
   of success or failure is the return code in the header.

2.2.8 Bind

   The DIXIE bind operation corresponds to an X.500 DAP BIND operation
   using simple authentication as defined in Recommendation X.509.

2.2.8.1 Bind Request

   The header opcode should be set to 0x04.  The data portion of the
   packet consists of the DN of the entry as which to bind, followed by
   a null octet, followed by the password of the entry as which to bind,
   followed by a final null octet.  A null DN corresponds causes a bind
   as NULLDN to occur.





Howes, Smith, & Beecher                                         [Page 7]

RFC 1249                         DIXIE                       August 1991


2.2.8.2 Bind Reply

   The format of the bind reply packet depends on whether the operation
   was invoked over TCP or UDP.  If the operation was invoked over TCP,
   there is no reply data.  Success or failure of the operation is
   indicated by the return code in the packet header.

   If the bind operation was invoked over UDP, the data portion of the
   reply packet consists of an Internet address in standard dot
   notation, followed by a 0x01 octet, followed by a decimal number (in
   text form), followed by a null octet.  The address and number should
   be taken to be the IP address and port number to which the client
   should connect to obtain an authenticated TCP connection, bound as
   the entity specified in the request packet.

2.3 Operation Code Summary

   This section describes the  possible  values  for  the  DIXIE  header
   operation code.  There are currently 8 possible values:

      0x01    Read
      0x02    Modify
      0x04    Bind
      0x0f    Search
      0x10    List
      0x11    Add
      0x12    Remove
      0x13    Modify RDN

2.4 Return Code Summary

   This section describes the possible values for the the DIXIE header
   return code.  There are currently 17 possible values:

      0x01    The request was successful.
      0x02    The search did not find any matches.
      0x03    Some unknown, generic DIXIE error has occurred.
      0x04    The DIXIE opcode was not recognized by the DIXIE server.
      0x05    Insufficient access to perform a modification.
      0x06    A malformed DN was supplied.
      0x07    Some time limit or size limit was reached.
              Partial results will be returned.
      0x08    A modify was attempted before a bind.
      0x09    A fragment requested was not found.
      0x0a    An attribute type specified is invalid.
      0x0b    An attribute specified does not exist in the entry.
      0x0c    An attribute value specification is invalid.
      0x0d    An attribute value does not exist (as for removal of the



Howes, Smith, & Beecher                                         [Page 8]

RFC 1249                         DIXIE                       August 1991


              value).
      0x0e    A modification of an entry's RDN was attempted via a modify
              operation.  This is not allowed (use modrdn instead).
      0x0f    A supplied DN references an invalid portion of the tree.
      0x10    The DSA has passed back a referral to another DSA (as for a
              modification to a non-local entry), and the DIXIE server was
              unable to follow it.
      0x11    The DSA is down or unreachable.

3.    References

   [1] Information Processing - Open Systems Interconnection - The
       Directory, International Organization for Standardization,
       International Standard 9594, 1988.

   [2] Kille, S., Robbins, C., Roe, M., and A. Turland, "The ISO
       Development Environment: User's Manual", Volume 5: QUIPU,
       Performance Systems International, January 1990.

   [3] Rose, M., "Directory Assistance Service", RFC 1202, Performance
       Systems International, February 1991.

4.    Available Implementations

       This section is not meant as an endorsement of any
       implementation, it is provided merely as information for the
       Internet community.  A full Un*x-based implementation of the
       DIXIE protocol in the form of a DIXIE server and DIXIE
       application library is freely available for anonymous FTP from
       the host terminator.cc.umich.edu in the ~ftp/x500 directory.
       Un*x and Macintosh clients that use the DIXIE protocol have also
       been implemented and are available from the same location.

       There is also a discussion list for DIXIE-related topics called
       [e-mail].  To join, send mail to dixie-
       [e-mail].

5.    Security Considerations

   Security issues are not discussed in this memo.











Howes, Smith, & Beecher                                         [Page 9]

RFC 1249                         DIXIE                       August 1991


6.    Authors' Addresses

   Tim Howes
   University of Michigan
   Information Technology Division
   535 West William St.
   Ann Arbor, MI 48103-4943

   Phone: [phone]
   EMail: [e-mail]


   Mark Smith
   University of Michigan
   Information Technology Division
   535 West William St.
   Ann Arbor, MI 48103-4943

   Phone: [phone]
   EMail: [e-mail]


   Bryan Beecher
   University of Michigan
   Information Technology Division
   535 West William St.
   Ann Arbor, MI 48103-4943

   Phone: [phone]
   EMail: [e-mail]





















Howes, Smith, & Beecher                                        [Page 10]