Multicast (also known as a group address in some context) are used
as a destination address in packets *from* your server, allowing
to reach a group of destinations (the delivery towards the group
is another discussion, as Gert discussed). The source IP must still
be a global unicast. The 233/8 can not solve IPv4 depletion.
MC may not be used as source from your server, neither as a destination
to your server. That's why you can't create a route object.
Rgds
On 2022-06-02 16:08, Max Tulyev via db-wg wrote:
Sure, I know this. Now there is a global lack of IPv4 address space, so
things can be changed. I would like to try. And may be to push some
things globally.
I do not know any example of 233 net usage like it was designed. Are
there any?
02.06.22 16:59, Gert Doering via db-wg пише:
Hi,
On Thu, Jun 02, 2022 at 04:55:12PM +0300, Max Tulyev via db-wg wrote:
May be you know, if you have a 16-bit ASN, you have a /24 IPv4 network
reserved for you for multicast purposes. It is
233.asnum-hi-octets.asnum-lo-octets.0/24:
https://datatracker.ietf.org/doc/html/rfc2770
My ASN is 29632, so the prefix is 233.115.192.0/24
I would like to start using it (well, for testing purposes now). To do
so, I need a route object in the RIPE database.
Multicast networks are not announced in BGP, so, why do you need a route:
object for?
(These addresses must never be used as a source IP, and for destination
resolution, a multicast tree needs to be built by MP-BGP, MSDP, PIM)
Gert Doering
-- NetMaster
--
NetCaT GmbH, Bennogasse 13/5, 1080 Wien
FN 433437 h, Handelsgericht Wien, UID: ATU69635335
GF: Michael Kafka, Georg Kraus
--
To unsubscribe from this mailing list, get a password reminder, or change your
subscription options, please visit:
https://lists.ripe.net/mailman/listinfo/db-wg
