⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 rfc1804.txt

📁 中、英文RFC文档大全打包下载完全版 .
💻 TXT
📖 第 1 页 / 共 2 页
字号:
RFC 1804          Schema Publishing in X.500 Directory         June 19955. The Meta-Schemaexperimental = 1.3.6.1.3schema OBJECT IDENTIFIER        ::= {experimental 65}schemaObjectClass OBJECT IDENTIFIER        ::= {schema.1}schemaAttribute OBJECT IDENTIFIER        ::= {schema.2}subschema OBJECT CLASS    Subclass of TOP        MUST CONTAIN {            commonName            - -  For naming        }        ::= {schemaObjectClass.1}objectClass OBJECT CLASS    Subclass of TOP        MUST CONTAIN {            objectIdentifier                - - This field stores the object identifier of object                - - represented by an object class entry. This attribute                - - is used for naming an object class entry.        }        MAY CONTAIN {            commonName,                 - - This field is used to store the name of the object            mandatoryNamingAttributes,            mandatoryAttributes,            optionalNamingAttibutes,            optionalAttributes,            obsolete,            description,            subClassOf        }        ::= {schemaObjectClass.2}attributeType OBJECT CLASS    Subclass of Top        MUST CONTAIN {            objectIdentifier        }        MAY CONTAIN {Mansfield, et al              Experimental                      [Page 6]RFC 1804          Schema Publishing in X.500 Directory         June 1995             commonName,                - - used to store the name of the attribute type             constraint,             attributeSyntax,             multivalued,             obsolete,             matchRules,             description        }        ::= {schemaObjectClass.3}matchingRule OBJECT CLASS     Subclass of Top        MUST CONTAIN {             objectIdentifier        }         MAY CONTAIN {             commonName,             matchtype,             description,             obsolete        }        ::= {schemaObjectClass.4}objectIdentifier ATTRIBUTE       WITH ATTRIBUTE-SYNTAX            objectIdentifierSyntax       ::= {schemaAttribute.1}mandatoryNamingAttributes ATTRIBUTE       WITH ATTRIBUTE-SYNTAX            SET OF OBJECT IDENTIFIER       ::= {schemaAttribute.2}mandatoryAttributes ATTRIBUTE       WITH ATTRIBUTE-SYNTAX            SET OF OBJECT IDENTIFIER       ::= {schemaAttribute.3}optionalNamingAttibutes ATTRIBUTE       WITH ATTRIBUTE-SYNTAX            SET OF OBJECT IDENTIFIER       ::= {schemaAttribute.4}optionalAttibutes ATTRIBUTE       WITH ATTRIBUTE-SYNTAX            SET OF OBJECT IDENTIFIER       ::= {schemaAttribute.5}Mansfield, et al              Experimental                      [Page 7]RFC 1804          Schema Publishing in X.500 Directory         June 1995obsolete ATTRIBUTE       WITH ATTRIBUTE-SYNTAX            BOOLEAN                           -- DEFAULT FALSE       ::= {schemaAttribute.6}subClassOf      ATTRIBUTE        WITH ATTRIBUTE-SYNTAX                SET OF OBJECT IDENTIFIER       ::= {schemaAttribute.7}constraint ATTRIBUTE       WITH ATTRIBUTE-SYNTAX            Constraint       ::= {schemaAttribute.8}Constraint ::=Choice {             StringConstraint,             IntegerConstraint        }StringConstraint ::= SEQUENCE {             shortest INTEGER,             longest  INTEGER        }IntegerConstraint ::= SEQUENCE {             lowerbound INTEGER,             upperbound INTEGER OPTIONAL        }attributeSyntax ATTRIBUTE       WITH ATTRIBUTE-SYNTAX              ASN1DataType       ::= {schemaAttribute.9}multivalued ATTRIBUTE       WITH ATTRIBUTE-SYNTAX            BOOLEAN             -- DEFAULT FALSE       ::= {schemaAttribute.10}matchRules ATTRIBUTE       WITH ATTRIBUTE-SYNTAX            SET OF OBJECT IDENTIFIER       ::= {schemaAttribute.11}matchtype ATTRIBUTE       WITH ATTRIBUTE-SYNTAXMansfield, et al              Experimental                      [Page 8]RFC 1804          Schema Publishing in X.500 Directory         June 1995            INTEGER {             PRESENT                    (0),             EQUALITY                   (1),             ORDERING                   (2),             CASESENSITIVEMATCH         (3),             CASEINSENSITIVEMATCH       (4)            }       ::= {schemaAttribute.12}6. References   [1] CCITT. "Data Communication Networks: Directory", Recommendations       X.500 - X.521 1988.   [2] CCITT. "Data Communication Networks: Directory", Recommendations       X.500 - X.525 1993.   [3] Barker, P., and S. Kille, "The COSINE and Internet X.500 Schema",       RFC 1274, University College London, November 1991.   [4] Howes, T., "Schema Information in the X.500 Directory", Work in       Progress, University of Michigan, July 1992.   [5] Howes, T., Rossen, K., Sataluri, S., and R. Wright, "Procedures       for Formalization, Evolution, and Maintenance of the Internet       X.500 Directory Schema", Work in Progress, June 1995.7. Security Considerations   Security issues are not discussed in this memo.Mansfield, et al              Experimental                      [Page 9]RFC 1804          Schema Publishing in X.500 Directory         June 19958. Authors' Addresses   Glenn Mansfield   AIC Systems Laboratories,   6-6-3, Minami Yoshinari, Aoba-Ku, Sendai,   Japan   Phone: +81 (22) 279-3310   Fax: +81 (22) 279-3640   EMail: glenn@aic.co.jp   P. V. Rajeev   Hughes Software Systems,   2nd Floor, International Trade Tower,   Nehru Place, New Delhi,   India   EMail: rajeev%hss@lando.hns.com   S. V. Raghavan   Department of Computer Science and Engineering,   Indian Institute of Technology, Madras 600 036,   India   EMail: svr@iitm.ernet.in   Tim Howes   University of Michigan   ITD Research Systems   535 W William St.   Ann Arbor, MI 48103-4943, USA   Phone: +1 (313) 747-4454   EMail: tim@umich.eduMansfield, et al              Experimental                     [Page 10]

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -