Re: Draft Review Request - IRTP IANA Considerations

Mykyta Yevstifeyev <evnikita2@gmail.com> Fri, 07 January 2011 06:06 UTC

Return-Path: <evnikita2@gmail.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E37F33A67B7 for <tsvwg@core3.amsl.com>; Thu, 6 Jan 2011 22:06:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.76
X-Spam-Level:
X-Spam-Status: No, score=-2.76 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wnZ8qEsLnlJT for <tsvwg@core3.amsl.com>; Thu, 6 Jan 2011 22:06:18 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 4CFB63A67B1 for <tsvwg@ietf.org>; Thu, 6 Jan 2011 22:06:18 -0800 (PST)
Received: by bwz12 with SMTP id 12so16950599bwz.31 for <tsvwg@ietf.org>; Thu, 06 Jan 2011 22:08:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type; bh=81rGhDVaks/3L9osXWeztvjif/N+4LbPRl0wdf3jY3I=; b=m6QwofpqjbHkEAp0/COXUJvPjkb7ZYu5US0O8Cu/r83gd/Xex8dPARIfHaTZcvjYSK lMpvSe4zDqTXe6VDQ2FbLdYpFgfuGOINGmBTja9/PBuR316BWiDfESFTn0uUFZING1XK v+KBargPRltmW0Sg8AJ76HWP2/onUC8WC9FZs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; b=GJCEF2dneHXNtgPAy++3/1skvBi/BbM85cXQP5QSt4X7HAGKhMJTH5Owhsqkmbmepd sKsGK6YFqqX7wFQMmbzzoCg9AlnFIZ9Gw5DHoklwVVqetcAEePu6holMpP7UkRI5L2fH 7BXhWt5e50reVsqaU9QBcYKGTtdMF2f2emCek=
Received: by 10.204.53.148 with SMTP id m20mr3103413bkg.150.1294380504435; Thu, 06 Jan 2011 22:08:24 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id v25sm13843872bkt.6.2011.01.06.22.08.22 (version=SSLv3 cipher=RC4-MD5); Thu, 06 Jan 2011 22:08:23 -0800 (PST)
Message-ID: <4D26ADE8.5080001@gmail.com>
Date: Fri, 07 Jan 2011 08:08:40 +0200
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Draft Review Request - IRTP IANA Considerations
References: <4D1715BE.6040100@gmail.com> <4D199D89.4080508@gmail.com> <00eb01cba6a5$b5606840$4001a8c0@gateway.2wire.net> <4D1D6EB3.40803@gmail.com> <4D2223E4.2040104@isi.edu> <D3AB3EC9-7C73-4CDA-8702-3B70CD778ED7@nokia.com> <4D240101.6090308@gmail.com> <5131531F-D1E6-44F1-8FC0-94CBCF6CC2A8@isi.edu> <024801cbaccd$e347d580$4001a8c0@gateway.2wire.net> <4D2554F8.7060201@gmail.com> <4D257766.7060808@isi.edu> <4D25A0BC.9050505@gmail.com> <84DCE00C-E6FE-4148-9ADB-A573672DC5F0@isi.edu>
In-Reply-To: <84DCE00C-E6FE-4148-9ADB-A573672DC5F0@isi.edu>
Content-Type: multipart/alternative; boundary="------------060401030108000703070100"
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "tsvwg@ietf.org" <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jan 2011 06:06:20 -0000

06.01.2011 18:01, Joe Touch wrote:
> On Jan 6, 2011, at 3:00 AM, Mykyta Yevstifeyev<evnikita2@gmail.com>  wrote:
>
>> 06.01.2011 10:03, Joe Touch wrote:
>>> On 1/5/2011 9:36 PM, Mykyta Yevstifeyev wrote:
>>> ...
>>>>>> Maybe there is no doubt that this protocol should be Historic - so
>>>>>> could you
>>>>> please sponsor the publication of this document as RFC?
>>>>>
>>>>> There us also neither a need nor a utility. Is there some other reason
>>>>> you ate
>>>>> trying so hard to get an RFC published?
>>>> If you mean IRTP IANA Considerations, I have asked to withdraw it. Now I
>>>> propose tsvwg-irtp-to-historic-00. Moreover, I think that would be OK
>>>> for RDP too.
>>> This too has no need nor utility.
>>>
>>> They're experimental. They're outdated and not in use. They're not being replaced with anything. There's no point in doing *anything* associated with *any* of these protocols (IRTP, NETBLT, RDP).
>> But there will be no harm if we mark them as Historic. That would just indicate that they are deprecated.
> The harm is the time and resources you're wasting on what really does look like a desperate attempt to write an RFC - any RFC.
>
> You need to explain why these protocols *need* to be deprecated, and why that has to happen now, *except* as a way to stop you from chasing useless IANA support for these protocols.
Dear Joe,

Firstly, what draft we are speaking about? I consider the topic we are 
discussing to be 'moving old transport protocols to Historic'. So why 
you talk about IANA considerations for that?

Moreover, let me cite your message I received before:

> That's the key. This (and the other protocols you wrote similar docs 
> for, e.g., NETBLT and RDP) don't use IANA-assigned values. They have 
> values, but there was not a need for a registry for several reasons, 
> including the fact that they were experimental.
>
> At this point, they might be *better moved to historic* than anything 
> else. There's no reason to have IANA track or manage their values.
>
> Joe 
So on 3 January you say that they should be moved to Historic and now, 
after 3 days that there no need for this. Could you please claim your 
opinion clearly?

Lastly, toy said: "You need to explain why these protocols *need* to be 
deprecated, and why that has to happen now". Let me explain this issues. 
They are *already* deprecated and my draft explains reasons that caused 
it clearly. Read it please carefully.

All the best,
Mykyta Yevstifeyev
> Joe