Scope

An OSS implementation of the IEEE 1722 standard that runs on Linux in user space

Fit to COVESA

IEEE1722 (AVTP) is a very "automotive" technology to transport or tunnel various data formats in a vehicle. Compared to high level protocols such as SOME-IP or DDS, 1722 is a layer-2 protocol, that emphasizes simplicity and performance.  For certain applications it can even be implemented "in hardware" without the need for a microcontroller running a full stack.

Gap

The proposed project will greatly change and extend the scope of an existing project https://github.com/Avnu/libavtp that is not active anymore, and merely focusses on the audio/video ports, but leaves out automotive relevant things such as CAN. The goal is to make this transparent by forking form the original repository.

This is allowed, as the original is licenses under a 3-clause BSD license.

The goal is to keep the license as 3-clause BSD, as it is very permissive. (Except making it easy to apply it commercially, it also fully compatible with Apache-2.0 license used by many "new" SDV projects or MPL license used core COVESA projects)

Questionnaire for the Project:

What is the purpose of the project?

Open1722 is intended to be an open source userspace implementation of the IEEE 1722 standard that defines the Audio/Video Transport Protocol (AVTP).
Despite its name, the protocol covers the transport of data beyond audio and video formats, such as automotive fieldbus technologies like CAN, LIN, etc. over a layer 2 Ethernet network.
This protocol is gaining traction in the automotive domain because, compared to higher-level protocols such as SOME/IP or DDS, it is well suited for transporting data to and from extremely resource-constrained devices, or even for full hardware implementation. 

Use cases include tunneling of fieldbuses over an Ethernet network across domains/zones, remote control of deeply embedded sensors/actuators etc.

What is the intended outcome/deliverable of the project?

Open1722 intends to be a full implementation of the IEEE 1722-2016 standard.
Eventually the implementation maybe updated to cover the newer releases of the standard.

How will the project be licensed?

The project will be forked from AVNU/libavtp which is licensed under 3-clause BSD.
Open1722 will retain the license and continue to make the implementation available under 3-clause BSD.

Who are the maintainers/leads?

Naresh Nayak - Robert Bosch GmbH
Adriaan Niess - Robert Bosch GmbH

What other companies/contributors are likely to be involved?

Bosch & ETAS are expected to kickstart the development and initial maintenance.

What will be the way of working for the project?

Open1722 will be developed following the OSS best practices.
Contributions are welcome from the automotive community via pull requests. 
These will be reviewed on a timely basis before being merged in the codebase.