Hi Randy, The question isn’t about some ( non-RIR ) publication point .. but if the RIPE NCC should support an open publication point .. or a more restricted one.. And I would say that a more restricted version is preferred. ( due to the number of support tickets at the NCC). If you don’t want to use PiP but rather a third party high available fancy publication service .. feel free to do so.. it is just not the question here. Regards, Erik Bais Verstuurd vanaf mijn iPhone
Op 29 sep. 2022 om 18:55 heeft Randy Bush <randy@psg.com> het volgende geschreven:
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
--
To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/routing-wg