[zeromq-dev] suggestion for two more Guide examples

[Wes Young]

fwiw:

sometime within the next six months or so; we[1] should have a decent set of examples in the security space demo'ing this functionality. Right now we're building google protobufs and thrift bufs for a few security protocols (IDMEF, IODEF, ICSG and MAEC). This is what sort of drove the previous libzfl and device discussion. I would imagine building some generic code to handle these serialization cases being built into the devices (libzfl for instance). Same with some of the certificate based crypto code.. I know the ZeroMQ-perl does something neat with serialization hooks already, just needs some better hooks at the C level (unless i'm missing them…).

Too many people (in the security space) gave up on these protocols (mainly IETF RFC's) due to their complexity. We're working (via the NSF) to capitalize on their "international standard-ness" and lower the barrier to entry so they're usable at faster data-rates (rather than everyone defining their own key-pair 'protocol') and then not being able to exchange data in the international security space.

[1] https://github.com/collectiveintel

On Feb 27, 2012, at 4:30 PM, Pieter Hintjens wrote:

> Actually this is a really nice idea and could lend itself to a
> 0MQ-specific serialization layer.

--
Wes
claimid.com/wesyoung