Paul, FWIW, my advice on writing protocol specs is not to place them in the public domain (which has no legal meaning in many countries) but to license them under the GPL. This ensures that extensions to your protocol are published. (The protocol license obviously has no impact on software that implements it.)
You may find the templates at rfc.zeromq.org useful. They come from the Digital Standards Organization (www.digistan.org). If you really want to allow people to create closed extensions, then you might use CC0 (http://creativecommons.org/publicdomain/zero/1.0/). -Pieter On Thu, May 31, 2012 at 11:42 PM, Paul Colomiets <[email protected]> wrote: > Hi, > > I'm starting new thread to bring more attention. > > Here is brief description of the protocol structure: > > https://github.com/tailhook/estp/blob/master/specification.rst > > It's currently under-specified, because I want to settle basic > structure, before diving into deep description of the details. > > -- > Paul > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
