![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to ns-3 CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [Research Unix] / researchv10dc / doc / csnet|
Return to ns-3 CVS log | Up to [Research Unix] / researchv10dc / doc / csnet |
1.1 root 1: From research!mtune!rutgers!SH.CS.NET!cic Thu Oct 1 23:21:27 1987
2: Received: by mtune.ATT.COM (smail2.5)
3: id AA13402; 1 Oct 87 23:21:27 EDT (Thu)
4: Received: by RUTGERS.EDU (5.54/1.14)
5: id AA29881; Thu, 1 Oct 87 01:28:21 EDT
6: Message-Id: <[email protected]>
7: Received: by SH.CS.NET id aj10308; 29 Sep 87 15:26 EDT
8: Date: Tue, 29 Sep 87 14:25:22 EDT
9: Subject: ns-3 QUERY by Electronic Mail
10: Reply-To: rutgers!SH.CS.NET!cic
11: From: CSNET INFO SERVER <rutgers!SH.CS.NET!info>
12: To: [email protected]
13:
14: Request: info
15: Topic: ns-3
16: ========================================================================
17: CSNET Coordination and Information Center (CIC) [email protected]
18: 10 Moulton St, Cambridge MA 02238 617/497-2777 ([email protected])
19: ========================================================================
20: Updated: 27 Jul 84
21:
22: QUERY BY ELECTRONIC MAIL
23:
24: If your local CSNET site has no Local Agent software and no TELNET
25: access you can send and receive queries by electronic mail. You can
26: use this technique on any X25Net or Arpanet site when you want the
27: results of your queries in message form.
28:
29:
30: HOW TO PREPARE YOUR NAME SERVER MESSAGES
31:
32: Address your messages to the registrar at the CSNET Service Host:
33:
34: To: registrar@csnet-sh
35:
36: You will receive an automatic answer to your query by message from
37: NS_Service@CSNET-SH.
38:
39: The subject field of the message you send will not be read by the Name
40: Server, and may contain any text (or no text).
41:
42: The body of the message should contain only the commands and keywords
43: for the query, and no other text. The general form is:
44:
45: whois
46: exact
47: keyword1 keyword2 ...
48: end
49:
50: The words "whois", "exact", and "end" must each begin in column 1 of
51: a new line. The keywords may begin anywhere except column one. Any
52: number of keywords, possibly extending over more than one line, is
53: acceptable.
54:
55: Table ns-3.1 is similar to Table ns-2.1 (in Message ns-2), but shows
56: both interactive query commands and the equivalent forms that you
57: should use in your message.
58:
59:
60: COMPOSING YOUR QUERY
61:
62: The selection method used in the name Server is that of the "inverted
63: index". Each word in each entry is indexed separately, and, in
64: general, the Name Server selects only on whole words. A search
65: specification consists of one or more words, and selection occurs when
66: all the specified words are present in an entry. It is not possible
67: to specify other types of relationships between words.
68:
69: A word is a string of characters between two delimiters. The delimiters
70: recognized by the Name Server are:
71:
72:
73: <space> <tab> <end-of-line> ; . , ( ) & #
74:
75:
76: A CAUTION ABOUT "%"
77:
78: Please note that the "%" character is NOT a delimiter at the present
79: time. For this reason, the Name Server treats "name%host" as a single
80: word but "name.host" as two words. At the time that the Name Server
81: was designed, the full Arpanet address for a PhoneNet site was
82: "name.host@csnet-relay"; at the current time, the Internet is in the
83: process of preparing for domain-style addresses, and the Internet
84: address which is recommended by the Arpanet Network Information Center
85: is "name%host@csnet-relay".
86:
87: The reason is that many sites are now including a domain name to the
88: left of the "@", for example, "name%[email protected]". The
89: use of "%" clarifies the distinction between hosts and domains. When
90: the domain system is fully implemented, this special use of "%" will
91: probably be discarded. However, if "%" remains special, the Name
92: Server will be changed to treat "%" as a delimiter.
93:
94:
95: REVISING THE DATABASE
96:
97: The CSNET Staff is in the process of revising the Name Server database
98: to update the old relay names, "udel-relay" and "rand-relay" and
99: replace them with "csnet-relay". At the same time, all entries
100: "name.host-relay" will be changed to "name%host@csnet-relay".
101:
102:
103: SEARCHING FOR WORDS IN THE DATABASE
104:
105: There are a few restrictions on the characters in a word: The words
106: must be strings of letters and numbers, or of letters only, but not of
107: numbers only, so that you cannot select on a zip code or a telephone
108: area code. You can select on "@", but only if it is in the middle of
109: a word. You can use the wildcards, "*" and "?" at the middle or end
110: of a word, but not at the beginning. Because the analysis of the
111: words is done before the query is made, there is no method for
112: "quoting" numbers, the "@", wildcards or delimiters to allow
113: selection.
114:
115:
116: TABLE ns-3.1. EXAMPLES OF INTERACTIVE AND MESSAGE QUERIES
117: +--------------------------------------------------------------------+
118: | You may abbreviate "-account", "-ident", "-short" or |
119: | "-threshold" as "-a", "-i", "-s" or "-t". |
120: +----------------------------------------------+---------------------+
121: |INTERACTIVE COMMANDS |MESSAGE COMMANDS |
122: +----------------------------------------------+---------------------+
123: |site |whois |
124: | |exact |
125: | Selects the site entry for your site. | site |
126: | |end |
127: +----------------------------------------------+---------------------+
128: |site oregon-grad |whois |
129: | |exact |
130: | Selects the site entry for the Oregon | site oregon-grad |
131: | Graduate Center, Beaverton, OR |end |
132: +----------------------------------------------+---------------------+
133: |site list |whois |
134: | |exact |
135: | Either command selects the long "sites" | sites list |
136: | entry, which contains the list of all |end |
137: | CSNET sites (PhoneNet, X25Net, ARPANET). | |
138: | | |
139: | To avoid selecting the "sites" entry, | |
140: | try to frame your query to include more | |
141: | than the site name in the specification. | |
142: +----------------------------------------------+---------------------+
143: |whois oregon-grad@*relay |whois |
144: | |exact |
145: | Returns all selections at oregon-grad, | oregon-grad@*relay |
146: | which is a PhoneNet site. Does not return |end |
147: | the long "sites" entry. | |
148: | | |
149: | Returns the "long" form of the entries if | |
150: | there 9 or fewer selections. Returns the | |
151: | one-line "short" form if there are | |
152: | between 9 and 200. Rejects the query as | |
153: | too ambiguous if there are more than 200. | |
154: | "*" is a wild-card. | |
155: +----------------------------------------------+---------------------+
156: |whois rice -threshold 100 |whois |
157: | |exact |
158: | Returns all users at Rice University, | rice |
159: | if there are 100 or fewer. Also |threshold |
160: | returns the long "sites" entry, the | 100 |
161: | site entry for Rice and the entries for |end |
162: | people named "Rice". There is no fool- | |
163: | proof way select only entries for the | |
164: | Rice site. | |
165: +----------------------------------------------+---------------------+
166: |whois bob -short |whois |
167: | |exact |
168: | Selects all entries with the word | bob |
169: | "bob" anywhere in the entry, if there are |short |
170: | 200 or fewer, in one-line "short" form. |end |
171: +----------------------------------------------+---------------------+
172: |whois bob purdue |whois |
173: | |exact |
174: | Selects entries that contain both "bob" | bob purdue |
175: | and "purdue". |end |
176: +----------------------------------------------+---------------------+
177: |whois bob purdue [smith schmidt] |whois |
178: | |exact |
179: | Tries to disambiguate by selecting on | bob purdue |
180: | either "smith" or "schmidt", but only |disambig |
181: | if "exact" selects multiple entries. | smith schmidt |
182: | |end |
183: +----------------------------------------------+---------------------+
184: |whois ric? purdue [s*m*t*] |whois |
185: | |exact |
186: | Selects entries with "rich", "rick" or | ric? purdue |
187: | "rice", etc., and "purdue", then disam- |disambig |
188: | biguates with "smith" or "schmidt". | s*m*t* |
189: | The "*" is a wildcard that matches any |end |
190: | number of characters, including zero, | |
191: | and a "?" matches any one character. A | |
192: | wildcard can be used only in the middle | |
193: | or at the end of a word. | |
194: +----------------------------------------------+---------------------+
195: |whois jones -short -threshold 10 [purdue] |whois |
196: | |exact |
197: | Tries to select entries for Jones | jones |
198: | that include "purdue", if any. |short |
199: | Otherwise returns all, if there are |threshold |
200: | 10 or fewer. (Note that the field | 10 |
201: | contents may begin at any column |disambig |
202: | except column 1.) | purdue |
203: | |end |
204: +----------------------------------------------+---------------------+
205: |whois -account bjones |whois |
206: | |account |
207: | Selects the owner of the account | bjones |
208: | "bjones,host,site" with your host and |end |
209: | site. On a CSNET site such as Purdue, | |
210: | the account is "bjones,purdue,purdue". | |
211: | You may type in a complete account, | |
212: | such as "bjones,purdue-ee,purdue". | |
213: | There are no spaces in the string. | |
214: +----------------------------------------------+---------------------+
215: |whois -account purdue,csnet,csnet |whois |
216: | |account |
217: | Returns the site entry for Purdue. | purdue,csnet,csnet |
218: | The account string for a site is |end |
219: | "site,csnet,csnet". | |
220: +----------------------------------------------+---------------------+
221: |whois -ident 2573 |whois |
222: | |ident |
223: | Selects the owner of the account with | 2573 |
224: | the csnet-id number "2573". This |end |
225: | feature is included for the benefit of | |
226: | programs that query the name server. | |
227: +----------------------------------------------+---------------------+
228:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.