Search the Archives

RFC 854: What to do outside the rules?(From the perspective of a...

Reader comments:

Comment by M0les
Submitted on 1/5/2006
Related RFC: RFC 854
Rating: Not yet rated	Rate this comment:
What to do outside the rules?(From the perspective of a client implementation between a bi-directional data stream and some terminal implementation/emulation)a)What if a client implementation receives an IAC followed by a byte that is not a valid command? Solution 1 is to ignore the IAC and the invalid command byte (I think this is the best approach). Option two is to assume the sender is trying to send hte IAC and the bad command byte as data for the client to receive directly and pass them both on. I think this approach is flawed as the data stream is going to be corrupted anyway by other parts of the protocol anyway (e.g. valid command sequences the sender unintentionally inserted into the input stream, intending them to be data bytes for the end client).b)What if a CR is recevied that is not followed by either an LF or a NUL? My opinion is that the implementation should pass these on to the end-client without interpretation (unless explicitly asked-to by the client, e.g. translate local CRLF, LF or CR line termination into CRLF network line termination).

FAQS.ORG makes no guarantees as to the accuracy of the posts. Each post is the personal opinion of the poster. These posts are not intended to substitute for medical, tax, legal, investment, accounting, or other professional advice. FAQS.ORG does not endorse any opinion or any product or service mentioned mentioned in these posts.

<< Back to: RFC 854