Osids Workgroup RFCs

Browse Osids Workgroup RFCs by Number

RFC1274 - The COSINE and Internet X.500 Schema: This document suggests an X.500 Directory Schema, or Naming Architecture, for use in the COSINE and Internet X.500 pilots. [STANDARDS-TRACK]
RFC1275 - Replication Requirements to provide an Internet Directory using X.500: This RFC considers certain deficiencies of the 1988 X.500 standard, which need to be addressed before an effective open Internet Directory can be established using these protocols and services [CCI88]. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC1276 - Replication and Distributed Operations extensions to provide an Internet Directory using X.500: 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. [STANDARDS-TRACK]
RFC1277 - Encoding Network Addresses to Support Operation over Non-OSI Lower Layers: This document defines a new network address format, and rules for using some existing network address formats. [STANDARDS-TRACK]
RFC1278 - A string encoding of Presentation Address: There are a number of environments where a simple string encoding of Presentation Address is desirable. This specification defines such a representation. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC1279 - X.500 and Domains: This RFC considers X.500 in relation to Internet and UK Domains. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.
RFC1384 - Naming Guidelines for Directory Pilots: This document defines a number of naming guidelines. Alignment to these guidelines is recommended for directory pilots. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC1430 - A Strategic Plan for Deploying an Internet X.500 Directory Service: This document describes an overall strategy for deploying a Directory Service on the Internet, based on the OSI X.500 Directory Service. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC1431 - DUA Metrics (OSI-DS 33 (v2)): This document defines a set of criteria by which a DUA implementation, or more precisely a Directory user interface, may be judged. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC1484 - Using the OSI Directory to achieve User Friendly Naming (OSI-DS 24 (v1.2)): This proposal sets out some conventions for representing names in a friendly manner, and shows how this can be used to achieve really friendly naming. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.
RFC1485 - A String Representation of Distinguished Names (OSI-DS 23 (v5)): When a distinguished name is communicated between to users not using a directory protocol (e.g., in a mail message), there is a need to have a user-oriented string representation of distinguished name. [STANDARDS-TRACK]
RFC1487 - X.500 Lightweight Directory Access Protocol: The protocol described in this document is designed to provide access to the Directory while not incurring the resource requirements of the Directory Access Protocol (DAP). [STANDARDS-TRACK]
RFC1488 - The X.500 String Representation of Standard Attribute Syntaxes: This document defines the requirements that must be satisfied by encoding rules used to render Directory attribute syntaxes into a form suitable for use in the LDAP, then goes on to define the encoding rules for the standard set of attribute syntaxes defined in [1,2] and [3]. [STANDARDS-TRACK]
RFC1564 - DSA Metrics (OSI-DS 34 (v3)): This document defines a set of criteria by which a DSA implementation may be judged. Particular issues covered include conformance to standards; performance; demonstrated interoperability. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC1608 - Representing IP Information in the X.500 Directory: This document describes the objects necessary to include information about IP networks and IP numbers in the X.500 Directory. It extends the work "Charting networks in the X.500 Directory" [1] where a general framework is presented for representing networks in the Directory by applying it to IP networks. This memo defines an Experimental Protocol for the Internet community.
RFC1609 - Charting Networks in the X.500 Directory: This document presents a model in which a communication network with all its related details and descriptions can be represented in the X.500 Directory. This memo defines an Experimental Protocol for the Internet community.
RFC1798 - Connection-less Lightweight X.500 Directory Access Protocol: The protocol described in this document is designed to provide access to the Directory while not incurring the resource requirements of the Directory Access Protocol (DAP). [STANDARDS-TRACK]