1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
|
Network Working Group L. Daigle
Request for Comments: 2957 Thinking Cat Enterprises
Category: Informational P. Faltstrom
Cisco Systems Inc.
October 2000
The application/whoispp-query Content-Type
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2000). All Rights Reserved.
Abstract
This document defines the expression of Whois++ protocol (RFC 1835)
queries within MIME (Multipurpose Internet Mail Extensions) (RFC
2046) media types. The intention of this document, in conjunction
with RFC 2958 is to enable MIME-enabled mail software, and other
systems using Internet media types, to carry out Whois++
transactions.
1. MIME Registration Information
To: iana@isi.edu
Subject: Registration of MIME media type application/whoispp-query
MIME Type name: Application
MIME subtype name: whoispp-query
Required parameters: none
Optional parameters: none
Encoding considerations: Any valid MIME encodings may be used
Security considerations: This content-type contains purely
descriptive information (i.e., no directives). There are security
considerations with regards to the appropriateness (privacy) of
information provided through the use of this content-type, and the
authenticity of the information so-provided. This content-type
Daigle & Faltstrom Informational [Page 1]
^L
RFC 2957 application/whoispp-query Content-Type October 2000
provides no native mechanisms for authentication.
Published specification: this document
Person & email address to contact for further information:
Leslie L. Daigle
leslie@thinkingcat.com
Intended usage: common
2. whoispp-query Syntax
The following grammar, which uses BNF-like notation as defined in
[RFC2234] defines the set of acceptable input to a Whois++ server.
As such, it describes the expected structure of a whoispp-query media
type object.
N.B.: As outlined in the ABNF definition, rule names and string
literals are in the US-ASCII character set, and are case-insensitive.
whois-command = ( system-command / terms [":" globalcnstrnts] )
nl
system-command = "constraints" / "describe" / "commands" /
"polled-by" / "polled-for" / "version" / "list" /
"show" [1*sp bytestring] / "help" [1*sp
bytestring] / "?" [bytestring]
terms = and-expr *("or" and-expr)
and-expr = not-expr *("and" not-expr)
not-expr = ["not"] (term / ( "(" terms ")" ))
term = ( generalterm / specificterm / combinedterm )
localcnstrnts
generalterm = bytestring
specificterm = specificname "=" bytestring
specificname = "handle" / "value" / "template"
combinedterm = attributename "=" bytestring
globalcnstrnts = globalcnstrnt *(";" globalcnstrnt)
Daigle & Faltstrom Informational [Page 2]
^L
RFC 2957 application/whoispp-query Content-Type October 2000
globalcnstrnt = "format" "=" format / "maxfull" "=" 1*digit /
"maxhits" "=" 1*digit / "case" "=" casevalue /
"search" "=" searchvalue / opt-globalcnst
opt-globalcnst = "authenticate" "=" auth-method / "language" "="
language / "incharset" "=" characterset /
"outcharset" "=" characterset / "ignore" "="
attriblist / "include" "=" attriblist
localcnstrnts = 0*(";" localcnstrnt)
localcnstrnt = "case" "=" casevalue / "search" "=" searchvalue
format = "full" / "abridged" / "handle" / "summary" /
"server-to-ask"
auth-method = bytestring
language = <The language code defined in RFC1766 [ALVE95]>
characterset = "us-ascii" / "iso-8859-1" / "iso-8859-2" / "iso-
8859-3" / "iso-8859-4" / "iso-8859-5" / "iso-
8859-6" / "iso-8859-7" / "iso-8859-8" / "iso-
8859-9" / "iso-8859-10" / "UNICODE-1-1-UTF-8" /
"UNICODE-2-0-UTF-8" "UTF-8"
;"UTF-8" is as defined in [RFC2279]. This is
;the character set label that should be used
;for UTF encoded information; the labels
;"UNICODE-2-0-UTF-8" and "UNICODE-1-1-UTF-8"
;are retained primarily for compatibility with
;older Whois++ servers (and as outlined in
;[RFC2279]).
searchvalue = "exact" / "substring" / "regex" / "fuzzy" /
"lstring"
casevalue = "ignore" / "consider"
bytestring = 0*charbyte
attributename = 1*attrbyte
attriblist = attributename 0*("," attributename)
charbyte = "\" specialbyte / normalbyte
normalbyte = <%d33-255, except specialbyte>
Daigle & Faltstrom Informational [Page 3]
^L
RFC 2957 application/whoispp-query Content-Type October 2000
attrbyte = <%d33-127 except specialbyte> /
"\" <specialbyte except
":" " " tab nl>
specialbyte = " " / tab / "=" / "," / ":" / ";" / "\" /
"*" / "." / "(" / ")" /
"[" / "]" / "^" /
"$" / "!" / "?"
tab = %d09
sp = %d32 ; space
digit = "0" / "1" / "2" / "3" / "4" /
"5" / "6" / "7" / "8" /
"9"
nl = %d13 %d10 ; CR LF
NOTE: Blanks that are significant to a query must be escaped. The
following characters, when significant to the query, may be preceded
and/or followed by a single blank:
: ; , ( ) = !
3. Security Considerations
Security issues are discussed in section 1.
4. References
[ALVE95] Alvestrand H., "Tags for the Identification of Languages",
RFC 1766, March 1995.
[RFC2234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997.
[RFC2958] Daigle, L. and P. Faltstrom, "The application/whoispp-
response Content-type", RFC 2958, October 2000.
[RFC1835] Deutsch, P., Schoultz, R., Faltstrom, P. and C. Weider,
"Architecture of the WHOIS++ service", RFC 1835, August
1995.
[RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part Two: Media Types", RFC 2046,
November 1996.
Daigle & Faltstrom Informational [Page 4]
^L
RFC 2957 application/whoispp-query Content-Type October 2000
[HARR85] Harrenstein K., Stahl M. and E. Feinler, "NICNAME/WHOIS",
RFC 954, October 1985.
[POST82] Postel J., "Simple Mail Transfer Protocol", STD 10, RFC
821, August 1982.
[IIIR] Weider C. and P. Deutsch, "A Vision of an Integrated
Internet Information Service", RFC 1727, December 1994.
[WINDX] Weider, C., Fullton, J. and S. Spero, "Architecture of the
Whois++ Index Service", RFC 1913, February 1996.
[RFC2279] Yergeau F., " UTF-8, a transformation format of ISO 10646",
RFC 2279, January 1998.
5. Authors' Addresses
Leslie L. Daigle
Thinking Cat Enterprises
Email: leslie@thinkingcat.com
Patrik Faltstrom
Cisco Systems Inc
170 W Tasman Drive SJ-13/2
San Jose CA 95134
USA
EMail: paf@cisco.com
URL: http://www.cisco.com
Daigle & Faltstrom Informational [Page 5]
^L
RFC 2957 application/whoispp-query Content-Type October 2000
6. Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Daigle & Faltstrom Informational [Page 6]
^L
|
