Jeffrey Altman wrote:
The reality is RFC is experimental and not authoritative. The only thing that really counts is what Cisco actually shipped in their IOS implementation. Lucky me I actually have a terminal
server that implements it. If you look at the C-Kermit sources you will see that the client is written to accept both values from the server. You will also find that Cisco does not send the baudrates as specified in the RFC but instead uses an enumeration.
True. But if I had been lucky and had a terminal server, I would not have written ser2net :).
So Cisco uses a enumeration? Do you think it is possible to make them compatible and do both in ser2net, or is it a non-issue?
Clients can use heuristics to determine which should be used. Servers must choose one; but I would make a configurable option.
(The clock is off by one day 4 hours and 12 minutes. This causes your e-mail to get lost way down in my queue.)
smime.p7s
Description: S/MIME Cryptographic Signature
