Discussion in 'The Family Room' started by multicast, Jan 27, 2017.
sorry but im dumb- pass dont get it
cheers Boof63 :-\ :-\
makes 2 of us...
Being a computer geek.
Would it be 255 or 11111111?
We had a E131 task Group meeting today, One of the thigns we did was allocate the multicast address's for sACN over Ipv6
Its likely to be FF03::83:00:00:00/16 The last two bytes will get used exactly the same as they do in ipv4. to map your 64000 odd universes to. The 3rd least significant byte is reserved.. ( it gives us 8 more bits for some trickery later ), and we picked 83, becuase we needed to use *something*.
The address's likely will be a from the link-local scope ( same as ipv4 ) and ( thats what the 03 is ).. FF on teh front means its multicast.
We need to do some research to confimr that link-local scope is the correct thing to do. What this means is that multicast packets will not cross a l3 routed boundary without being routed.. ( if they were org-local scope they can cross those boundarys without it being routed ). Its a subtle but important thing for us to determine.
As usual, the invitation is always out there for someone else to join the CPWG, it woudl awesome for someone from this community ( I suspect the Blinkys are probalby the biggest user-group of this standard )... to join.
Separate names with a comma.