Re: [dispatch] Event Streaming Open Network Draft & BoF Request

Having been a designer of AWS EventBridge and worked with the AWS Managed
Kafka service, I'm reasonably well-exposed to these issues.  I suspect
that (a) a standardized framework such as proposed here would be generally
useful, but (b) it would be a ton of work and I'd be hesitant to take it on
without plausible commitments to put the work in.

The draft is immensely long and the ratio of motivation and evangelism to
specification much too high, but the breakdown of components seems broadly
sane. There are issues, for example: (a) it wouldn’t be OK to require
Kubernetes, or specific programming languages for compliance and (b) the
draft doesn't say anything about message schemas, which are a big and
fairly central problem in these applications.

I'd also wonder to what extent this work is being addressed by the CNCF.

On Sat, Jan 29, 2022 at 4:03 AM Emiliano Spinella <
emiliano.spinella@syndeno.com> wrote:

> Hello everyone,
>
> I have submitted a new draft for discussion:
> https://datatracker.ietf.org/doc/draft-spinella-event-streaming-open-network/
>
> The draft contains several images which are broken in the Datatracker html
> version (still dealing with SVG Tiny 1.2 format). In the meantime, you can
> read the draft including images at:
> https://github.com/syndeno/draft-spinella-event-streaming-open-network
>
> The general idea of an Event Streaming Open Network is to have an open
> framework for the discovery, name resolution and overall communication of
> event streams. The participants of this network could use whatever event
> broker implementation they want. Thus, they would be able to consume and
> produce events independently of the event broker used by their peers.
>
> The document describes the motivation, design and an initial
> implementation of a (free and open) way to connect event streams across
> different network participants. The purpose is to facilitate
> cross-organizational event flow connections over the Internet. This work
> has been highly influenced by the Email architecture and its protocols
> (RFC5321, RFC3501 and RFC6068; among others). Also, it leverages unicast
> DNS-SD for resource discovery (RFC6763).
>
> Although a A BoF request has been submitted for this topic (
> https://datatracker.ietf.org/doc/bofreq-spinella-event-streaming-open-network/)
> I would like to request agenda time for a presentation in Dispatch during
> IETF 113.
>
> I would be happy to hear your feedback about this draft.
>
> Thanks,
> Emiliano
>
>
> *LEGAL NOTICE: The content of this email message, including the attached
> files, is confidential and is protected by article 18.3 of the Spanish
> Constitution, which guarantees the secrecy of communications. If you
> receive this message in error, please contact the sender to inform them of
> this fact, and do not broadcast its content or make copies.*
> **** This message has been verified with removal tools for viruses and
> malicious content ****
> *This legal notice has been automatically incorporated into the message.*
> *---------------------------------------------*
>
> *AVISO LEGAL: El contenido de este mensaje de correo electrónico,
> incluidos los ficheros adjuntos, es confidencial y está protegido por el
> artículo 18.3 de la Constitución Española, que garantiza el secreto de las
> comunicaciones. Si usted recibe este mensaje por error, por favor póngase
> en contacto con el remitente para informarle de este hecho, y no difunda su
> contenido ni haga copias.*
> **** Este mensaje ha sido verificado con herramientas de eliminación de
> virus y contenido malicioso ****
> *Este aviso legal ha sido incorporado automáticamente al mensaje.*
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>