Re: [apps-discuss] Missing IANA Considerations for TFTP
"t.petch" <ietfc@btconnect.com> Mon, 22 August 2011 08:43 UTC
Return-Path: <ietfc@btconnect.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BABB321F8AD1 for <apps-discuss@ietfa.amsl.com>; Mon, 22 Aug 2011 01:43:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.445
X-Spam-Level:
X-Spam-Status: No, score=-2.445 tagged_above=-999 required=5 tests=[AWL=0.154, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 95HM9zOtVB1y for <apps-discuss@ietfa.amsl.com>; Mon, 22 Aug 2011 01:43:56 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr10.btconnect.com [213.123.26.188]) by ietfa.amsl.com (Postfix) with ESMTP id BF0FD21F8ACC for <apps-discuss@ietf.org>; Mon, 22 Aug 2011 01:43:55 -0700 (PDT)
Received: from host109-153-79-81.range109-153.btcentralplus.com (HELO pc6) ([109.153.79.81]) by c2beaomr10.btconnect.com with SMTP id EAB68997; Mon, 22 Aug 2011 09:44:52 +0100 (BST)
Message-ID: <011f01cc609e$e02dd0e0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: Mykyta Yevstifeyev <evnikita2@gmail.com>, Apps-discuss list <apps-discuss@ietf.org>
References: <4E50D21B.1070500@gmail.com>
Date: Mon, 22 Aug 2011 09:41:09 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4E521704.004B, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.8.22.80018:17:7.586, ip=109.153.79.81, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __FRAUD_BODY_WEBMAIL, __URI_NO_WWW, __URI_NO_PATH, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_1000_1099, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_2000_LESS, __FRAUD_WEBMAIL, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0207.4E52170A.00BC, ss=1, fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
Subject: Re: [apps-discuss] Missing IANA Considerations for TFTP
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 08:43:56 -0000
----- Original Message ----- From: "Mykyta Yevstifeyev" <evnikita2@gmail.com> To: "Apps-discuss list" <apps-discuss@ietf.org> Sent: Sunday, August 21, 2011 11:38 AM > Hello all, > > Trivial File Transfer Protocol (TFTP), which is defined in RFC 1350 > (that is currently at Full Standard level, BTW), makes use of several > values which are to be tracked by IANA. They include: OpCode values, > transfer modes, error codes, and option numbers (see RFC 2347 for > description of the latter). However, currently IANA doesn't maintain > any registries related to TFTP, neither can I find any in RFC 1700, the > last of "Assigned Numbers" series. Correspondingly, the question: Is > it useful to write and publish the document defining IANA considerations > for TFTP? No. Dead protocol in the sense that it is not one that the IETF has worked on for decades. Now an I-D which declared it Historic, for some meaning of Historic, that might be interesting .... Tom Petch > > Mykyta Yevstifeyev
- [apps-discuss] Missing IANA Considerations for TF… Mykyta Yevstifeyev
- Re: [apps-discuss] Missing IANA Considerations fo… Frank Ellermann
- Re: [apps-discuss] Missing IANA Considerations fo… Mykyta Yevstifeyev
- Re: [apps-discuss] Missing IANA Considerations fo… Harald Alvestrand
- Re: [apps-discuss] Missing IANA Considerations fo… John C Klensin
- Re: [apps-discuss] Missing IANA Considerations fo… t.petch
- Re: [apps-discuss] Missing IANA Considerations fo… Frank Ellermann