Re: Draft Review Request - IRTP IANA Considerations

Mykyta Yevstifeyev <evnikita2@gmail.com> Wed, 05 January 2011 05:24 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 BDFEB3A67E6 for <tsvwg@core3.amsl.com>; Tue, 4 Jan 2011 21:24:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.838
X-Spam-Level:
X-Spam-Status: No, score=-1.838 tagged_above=-999 required=5 tests=[AWL=-0.998, BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96, 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 Ra0vqdlh1aX8 for <tsvwg@core3.amsl.com>; Tue, 4 Jan 2011 21:24:04 -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 B89183A67A2 for <tsvwg@ietf.org>; Tue, 4 Jan 2011 21:24:03 -0800 (PST)
Received: by bwz12 with SMTP id 12so15065003bwz.31 for <tsvwg@ietf.org>; Tue, 04 Jan 2011 21:26:10 -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:content-transfer-encoding; bh=kLkSpf/QWiBe5C5o6FSuz0UUybMf/hvszQHfDM+O2HY=; b=OBm6AqGaHGn5W3XAga+zwdj1LcDUU+JjRIhLMgi1FHdaWdwxcKDPqXymFuOyL2T8/v 0uDdI4auj1UZ3U+aeaz1CGTRWhfgcPWZRGOrk3k/vQTvAnsk2Q1lJ26i6JcWttCM5zVb bDsh3/13JAKsN/3Jp7d59/pqvEIbzHc7G/mo4=
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:content-transfer-encoding; b=F5Vsx31xvuR5InMsT4IjhIK8+gmpuxFB7BPVcmIZVOf8/m8U1pki43EQHEy+vQv62C yTFIbZD923Vqkd3Nj3nFJ5FtXhNitiPTNW93Yl62Xmqru2IPPvkcL7DNSR2+RZuc29XC y+xWvnW08YhVepBstZFbjflTPvRt4WgJCPxXc=
Received: by 10.204.33.74 with SMTP id g10mr4264151bkd.131.1294205169667; Tue, 04 Jan 2011 21:26:09 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id v1sm12528351bkt.5.2011.01.04.21.26.07 (version=SSLv3 cipher=RC4-MD5); Tue, 04 Jan 2011 21:26:08 -0800 (PST)
Message-ID: <4D240101.6090308@gmail.com>
Date: Wed, 05 Jan 2011 07:26:25 +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: Lars Eggert <lars.eggert@nokia.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>
In-Reply-To: <D3AB3EC9-7C73-4CDA-8702-3B70CD778ED7@nokia.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: gorry@erg.abdn.ac.uk, jmpolk@cisco.com, jccw@jccw.org, tsvwg@ietf.org, Joe Touch <touch@isi.edu>
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: Wed, 05 Jan 2011 05:24:04 -0000

04.01.2011 13:00, Lars Eggert wrote:
> On 2011-1-3, at 21:30, Joe Touch wrote:
>> 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.
> As an individual WG participant, I fully agree with Joe.
Lars

As I have mentioned before, I can agree with this only for IRTP (and 
maybe for RDP), but not NETBLT. I have recently made a draft moving IRTP 
to historic - here is a link

https://datatracker.ietf.org/doc/draft-yevstifeyev-tsvwg-irtp-to-historic/

Maybe there is no doubt that this protocol should be Historic - so could 
you please sponsor the publication of this document as RFC?

Mykyta
> Lars