| 1 |
<pre>Network Working Group D. Crocker (UCLA-NMC) |
| 2 |
Request For Comment: #539 J. Postel (UCLA-NMC) |
| 3 |
NIC 17644 July 9, 1973 |
| 4 |
References: 524 |
| 5 |
|
| 6 |
|
| 7 |
Thoughts on the Mail Protocol Proposed in <a href="./rfc524">RFC 524</a> |
| 8 |
|
| 9 |
|
| 10 |
Generally, we feel that the protocol is extremely rich. We also feel |
| 11 |
that there are some minor and some major problems. |
| 12 |
|
| 13 |
The minor points first: |
| 14 |
|
| 15 |
1. <CA> and <CA2> are not explained until the formal syntax. It |
| 16 |
would be more convenient, if they were explained sooner. |
| 17 |
|
| 18 |
2. The Proposed <CA2> is a bad thing, since it is the Telnet Go- |
| 19 |
Ahead, which should not be used by higher level protocols. |
| 20 |
|
| 21 |
3. The default SIGNATURE should be the sign-on or ident of the |
| 22 |
author(s). |
| 23 |
|
| 24 |
4. The Disposition INTERRUPT would be more useful if it had |
| 25 |
author/clerk-assigned "levels". Currently mail would be either |
| 26 |
urgent or not. With levels (say 1 to 10), the sender could rate the |
| 27 |
degree of urgency. |
| 28 |
|
| 29 |
There would be no precise defined meaning to any of these |
| 30 |
levels, merely the opportunity for a subjective evaluation by |
| 31 |
the sender. The receiver (process or person) may do whatever |
| 32 |
they wish with the information. |
| 33 |
|
| 34 |
A user could thereby direct a receiving process to notify him |
| 35 |
immediately of Priority 5 or higher Short mail or any Priority |
| 36 |
10 mail immediately, but defer notification of any other mail. |
| 37 |
(Length is discussed later in this note.) |
| 38 |
|
| 39 |
5. Also, we would like the word, "INTERRUPT", to be changed to |
| 40 |
URGENT or PRIORITY |
| 41 |
|
| 42 |
6. In keeping with offering the sender the opportunity to 'rate' his |
| 43 |
mail, we would like to allow him the chance to warn the receiver of |
| 44 |
the size of the mail. This could be a byte count and/or an |
| 45 |
imprecise SHORT/MEDIUM/LONG. Again, the receiver may use this |
| 46 |
information as he/it sees fit. |
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">D. Crocker & Postel [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc539">RFC 539</a> Thoughts on the <a href="./rfc524">RFC 524</a> Mail Protocol July 1973</span> |
| 55 |
|
| 56 |
|
| 57 |
7. The ID command seems confusing. |
| 58 |
|
| 59 |
If I am a clerk and sending to someone on another host, that |
| 60 |
host may ask me to 'prove' my identity by using an ID. How can |
| 61 |
the Sigma-7 at UCLA-NMC know WHITE's id? He does not have one on |
| 62 |
the Sigma, but certainly should be able to send mail to us |
| 63 |
there. |
| 64 |
|
| 65 |
8. How do ACK's, Progress Reports, or Replies work when there is no |
| 66 |
Reference Serial number? |
| 67 |
|
| 68 |
9. Please include the distinction between Static and Dynamic |
| 69 |
attributes as part of the formal syntax. |
| 70 |
|
| 71 |
10. Though hosts must be allowed to require a login, before they |
| 72 |
will accept mail, would like the Protocol document to reflect a |
| 73 |
negative attitude towards such a requirement. |
| 74 |
|
| 75 |
11. In describing defaults, relatively cryptic phrases such as |
| 76 |
"Author to the Clerk" are sometimes used. Please be a bit more |
| 77 |
clear. |
| 78 |
|
| 79 |
12. The sender is required to send Static, Dynamic, and then |
| 80 |
Optional parameters. |
| 81 |
|
| 82 |
This requires receiving hosts to buffer the contents before |
| 83 |
passing them on to the appropriate recipient. (In fact, before |
| 84 |
finding out whether it can/will accept the mail.) |
| 85 |
|
| 86 |
The order should be: Dynamic, Optional, Static. |
| 87 |
|
| 88 |
By requiring the sending host to transmit the dynamic and |
| 89 |
optional attributes first, the receiving host can also reroute |
| 90 |
mail based upon its Priority and Length. |
| 91 |
|
| 92 |
Now for the hairier problems: |
| 93 |
|
| 94 |
1. We would like to make a strong statement in favor of the |
| 95 |
unified-access (one selector process with one listening socket) |
| 96 |
approach. However, since it does not exist, yet: |
| 97 |
|
| 98 |
The Mail Protocol should NOT be a subsystem of FTP. The Mail |
| 99 |
Protocol USES the File Transfer Protocol, the same as RJE uses |
| 100 |
FTP. We therefore suggest the use of the RJE model. |
| 101 |
|
| 102 |
This unfortunately opens up the issue of logging in, to send |
| 103 |
mail. The advantage of having FTP have a MAIL command is that it |
| 104 |
defines a class of data transfer which many hosts will allow for |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">D. Crocker & Postel [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc539">RFC 539</a> Thoughts on the <a href="./rfc524">RFC 524</a> Mail Protocol July 1973</span> |
| 111 |
|
| 112 |
|
| 113 |
free, while maintaining control over other, 'normal' file |
| 114 |
transfer. |
| 115 |
|
| 116 |
The solution should be the same as that currently used by RJE. |
| 117 |
|
| 118 |
2. The FORWARD function allows a site to receive and hold mail |
| 119 |
during and/or, until a transfer request is received from the |
| 120 |
'recipient' at another host. |
| 121 |
|
| 122 |
This action takes place AFTER receipt of the mail, so we would |
| 123 |
like to suggest a command for "Rerouting" mail just PRIOR to its |
| 124 |
receipt. |
| 125 |
|
| 126 |
This allows a receiving host to refuse a given piece of mail, |
| 127 |
but suggest an alternate receiver. This would be useful if the |
| 128 |
recipient were using another host for a while, or if the |
| 129 |
recipient didn't want to rack up storage charges at the first |
| 130 |
site. |
| 131 |
|
| 132 |
Three variation can occur, one of which will require a special |
| 133 |
MP reply code: |
| 134 |
|
| 135 |
Automatic forwarding: Accept the mail and then |
| 136 |
automatically transfer it to the user's alternate mailbox. |
| 137 |
|
| 138 |
This could be classed as a user "feature" and would |
| 139 |
not be part of the protocol. However, it would be quite |
| 140 |
useful. |
| 141 |
|
| 142 |
Automatic forwarding with copy held: The same as the first |
| 143 |
case, but the transferring server keeps a copy of the mail. |
| 144 |
|
| 145 |
Rerouting without accepting: The mail is never accepted |
| 146 |
from the sender. The sender is, however, informed of an |
| 147 |
alternate mailbox. |
| 148 |
|
| 149 |
The Rerouting information would be in reply to a |
| 150 |
RECIPIENT command. |
| 151 |
|
| 152 |
476 <recipient> IS AT <pathname> |
| 153 |
|
| 154 |
|
| 155 |
|
| 156 |
[ This RFC was put into machine readable form for entry ] |
| 157 |
[ into the online RFC archives by Alex McKenzie with ] |
| 158 |
[ support from GTE, formerly BBN Corp. 10/99 ] |
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="h2"><a class="selflink" id="appendix-D" href="#appendix-D">D</a>. Crocker & Postel [Page 3]</span> |
| 165 |
</pre> |