|
A. BASIC SEARCHING |
|
To search the RFC index, enter a search argument in the empty box and select "Search".
The search engine will display all RFC index entries that match the argument. These index entries will include hyper-linked references to retrieve the corresponding RFC text. Current RFCs (i.e., those that have not been obsoleted) have their titles shown in bold face. |
|
B. MATCHING RULES |
||
|
Matches are always case-insensitive. The search argument may contain one or more words separated by spaces. Multiple words must each match; that is, the match is by default the logical "AND" of multiple argument words. The default is to do "prefix" matching, that is, the argument word must be a prefix of a matching word in the index. However, "entire word" matching can also be requested. |
||
Example of prefix match: |
||
| Argument: "inet" will match RFCs whose titles include "inetOrgPerson" and "INETPhone". | ||
|
C. RESULTS |
|
Search results can be displayed in order of decreasing
document number (the default) or increasing document number. The maximum number of index entries to be shown on the screen at a time can be selected (default 25). Click the 'Next' button to show the next screen. The Abstract and/or the keywords associated with each RFC entry can be displayed. |
|
D. FIELDS Each index entry displays the following fields: |
|||
(1) Document ID ("Number") (2) Title (3) Author (4) Keywords (5) Date |
|||
|
The Search Field can be set to limit the search to any one of (1)-(4).
Keywords (4) are not displayed unless explicitly requested.
Note that all words in the Title field are considered keywords. The
RFC Editor supplies other descriptive keywords for each RFC.
The Document ID field (1) effectively contains two fields: the document type (RFC, STD, FYI, or BCP) and the document number. |
|||
| Examples: |
|||
|
Argument: "Smith" on Author field: 23 matches. |
|||
| Argument: "A. Smith" on Author field: 8 matches | |||
|
(This includes a bogus match:
"D. Sitzler, P. Smith, A. Marine", because
the two argument words "A." and "Smith"
were matched independently) |
|||
|
Argument: "Smith" on Title field: 0 matches |
|||
| Argument: "1123" on Document ID: 1 match | |||
|
(Returns RFC 1123) |
|||
| Argument: "11" on Document ID: 4 matches | |||
| (RFC 11, BCP 11, STD 11, and FYI 11) | |||
|
Finally, the search field can be set to All Fields (this is the default). This effectively combines all the fields of each index entry into a single string for matching against the argument words. |
|||
Examples: |
|||
| Argument: "Smith LDAP" on All Fields | |||
| (Four matches with "LPAP" in the Title field and "Smith" in the Author field). | |||
Argument: "Smith 1996" on All Fields |
|||
|
(Note that the Date field is implicitly
included in matches,although one cannot
explicitly select the Date field for
exclusive matching) |
|||
|
E. MORE DETAILS 2) Related Documents ( "SeeAlso" field ) Some entries in the RFC Editor database contain a "SeeAlso" field that indicates one or more related documents. Index entries for any such related documents will also be displayed as search results. o Such related index entries will be displayed right after the primary match but with a different background color (light yellow). o The related documents will not be included in the count of matches. o An STD may include a set of RFCs. If an STD number is used as an argument (e.g., "std 3"), all the component RFCs will be shown. One is considered the primary protocol, while the others are shown as related RFCs. 3) Document Number Parsing For matching on document numbers, leading zeros are ignored, and a space between prefix letters and number is optional. The prefix is also optional; rfc is assumed unless you have explicitly specified a search limited to STDs, BCPs, or FYIs. For example, entering any of the following search arguments: |
|||||||||||
|
|||||||||||
|
will retrieve information about RFC 83. 4) Advanced Searches If multiple words are included in the search argument, the search is normally a logical "and" of these words. However, this will become a logical "or" when the word "or" is explicitly included in the search argument. |
|||||||||||
| Example: | |||||||||||
| "mime pgp" has 1 match "mime or pgp" has 97 matches | |||||||||||