|
From: Alexander <ale...@ne...> - 2002-11-04 09:26:21
|
> 1) Convert the current documentation text file to RFC2629 format. > RFC2629 specifies an xml dtd for Internet Drafts and RFC documents. > There are tools to convert from the format to correctly formatted text > as well as HTML at http://xml.resource.org/ Yup, sounds like the way to go. I suspect there are good tools to convert this XML to txt? > 2) Ask pesky questions to this list about everything in the > specification that I can think of being non-optimal or unclear. :) > 3) Extend the documentation so that it can be used as an guide for > protocol implementors, with information from the creators, of course I see two things that really need documentation. 1) The protocol and implementation techniques. 2) The gstplib implementation. > 4) Write a very simple command-line file GSTP client that works a bit > like GNU wget without even looking at the reference implementation. If i > succeed we can know that the specification serves it's purpose. Having a > secondary independent implementation of the protocol is also good when > we want to promote the protocol as an Internet standard (RFC). gstpget(1) seems like a very suitable project. In theory you could use gstplib, but from a RFC-suitability standpoint, this would not be the best way to go. > What do you fellows think about this plan? I must once again warn you > that I don't have much time to put in, but i guess something is better > than nothing. GSTP is a slow moving project anyway.. there's no rush :) //Alexander |