|
|
3.2.1 Option Negotiation: RFC-854, pp. 2-3
Connected: An Internet Encyclopedia
3.2.1 Option Negotiation: RFC-854, pp. 2-3
Up:
Connected: An Internet Encyclopedia
Up:
Requests For Comments
Up:
RFC 1123
Up:
3. REMOTE LOGIN -- TELNET PROTOCOL
Up:
3.2 PROTOCOL WALK-THROUGH
Prev: 3.2 PROTOCOL WALK-THROUGH
Next: 3.2.2 Telnet Go-Ahead Function: RFC-854, p. 5, and RFC-858
3.2.1 Option Negotiation: RFC-854, pp. 2-3
3.2.1 Option Negotiation: RFC-854, pp. 2-3
Every Telnet implementation MUST include option negotiation and
subnegotiation machinery [TELNET:2].
A host MUST carefully follow the rules of RFC-854 to avoid
option-negotiation loops. A host MUST refuse (i.e, reply
WONT/DONT to a DO/WILL) an unsupported option. Option
negotiation SHOULD continue to function (even if all requests
are refused) throughout the lifetime of a Telnet connection.
If all option negotiations fail, a Telnet implementation MUST
default to, and support, an NVT.
- DISCUSSION:
Even though more sophisticated "terminals" and supporting
option negotiations are becoming the norm, all
implementations must be prepared to support an NVT for any
user-server communication.
Next: 3.2.2 Telnet Go-Ahead Function: RFC-854, p. 5, and RFC-858
Connected: An Internet Encyclopedia
3.2.1 Option Negotiation: RFC-854, pp. 2-3
|
|
|
 |
|
|
|
Protect yourself from cyberstalkers, identity thieves, and those who would snoop on you.
| |
Stop spam from invading your inbox without losing the mail you want. We give you more control over your e-mail than any other service.
| |
Block popups, ads, and malicious scripts while you surf the net through our anonymous proxies.
| |
Participate in Usenet, host your web files, easily send anonymous messages, and more, much more.
| |
All private, all encrypted, all secure, all in an easy to use service, and all for only $5.95 a month!
|
|
Service Details
|
|
|
|
