Re: draft-yevstifeyev-netblt-iana-00.txt

John C Klensin <klensin@jck.com> Sun, 02 January 2011 18:22 UTC

Return-Path: <klensin@jck.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 E1EA13A69B8 for <tsvwg@core3.amsl.com>; Sun, 2 Jan 2011 10:22:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.512
X-Spam-Level:
X-Spam-Status: No, score=-2.512 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599]
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 A2keUCGoPaVy for <tsvwg@core3.amsl.com>; Sun, 2 Jan 2011 10:22:32 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 1EC953A6925 for <tsvwg@ietf.org>; Sun, 2 Jan 2011 10:22:32 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PZSbW-000FAg-PX; Sun, 02 Jan 2011 13:24:31 -0500
Date: Sun, 02 Jan 2011 13:24:29 -0500
From: John C Klensin <klensin@jck.com>
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: draft-yevstifeyev-netblt-iana-00.txt
Message-ID: <B89227A2634781B89FB3F584@PST.JCK.COM>
In-Reply-To: <4D2048A5.8090106@gmail.com>
References: <A402F767D6FBE228258439B1@[192.168.1.128]> <4D2048A5.8090106@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Mailman-Approved-At: Mon, 03 Jan 2011 08:09:15 -0800
Cc: John C C White <jccw@jccw.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: Sun, 02 Jan 2011 18:22:34 -0000

Mykyta,

This is very encouraging.  Thanks.

best new year's wishes,
   john


--On Sunday, January 02, 2011 11:43 +0200 Mykyta Yevstifeyev
<evnikita2@gmail.com> wrote:

> John, all,
> 
> I have read the document you mentioned (MIL-STD-.....). And
> the only thing I found interesting on these 111 pages is that
> the port number 1 is used for TACO2 and what mentioned in
> section 6.2 of it.
> 
> As for White's draft. If he could kindly allow me to be the
> co-author of the document, I would like to work on this
> document.
> 
> So, as I have applied for adopting my drafts as WG items, I
> ask to mention the corresponding port number (1) for TACO2 in
> /draft-yevstifeyev-netblt-iana/ while publishing it as WG
> draft (if that would be approved).
> 
> All the best,
> Mykyta Yevstifeyev
> 
> 28.12.2010 18:54, John C Klensin wrote:
>> Mykyta,
>> 
>> Are you aware of NetBLT actually being in active use in the
>> public Internet, in the form documented in RFC 998?  I'm not,
>> but that sort of transport protocol isn't something I've paid
>> careful attention to in many years.
>> 
>> John C C White's 1997 Internet-Draft,
>> http://tools.ietf.org/html/draft-white-protocol-stack-00,
>> suggests that, in its original form, NetBLT contained some
>> defects that made it undesirable in practice.  That draft also
>> suggested an update that would align NetBLT with then-current
>> practice in some private (in this case military) network
>> applications.  As far as I can tell, that update never went
>> anywhere in the IETF, but that is (sadly) typical of such
>> things if no one is pushing for it.
>> 
>> Especially if there is not significant evidence of its being
>> in active use in RFC 998 form on the public Internet, it
>> might be worthwhile to combine your effort to get the IANA
>> registry in order with some version or variation on John's
>> draft so as to bring the protocol itself up-to-date.
>> 
>> The information on the standard to which John referred is at
>> http://www.gwg.nga.mil/ntb/baseline/docs/44500/index.html; it
>> doesn't appear to have changed much since his draft was
>> produced.
>> 
>> Even if it isn't useful to try to publish an updated version
>> of the specification, it would probably be desirable to get
>> any non-998 values used by the military standard into the
>> registry as well.
>> 
>> I've copied John on this note.  Since I don't know if he is
>> still at MITRE, I've also copied what is possibly his current
>> address based on a web search.  I have no idea whether he
>> would still be interested, but he should at least be aware
>> that I'm suggesting another look at his 13+ year old work.
>> 
>> best regards and best new year's wishes to both of you,
>>      john
>