Open larsbrinkhoff opened 5 years ago
Recall from #674, when a connection is made to an NCP socket less than 1000, ITS will start SYS; ATSIGN NETRFC to handle it.
I see these LBSIGN files and links. Socket assignments as per old RFC documents (the other RFC).
RFC | Timestamp | Socket | Official Protocol | Link to |
---|---|---|---|---|
001 | 1 | Old TELNET | SYSBIN; TELSER BIN | |
003 | 1978 | 3 | Old FTP | |
025 | 1980 | 21 | New FTP | |
027 | 1975 | 23 | New TELNET | SYSBIN; TELSER BIN |
045 | 1976-77 | 37 | Time Server | |
103 | 1976-77 | 67 | Datacomputer | |
105 | 1977 | 69 | Trivial File Transfer | |
107 | 1976 | 71 | NETRJS [EBCDIC] | SYS1; TS SUPDUP |
113 | 1976 | 75 | NETRJS [TTY] | |
115 | 1975 | 77 | "any private RJE server" | GLS; TEMP BIN |
117 | 1975 | 79 | Finger | SYSBIN; NAME BIN |
121 | 1981 | 81 | Network BSYS | |
261 | 1977 | 177 |
Checking network servers to see if they support NCP.
SYSENG; NETRFC 3 has some features that SYSEN2; NETRFC 3 doesn't.
The SYSEN2 version seems tailored for DM. When run, it will use the DEMSIG UUO to start a demon from SYS; ATSIGN RFCfoo.
The SYSENG version, if assembled with DEMONP on, is identical to the SYSEN2 version. However, if assembled with DEMONP off, it will instead load and run a program from DEVICE; LBSIGN RFCfoo.