Re: Draft Review Request - IRTP IANA Considerations

Joe Touch <touch@isi.edu> Thu, 06 January 2011 08:00 UTC

Return-Path: <touch@isi.edu>
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 859963A6EF6 for <tsvwg@core3.amsl.com>; Thu, 6 Jan 2011 00:00:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.169
X-Spam-Level:
X-Spam-Status: No, score=-102.169 tagged_above=-999 required=5 tests=[AWL=-0.369, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
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 jmFPiMuK0IlD for <tsvwg@core3.amsl.com>; Thu, 6 Jan 2011 00:00:58 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id BA3EE3A6C5A for <tsvwg@ietf.org>; Thu, 6 Jan 2011 00:00:58 -0800 (PST)
Received: from [192.168.1.90] (pool-71-105-94-39.lsanca.dsl-w.verizon.net [71.105.94.39]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p06821AD012936 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 6 Jan 2011 00:02:13 -0800 (PST)
Message-ID: <4D2576F8.4060402@isi.edu>
Date: Thu, 06 Jan 2011 00:02:00 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
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> <4D25548C.5000800@gmail.com>
In-Reply-To: <4D25548C.5000800@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: gorry@erg.abdn.ac.uk, 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: Thu, 06 Jan 2011 08:00:59 -0000

On 1/5/2011 9:35 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.

I mean moving any of these to historic as well. There is neither a need 
nor a utility to doing this.

Joe