[zeromq-dev] Virtual Adressing

Laurent Alebarde l.alebarde at free.fr
Wed Jan 15 14:11:21 CET 2014

Le 15/01/2014 12:27, Pieter Hintjens a écrit :
> On Wed, Jan 15, 2014 at 11:55 AM, Laurent Alebarde <l.alebarde at free.fr> wrote:
>> My point is not to create a new document, but to :
>> 1) put the RFC inside the libzmq repository
>> 2) add flags to each requirement
> The RFCs do not belong to libzmq; they are separate documents which
> have multiple implementations. Duplicating the RFCs just leads you to
> confusion. What we could do is remove all speculative aspects from the
> current ZMTP draft and create a new V3.1 RFC with them in.
In my experience in industry, requirements are numbered, and subsequent 
deliveries include a SoC (status of conformance), which is a table with 
the requirement numbers, a conformance status: applicable (A), or not 
(NA), and usually a test status: analysis, code review, test, missing. 
Of course, the SoC starts with the reference and version of the RFC it 

Then you can have with such a quality system RFCs in one unique place as 
today for every implementations - it just need requirements numbering - 
and a SoC included in each implementation. Some copy the requirements in 
the SoC for conveniance (I do), but it is not mandatory. It is also easy 
to read the RFC with the SoC aside, or to write a script to merge them.

Just ideas.

>> The RFC is a very usefull document and it would be nice have the whole (lib
>> + doc + rfc) in perfect sync.
> Sure, I agree. We've not been able to work on the core engine as much
> as we wanted to.
> -Pieter
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20140115/a7411ded/attachment.htm>

More information about the zeromq-dev mailing list