Documenting Telnet options

There is a special RFC [3] which specifies how new Telnet Options should be documented. This RFC recommends at least the following sections be included:

• Section 1 Command Name and Option Code
• Section 2 Command Meanings
  Describes the meaning of each DO, DON'T, WILL and WON'T command for this option.
• Section 3 Default Specification
  The default assumptions for hosts which do not implement, or use, this option.
• Section 4 Motivation
  Should inform on the motivation for inventing this option.
• Section 5 Description (or Implementation Rules)
  A more complete description on the use of the option. Could take the form of a text, sample implementation, hints to implementers, etc.

This RFC suggests that sub-negotiation shall only take place after a prior successful option code negotiation. But even if the receiver is unable to parse the contents of a sub-negotiation, he will always be able to ignore the SB -- SE sequence by skipping to after the IAC SE in the incoming data stream.