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/routing-wg@ripe.net/
[routing-wg] Publish in Parent - input requested
- Previous message (by thread): [routing-wg] Publish in Parent - input requested
- Next message (by thread): [routing-wg] Publish in Parent - input requested
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Thu Sep 29 18:43:01 CEST 2022
> If you ask me, publishing at the RIR that also provided the resources > should be the only way … nope. consider that someone could put up a highly reliable publication service and i might want to use it. the protocols were designed specifically to accommodate a variety of publishers. > As a community we have been dealing with objects in the RIPE DB for > years ( and still have, if you look at the RIPE NON-Auth issues ) > .. and I would like to avoid any pollution. RPKI != IRR > If a particular member is both an ARIN and RIPE member, and everything > is published to the RIPE parent .. and at some day, the RIPE > membership is stopped.. the ARIN resources will also not be accepted > anymore .. And this will have similar scenario’s the other way around if i run a CA, i can choose where i publish. my memory is that i can not choose to publish some produced objects in one PP and others in another PP. but my memory is not what it used to be. > It isn’t called .. Publish in Parent for no reason correct. it is to differentiate a particular instance of publish arbitrarily, which is what the protocols provide. randy
- Previous message (by thread): [routing-wg] Publish in Parent - input requested
- Next message (by thread): [routing-wg] Publish in Parent - input requested
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]