blob: a91ceba5021b51b0884bd8bcdab4f893b453c18e (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
|
Network Working Group Buz Owen
RFC # 552 SDAC-TIP
NIC # 17809 13 July, 1973
Single access to Standard Protocols
Isn't the idea of a single access protocol simple enough that one could
be specified, and a socket reserved for it, before the proposed mail
protocol becomes official? The result would be that MP could be the
first protocol implemented under UULP (or whatever it is to be called),
and the other protocols could be "moved" as soon as any problems in the
official specifications could be worked out, and at the convenience of
implementors.
The single access protocol might have the following commands:
USER
PASS
ACCT
MAIL
FTP
RJS
DRS (?)
HELP (?)
BYE
following Jim White's idea of nested command and reply spaces.
This doesn't address the question of "what is free", or of the
interrelationships between the various protocols, but it doesn't make
those problem any worse, only a little different.
[ This RFC was put into machine readable form for entry ]
[ into the online RFC archives by Alex McKenzie with ]
[ support from GTE, formerly BBN Corp. 10/99 ]
Owen [Page 1]
^L
|
