Re: Old transport-layer protocols to Historic?

Mykyta Yevstifeyev <evnikita2@gmail.com> Tue, 11 January 2011 09:19 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 C1B0C3A69F8 for <tsvwg@core3.amsl.com>; Tue, 11 Jan 2011 01:19:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.123
X-Spam-Level:
X-Spam-Status: No, score=-4.123 tagged_above=-999 required=5 tests=[AWL=-0.524, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 RgAlmNjFQuj3 for <tsvwg@core3.amsl.com>; Tue, 11 Jan 2011 01:19:22 -0800 (PST)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by core3.amsl.com (Postfix) with ESMTP id BDF2A3A63EB for <tsvwg@ietf.org>; Tue, 11 Jan 2011 01:19:22 -0800 (PST)
Received: by yie19 with SMTP id 19so6577935yie.31 for <tsvwg@ietf.org>; Tue, 11 Jan 2011 01:21:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=J89ePrRr4zZmA3cpYV3l8iIko0Kl1bRU4nYgFyPNKds=; b=wotHg21GSUGCvnvoBrFaqiLrkBehCMQ5J/RO/e0NdsvTJA/MIvUfct1qx4v4bMC/LP PTNhL0y6Fy/FX8j48ErHYCwd+u0VliqKOobaukRPc0XXhi6CQ6/aFNP+ClkU4F05jlF3 1J2fOTLZiHYmvC1ofYH2N99aJqH4eqISFppQM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ktsezkmRj/TLMKvDSE9dQWYLgMBa3COy/YQvIWjqF3mOyXjbJgXjp/IE6ICHe2+smd 34OA9NbgsxudQlNtJWUpC8jBGNdDqjXoWu18NMItq4S6jqnyeyc+OEUma1Ww6oEE1NTW KeBr+wgufTZLgNqwbw6j8b5Y+UKCywqampcys=
MIME-Version: 1.0
Received: by 10.151.84.11 with SMTP id m11mr7296608ybl.212.1294737698688; Tue, 11 Jan 2011 01:21:38 -0800 (PST)
Received: by 10.150.53.6 with HTTP; Tue, 11 Jan 2011 01:21:38 -0800 (PST)
In-Reply-To: <4D2B4825.5090807@isi.edu>
References: <4D2556C9.9020901@gmail.com> <AFC50009-6908-4AAB-89FB-45C776F40BE2@gmail.com> <4D2842B8.7090100@gmail.com> <4D29556A.6060902@gmail.com> <4D2B4825.5090807@isi.edu>
Date: Tue, 11 Jan 2011 11:21:38 +0200
Message-ID: <AANLkTi=wOurS4rfJrvNH64pn8_RoXrfJ9-HioXG8XeAt@mail.gmail.com>
Subject: Re: Old transport-layer protocols to Historic?
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
To: Bob Braden <braden@isi.edu>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: 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: Tue, 11 Jan 2011 09:19:23 -0000

Bob,

2011/1/10, Bob Braden <braden@isi.edu>:
> The Subject line of this discussion should read: "Experimental
> transport-layer protocols to Historic?"  That might reduce some of the
> confusion.
>
> The questions under discussion seem to be:
> 1.	What are the IANA rules for number assignments to new
> 	Experimental protocols?  (Preumably the same rules would
> 	hold for old Experimental protocols).
Do you think there are some special rules for creation of new
regsitries for experimental protocols? Could you please refer to any
of documents on this topic?
>
> 2. Under what circumstances might (or should) the category of a
> 	Technical Spec be changed from Experimental to Historic?
The same as below.
>
> 	The traditional IETF view, which was handed down from the
> 	Internet Protocol Czar, has been "almost never", and only
> 	when wide use of the experimental protocol might
> 	pose real and present danger to the Internet.  One could
> 	take that view about NETBLT, but personally I think that
> 	would be an over-reaction.
I personally think there is no useful way in moving NETBLT spec to
historic, as well as RDP. I consider that useful only for IRTP. Do you
think there is still a need in such protocol? what has it been made
for?

Mykyta.
>
> Bob Braden
>
>