Tech-invite3GPPspaceIETFspace
96959493929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 0552

Single access to standard protocols

Pages: 1
Unclassified

ToP   noToC   RFC0552 - Page 1
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 ]