Browse Prior Art Database

The Finger User Information Protocol (RFC1288)

IP.com Disclosure Number: IPCOM000002107D
Original Publication Date: 1991-Dec-01
Included in the Prior Art Database: 2000-Sep-12
Document File: 10 page(s) / 23K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Zimmerman: AUTHOR

Abstract

This memo describes the Finger user information protocol. This is a simple protocol which provides an interface to a remote user information program.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 12% of the total text.

Network Working Group D. Zimmerman

Request for Comments: 1288 Center for Discrete Mathematics and

Obsoletes: RFCs 1196, 1194, 742 Theoretical Computer Science

December 1991

The Finger User Information Protocol

Status of this Memo

This memo defines a protocol for the exchange of user information.

This RFC specifies an IAB standards track protocol for the Internet

community, and requests discussion and suggestions for improvements.

Please refer to the current edition of the "IAB Official Protocol

Standards" for the standardization state and status of this protocol.

Distribution of this memo is unlimited.

Abstract

This memo describes the Finger user information protocol. This is a

simple protocol which provides an interface to a remote user

information program.

Based on RFC 742, a description of the original Finger protocol, this

memo attempts to clarify the expected communication between the two

ends of a Finger connection. It also tries not to invalidate the

many existing implementations or add unnecessary restrictions to the

original protocol definition.

This edition corrects and clarifies RFC 1196.

Table of Contents

1. Introduction ........................................... 2

1.1. Intent ............................................... 2

1.2. History .............................................. 3

1.3. Requirements ......................................... 3

1.4. Updates .............................................. 3

2. Use of the protocol .................................... 4

2.1. Flow of events ....................................... 4

2.2. Data format .......................................... 4

2.3. Query specifications ................................. 4

2.4. RUIP {Q2} behavior ................................... 5

2.5. Expected RUIP response ............................... 6

2.5.1. {C} query .......................................... 6

2.5.2. {U}{C} query ....................................... 6

2.5.3. {U} ambiguity ...................................... 7

2.5.4. /W query token ..................................... 7

2.5.5. Vending machines ................................... 7

3. Security ............................................... 7

3.1. Implementation security .............................. 7

3.2. RUIP security ........................................ 8