| |
| | [No title] |
 | | Leech, et al Standards Track [Page 1] RFC 1928 SOCKS Protocol Version 5 March 1996 There exists, also, a need for strong authentication of such traversal in as fine-grained a manner as is practical. |
 | | This requirement stems from the realization that client-server relationships emerge between the networks of various organizations, and that such relationships need to be controlled and often strongly authenticated. |
 | | If the connection request succeeds, the client enters a negotiation for the Leech, et al Standards Track [Page 2] RFC 1928 SOCKS Protocol Version 5 March 1996 authentication method to be used, authenticates with the chosen method, then sends a relay request. |
| www.ietf.org /rfc/rfc1928.txt (2026 words) |
|