[routing-wg] RPKI Route Origin Validation and AS3333

Hi,

On Thu, Mar 18, 2021 at 05:13:06PM +0100, Kurt Kayser wrote:
> but you are assuming that the person trying to access RIPE NCC Service
> is the SAME that is responsible for messing/clearing it up?
> 
> That is for me not necessarily the same person.

Well, this is the case that is relevant here: someone in a given
network cannot access the LIR portal anymore, because of invalid ROA
for their very network, and to *fix* the ROA, this access is needed.  

Catch-22.

Any other sort of "someone messed up routing for someone else, for
some reason" is indeed nothing the RIPE NCC needs to concern themselves
over - but the case above is something that needs consideration and then
a well-communicated decision.

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3603 bytes
Desc: not available
URL: </ripe/mail/archives/routing-wg/attachments/20210318/7793c398/attachment.bin>