Re: [apps-discuss] Missing IANA Considerations for TFTP

[Harald Alvestrand <[e-mail]>]

TFTP is a protocol of ultimate stupidity^^^^naivete, made for a simpler 
and less paranoid world; why do you want to touch it at all?

As to why the protocol action from May 1998 does not mention IANA 
considerations - this was before the IANA considerations got completely 
institutionalized - RFC 2434 was still 5 months in the future.

My very vague memory of this action was that it was a personal effort 
from Gary Malkin to promote to Draft the useful parts of the results of 
the expired TFTP group, hoping eventually to be on the same level 
(Standard) as the base spec. Note that these are advancement-in-grade 
RFCs; the Proposed Standard versions were published in 1995.

My recommendation: It's been 15 years or more since someone really cared 
about these non-registries. Let this particular corpse sleep in peace.

                         Harald

On 08/22/2011 06:18 AM, Mykyta Yevstifeyev wrote:
> 21.08.2011 20:49, Frank Ellermann wrote:
>> On 21 August 2011 11:38, Mykyta Yevstifeyev wrote:
>>
>>> currently IANA doesn't maintain any registries related to TFTP
>> Arguably "bootp-dhcp-parameters" is related, maybe TFTP assignments
>> could be merged into this existing registry.
>
> I had a look at this registry - it isn't related to TFTP in any way 
> other than listing several DHCP options related to TFTP.
>
>>
>>> Is it useful to write and publish the document defining IANA
>>> considerations for TFTP?
>> The authors of RFCs 2347..2349 apparently decided that it was not
>> necessary to create TFTP registries in 1998.  Only a wild guess,
>> "missing" IANA considerations cannot say why they are "missing".
>> Did you look into old mailing list archives?
>
> Well, the only WG ever chartered and related to TFTP is some way is 
> tftpext, which produced RFCs 1782-1784 
> (http://tools.ietf.org/wg/tftpexts/).  IETF site has no archives; 
> neither have some non-IETF archives (I found 
> http://mirrors.fe.up.pt/pub/rfc/concluded-wg-ietf-mail-archive/tftpexts/ 
> and 
> http://ftp.sh.cvut.cz/MIRRORS/ietf/concluded-wg-ietf-mail-archive/tftpexts/).  
> The original mailing list was hosted at hpindsh.cup.hp.com and 
> original archive was placed at 
> onet2.cup.hp.com/pub/dist/tftpexts/tftpexts_archive (see 
> http://webcache.googleusercontent.com/search?q=cache:xueLfMKFuxoJ:ftp://ftp.ietf.org/ietf-online-proceedings/94dec/area.and.wg.reports/app/tftpexts/tftpexts.malkin.slides.ps+Tftpexts+mailing+archive&cd=1&hl=en&ct=clnk&client=firefox&source=www.google.com).  
> However, none of those servers responded to me; so I conclude it is 
> impossible to find tftpext archives.
>
> RFCs 2347..2349 were Individual Submissions, and their only purpose, I 
> guess, was to advance tftpext stuff to Draft Standard.
>
> IESG "protocol action" message 
> (http://www.ietf.org/mail-archive/web/ietf/current/msg05939.html) 
> doesn't have the "community consensus" section, which would point me 
> to some discussion forum.  It mentions, though, that IESG contact 
> person is Harald Alvestrand, whom I'm cc'ing this message to supposing 
> he has some additional info for this topic.
>
> So now I have no idea why TFTP IANA considerations are missing.
>
>>
>> If it is a general IANA registry problem let's discuss it on the
>> "happy IANA" list.  The service-names-port-numbers.xml is *huge*,
>> but the TFTP ports, four SUBNTBCST_TFTP variants, tftp-mcast,
>> etftp, and tftps are listed.  But this registry doesn't tell me
>> what ETFTP, TFTPS, etc. really was or is.
>
> I guess the situation is:
>
> tftp - RFC 1350;
> subntbcast-tftp - have no idea what is stands for;
> tftps - I suppose this is used with something like an "adaptation of 
> 4217 for TFTP";
> tftp-mcast - 
> https://datatracker.ietf.org/doc/draft-koren-tftp-multicast-option/; 
> https://datatracker.ietf.org/doc/draft-rfced-exp-yung/;
> etftp - RFC 1986; http://www.networksorcery.com/enp/protocol/etftp.htm.
>
> Mykyta Yevstifeyev
>
>>
>> -Frank
>>
>
>