idnits 2.17.1 draft-ietf-tftpexts-options-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([2], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (December 1994) is 10724 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Unexpected draft version: The latest known version of draft-ietf-tftpexts-options is -00, but you're referring to -02. (However, the state information for draft-ietf-tftpexts-options is not up-to-date. The last update was unsuccessful) Summary: 10 errors (**), 0 flaws (~~), 1 warning (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 draft-ietf-tftpexts-options-00.txt G. Malkin / Xylogics, Inc. 2 TFTP Blocksize Option A. Harkin / Hewlett Packard Co. 3 December 1994 5 TFTP Timeout Interval and Transfer Size Options 7 Abstract 9 The Trivial File Transfer Protocol [1] is a simple, lock-step, file 10 transfer protocol which allows a client to get or put a file onto a 11 remote host. 13 This document describes two TFTP options. The first allows the client 14 and server to negotiate the Timeout Interval. The second allows the 15 side receiving the file to determine the ultimate size of the 16 transfer before it begins. The TFTP Option Extension mechanism is 17 described in [2]. 19 Status of this Memo 21 This document is an Internet-Draft. Internet-Drafts are working 22 documents of the Internet Engineering Task Force (IETF), its areas, 23 and its working groups. Note that other groups may also distribute 24 working documents as Internet-Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 To learn the current status of any Internet-Draft, please check the 32 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 33 Directories on ds.internic.net (US East Coast), nic.nordu.net 34 (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific 35 Rim). 37 Timeout Interval Option Specification 39 The TFTP Read Request or Write Request packet is modified to include 40 the timeout option as follows: 42 +-------+---~~---+---+---~~---+---+---~~---+---+---~~---+---+ 43 | opc |filename| 0 | mode | 0 | timeout| 0 | #secs | 0 | 44 +-------+---~~---+---+---~~---+---+---~~---+---+---~~---+---+ 45 opc 46 The opcode field contains either a 1, for Read Requests, or 2, 47 for Write Requests, as defined in [1]. 49 filename 50 The name of the file to be read or written, as defined in [1]. 51 This is a NULL-terminated field. 53 mode 54 The mode of the file transfer: "netascii", "octet", or "mail", 55 as defined in [1]. This is a NULL-terminated field. 57 timeout 58 The Timeout Interval option, "timeout" (case in-sensitive). 59 This is a NULL-terminated field. 61 #secs 62 The number of seconds to wait before retransmitting, specified 63 in ASCII. Valid values range between "1" and "255" octets, 64 inclusive. This is a NULL-terminated field. 66 For example: 68 +-------+--------+---+--------+---+--------+---+--------+---+ 69 | 1 | foobar | 0 | binary | 0 | timeout| 0 | 1 | 0 | 70 +-------+--------+---+--------+---+--------+---+--------+---+ 72 is a Read Request, for the file named "foobar", in binary transfer 73 mode, with a timeout interval of 1 second. 75 If the server is willing to accept the timeout option, it sends an 76 Option Acknowledgment (OACK) to the client. The specified timeout 77 value must match the value specified by the client. 79 Transfer Size Option Specification 81 The TFTP Read Request or Write Request packet is modified to include 82 the tsize option as follows: 84 +-------+---~~---+---+---~~---+---+---~~---+---+---~~---+---+ 85 | opc |filename| 0 | mode | 0 | tsize | 0 | size | 0 | 86 +-------+---~~---+---+---~~---+---+---~~---+---+---~~---+---+ 88 opc 89 The opcode field contains either a 1, for Read Requests, or 2, 90 for Write Requests, as defined in [1]. 92 filename 93 The name of the file to be read or written, as defined in [1]. 94 This is a NULL-terminated field. 96 mode 97 The mode of the file transfer: "netascii", "octet", or "mail", 98 as defined in [1]. This is a NULL-terminated field. 100 tsize 101 The Transfer Size option, "tsize" (case in-sensitive). This is 102 a NULL-terminated field. 104 size 105 The size of the file to be transfered. This is a NULL- 106 terminated field. 108 For example: 110 +-------+--------+---+--------+---+--------+---+--------+---+ 111 | 2 | foobar | 0 | binary | 0 | tsize | 0 | 673312 | 0 | 112 +-------+--------+---+--------+---+--------+---+--------+---+ 114 is a Write Request, with the 673312-octet file named "foobar", in 115 binary transfer mode. 117 In Read Request packets, a size of "0" is specified in the request 118 and the size of the file, in octets, is returned in the OACK. If the 119 file is too large for the client to handle, it may abort the transfer 120 with an Error packet (error code 3). In Write Request packets, the 121 size of the file, in octets, is specified in the request and echoed 122 back in the OACK. If the file is too large for the server to handle, 123 it may abort the transfer with an Error packet (error code 3). 125 Security Considerations 127 Security issues are not discussed in this memo. 129 References 131 [1] Sollins, K., "The TFTP Protocol (Revision 2)", Request for 132 Comments 1350 (STD 33), October 1992. 134 [2] Malkin, G., Harkin, A., "TFTP Option Extension", Internet Draft, 135 draft-ietf-tftpexts-options-02.txt, December 1994. 137 Authors' Addresses 139 Gary Scott Malkin 140 Xylogics, Inc. 141 53 Third Avenue 142 Burlington, MA 01803 144 Phone: (617) 272-8140 145 EMail: gmalkin@xylogics.com 147 Art Harkin 148 Internet Services Project 149 Information Networks Division 150 19420 Homestead Road MS 43LN 151 Cupertino, CA 95014 153 Phone: (408) 447-3755 154 EMail: ash@cup.hp.com