Hi All! 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. How can I create it?
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 -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
Gert Doering via db-wg wrote on 02/06/2022 14:59:
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)
GLOP was only ever experimental to start with, and is not relevant to SSM - hopefully Max you're not using ASM. I don't think there was ever any scope to include it in the RIR assignment mechanism, and given that it breaks with ASN32, its status as experimental + lack of support in the RIRs are unlikely to change in future. Nick
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
Hi, On Thu, Jun 02, 2022 at 05:08:36PM +0300, 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?
This is multicast. It will not work as unicast. And, the GLOP RFC does not authorize use as anything else but multicast. Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
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?
Yes, there are. If you want to re-assign 233/8 to unicast usage, I suggest this be done the proper way (through the IETF and IANA), not just by sqatting on it with a different type of usage and trying to intimidate others to dance to your pipe. Regards, - Håvard
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
participants (5)
-
Gert Doering -
Havard Eidnes -
Max Tulyev -
Michael Kafka -
Nick Hilliard