multicast
Senior elf
- Joined
- Jul 13, 2013
- Messages
- 715
We've made it.. E1.31 - 2016 is now a published standard. Its downloadable at the link below.
ANSI E1.31 - 2016, Entertainment Technology - Lightweight streaming protocol for transport of DMX512 using ACN, is a revision of the 2009 standard. It describes a mechanism to transfer DMX512A packets over a TCP/IP network using a subset of the ACN protocol suite. It covers data format, data protocol, data addressing, and network management It also outlines a synchronization method to help ensure that multiple sinks can process this data concurrently when supervised by the same controller. This revision includes DMX512 universe synchronization.
http://tsp.esta.org/tsp/documents/published_docs.php
Its likely that the E1.31 standard will pretty much now sit like this for a long time, with only one small addition which will describe how E1.31 should work in an Ipv6 environment.
The Task Group met on Thursday and started work on the framework for sACN 2. In all likelyhood sACN 2 will be a new protocol. ( we are trying to get e1.61 as our standard number, but we'll have to see ).
Increased universes - we likely will have 2^32 universes
It will be an ipv6 only protocol.
Security will get provided by the protocols that are native in ipv6
packet redundancy flags will be in the header
there will likely be a different mapping of Multicast groups to universes. It probably wont' be the 1:1 mapping we have today.
There is a lot of resistance to changing the size of a universe from 512.. If you feel strongly about this, then you really should be contributing..
ANSI E1.31 - 2016, Entertainment Technology - Lightweight streaming protocol for transport of DMX512 using ACN, is a revision of the 2009 standard. It describes a mechanism to transfer DMX512A packets over a TCP/IP network using a subset of the ACN protocol suite. It covers data format, data protocol, data addressing, and network management It also outlines a synchronization method to help ensure that multiple sinks can process this data concurrently when supervised by the same controller. This revision includes DMX512 universe synchronization.
http://tsp.esta.org/tsp/documents/published_docs.php
Its likely that the E1.31 standard will pretty much now sit like this for a long time, with only one small addition which will describe how E1.31 should work in an Ipv6 environment.
The Task Group met on Thursday and started work on the framework for sACN 2. In all likelyhood sACN 2 will be a new protocol. ( we are trying to get e1.61 as our standard number, but we'll have to see ).
Increased universes - we likely will have 2^32 universes
It will be an ipv6 only protocol.
Security will get provided by the protocols that are native in ipv6
packet redundancy flags will be in the header
there will likely be a different mapping of Multicast groups to universes. It probably wont' be the 1:1 mapping we have today.
There is a lot of resistance to changing the size of a universe from 512.. If you feel strongly about this, then you really should be contributing..