Re: Multicasting addresses

Hi xtof and all,

> For the rulebook on address assigment, see
> http://www.iana.org/assignments/multicast-addresses.
Hmmm,
"Addresses within the 232.0.1.0-232.255.255.255 are dynamically 
allocated by hosts when needed [RFC4607]"

Does this mean that 232.144.144.X
with X=0 to 255 could be a good choice for Linrad?
(easy management of an integer 0-255 in a par file)

> Regarding the use of fixed address and port numbers. The question
> is, do we want to keep compatibility with the existing multicast
> capable network MBONE that is an overlay on the current IPv4 net.
> If you want to retain compatibility with that net you need to
> dynamically request a session address/port and advertise is in
> the "multicast directory" that has by itself a group address,
> using the service annoucement protocol.
> (for those interested in the current MBONE, see Mantra
> http://www.caida.org/tools/measurement/Mantra/topology/topology.html)
Sorry, I do not understand anything of this

> My feelings is with current state of Linrad technology and
> the bandwidth required we will exclusively use this on the
> LAN, or within locally closed user environments. In that case
> it is good practice to use locally scoped multicast address
> space as per RFC2365 (just like our local 192.168. IPv4 addresses).
> This range is 239.255.0.0/16.
So you say Linrad should use 239.255.0.X with X=0 to 16.