As per Relevance of the word response, we have this rfc below:
Network Working Group R.
Request for Comments: 2378 Umea
Category: Informational P.
QUALCOMM, Inc
September 1998
The CCSO Nameserver (Ph)
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 (1998). All Rights Reserved
The Ph Nameserver from the Computing and Communications
Office (CCSO), University of Illinois at Urbana-Champaign has
some time now been used by several organizations as their choice
publicly available database for information about people as well
other things. This document provides a formal definition of
client-server protocol. The Ph service as specified in this
is built around an information model, a client command language
the server responses
1.
1.1. Basic Information
At its simplest the Ph database can be thought of as a computer
resident "phone book". However, it can be used to collect
information about people, and in response to a query about an
named in the database, return information about that entity. It
in short a nameserver for people and objects. It was designed
keep a relatively small amount of arbitrary information about
relatively large number of people or things, and provide access
that information over the Internet. In order to structure
information the manager of the database has to decide which views
present of the real-world objects that are to be represented in
database. Each view is then composed of a number of fields and
values. To support this concept Ph has the notion of
information, i.e., categorizing information into what are
fields and assigning descriptive names to those fields
Hedberg & Pomes Informational [Page 1]
RFC 2378 The CCSO Nameserver (Ph) Architecture September 1998
Even if the database resides and is reachable from the Internet it
local in the meaning that no server is supposed to be able to refer
client to another server which might hold the wanted information
However a server may contain a list of other Nameservers which can
used by clients to query other Nameservers for information
1.1.1.
A field descriptor is associated with each field and is used
describe the type and behavior of the field. A field
includes the fieldname, the maximum length of information the
can store before truncation, keywords describing the properties
the field as well as free text describing what kind of
the field is supposed to hold
The keywords can be any of the following
Always: Forces the field's contents to be always printed
addition to whatever fields specified by the query
Any: This field is always searched by queries. To be
use ful, a field marked as Any should also have the
and Lookup keywords as well
Change: Can be changed by the owner of the entry
Default: Printed if no return clause is given in the query
Encrypt: Must be encrypted before transmission
ForcePub: Viewable/searchable regardless of the content of
suppress
Indexed: Fields that are kept track of in the database's index
efficient lookups. At least one indexed field must
present in each query
LocalPub: May be viewed by anyone in the "local" domain or
space. Fields with this keyword are completely
outside of the "local" domain. They will not be shown
the fields command (section 3.3), and are disallowed
query commands or return clauses (section 3.8).
Lookup: May be used in the selection part of a query. A
without this keyword may not be used to select entries
NoMeta: Wildcard searches are disallowed
Hedberg & Pomes Informational [Page 2]
RFC 2378 The CCSO Nameserver (Ph) Architecture September 1998
NoPeople: No entry of type "person" may include this field
Private: Field may be viewed by Heros (section 1.4) only
Public: May be viewed by anyone. Fields not marked with
keyword may only be viewed by the entry's owner or a Hero
Sacred: Changes to the field are prohibited except via non-
invocations of the server, i.e., from a tty, file, or pipe
Turn: Users may turn off visibility of a field to everyone
themselves and Heros by prefixing the field text with '*'.
Unique: Any change to the field will be rejected if the
causes the modified field to match the same field in
other entry
1.1.2. Character
Historically Ph has been restricted to only handle
characters, that is characters with hexadecimal values between 0x20
and 0x7f. Lately with the spreading of 8-bit clean Operating
there is no reason to keep this limitation
This document therefore proposes that ISO-8859-1 shall be regarded
an alternative character set for Ph, the default still being US
ASCII
Clients that utilize ISO-8859-1 should request that the server
ISO-8859-1 by using the "set"-command
In the instance that values are stored using ISO-8859-1 and are to
shown to a client expecting US-ASCII, the characters with
codes outside of the US-ASCII range should be displayed in
"Quoted-Printable" content-transfer-encoding form defined in RFC-2045
[MIME].
1.2. Standardization
Each Nameserver manager is in essence free to name new fields to
the special needs of his/her organization. But in order to make
directory service useful outside of the organization it
recommended that a core set of standard fields always should
present
Therefore this document defines a couple of standard collections
fields (Appendix A).
Hedberg & Pomes Informational [Page 3]
RFC 2378 The CCSO Nameserver (Ph) Architecture September 1998
Also note that the architecture makes no assumption about the
and retrieval mechanisms used within individual servers.
are thereby free to use any kind of dedicated databases,
indexing software or even gateways to other directory services
store and retrieve the information, if desired
Ph simply functions as a known front-end, offering a simple
model in addition to a well known port and simple query language
1.3. Conventions Used in this
In examples, "C:" and "S:" indicate lines sent by the client
server respectively
1.4.
For Ph a Hero is equivalent to a superuser or operator. Being
Hero mode means that some or all artificial limits are removed;
Heros may change any field in any entry in the database, as well
view as many entries as they wish. Heros can also be limited to
field of one other entry. Hero mode is used mostly
administrative purposes, delegation of group authority over
fields, and is controlled by the acl field
2. Basic
Initially, the server host starts the Ph service by listening on
port 105. When a client host wishes to make use of the service,
establishes a TCP connection to the server host. The client and
Ph server then exchange commands and responses (respectively)
the connection is closed or aborted
2.1. Command
Commands in Ph consist of a keyword optionally followed by zero
more keywords or values, separated by spaces, tabs or newlines,
followed by a carriage return-linefeed (CRLF) pair. A more
description using BNF is given in Appendix C
Values containing spaces, tabs or newlines must be enclosed in
quotes ('"'). In addition the sequences "\n", "\t","\"" and "\\"
be used to mean newline, tab, double quote and backslash
respectively
Keywords must be given in lower case; case in the values of fields
preserved, although queries are not case-sensitive
Hedberg & Pomes Informational [Page 4]
RFC 2378 The CCSO Nameserver (Ph) Architecture September 1998
2.2. Response
Responses consist of a result code followed by additional
possibly separated by entry index and/or field name and
terminated by a CRLF pair
result code:[entry index:][field name:]
Responses to some commands might be multi-lined. In these cases
line in the response, except the last, has the appropriate
code negated (prefaced with "-"). The last line then starts with
appropriate result code without negation. Each line must
terminated by a CRLF pair
If a particular command can apply to more than one entry, then
multilined response must be so organized that all
pertaining to each entry is returned on consecutive lines, and
each of those lines must have one and the same entry index
following the resultcode. The first entry index should be 1
incremented each time a new entry is referred to
C: query hedberg return email name
S: 102:There were 3 matches to your request
S: -200:1: email: canheg95@student.umu.
S: -200:1: name: Carl Johan
S: -200:1: title:
S: -200:2: email: parheg95@student.umu.
S: -200:2: name: Par
S: -200:2: title:
S: -200:3: email: Roland.Hedberg@umdac.umu.
S: -200:3: name: Roland
S: -200:3: title: Boss of the Network
S: 200:
Commands that can apply to more than one field must have the name
the field to which the response applies directly following the
index
The text of the response will be either an error message in
readable format, or data from the Nameserver. Whitespace (spaces
tabs) may appear anywhere in the response, but the field name
text columns if present must each begin with a whitespace character
Since more than one specific piece of information may be
by a particular command, it is possible for parts of a command
succeed, while other parts of the same command fail. This
is handled as a single multi-line response with the result
changing as appropriate
Hedberg & Pomes Informational [Page 5]
RFC 2378 The CCSO Nameserver (Ph) Architecture September 1998
As for FTP, the result codes are in the range 100-699 (or from -699
to -100 for multiline responses), where the leading digit has
following significance
1: In
2:
3: More information
4: Temporary failure; it may be worthwhile to try again
5: Permanent
6: Phquery specific
Many commands generate more than one line of response; every
should be prepared to deal with such continued responses. Note
a command is finished when and only when the result code on
response line (treated as a signed integer) is greater than or
to 200.
Clients should assume that any numeric response, within the
mentioned ranges, are valid. Also note that the server is allowed
send one or more lines with result codes between -199 - -100 (
leading "-" indicates a continuation line) and 100 - 199, as
information, before the actual results are transmitted
2.3. Format of a search
Matching is not sensitive to upper or lower case letters and
normally done on a word-by-word basis. That is, both the
expression and the entry information is broken up into words,
individual words are compared using exact matching. If the order
the words is important in a query, then the query string can
surrounded by '"' (double quotes), whereby the complete search
is matched against the information in the Nameserver database
Word delimiters are the following characters: , ,
LINE>, ",", ";" and ":" . These characters are not indexed
should not be part of the search string
However, special symbols, called "wildcard" characters, can be
if the exact spelling is unknown. The '*' (asterisk, 0x2A) is
in place of zero or more characters, '+' (plus, 0x2B) in place of
or more unknown characters, and '?' (question mark, 0x3F) can be
when exactly one character is unknown. If the unknown character
be one of a limited set this can be specified by surrounding the
with brackets, e.g., [ei] means that in that place an 'e' or an 'i
would match
Hedberg & Pomes Informational [Page 6]
RFC 2378 The CCSO Nameserver (Ph) Architecture September 1998
3.
3.1.
Prints the message of the day and the current status of
nameserver
C:
S: 100:Qi server $Revision: 1.6 $
S: 100:Ph passwords may be obtained at CCSO Accounting
S: 100:1420 Digital Computer Lab, between 8:30 and 5 Monday-Friday
S: 100:Be sure to bring your U of I ID card
S: 200:Database
3.2.
Returns information about the servers site. Possible fields
Version Version information for the server
Maildomain The mail domain to use for phquery-type mail
Mailfield The field containing the specific email address
Mailbox Mandatory entry that names the field to use
maildrop
Administrator Guru in charge of service
Passwords Person in charge of ordinary password/change requests
Authenticate Authentication methods supported by the server
ordered in the site-preferred way. Presently
following options are defined
1 attempt auto
2 allowed to be interactive if
4 use ANSI X9.9 challenge/
8 use v4 Kerberos
16 use v5 Kerberos [KRB5]
32 use GSS-API [GSS-API]
64 use email
128 password encrypted response to
256 use clear-text
512 use HMAC [HMAC] with SHA-1 of challenge
Hedberg & Pomes Informational [Page 7]
RFC 2378 The CCSO Nameserver (Ph) Architecture September 1998
C:
S: -200:1:version:3.1
S: -200:2:maildomain:umu.
S: -200:3:mailfield:
S: -200:4:mailbox:
S: -200:5:administrator:roland.hedberg@umdac.umu.
S: -200:6:passwords:roland.hedberg@umdac.umu.
S: -200:7:authenticate:64:32:128
S: 200: Ok
The mail fields in the siteinfo command direct how
information stored in the Nameserver is to be used for
mail
The specific (username, host) pair to where a user's mail should
sent for final delivery is stored in the field named by {mailbox}.
Phquery and like utilities will use this field
To construct a useable email address from Nameserver information,
algorithm below is followed
if ({maildomain} is not null)
address = (contents of {mailfield})@{maildomain
address = (contents of {mailfield})
Some existing client software will not format email
correctly if the value of {mailbox} is set to anything other
"email" when {maildomain} is non-empty
If {mailbox} is set to anything other than {email}, {maildomain}
be reported empty by the siteinfo command. Also reformatting of
record's {mailfield} must be done by the server before reporting
to the client
3.3.
fields [field ...]
Without an argument, a list of all available field descriptors
be delivered. Any space-separated argument(s) restricts the list
the named fields. Fields marked with the "LocalPub" keyword (
1.1.1) should not be delivered outside of the local domain
Hedberg & Pomes Informational [Page 8]
RFC 2378 The CCSO Nameserver (Ph) Architecture September 1998
The output of the command consists of two lines describing
field. The first line defines the field in technical terms (
length and field attributes), while the second line is a
description of what the field is intended to hold. The
number of each response is the field id number
C:
S: -200:6:alias:max 32 Indexed Lookup Public
S: -200:6:alias:Unique name for user
S: -200:3:name:max 64 Indexed Lookup Public
S: -200:3:name:
S: -200:2:email:max 128 Lookup Public
S: -200:2:email:Account to receive electronic mail
S: -200:16:other:max 256 Lookup Public Default
S: -200:16:other:Other info the user finds important
S: -200:33:home_phone:max 60 Lookup Public Change
S: -200:33:home_phone:Home telephone number
S: 200:Ok
3.4.
id
Enters the given information in the Nameserver's log. This
is used by the Ph client to enter the user id of the person
it
3.5.
set [option[=value] ...]
Sets the named option for this nameserver session to a value.
default string "on" is used if no value is supplied. Used
arguments it return the settable options and their current value
Some common options
echo If on, echo the client's commands back to the client
limit Changes that affect more than the specified number
entries results in an error
charset Return responses to the client in the character
specified
verbose If on, report interim progress messages to the client
addonly If on, change commands can only create fields in entries
not modify them
nolog If on, disable logging
external If on, make Fields marked as "LocalPub" invisible
Hedberg & Pomes Informational [Page 9]
RFC 2378 The CCSO Nameserver (Ph) Architecture September 1998
C: set verbose=
S: 200:Done
C:
S: -200:echo:
S: -200:limit:2
S: -200:charset:iso-8859-1
S: -200:verbose:
S: -200:addonly:
S: -200:nolog:
S: -200:external:
S: 200:Done
3.6. login, logout, answer, clear, email, and
3.6.1.
login [alias
The "login" command allows client users to identify themselves to
Nameserver. More specifically it identifies a client user with
particular entry in the Nameserver and allows them to change
in that entry and possibly other entries. It is also necessary to
logged in to the Nameserver to view certain sensitive fields in
user's own entry
In order to use the "login" command the client must prompt the
for their ph alias and password. The client is then responsible
(optionally) encrypting the password and sending it to the server
This will be covered in sections 3.6.3 (answer) and 3.6.4 (clear).
C: login
S: 301:,:P"_Y$ONU%"SDUQ6&^`ZZ'?*#Y`A_.Z/A>?@SH>*-
3.6.2.
The "logout" command allows a user who is logged in to the
to logout
C: logout S: 200:Ok
Hedberg & Pomes Informational [Page 10]
RFC 2378 The CCSO Nameserver (Ph) Architecture September 1998
3.6.3.
answer encrypted-
In response to the login command, the Nameserver responds with
random challenge string. The Nameserver client encrypts
challenge with the password supplied by the user, uuencodes
result into US-ASCII, and returns the printable result in
"answer" command
C: login
S: 301:.%$&.D^67$*1?<.2S@DR:Z@M*)AV-<:4QM>#R>M*
C: answer M5K'F:NI(a?M?O2+-a9`48RA#ZF=L9)G)/XRS7Q^0>0@-R7X$WGb`50B
S: 200:ppomes:Hi how are you
The encryption algorithm is based on a three rotor Enigma engine
There are known attacks on the security of this approach
The answer command is also used to return method-specific
to the xlogin command (section 3.6.6).
3.6.4.
clear cleartext-
The "clear" command can be used instead of the "answer" command
complete a login sequence. It's argument is the user's
password. This command is supplied only to support those
that have not implemented one of the encryption engines used by
"answer" command. It's use is strongly discouraged
C: login
S: 301:E=@Y&VW^_9YVI;D5.[EB0:B)9Z#_&X$:2)/eL$VJC87
C: clear
S: 200:ppomes:Hi how are you
3.6.5.
email local-
The "email" command can also be used instead of the "answer"
to complete a login sequence. The value of local-userid is
user's login name on the local machine. If all of the
conditions are true, then the email command will be accepted by
server
Hedberg & Pomes Informational [Page 11]
RFC 2378 The CCSO Nameserver (Ph) Architecture September 1998
1) The connection to the server originates on port 1023 or less
the client. Note: This is a system port. Port 1023 is
allocated to this use
2) The canonical name of the client's host matches the right-
side of the email address of the requested alias specified in
"login" command
3) The "local-userid" matches the left-hand side of the
address belonging to the requested alias
This is a weak but convenient form of authentication. Depending
the information users are allowed to change about themselves and
threat environment the server operates in, this method may
appropriate. Servers should take care to avoid DNS spoofing
3.6.6.
xlogin option
Extended login command for GSS, Kerberos v4 and v5, ANSI X9.9
devices (e.g., SNK/4), etc. The option is one of the values
in the Authenticate field of the "siteinfo" command (section 3.2).
Alias is the user's alias
C: xlogin 16
S: 301:DoKrbLogin started; send Kerberos mutual authenticator
C: answer MJa8QO1cJHYz2IdWyg7uhAnixVqgCZQBWr64ciXYku1ktdu....
S: 200:ppomes:Hi how are you
C: xlogin 4
S: 302:SNK Challenge "024142":
C: answer 82344338
S: 200:ppomes:Hi how are you
The answer command returns the requested quantity,
authenticator, X9.9 device response, etc. Binary quantities
first uuencoded into US-ASCII
3.7.
add field=value...
This command is used to add new entries to the database. You must
logged in and have full Hero privileges (section 1.4) to use "add".
C: add name="doe john" id="123456789" alias="j-doe
S: 200:Ok
Hedberg & Pomes Informational [Page 12]
RFC 2378 The CCSO Nameserver (Ph) Architecture September 1998
3.8.
query [field=]value [field=value] . . . [return field1 [field2]]
If no field is specified together with a value then the field
assumed to be "name" and/or "nickname". When more than one field
value specification are given in a query, entries matching
specifications are returned (implicit AND).
It is possible to define which fields should be returned by adding
"return" clause. If no return clause is defined the Ph server
return a default list of fields. Typical default fields are "alias",
"name", "title", "email", "phone", "address", "department", "www",
and "other". A return clause consists of the word "return"
by a list of fields or the word "all". If the word "all" is
then all viewable fields will be returned
C: query name=doe name=
S: 102:There was 1 match to your request
S: -200:1: alias: j-
S: -200:1: name: doe
S: 200:Ok
3.9.
delete [field=]value...
This command is used to delete entire entries from the database.
must be logged in and have full Hero (section 1.4) privileges to
"delete".
The arguments to the "delete" command are the same as the
part of a "query" command. "Delete" finds all the entries that
the argument(s) and deletes them
The "delete" command obeys the Nameserver "limit" option, which
be used to prevent deletion of more entries than intended
C: delete name="doe john" id="123456789" alias="j-doe
S: 200:1 entries deleted
3.10.
change [field=]value [make|force] field="value"...
This command is used to change one or more fields in one or
entries to the values specified. The "change" command consists
two clauses, the "change" clause and the "make" or "force" clause
Hedberg & Pomes Informational [Page 13]
RFC 2378 The CCSO Nameserver (Ph) Architecture September 1998
The "change" clause determines which entries will be affected by
command. It uses the same arguments as the selection clause of
"query" command. The "make" or "force" clause specifies
field(s) will be changed and the new value(s) of the
field(s). The "force" clause is only used to make non-
changes to fields marked "Encrypt".
You must be logged in to use "change".
The "change" command obeys the Nameserver "limit" option, which
be used to prevent changing the field contents of more entries
intended
C: change alias=j-doe force password=
S: 200:1 entry changed
C: set limit=500
S: 200:Done
C: change fax="(619) 555-1212" make fax="(760) 555-1212"
S: 200: 113 entries changed
3.11.
help [{native|client} [topic ...]]
Prints help on the Nameserver or on specific clients. If client
specified, it should be a valid Nameserver client identifier, such
"ph". The client-specific help will first be searched for topic,
then the native help will be searched. If topic is omitted, a
of all available help texts will be returned. If "native" or
are also omitted, a list of clients will be returned
C: help native 101
-200:1:101:
-200:1: The Nameserver echo option is set. The text of this response
-200:1: the command you just gave, which has not (yet) been executed
200:Ok
3.12. quit/exit/
Terminates the session with the Nameserver and causes the client
exit
C:
S: 200:Bye
Hedberg & Pomes Informational [Page 14]
RFC 2378 The CCSO Nameserver (Ph) Architecture September 1998
4.
4.1. Transport
In the absence of encryption between client and server,
Nameserver traffic is unsecure. Kerberos v4, v5, and the GSS-API
provide encryption mechanisms, however the Nameserver protocol
not support the means to negotiate encryption between client
server. This implies that all traffic can be seen by other
having access to the network linking the client and server
Furthermore clear-text traffic is subject to modification in
between client and server. Possible ways of augmenting this would
to use something like TLS [TLS] or IPSec [IPSEC].
4.2. Server
Unless one of the mutual authentication mechanisms is used, e.g.,
Kerberos 4/5 or GSS-API, there is no way to prove the identity of
server. Further, there is no mechanism to prove a given server
authoritative for a set of information
4.3. Secure User
The Ph protocol allows the negotiation of several
protocols between client and server, some weak and some strong.
does not prohibit the use of cleartext passwords, something
should be depreciated, but is useful when dealing with some clients
4.4. Privacy and Access
Directory services like the CCSO white pages server that
information on persons have to consider privacy issues. This
describes one way of partitioning specific attributes from
access by designating them visible only to the "local" community
visible only to the person connected with the information, or
only to the database administrator
Hedberg & Pomes Informational [Page 15]
RFC 2378 The CCSO Nameserver (Ph) Architecture September 1998
4.5.
[GSS-API] Linn, J., "Generic Security Service Application
Interface, Version 2", RFC 2078, January 1997.
[HMAC] Krawczyk, H., Bellare, M., and R. Canetti, "HMAC: Keyed
Hashing for Message Authentication", RFC 2104,
1997.
[IPSEC] Atkinson, R., "Security Architecture for the
Protocol", RFC 1825, August 1995.
[KRB5] Kohl, J., and C. Neuman, "The Kerberos
Authentication Service (V5)", RFC 1510, September 1993.
[TLS] Dierks, T., and C. Allen, "The TLS Protocol
Version 1.0", Work in Progress
[MIME] Freed, N., and N. Borenstein, "Multipurpose Internet
Extensions, (MIME) Part One: Format of Internet
Bodies", RFC 2045, November 1996.
5.
5.1. Authors'
Roland
Umea
901 87
EMail: Roland.Hedberg@umdac.umu.
Paul
Qualcomm
6455 Lusk
San Diego,
EMail: ppomes@qualcomm.
Hedberg & Pomes Informational [Page 16]
RFC 2378 The CCSO Nameserver (Ph) Architecture September 1998
Appendix
Default fields and suggested lengths connected to different
types
All entries: Information common to all
type 64
name 256
address 128
proxy 32
password 32
type=phone: Information found in a
phone 64
fax 64
type=person: Information about a human
alias 32
forename 64
surname 64
group 32
email 128
public_key 4096
nickname 128
www 256
acl 128
type=staff: Information about an
empno 16
department 64
supervisor 64
secretary 64
office_location 128
office_address 128
office_phone 64
title 64
pager 64
hours 128
type=unit: Information about an organizational
email 128
www 256
public_key 4096
Hedberg & Pomes Informational [Page 17]
RFC 2378 The CCSO Nameserver (Ph) Architecture September 1998
Appendix
Result
100 In progress (general).
101 Echo of current command
102 Count of number of matches to query
103 No hostname found for IP address
200 Success (general).
201 Database ready, but read-only
300 More information (general).
301 Encrypt this string
302 Print this prompt
400 Temporary error (general).
401 Internal database error
402 Lock not obtained within timeout period
403 Login would have been OK, but database read-
475 Database unavailable; try later
500 Permanent error (general).
501 No matches to query
502 Too many matches to query
503 Not authorized for requested information
504 Not authorized for requested search criteria
505 Not authorized to change requested field
506 Request refused; must be logged in to execute
507 Field does not exist
508 Field is not present in requested entry
509 Alias already in use
510 Not authorized to change this entry
511 Not authorized to add entries
512 Illegal value
513 Unknown option
514 Unknown command
515 No indexed field in query
516 No authorization for request
517 Operation failed because database is read-only
518 To many entries selected by change command
520 CPU usage limit exceeded
521 Change command would have overridden existing field
and the "addonly" option is on
522 Attempt to view "Encrypted" field
523 Expecting "answer" or "clear".
524 Names of help topics may not contain "/".
525 Email authentication
526 Host name address not found in
527 Reverse DNS lookup does not match forward DNS
528 General Kerberos database error
529 Selected authentication method not
Hedberg & Pomes Informational [Page 18]
RFC 2378 The CCSO Nameserver (Ph) Architecture September 1998
590 Remote queries not allowed
598 Command unknown
599 Syntax error
600 Ambiguous or multiple
Hedberg & Pomes Informational [Page 19]
RFC 2378 The CCSO Nameserver (Ph) Architecture September 1998
Appendix
Description of the client command language using the
Backus-Naur Form (RFC822).
response = code [index] [field] text
code = [-] LDIG 2DIGIT ":"
index = number ":"
field = 1*SPACE attribute ":" 1*
text = 1*( CHAR / LWSP-char )
command = ph-command
ph-command = "status" / a-command / oa-
ph-command =/ av-command / answer-command / query-
ph-command =/ delete-command / change-command / "help" / quit-
a-command = ("siteinfo"/"fields"/"id"/"login"/"help"/"email"/
"clear") [attribute
oa-command = ("xlogin") number
av-command = ("set"/"add"/"make") 1*attribute-
answer-command = ("answer") 1*
query-command = ("query"/"ph") 1*selection ["return" 1*attribute
quit-command = "quit" / "exit" / "stop
change-command = "change" 1*selection make 1*attribute-
delete-command = "delete"
selection = value / attribute-
attribute-value = attribute "="
value = 1*(cstring / quoted-string / set
cstring = 1*( ALPHA / DIGIT / S_SPEC / set / quoted-pair )
attribute = 1*( ALPHA / DIGIT / "_" / "-" )
number = 1*(DIGIT
quoted-string = <"> 1*(qtext/quoted-pair) <">
quoted-pair = "\"
qtext = 1*( CHAR / CR / SPEC1 / DELIMIT1 / DELIMIT2 / LWS )
set = '[' 1*(ALPHA/DIGIT) ']'
LWSP-char = SPACE /
LWS = 1*([CRLF] (LWSP-char))
CRLF = CR
Hedberg & Pomes Informational [Page 20]
RFC 2378 The CCSO Nameserver (Ph) Architecture September 1998
S_SPEC = '*'/'+'/'?'
SPEC1 = "=" / "*" / "?" / "+" / "[" / "]"
SPEC2 = "\" / """
DELIMIT1 = SPACE / HTAB /
DELIMIT2 = "," / ";" / ":"
PRINTABLE = %d32..%d126
CTL = %d0..%d31 / %d127..%d160
ALPHA = %d65..%d90 / %d97..%d122
DIGIT = %d48..%d57
LDIG = %d49..%d54
SPACE = %d32
SEP = (CR LF) /
CR = %d13
LF = %d10
HTAB = %d
CHAR = %d33..%d126 / %d160..%d255
OTHER = "(" / ")" / "-" / "." / "/"
"@" / "$" / "_" / "!" / "~" /
"'" / "#" / "&" / "<" / ">" /
"^" / "`" / "{" / "|" / "}"
Hedberg & Pomes Informational [Page 21]
RFC 2378 The CCSO Nameserver (Ph) Architecture September 1998
Full Copyright
Copyright (C) The Internet Society (1998). 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
Hedberg & Pomes Informational [Page 22]
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
