idnits 2.17.00 (12 Aug 2021) /tmp/idnits11515/draft-legg-ldap-cmr-module-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 86: '...nentReference (SIZE(1..MAX)) OPTIONAL,...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (January 7, 2004) is 6708 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '0' on line 94 -- Looks like a reference, but probably isn't: '1' on line 95 -- Looks like a reference, but probably isn't: '2' on line 96 -- Looks like a reference, but probably isn't: '3' on line 97 -- No information found for draft-legg-ldapext-component-matching-xx - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'CMR' -- Possible downref: Non-RFC (?) normative reference: ref. 'X501' -- Possible downref: Non-RFC (?) normative reference: ref. 'ASN1' -- Obsolete informational reference (is this intentional?): RFC 3377 (ref. 'LDAP') (Obsoleted by RFC 4510) Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 11 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT S. Legg 3 draft-legg-ldap-cmr-module-00.txt Adacel Technologies 4 Intended Category: Standards Track January 7, 2004 5 Updates: draft-legg-ldapext-component-matching-00.txt 7 ASN.1 Module Definition for the 8 LDAP & X.500 Component Matching Rules 10 Copyright (C) The Internet Society (2004). All Rights Reserved. 12 Status of this Memo 14 This document is an Internet-Draft and is in full conformance with 15 all provisions of Section 10 of RFC2026. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as 20 Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress". 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 Distribution of this document is unlimited. Comments should be sent 34 to the LDAPEXT working group mailing list 35 or to the author. 37 This Internet-Draft expires on 7 July 2004. 39 Abstract 41 This document updates the specification of the component matching 42 rules for Lightweight Directory Access Protocol (LDAP) and X.500 43 directories (draft-legg-ldapext-component-matching-xx.txt) by 44 collecting the Abstract Syntax Notation One (ASN.1) definitions of 45 the component matching rules into an appropriately identified ASN.1 46 module so that other specifications may reference the component 47 matching rule definitions from within their own ASN.1 modules. 49 1. Introduction 51 The structure or data type of data held in an attribute of a 52 Lightweight Directory Access Protocol (LDAP) [LDAP] or X.500 [X500] 53 directory is described by the attribute's syntax. Attribute syntaxes 54 range from simple data types, such as text string, integer, or 55 boolean, to complex data types, for example, the syntaxes of the 56 directory schema operational attributes. RFC XXXX [CMR] defines a 57 generic way of matching user selected components in a directory 58 attribute value of any arbitrarily complex attribute syntax. 60 This document updates RFC XXXX by collecting the Abstract Syntax 61 Notation One (ASN.1) [ASN1] definitions of RFC XXXX into an 62 appropriately identified ASN.1 module so that other specifications 63 may reference these definitions from within their own ASN.1 modules. 65 2. Module Definition for Component Matching 67 ComponentMatching 68 {iso(1) 2 36 79672281 xed(3) module(0) component-matching(4)} 70 -- Copyright (C) The Internet Society (2004). This version of 71 -- this ASN.1 module is part of RFC YYYY; see the RFC itself 72 -- for full legal notices. 74 DEFINITIONS 75 EXPLICIT TAGS 76 EXTENSIBILITY IMPLIED ::= BEGIN 78 IMPORTS 79 MATCHING-RULE, 80 RelativeDistinguishedName 81 FROM InformationFramework 82 {joint-iso-itu-t ds(5) module(1) 83 informationFramework(1) 4} ; 85 ComponentAssertion ::= SEQUENCE { 86 component ComponentReference (SIZE(1..MAX)) OPTIONAL, 87 useDefaultValues BOOLEAN DEFAULT TRUE, 88 rule MATCHING-RULE.&id, 89 value MATCHING-RULE.&AssertionType } 91 ComponentReference ::= UTF8String 93 ComponentFilter ::= CHOICE { 94 item [0] ComponentAssertion, 95 and [1] SEQUENCE OF ComponentFilter, 96 or [2] SEQUENCE OF ComponentFilter, 97 not [3] ComponentFilter } 99 componentFilterMatch MATCHING-RULE ::= { 100 SYNTAX ComponentFilter 101 ID { 1 2 36 79672281 1 13 2 } } 103 allComponentsMatch MATCHING-RULE ::= { 104 ID { 1 2 36 79672281 1 13 6 } } 106 directoryComponentsMatch MATCHING-RULE ::= { 107 ID { 1 2 36 79672281 1 13 7 } } 109 -- Additional Useful Matching Rules -- 111 rdnMatch MATCHING-RULE ::= { 112 SYNTAX RelativeDistinguishedName 113 ID { 1 2 36 79672281 1 13 3 } } 115 presentMatch MATCHING-RULE ::= { 116 SYNTAX NULL 117 ID { 1 2 36 79672281 1 13 5 } } 119 END 121 The InformationFramework ASN.1 module from which the MATCHING-RULE 122 and RelativeDistinguishedName definitions are imported is defined in 123 X.501 [X501]. 125 The object identifiers used in this document have been assigned for 126 use in specifying the component matching rules by Adacel 127 Technologies, under an arc assigned to Adacel by Standards Australia. 129 3. Security Considerations 131 This document collects together the ASN.1 definitions of the 132 component matching rules into an ASN.1 module, but does not modify 133 those definitions in any way. See RFC XXXX [CMR] for the security 134 considerations of using the component matching rules. 136 4. References 138 4.1. Normative References 140 [CMR] Legg, S., "LDAP & X.500 Component Matching Rules", 141 draft-legg-ldapext-component-matching-xx.txt, April 2003. 143 [X501] ITU-T Recommendation X.501 (1993) | ISO/IEC 9594-2:1994, 144 Information Technology - Open Systems Interconnection - The 145 Directory: Models 147 [ASN1] ITU-T Recommendation X.680 (07/02) | ISO/IEC 8824-1:2002, 148 Information technology - Abstract Syntax Notation One 149 (ASN.1): Specification of basic notation 151 4.2. Informative References 153 [LDAP] Hodges, J. and R. Morgan, "Lightweight Directory Access 154 Protocol (v3): Technical Specification", RFC 3377, September 155 2002. 157 [X500] ITU-T Recommendation X.500 (1993) | ISO/IEC 9594-1:1994, 158 Information Technology - Open Systems Interconnection - The 159 Directory: Overview of concepts, models and services 161 5. Intellectual Property Notice 163 The IETF takes no position regarding the validity or scope of any 164 intellectual property or other rights that might be claimed to 165 pertain to the implementation or use of the technology described in 166 this document or the extent to which any license under such rights 167 might or might not be available; neither does it represent that it 168 has made any effort to identify any such rights. Information on the 169 IETF's procedures with respect to rights in standards-track and 170 standards-related documentation can be found in BCP-11. Copies of 171 claims of rights made available for publication and any assurances of 172 licenses to be made available, or the result of an attempt made to 173 obtain a general license or permission for the use of such 174 proprietary rights by implementors or users of this specification can 175 be obtained from the IETF Secretariat. 177 The IETF invites any interested party to bring to its attention any 178 copyrights, patents or patent applications, or other proprietary 179 rights which may cover technology that may be required to practice 180 this standard. Please address the information to the IETF Executive 181 Director. 183 6. Author's Address 185 Steven Legg 186 Adacel Technologies Ltd. 187 250 Bay Street 188 Brighton, Victoria 3186 189 AUSTRALIA 190 Phone: +61 3 8530 7710 191 Fax: +61 3 8530 7888 192 EMail: steven.legg@adacel.com.au 194 7. Full Copyright Statement 196 Copyright (C) The Internet Society (2004). All Rights Reserved. 198 This document and translations of it may be copied and furnished to 199 others, and derivative works that comment on or otherwise explain it 200 or assist in its implementation may be prepared, copied, published 201 and distributed, in whole or in part, without restriction of any 202 kind, provided that the above copyright notice and this paragraph are 203 included on all such copies and derivative works. However, this 204 document itself may not be modified in any way, such as by removing 205 the copyright notice or references to the Internet Society or other 206 Internet organizations, except as needed for the purpose of 207 developing Internet standards in which case the procedures for 208 copyrights defined in the Internet Standards process must be 209 followed, or as required to translate it into languages other than 210 English. 212 The limited permissions granted above are perpetual and will not be 213 revoked by the Internet Society or its successors or assignees. 215 This document and the information contained herein is provided on an 216 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 217 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 218 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 219 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 220 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.