This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] rfc2770
- Previous message (by thread): [db-wg] rfc2770
- Next message (by thread): [db-wg] rfc2770
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Thu Jun 2 16:07:59 CEST 2022
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
- Previous message (by thread): [db-wg] rfc2770
- Next message (by thread): [db-wg] rfc2770
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]