Hello Rich, AS3333 is RIPE NCC's ASN, RIS (the route collector) has AS12654. So this should have no significant impact on RIPE Stat.
Kind regards, Paul. > I am wondering if RIPE will still keep the BGP sessions to peers that feed > the data for RIPEstat unfiltered (no dropping of invalids). It is nice to > have a view of what invalids ASNs are advertising in that tool. I'm > assuming that if they are filtered out, we would lose that visibility. > > -Rich > > On 3/26/21, 10:08 AM, "routing-wg on behalf of Paul Hoogsteder" > <[email protected] on behalf of [email protected]> wrote: > > CAUTION: The e-mail below is from an external source. Please exercise > caution before opening attachments, clicking links, or following > guidance. > > Dear RIPE Routing WG and RIPE NCC, > > after having gone through all responses on the mailing list there > seems to > be unanimous support for RIPE NCC to proceed with the deployment of > "RPKI > Invalid == Reject" policies on the AS 3333 EBGP border. > > Kind regards, > > Job Snijders & Paul Hoogsteder > > > > > E-MAIL CONFIDENTIALITY NOTICE: > The contents of this e-mail message and any attachments are intended > solely for the addressee(s) and may contain confidential and/or legally > privileged information. If you are not the intended recipient of this > message or if this message has been addressed to you in error, please > immediately alert the sender by reply e-mail and then delete this message > and any attachments. If you are not the intended recipient, you are > notified that any use, dissemination, distribution, copying, or storage of > this message or any attachment is strictly prohibited. >
