IETF Logo Mail Archive

[apps-discuss] Missing IANA Considerations for TFTP

Mykyta Yevstifeyev <evnikita2@gmail.com> Sun, 21 August 2011 09:37 UTC

Return-Path: <evnikita2@gmail.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 EC52821F8ABB for <apps-discuss@ietfa.amsl.com>; Sun, 21 Aug 2011 02:37:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.456
X-Spam-Level:
X-Spam-Status: No, score=-3.456 tagged_above=-999 required=5 tests=[AWL=0.143, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 nhCFrPSuRBUh for <apps-discuss@ietfa.amsl.com>; Sun, 21 Aug 2011 02:37:03 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id D413C21F8AAC for <apps-discuss@ietf.org>; Sun, 21 Aug 2011 02:37:02 -0700 (PDT)
Received: by fxe6 with SMTP id 6so3013150fxe.31 for <apps-discuss@ietf.org>; Sun, 21 Aug 2011 02:38:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=UWS9cJHjs/+clOredrNyK6Mp/e5RjOgI1y48A4ZmTik=; b=PqbiW0+Qh4REAZX1BcdCyD7a7htk7pZg8MhPBJ37fkbaSnN1D8WvPxyty0okMoimVu YOTK5/X2tO+ihIR7CWRpweGzr19Nz/ThySE5PMgkJvaddjw9Hbj0E9YgwAUeNGqXg55R mbRA5hhBIG9TklzJ/5O2wEhuYU6EOEFWCgwXo=
Received: by 10.223.55.205 with SMTP id v13mr1897601fag.88.1313919482406; Sun, 21 Aug 2011 02:38:02 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id d1sm4103065fai.4.2011.08.21.02.37.59 (version=SSLv3 cipher=OTHER); Sun, 21 Aug 2011 02:38:01 -0700 (PDT)
Message-ID: <4E50D21B.1070500@gmail.com>
Date: Sun, 21 Aug 2011 12:38:35 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Apps-discuss list <apps-discuss@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [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: Sun, 21 Aug 2011 09:37:04 -0000

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?

Mykyta Yevstifeyev

v2.37.1 | Report a Bug | By Email | System Status