| 1 |
<pre>Network Working Group A. Emberson |
| 2 |
Request for Comments: 2090 Lanworks Technologies Inc. |
| 3 |
Category: Experimental February 1997 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">TFTP Multicast Option</span> |
| 7 |
|
| 8 |
Status of this Memo |
| 9 |
|
| 10 |
This memo defines an Experimental Protocol for the Internet |
| 11 |
community. This memo does not specify an Internet standard of any |
| 12 |
kind. Discussion and suggestions for improvement are requested. |
| 13 |
Distribution of this memo is unlimited. |
| 14 |
|
| 15 |
Abstract |
| 16 |
|
| 17 |
The Trivial File Transfer Protocol [<a href="#ref-1" title=""The TFTP Protocol (Revision 2)"">1</a>] is a simple, lock-step, file |
| 18 |
transfer protocol which allows a client to get or put a file onto a |
| 19 |
remote host. |
| 20 |
|
| 21 |
This document describes a new TFTP option. This new option will allow |
| 22 |
the multiple clients to receive the same file concurrently through |
| 23 |
the use of Multicast packets. The TFTP Option Extension mechanism is |
| 24 |
described in [<a href="#ref-2" title=""TFTP Option Extension"">2</a>]. |
| 25 |
|
| 26 |
Often when similar computers are booting remotely they will each |
| 27 |
download the same image file. By adding multicast into the TFTP |
| 28 |
option set, two or more computers can download a file |
| 29 |
concurrently, thus increasing network efficiency. |
| 30 |
|
| 31 |
This document assumes that the reader is familiar with the |
| 32 |
terminology and notation of both [<a href="#ref-1" title=""The TFTP Protocol (Revision 2)"">1</a>] and [<a href="#ref-2" title=""TFTP Option Extension"">2</a>]. |
| 33 |
|
| 34 |
Multicast Option Specification |
| 35 |
|
| 36 |
The TFTP Read Request packet is modified to include the multicast |
| 37 |
option as follows: |
| 38 |
|
| 39 |
+--------+----~~----+---+--~~--+---+-----------+---+---+ |
| 40 |
| opc=1 | filename | 0 | mode | 0 | multicast | 0 | 0 | |
| 41 |
+--------+----~~----+---+--~~--+---+-----------+---+---+ |
| 42 |
|
| 43 |
opc |
| 44 |
The opcode field contains a 1, for Read Requests, as defined |
| 45 |
in [<a href="#ref-1" title=""The TFTP Protocol (Revision 2)"">1</a>]. |
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Emberson Experimental [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc2090">RFC 2090</a> TFTP Multicast Option February 1997</span> |
| 55 |
|
| 56 |
|
| 57 |
filename |
| 58 |
The name of the file to be read, as defined in [<a href="#ref-1" title=""The TFTP Protocol (Revision 2)"">1</a>]. This is a |
| 59 |
NULL-terminated field. |
| 60 |
|
| 61 |
mode |
| 62 |
The mode of the file transfer: "netascii", "octet", or |
| 63 |
"mail", as defined in [<a href="#ref-1" title=""The TFTP Protocol (Revision 2)"">1</a>]. This is a NULL-terminated field. |
| 64 |
|
| 65 |
multicast |
| 66 |
Request for multicast transmission of the file option, |
| 67 |
"multicast" (case insensitive). This is a NULL-terminated |
| 68 |
field. The value for this option request is a string of zero |
| 69 |
length. |
| 70 |
|
| 71 |
If the server is willing to accept the multicast option, it |
| 72 |
sends an Option Acknowledgment (OACK) to the client including |
| 73 |
the multicast option, as defined in [<a href="#ref-2" title=""TFTP Option Extension"">2</a>]. The OACK to the client |
| 74 |
will specify the multicast address and flag to indicate whether |
| 75 |
that client should send block acknowledgments (ACK). |
| 76 |
|
| 77 |
+-------+-----------+---+-------~~-------+---+ |
| 78 |
| opc | multicast | 0 | addr, port, mc | 0 | |
| 79 |
+-------+-----------+---+-------~~-------+---+ |
| 80 |
|
| 81 |
opc |
| 82 |
The opcode field contains the number 6, for Option |
| 83 |
Acknowledgment, as defined in [<a href="#ref-2" title=""TFTP Option Extension"">2</a>]. |
| 84 |
|
| 85 |
multicast |
| 86 |
Acknowledges the multicast option. This is a NULL-terminated |
| 87 |
field. |
| 88 |
|
| 89 |
addr |
| 90 |
The addr field contains the multicast IP address. This field |
| 91 |
is terminated with a comma. |
| 92 |
|
| 93 |
port |
| 94 |
The port field contains the destination port of the multicast |
| 95 |
packets. The use of Registered Port number 1758 (tftp-mcast) |
| 96 |
is recommended. This field is terminated with a comma. |
| 97 |
|
| 98 |
mc |
| 99 |
This field will be either 0 or 1, to tell the client whether |
| 100 |
it is the master client, that is, it is responsible for |
| 101 |
sending ACKs to the server. This is NULL-terminated field. |
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Emberson Experimental [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc2090">RFC 2090</a> TFTP Multicast Option February 1997</span> |
| 111 |
|
| 112 |
|
| 113 |
Data Transfer |
| 114 |
|
| 115 |
After the OACK is received by the client it will send an ACK for |
| 116 |
packet zero, as in [<a href="#ref-2" title=""TFTP Option Extension"">2</a>]. With the multicast option being accepted this |
| 117 |
ACK will indicate to the server that the client wants the first |
| 118 |
packet. In other words the ACKs may now be seen as a request for the |
| 119 |
n+1th block of data. This enables each a client to request any block |
| 120 |
within the file that it may be missing. |
| 121 |
|
| 122 |
To manage the data transfer the server will maintain a list of |
| 123 |
clients. Typically the oldest client on the list, from here on |
| 124 |
referred to as the Master Client, will be responsible for sending |
| 125 |
ACKs. When the master client is finished, the server will send |
| 126 |
another OACK to the next oldest client, telling it to start sending |
| 127 |
ACKs. Upon receipt of this OACK the new master client will send an |
| 128 |
ACK for the block immediately before the first block required to |
| 129 |
complete its download. |
| 130 |
|
| 131 |
Any subsequent clients can start receiving blocks of a file during a |
| 132 |
transfer and then request any missing blocks when that client becomes |
| 133 |
the master client. When the current master client is finished, the |
| 134 |
server will notify the next client with an OACK making it the new |
| 135 |
master client. The new master client can start requesting missed |
| 136 |
packets. Each client must terminate the transfer by sending an |
| 137 |
acknowledgment of the last packet or by sending an error message to |
| 138 |
server. This termination can occur even if the client is not the |
| 139 |
master client. |
| 140 |
|
| 141 |
Any subsequent OACKs to a client may have an empty multicast address |
| 142 |
and port fields, since this information will already be held by that |
| 143 |
client. In the event a client fails to respond in a timely manner to |
| 144 |
a OACK enabling it as the master client, the server shall select the |
| 145 |
next oldest client to be the master client. The server shall |
| 146 |
reattempt to send a OACK to the non- responding client when the new |
| 147 |
master client is finished. The server may cease communication with a |
| 148 |
client after a reasonable number of attempts. |
| 149 |
|
| 150 |
Each transfer will be given a multicast address for use to distribute |
| 151 |
the data packets. Since there can be multiple servers on a given |
| 152 |
network or a limited number of addresses available to a given server, |
| 153 |
it is possible that their might be more than one transfer using a |
| 154 |
multicast address. To ensure that a client only accepts the correct |
| 155 |
packets, each transfer must use a unique port on the server. The |
| 156 |
source IP address and port number will identify the data packets for |
| 157 |
the transfer. Thus the server must send the unicast OACK packet to |
| 158 |
the client using the same port as will be used for sending the |
| 159 |
multicast data packets. |
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Emberson Experimental [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc2090">RFC 2090</a> TFTP Multicast Option February 1997</span> |
| 167 |
|
| 168 |
|
| 169 |
At any point if a client, other than the master client, sends a ACK |
| 170 |
to the server, the server will respond with another OACK with the mc |
| 171 |
field holding a value of zero. If this client persists in sending |
| 172 |
erroneous ACKs, the server may send an error packet to the client, |
| 173 |
discontinuing the file transfer for that client. |
| 174 |
|
| 175 |
The server may also send unicast packets to a lone client to reduce |
| 176 |
adverse effects on other machines. As it is possible that machines |
| 177 |
may be forced to process many extraneous multicast packets when |
| 178 |
attempting to receive a single multicast address. |
| 179 |
|
| 180 |
Example |
| 181 |
|
| 182 |
clients server message |
| 183 |
------------------------------------------------------------ |
| 184 |
1 C1 |1|afile|0|octet|0|multicast|0|0| -> RRQ |
| 185 |
2 C1 <- |6|multicast|224.100.100.100,1758,1| OACK |
| 186 |
3 C1 |4|0| -> ACK |
| 187 |
4 M <- |3|1|1| 512 octets of data| DATA |
| 188 |
5 C1 |4|1| -> ACK |
| 189 |
6 M <- |3|2|1| 512 octets of data| DATA |
| 190 |
7 C2 |1|afile|0|octet|0|multicast|0|0| -> RRQ |
| 191 |
8 C2 <- |6|multicast|224.100.100.100,1758,0| OACK |
| 192 |
9 C2 |4|0| -> ACK |
| 193 |
10 C1 |4|2| -> ACK |
| 194 |
11 M <- |3|3|1| 512 octets of data| DATA |
| 195 |
12 C3 |1|afile|0|octet|0|multicast|0|0| -> RRQ |
| 196 |
13 C3 <- |6|multicast|224.100.100.100,1758,0| OACK |
| 197 |
14 C1 |4|3| -> ACK |
| 198 |
15 C2 |4|0| -> ACK |
| 199 |
16 M (except C2) <- |3|4|1| 512 octets of data| DATA |
| 200 |
17 C1 |4|4| -> ACK |
| 201 |
18 M <- |3|5|1| 512 octets of data| DATA |
| 202 |
19 C1 |4|5| -> ACK |
| 203 |
20 M <- |3|6|1| 100 octets of data| DATA |
| 204 |
21 C1 |4|6| -> ACK |
| 205 |
22 C2 <- |6|multicast|,,1| OACK |
| 206 |
23 C2 |4|0| -> ACK |
| 207 |
24 M <- |3|1|1| 512 octets of data| DATA |
| 208 |
25 C2 |4|1| -> ACK |
| 209 |
26 M <- |3|2|1| 512 octets of data| DATA |
| 210 |
27 C2 |4|3| -> ACK |
| 211 |
28 M <- |3|4|1| 512 octets of data| DATA |
| 212 |
29 C2 |4|6| -> ACK |
| 213 |
30 C3 <- |6|multicast|,,1| OACK |
| 214 |
31 C3 |4|2| -> ACK |
| 215 |
32 M <- |3|3|1| 512 octets of data| DATA |
| 216 |
33 C3 |4|6| -> ACK |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Emberson Experimental [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc2090">RFC 2090</a> TFTP Multicast Option February 1997</span> |
| 223 |
|
| 224 |
|
| 225 |
Comments: |
| 226 |
1 request from client 1 |
| 227 |
2 option acknowledgment |
| 228 |
3 acknowledgment for option acknowledgment, |
| 229 |
or request for first block of data |
| 230 |
4 first data packet sent to the multicast address |
| 231 |
7 request from client 2 |
| 232 |
8 option acknowledgment to client 2, |
| 233 |
send no acknowledgments |
| 234 |
9 OACK acknowledgment from client 2 |
| 235 |
15 OACK acknowledgment from client 3 |
| 236 |
16 client 2 fails to receive a packet |
| 237 |
21 client 1 acknowledges receipt of the last block, |
| 238 |
telling the server it is done |
| 239 |
23 option acknowledgment to client 2, |
| 240 |
now the master client |
| 241 |
25 client 2 acknowledging with request for first block |
| 242 |
27 client 2 acknowledges with request for missed block |
| 243 |
29 client 2 signals it is finished |
| 244 |
31 client 3 is master client and asks for missing blocks |
| 245 |
33 client 3 signals it is finished |
| 246 |
|
| 247 |
Conclusion |
| 248 |
|
| 249 |
With the use of the multicast and blocksize[3] options TFTP will be |
| 250 |
capable of fast and efficient downloads of data. Using TFTP with the |
| 251 |
multicast option will maintain backward compatibility for both |
| 252 |
clients and servers. |
| 253 |
|
| 254 |
Security Considerations |
| 255 |
|
| 256 |
Security issues are not discussed in this memo. |
| 257 |
|
| 258 |
References |
| 259 |
|
| 260 |
[<a id="ref-1">1</a>] Sollins, K., "The TFTP Protocol (Revision 2)", STD 33, <a href="./rfc1350">RFC</a> |
| 261 |
<a href="./rfc1350">1350</a>, MIT, July 1992. |
| 262 |
|
| 263 |
[<a id="ref-2">2</a>] Malkin, G., and A. Harkin, "TFTP Option Extension", <a href="./rfc1782">RFC</a> |
| 264 |
<a href="./rfc1782">1782</a>, Xylogics, Inc., Hewlett Packard Co., March 1995. |
| 265 |
|
| 266 |
[<a id="ref-3">3</a>] Malkin, G., and A. Harkin, "TFTP Blocksize Option", <a href="./rfc1783">RFC</a> |
| 267 |
<a href="./rfc1783">1783</a>, Xylogics, Inc., Hewlett Packard Co., March 1995. |
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Emberson Experimental [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc2090">RFC 2090</a> TFTP Multicast Option February 1997</span> |
| 279 |
|
| 280 |
|
| 281 |
Author's Address |
| 282 |
|
| 283 |
A. Thomas Emberson |
| 284 |
Lanworks Technologies, Inc. |
| 285 |
2425 Skymark Avenue |
| 286 |
Mississauga, Ontario |
| 287 |
Canada L4W 4Y6 |
| 288 |
|
| 289 |
|
| 290 |
Phone: (905) 238-5528 |
| 291 |
EMail: [email protected] |
| 292 |
|
| 293 |
|
| 294 |
|
| 295 |
|
| 296 |
|
| 297 |
|
| 298 |
|
| 299 |
|
| 300 |
|
| 301 |
|
| 302 |
|
| 303 |
|
| 304 |
|
| 305 |
|
| 306 |
|
| 307 |
|
| 308 |
|
| 309 |
|
| 310 |
|
| 311 |
|
| 312 |
|
| 313 |
|
| 314 |
|
| 315 |
|
| 316 |
|
| 317 |
|
| 318 |
|
| 319 |
|
| 320 |
|
| 321 |
|
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
Emberson Experimental [Page 6] |
| 333 |
</pre> |