idnits 2.17.1 draft-ietf-asid-x500-url-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** 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 abstract seems to contain references ([2], [3], [4], [2,3], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 (8 November 1994) is 10762 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) -- Missing reference section? '1' on line 110 looks like a reference -- Missing reference section? '2' on line 115 looks like a reference -- Missing reference section? '3' on line 118 looks like a reference -- Missing reference section? '4' on line 122 looks like a reference Summary: 9 errors (**), 0 flaws (~~), 1 warning (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 X.500 labeledURL Attribute Type Mark Smith 2 INTERNET-DRAFT University of Michigan 3 8 November 1994 5 Definition of an X.500 Attribute Type and Object Class to 6 Hold Uniform Resource Locators (URLs) 7 Filename: draft-ietf-asid-x500-url-00.txt 9 Status of this Memo 11 This document is an Internet-Draft. Internet-Drafts are working 12 documents of the Internet Engineering Task Force (IETF), its 13 areas, and its working groups. Note that other groups may also 14 distribute working documents as Internet-Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six 17 months and may be updated, replaced, or obsoleted by other 18 documents at any time. It is inappropriate to use Internet- 19 Drafts as reference material or to cite them other than as 20 ``work in progress.'' 22 To learn the current status of any Internet-Draft, please check 23 the ``1id-abstracts.txt'' listing contained in the Internet- 24 Drafts Shadow Directories on ds.internic.net (US East Coast), 25 nic.nordu.net (Europe), ftp.isi.edu (US West Coast), or 26 munnari.oz.au (Pacific Rim). 28 Distribution of this memo is unlimited. Editorial comments should be 29 sent to the author (mcs@umich.edu). Technical discussion will take 30 place on the IETF ASID mailing list (ietf-asid@umich.edu). 32 This Internet Draft expires May 12th, 1995. 34 Abstract 36 Uniform Resource Locators (URLs) as defined by [1] are being widely 37 used to specify the location of Internet resources. There is an 38 urgent need to be able to include URLs in the X.500 [2,3] Directory. 39 A number of independent groups are already experimenting with the 40 inclusion of URLs in the X.500 Directory through the use of existing 41 or newly defined attribute types. This document builds on the 42 experimentation to date and defines a new attribute type and an 43 auxiliary object class to allow URLs to be included in X.500 44 Directory entries in a standard way. It is intended that the schema 45 elements defined in this document will be progressed according to the 46 process defined by the Internet X.500 Schema Working Group [4]. 48 Schema Definition of labeledURL Attribute Type 50 Name: labeledURL 51 ShortName: 52 Description: Uniform Resource Locator with optional label 53 OID: umichAttributeType.41 (1.3.6.1.4.1.250.1.41) 54 Syntax: caseExactString 55 SizeRestriction: None 56 SingleValued: False 58 Discussion of the labeledURL Attribute Type 60 The labeledURL attribute type has the caseExactString syntax (since 61 URLs are case-sensitive) and it is multivalued. Values placed in the 62 attribute should consist of a URL, optionally followed by one or more 63 space characters and a label. Since space characters are not allowed 64 to appear un-encoded in URLs, there is no ambiguity about where the 65 label begins. The URL portion must comply with the URL specification 66 [1]. Multiple labeledURL values will generally indicate different 67 resources that are all related to the X.500 object, but may indicate 68 different locations for the same resource. 70 The label is used to describe the resource to which the URL points, 71 and is intended as a friendly name fit for human consumption. This 72 document does not propose any specific syntax for the label part. 73 Note that in some cases it may be helpful to include in the label 74 some indication of the kind and/or size of the resource referenced by 75 the URL. 77 Note that the label may include any characters allowed by the 78 caseExactString syntax, but that the use of non-IA5 (non-ASCII) 79 characters is discouraged as not all directory clients may handle 80 them in the same manner. 82 Some examples of valid labeledURL values (the first does not have a 83 label): 85 ftp://ds.internic.net/rfc/rfc1588.txt 87 http://www.umich.edu/ University of Michigan Home Page 89 http://champagne.inria.fr/Unites/rennes.gif Rennes [photo] 91 Schema Definition of labeledURLObject Object Class 93 Name: labeledURLObject 94 Description: object that contains the labeledURL attribute type 95 OID: umichObjectClass.14 (1.3.6.1.4.1.250.3.14) 96 SubclassOf: top 97 MustContain: 98 MayContain: labeledURL 100 Discussion of the labeledURLObject Object Class 102 The labeledURLObject class is a subclass of top and may contain the 103 labeledURL attribute. The intent is that this object class can be 104 added to existing objects to allow for inclusion of labeledURL 105 values. This approach does not preclude including the labeledURL 106 attribute type directly in other object classes as appropriate. 108 References 110 [1] Berners-Lee, T., Masinter, L., and McCahill, M., "Uniform 111 Resource Locators (URL)", Internet Draft (Work In Progress) of the 112 IETF URI Working Group, 115 [2] The Directory: Overview of Concepts, Models and Service. CCITT 116 Recommendation X.500, 1988. 118 [3] Information Processing Systems -- Open Systems Interconnection -- 119 The Directory: Overview of Concepts, Models and Service. ISO/IEC JTC 120 1/SC21; International Standard 9594-1, 1988. 122 [4] Howes, T., Rossen, K., Sataluri, S., and Wright, R., "Procedures 123 for Formalizing, Evolving, and Maintaining the Internet X.500 124 Directory Schema", Internet Draft (Work In Progress) of the Schema 125 Working Group, 128 Security Considerations 130 Security considerations are not discussed in this memo. 132 Acknowledgments 134 Paul-Andre Pays, Martijn Koster, Tim Howes, Rakesh Patel, and Russ 135 Wright provided invaluable assistance in the creation of this 136 document. 138 Author's Address 140 Mark Smith 141 University of Michigan 142 Information Technology Division 143 535 W. William St. 144 Ann Arbor, MI 48103-4943, USA 146 Phone: +1 313 764-2277 147 Fax: +1 313 765-5140 148 EMail: mcs@umich.edu 150 This Internet Draft expires May 12th, 1995.