2 Jan 2011 10:43
Re: draft-yevstifeyev-netblt-iana-00.txt
Mykyta Yevstifeyev <evnikita2 <at> gmail.com>
2011-01-02 09:43:01 GMT
2011-01-02 09:43:01 GMT
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:
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
> As you have figured out, my main interest in NETBLT was to use
> it as the core of the TACO2 protocol stack, whose purpose was
> to move large messages (images) over low-bandwidth, mostly
> slow-turnaround half-duplex links. At least 3 independent
> implementations of TACO2 were built, and they were extensively
> tested for interoperability, so I believe that the
> specifications in the MIL-STD and the internet draft are
> pretty complete. I don't know whether anyone is still using
> TACO2, but I'm inclined to suspect not.
>
> Around the time of the internet draft, I had a conversation
> with Allison Mankin, who was then something like director of
> the transport area for the IESG. One concern she expressed was
> that NETBLT could be a bandwidth hog, to the disadvantage of
> other protocol streams. For our application that wasn't a
> problem (it was a feature, actually), and it's not clear to me
> that it's a transport layer issue, but it certainly could be a
> problem elsewhere and deserves some thought.
I assume Allison is following the TSVWG mailing list, but have
copied her on this note just in case (and since I'm not on that
list).
> I'd certainly be happy to see someone else take up NETBLT as a
> project, and will gladly offer whatever support I can as long
> as it doesn't require me to do any actual work!
Thanks. This sort of thing is very much not in my area of
specialty, but I wanted to try to be sure that all possible
connections were made if Mykyta is inclined to do the work to
pursue this. In particular, it seemed to be that, if we were
going to update the registries to reflect the protocol, we
should know its current status and, if someone (presumably
Mykyta) is willing to do the bulk of the work, to update the
base document accordingly.
Allison, given John White's description of the objectives of
TACO2, would there be any advantage of passing this work by the
Delay Tolerant RG? Has that been done already?
Best new year's wishes,
john
)
Bob Braden
>
> I assume Allison is following the TSVWG mailing list, but have
> copied her on this note just in case (and since I'm not on that
> list).
>
>> I'd certainly be happy to see someone else take up NETBLT as a
>> project, and will gladly offer whatever support I can as long
>> as it doesn't require me to do any actual work!
>
> Thanks. This sort of thing is very much not in my area of
> specialty, but I wanted to try to be sure that all possible
> connections were made if Mykyta is inclined to do the work to
> pursue this. In particular, it seemed to be that, if we were
> going to update the registries to reflect the protocol, we
> should know its current status and, if someone (presumably
> Mykyta) is willing to do the bulk of the work, to update the
> base document accordingly.
>
> Allison, given John White's description of the objectives of
> TACO2, would there be any advantage of passing this work by the
> Delay Tolerant RG? Has that been done already?
>
> Best new year's wishes,
> john
>
>
>
RSS Feed