RFC 1914: How to Interact with a Whois++ Mesh
In plain English — editorial summary, not part of the RFC
In the Whois++ architecture [Deutsch94],[Weider94], mesh traversal is done by the client, since each server 'refers' the client to the next appropriate server(s). [STANDARDS-TRACK]
Document record
- Document ID
- RFC1914
- Published
- February 1996
- Authors
- P. Faltstrom; R. Schoultz; C. Weider
- Status
- HISTORIC
- Stream
- IETF
- Area
- usv
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1835Architecture of the WHOIS++ serviceCurrent
August 1995
- RFC 1834Whois and Network Information Lookup Service, Whois++Current
August 1995
- RFC 1564DSA Metrics (OSI-DS 34 (v3))Current
January 1994
- RFC 3098How to Advertise Responsibly Using E-Mail and Newsgroups or - how NOT to $$$$$ MAKE ENEMIES FAST! $$$$$Current
April 2001
- RFC 1959An LDAP URL FormatObsoleted
June 1996
- RFC 1960A String Representation of LDAP Search FiltersObsoleted
June 1996
- RFC 1961GSS-API Authentication Method for SOCKS Version 5Current
June 1996
- RFC 1964The Kerberos Version 5 GSS-API MechanismUpdated
June 1996
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?