RFC relevance of copyright

As per Relevance of the word copyright, we have this rfc below:

Network Working Group L.
Request for Comments: 2957 Thinking Cat
Category: Informational P.
Cisco Systems Inc
October 2000

The application/whoispp-query Content-

Status of this

This memo provides information for the Internet community. It
not specify an Internet standard of any kind. Distribution of
memo is unlimited

Copyright

Copyright (C) The Internet Society (2000). All Rights Reserved

This document defines the expression of Whois++ protocol (RFC 1835)
queries within MIME (Multipurpose Internet Mail Extensions) (
2046) media types. The intention of this document, in
with RFC 2958 is to enable MIME-enabled mail software, and
systems using Internet media types, to carry out Whois++
transactions

1. MIME Registration

To: iana@isi.
Subject: Registration of MIME media type application/whoispp-

MIME Type name:

MIME subtype name: whoispp-

Required parameters:

Optional parameters:

Encoding considerations: Any valid MIME encodings may be

Security considerations: This content-type contains
descriptive information (i.e., no directives). There are
considerations with regards to the appropriateness (privacy)
information provided through the use of this content-type, and
authenticity of the information so-provided. This content-

Daigle & Faltstrom Informational [Page 1]

RFC 2957 application/whoispp-query Content-Type October 2000

provides no native mechanisms for authentication

Published specification: this

Person & email address to contact for further information

Leslie L.
leslie@thinkingcat.

Intended usage:

2. whoispp-query

The following grammar, which uses BNF-like notation as defined
[RFC2234] defines the set of acceptable input to a Whois++ server
As such, it describes the expected structure of a whoispp-query
type object

N.B.: As outlined in the ABNF definition, rule names and
literals are in the US-ASCII character set, and are case-insensitive

whois-command = ( system-command / terms [":" globalcnstrnts] )

system-command = "constraints" / "describe" / "commands" /
"polled-by" / "polled-for" / "version" / "list" /
"show" [1*sp bytestring] / "help" [1*
bytestring] / "?" [bytestring

terms = and-expr *("or" and-expr

and-expr = not-expr *("and" not-expr

not-expr = ["not"] (term / ( "(" terms ")" ))

term = ( generalterm / specificterm / combinedterm )

generalterm =

specificterm = specificname "="

specificname = "handle" / "value" / "template

combinedterm = attributename "="

globalcnstrnts = globalcnstrnt *(";" globalcnstrnt

Daigle & Faltstrom Informational [Page 2]

RFC 2957 application/whoispp-query Content-Type October 2000

globalcnstrnt = "format" "=" format / "maxfull" "=" 1*digit /
"maxhits" "=" 1*digit / "case" "=" casevalue /
"search" "=" searchvalue / opt-

opt-globalcnst = "authenticate" "=" auth-method / "language" "="
language / "incharset" "=" characterset /
"outcharset" "=" characterset / "ignore" "="
attriblist / "include" "="

localcnstrnts = 0*(";" localcnstrnt

localcnstrnt = "case" "=" casevalue / "search" "="

format = "full" / "abridged" / "handle" / "summary" /
"server-to-ask

auth-method =

language = 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
;the character set label that should be
;for UTF encoded information; the
;"UNICODE-2-0-UTF-8" and "UNICODE-1-1-UTF-8"
;are retained primarily for compatibility
;older Whois++ servers (and as outlined
;[RFC2279]).

searchvalue = "exact" / "substring" / "regex" / "fuzzy" /
"lstring

casevalue = "ignore" / "consider

bytestring = 0*

attributename = 1*

attriblist = attributename 0*("," attributename

charbyte = "\" specialbyte /

normalbyte = <%d33-255, except specialbyte

Daigle & Faltstrom Informational [Page 3]

RFC 2957 application/whoispp-query Content-Type October 2000

attrbyte = <%d33-127 except specialbyte> /
"\" ":" " " tab nl

specialbyte = " " / tab / "=" / "," / ":" / ";" / "\" /
"*" / "." / "(" / ")" /
"[" / "]" / "^" /
"$" / "!" / "?"

tab = %d09
sp = %d32 ;

digit = "0" / "1" / "2" / "3" / "4" /
"5" / "6" / "7" / "8" /
"9"

nl = %d13 %d10 ; CR

NOTE: Blanks that are significant to a query must be escaped.
following characters, when significant to the query, may be
and/or followed by a single blank

: ; , ( ) = !

3. Security

Security issues are discussed in section 1.

4.

[ALVE95] Alvestrand H., "Tags for the Identification of Languages",
RFC 1766, March 1995.

[RFC2234] Crocker, D. and P. Overell, "Augmented BNF for
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,
1995.

[RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet
Extensions (MIME) Part Two: Media Types", RFC 2046,
November 1996.

Daigle & Faltstrom Informational [Page 4]

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,
821, August 1982.

[IIIR] Weider C. and P. Deutsch, "A Vision of an
Internet Information Service", RFC 1727, December 1994.

[WINDX] Weider, C., Fullton, J. and S. Spero, "Architecture of
Whois++ Index Service", RFC 1913, February 1996.

[RFC2279] Yergeau F., " UTF-8, a transformation format of ISO 10646",
RFC 2279, January 1998.

5. Authors'

Leslie L.
Thinking Cat

Email: leslie@thinkingcat.

Patrik
Cisco Systems
170 W Tasman Drive SJ-13/2
San Jose CA 95134

EMail: paf@cisco.
URL: http://www.cisco.

Daigle & Faltstrom Informational [Page 5]

RFC 2957 application/whoispp-query Content-Type October 2000

6. Full Copyright

Copyright (C) The Internet Society (2000). All Rights Reserved

This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English

The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns

This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE

Funding for the RFC Editor function is currently provided by
Internet Society

Daigle & Faltstrom Informational [Page 6]

if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.

RFC documents can be found at I.E.T.F.

Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX