Submit it as an internet-draft, as described at www.ietf.org (subscribe to the ietf-announce mailing list to see drafts posted.) On Wed, 26 Jun 2002, Thomas J. Hruska wrote: > Date: Wed, 26 Jun 2002 00:21:13 -0400 > From: Thomas J. Hruska <shinelight@shininglightpro.com> > To: ietf@ietf.org > Subject: Process of submitting an RFC for review... > > Hello, I am the lead developer for Shining Light Productions and over the > past two years I have worked with the various RFCs covering a variety of > protocols. As a developer, I have made several connections that include > the fact that every single protocol is very similar in nature (if not > exactly the same). > > As a result of working with those RFCs, I have prepared a document that > describes a fairly simple overview of a Unified RFC Protocol that combines > and brings all of the various, "disconnected" RFCs into one framework from > which the IETF and developers can easily work from. It preserves current > and historical (ancient) protocols and describes a framework for a general > communication protocol. > > My question is this: Where should I go and how do I start the process of > getting an official RFC created? The document I have is a start, but will > hardly get the coverage needed for acceptance by the industry. > > > Thomas J. Hruska -- shinelight@shininglightpro.com > Shining Light Productions -- "Meeting the needs of fellow programmers" > http://www.shininglightpro.com/ > > - > This message was passed through ietf_censored@carmen.ipv6.cselt.it, which > is a sublist of ietf@ietf.org. Not all messages are passed. > Decisions on what to pass are made solely by Raffaele D'Albenzio. > <http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@surrey.ac.uk>