idnits 2.17.1 draft-ietf-schema-whois-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-25) 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 == The page length should not exceed 58 lines per page, but there was 2 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 3 pages 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.) ** There are 2 instances of too long lines in the document, the longest one being 12 characters in excess of 72. ** The abstract seems to contain references ([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 (April 1998) is 9507 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 118 looks like a reference -- Missing reference section? '2' on line 121 looks like a reference -- Missing reference section? '3' on line 124 looks like a reference Summary: 9 errors (**), 0 flaws (~~), 3 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet-Draft Ryan Moats 3 draft-ietf-schema-whois-00.txt AT&T 4 Expires in six months April 1998 6 A MIME Content-Type for WHOIS 7 Filename: draft-ietf-schema-whois-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 ``work 20 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 ftp.is.co.za (Africa), nic.nordu.net 25 (Europe), munnari.oz.au (Pacific Rim), ftp.ietf.org (US East 26 Coast), or ftp.isi.edu (US West Coast). 28 Abstract 30 This document defines a MIME directory profile [1] for holding a 31 WHOIS [2] schema and is intended for communication with the Internet 32 schema listing service. 34 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 35 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 36 document are to be interpreted as described in RFC 2119 [3]. 38 1. Overview 40 The document defines how a MIME type may be used to transfer a single 41 WHOIS schema definition. Although [2] specifies the result as non- 42 machine readable it should be realized that the returned object is 43 simply text. Schemas created from this specify the parsing of the 44 text. Therefore an example of how a to register a WHOIS schema is 45 presented. 47 2. Example MIME Directory Type Registrations 49 This document defines an example whoisSchema used in the "schema- 50 whois-example-0" profile. 52 2.1 whoisSchema 54 To: ietf-mime-direct@imc.org 55 Subject: Registration of text/directory MIME type whoisSchema 57 Type name: whoisSchema 59 Type purpose: To represent an example WHOIS schema 61 Type encoding: 8bit 63 Type valuetype: text, encoded according to the BNF of section 2.1.1 65 Type special notes: Each value of this type specifies the contents of 66 a WHOIS schema definition. A definition of all attributes in the schema 67 MUST be present in the content containing this value. 69 Intended usage: COMMON 71 2.1.1 whoisSchema Syntax Definition 73 Values of whoisSchema are represented according to the following BNF: 75 whoisSchema = "(" whsp attribute-line *[whsp "$" whsp attribute-line] whsp ")" 76 attribute-line = *[ "line:" whsp attr *[whsp "$" whsp attr] 77 attr = 1*utf8 79 All attributes have text values. It should be noted that this 80 definition is not intended to handle all formatting circumstances nor 81 is intended for complete machine parsing. 83 3.0 Example 85 From: whomever@wherever.com 86 To: Someone@somewhere.com 87 Subject: schema information 88 MIME-Version: 1.0 89 Message-Id: 90 Content-Type: text/directory; profile="schema-whois-0";charset="utf-8" 91 Content-Transfer-Encoding: Quoted-Printable 92 whoisSchema: ( line: Lastname $ Firstname $ Handle $ Email $ 93 line: Address1 $ line: Address2 $ line: City $ State $ Zip $ 94 line: Phones $ line: null $ line: Record-Last-Updated $ 95 line: Database-Last-Updated $ line: Announcements ) 97 4. Security Considerations 99 A MIME body part containing a text/directory may be incorporated in a 100 digitally signed MIME content, which can be used to verify that the 101 body part has not been modified in transit. When the signer has been 102 certified by a trusted third party service, it may also be possible 103 to verify the origin of the content. 105 5. Acknowledgments 107 Thanks to various members of the SCHEMA Working Group for comments on 108 earlier drafts of this document. The work described in this document 109 is partially supported by the National Science Foundation, 110 Cooperative Agreement NCR-9218179. 112 6. Refernces 114 Request For Comments (RFC) are available from ftp://venera.isi.edu, 115 Internet Draft documents are available from ftp://ftp.ietf.org, and 116 both are available from numerous mirror sites. 118 [1] M. Wahl, "A MIME Content-Type for Directory Information," 119 Internet Draft (work in progress), March 8, 1998. 121 [2] K. Harrenstien, M.K. Stahl, E.J. Feinler, "NICNAME/WHOIS," 122 RFC 954, October 1985. 124 [3] S. Bradner, "Key words for use in RFCs to Indicate Require- 125 ment Levels," RFC 2119, March 1997. 127 7. Author's Address 129 Ryan Moats 130 AT&T 131 15621 Drexel Circle 132 Omaha, NE 68135-2358 133 USA 135 Email: jayhawk@att.com