idnits 2.17.1 draft-daigle-wppquery-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 == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 257 lines 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 document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 7 instances of lines with control characters in the document. ** The abstract seems to contain references ([RFC2046], [RFC1835]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The "Author's Address" (or "Authors' Addresses") section title is misspelled. -- 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 (March 1998) is 9539 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) == Unused Reference: 'ALVE95' is defined on line 183, but no explicit reference was found in the text == Unused Reference: 'HARR85' is defined on line 198, but no explicit reference was found in the text == Unused Reference: 'POST82' is defined on line 201, but no explicit reference was found in the text == Unused Reference: 'IIIR' is defined on line 205, but no explicit reference was found in the text == Unused Reference: 'WINDX' is defined on line 209, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1766 (ref. 'ALVE95') (Obsoleted by RFC 3066, RFC 3282) ** Obsolete normative reference: RFC 2234 (Obsoleted by RFC 4234) ** Downref: Normative reference to an Historic RFC: RFC 1835 ** Obsolete normative reference: RFC 954 (ref. 'HARR85') (Obsoleted by RFC 3912) ** Obsolete normative reference: RFC 821 (ref. 'POST82') (Obsoleted by RFC 2821) ** Downref: Normative reference to an Informational RFC: RFC 1727 (ref. 'IIIR') ** Downref: Normative reference to an Historic RFC: RFC 1913 (ref. 'WINDX') ** Obsolete normative reference: RFC 2279 (Obsoleted by RFC 3629) Summary: 19 errors (**), 0 flaws (~~), 8 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet-Draft Leslie L. Daigle 3 Expires: September 11, 1998 Bunyip Information Systems Inc. 4 draft-daigle-wppquery-00.txt Patrik Faltstrom 5 Tele2/Swipnet 6 March 1998 8 The application/whoispp-query Content-Type 10 Status of this Memo 12 This document is an Internet-Draft. Internet-Drafts are working 13 documents of the Internet Engineering Task Force (IETF), its 14 areas, and its working groups. Note that other groups may also 15 distribute working documents as Internet-Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six 18 months and may be updated, replaced, or obsoleted by other docu- 19 ments at any time. It is inappropriate to use Internet-Drafts as 20 reference material or to cite them other than as ``work in 21 progress.'' 23 To learn the current status of any Internet-Draft, please check 24 the ``1id-abstracts.txt'' listing contained in the Internet- 25 Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net 26 (Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East 27 Coast), or ftp.isi.edu (US West Coast). 29 Distribution of this document is unlimited. 31 Abstract 33 This document defines the expression of Whois++ protocol (originally 34 defined in [RFC1835] and updated in 35 [draft-ietf-asid-whoispp-02.txt])queries within MIME [RFC2046] 36 media types. The intention of this document, in conjunction with 37 [draft-daigle-wppquery-00.txt] is to enable MIME-enabled mail 38 software, and other systems using Internet media types, to carry 39 out Whois++ transactions. 41 1. MIME Registration Information 43 To: iana@isi.edu 44 Subject: Registration of MIME media type application/whoispp-query 46 MIME Type name: Application 48 MIME subtype name: whoispp-query 50 Required parameters: none 52 Optional parameters: none 54 Encoding considerations: Any valid MIME encodings may be used 56 Security considerations: This content-type contains purely descriptive 57 information (i.e., no directives). There are security considerations 58 with regards to the appropriateness (privacy) of information provided 59 through the use of this content-type, and the authenticity of the 60 information so-provided. This content-type provides no native 61 mechanisms for authentication. 63 Published specification: this document 65 Person & email address to contact for further information: 67 Leslie L. Daigle 68 leslie@bunyip.com 70 Intended usage: common 72 2. whoispp-query Syntax 74 The following grammar, which uses BNF-like notation as defined in 75 [RFC2234] defines the set of acceptable input to a Whois++ server. 76 As such, it describes the expected structure of a whoispp-query media 77 type object. 79 N.B.: As outlined in the ABNF definition, rule names and string 80 literals are in the US-ASCII character set, and are case-insensitive. 82 whois-command = ( system-command [":" "hold"] 83 / terms [":" globalcnstrnts] ) nl 85 system-command = "constraints" 86 / "describe" 87 / "commands" 88 / "polled-by" 89 / "polled-for" 90 / "version" 91 / "list" 92 / "show" [1*sp bytestring] 93 / "help" [1*sp bytestring] 94 / "?" [bytestring] 96 terms = and-expr *("or" and-expr) 98 and-expr = not-expr *("and" not-expr) 100 not-expr = ["not"] (term / ( "(" terms ")" )) 102 term = generalterm / specificterm 103 / combinedterm 105 generalterm = bytestring 107 specificterm = specificname "=" bytestring 109 specificname = "handle" / "value" 111 combinedterm = attributename "=" bytestring 113 globalcnstrnts = globalcnstrnt *(";" globalcnstrnt) 115 globalcnstrnt = "format" "=" format 116 / "maxfull" "=" 1*digit 117 / "maxhits" "=" 1*digit 118 / opt-globalcnst 120 opt-globalcnst = "authenticate" "=" auth-method 121 / "language" "=" language 122 / "incharset" "=" characterset 123 / "ignore" "=" bytestring 124 / "include" "=" bytestring 126 format = "full" / "abridged" / "handle" / "summary" 127 / "server-to-ask" 129 auth-method = bytestring 131 language = 133 characterset = "us-ascii" / "iso-8859-1" / "iso-8859-2" / 134 "iso-8859-3" / "iso-8859-4" / "iso-8859-5" / 135 "iso-8859-6" / "iso-8859-7" / "iso-8859-8" / 136 "iso-8859-9" / "iso-8859-10" / 137 "UNICODE-1-1-UTF-8" / "UNICODE-2-0-UTF-8" 138 "UTF-8" 139 ;"UTF-8" is as defined in [RFC2279]. This is 140 ;the character set label that should be used 141 ;for UTF encoded information; the labels 142 ;"UNICODE-2-0-UTF-8" and "UNICODE-1-1-UTF-8" 143 ;are retained primarily for compatibility with 144 ;older Whois++ servers (and as outlined in 145 ;[RFC2279]). 147 searchvalue = "exact" / "substring" / "regex" / "fuzzy" 148 / "lstring" 150 casevalue = "ignore" / "consider" 152 bytestring = 0*charbyte 154 attributename = 1*attrbyte 156 charbyte = "\" specialbyte / normalbyte 158 normalbyte = <%d33-255, except specialbyte> 160 attrbyte = <%d33-127 except specialbyte> / 161 "\" 163 specialbyte = " " / tab / "=" / "," / ":" / ";" / "\" / 164 "*" / "." / "(" / ")" / "[" / "]" / "^" / 165 "$" / "!" / "?" 167 tab = %d09 168 sp = %d32 ; space 170 digit = "0" / "1" / "2" / "3" / "4" / 171 "5" / "6" / "7" / "8" / "9" 173 nl = %d13 %d10 ; CR LF 175 NOTE: Blanks that are significant to a query must be escaped. The 176 following characters, when significant to the query, may be preceded 177 and/or followed by a single blank: 179 : ; , ( ) = ! 181 3. References 183 [ALVE95] Alvestrand H., "Tags for the Identification of 184 Languages", RFC 1766, UNINETT, March 1995. 186 [RFC2234] Crocker, D., and P. Overell, "Augmented BNF for 187 Syntax Specifications: ABNF", RFC 2234, November 188 1997. 190 [RFC1835] Deutsch, P., R. Schoultz, P. Faltstrom and C. 191 Weider. "Architecture of the WHOIS++ service", 192 RFC 1835. August 1995. 194 [RFC2046] Freed, N., and N. Borenstein, "Multipurpose Internet 195 Mail Extensions (MIME) Part Two: Media Types", 196 RFC 2046, November 1996. 198 [HARR85] Harrenstein K., Stahl M., and E. Feinler, 199 "NICNAME/WHOIS", RFC 954, SRI, October 1985. 201 [POST82] Postel J., "Simple Mail Transfer Protocol", STD 10, 202 RFC 821, USC/Information Sciences Institute, 203 August 1982. 205 [IIIR] Weider C., and P. Deutsch, "A Vision of an 206 Integrated Internet Information Service", RFC 1727 207 Bunyip Information Systems, Inc., December 1994. 209 [WINDX] Weider, C., J. Fullton, and S. Spero, "Architecture 210 of the Whois++ Index Service", RFC 1913, February 211 1996. 212 [RFC2279] F. Yergeau, " UTF-8, a transformation format of ISO 213 10646", RFC 2279, January 1998. 215 4. Authors Addresses 217 Leslie L. Daigle 218 Bunyip Information Systems Inc. 219 310 Ste. Catherine St. W 220 Suite 300 221 Montreal, Quebec, CANADA 222 H2X 2A1 224 Email: leslie@bunyip.com 226 Patrik Faltstrom 227 Tele2 228 Borgarfjordsgatan 16 229 BOX 62 230 194 64 Kista 231 SWEDEN 233 Email: paf@swip.net