Lumen / Level3 filtergen is trimming these routes now. Don't bother trying
to query filtergen.level3.net currently; server is full. Small AS cone does
not equal small societal footprint & impact. While I appreciate the
intention upthread of proxy registering at ATLDB, it really just distracted
On 4/4/2022 7:08 PM, Tom Beecher wrote:
I am an ARIN admin and tech POC for one of the affected ASNs/sets of
prefixes across 2 OrgIDs. I looked back at the messages I've received
that mention NONAUTH or Non-Authenticated. The only thing I've
gotten is
the message originally
Hope this is 40 business hours
--
J. Hellenthal
The fact that there's a highway to Hell but only a stairway to Heaven says a
lot about anticipated traffic volume.
> On Apr 5, 2022, at 22:42, Rubens Kuhl wrote:
>
> For the inclusion of proxy objects in ALTDB for ARIN-NONAUTH, this is
> the
For the inclusion of proxy objects in ALTDB for ARIN-NONAUTH, this is
the current state of objects among known IRRs:
source total obj rt objaut-num obj
On Mon, Apr 4, 2022 at 5:06 PM Kenneth Finnegan
wrote:
>
> Howdy All,
>
> While I agree that it might be politically entertaining to let this
> one blow up as a demonstration of how ARIN conducts business, this
> list of networks includes too many small networks who likely don't
> have a savy
> Kenneth Finnegan wrote on 04/04/2022 21:05:
> > I've taken it upon myself to create
> > proxy registrations for all of these prefixes in ALTDB.
>
> Please don't.
>
Too late, all 394 routes mentioned above are now in ALTDB.
> You're not doing the routing security ecosystem any favours by doing
On 4 Apr 2022, at 8:16 PM, John Gilmore mailto:g...@toad.com>>
wrote:
Let's not undermine one of the few remaining widely distributed (with no
center) technical achievements behind the Internet -- the decentralized
routing system.
I'm on the board of a large legacy allocation that is
Hello Job ,
On Tue, 5 Apr 2022, Job Snijders via NANOG wrote:
...snip...
I think there clearly is an industry-wide trend to move away from
'unsigned plain-text non-authoritative' datasets, towards better sources
of truth such as the VRP data available through the RIR RPKI Trust
Exiting panic mode and stopping to think for a second, the NON-AUTH
entry for this block is already invalid as it was entered by a previous
owner/AS, and it doesn't match the current announcement from the current
AS owner (my customer), so anything relying on NON-AUTH would have
marked this
Job Snijders via NANOG wrote:
> our community also has to be cognizant about there being parts of the
> Internet which are not squatting on anyone's numbers *and* also are
> not contracted to a specific RIR.
Let's not undermine one of the few remaining widely distributed (with no
center)
Thank you very much Job - a customer's block I've had trouble with in
the past is unsurprisingly listed here due to a legacy non-auth IRR
entry. When I first encountered this a few months ago, I was trying to
get modern IRR entries for this block entered into ARIN, and ARIN kept
returning an
>
> Cleaning it up is easy too. Publish an RPKI ROA for your space. We
> will automatically delete any route objects which disagree with an
> RPKI ROA. The routing security ecosystem should be doing that anyways.
>
"should" is a pretty tricky word to be using there.
On Mon, Apr 4, 2022 at 7:21
On Mon, Apr 4, 2022 at 4:04 PM Nick Hilliard wrote:
> Please don't.
>
> You're not doing the routing security ecosystem any favours by doing
> this.
The routing security ecosystem is less of a concern to me than the
lone network engineer at some water district or county who were about
to have a
>
> I am an ARIN admin and tech POC for one of the affected ASNs/sets of
> prefixes across 2 OrgIDs. I looked back at the messages I've received
> that mention NONAUTH or Non-Authenticated. The only thing I've gotten is
> the message originally sent via ARIN-Announce that John forwarded, plus
>
Kenneth Finnegan wrote on 04/04/2022 21:05:
I've taken it upon myself to create
proxy registrations for all of these prefixes in ALTDB.
Please don't.
You're not doing the routing security ecosystem any favours by doing
this. Couple of reasons why: 1. this isn't your data and this is an
On Mon, Apr 04, 2022 at 06:35:31PM -0400, Jon Lewis wrote:
> On Tue, 5 Apr 2022, Job Snijders wrote:
> > > Are others jumping ship or planning to from ALTDB (no offense intended,
> > > and
> > > grateful for the service you've provided) and other non-auth IRRs like
> > > RADB
> > > due to
On Tue, 5 Apr 2022, Job Snijders wrote:
Are others jumping ship or planning to from ALTDB (no offense intended, and
grateful for the service you've provided) and other non-auth IRRs like RADB
due to networks like Tata announcing that they won't honor route objects
created in non-authoratative
Dear Jon, others,
On Mon, Apr 04, 2022 at 05:48:42PM -0400, Jon Lewis wrote:
> On Mon, 4 Apr 2022, Kenneth Finnegan wrote:
> > While I agree that it might be politically entertaining to let this
> > one blow up as a demonstration of how ARIN conducts business, this
> > list of networks includes
On 4/4/2022 11:56 AM, Job Snijders via NANOG wrote:
One might argue "well, folks had more than a year to move their
objects!", but on the other hand, it is entirely possible not all the
right people were reached, or in cases where affected parties did
receive a communication from ARIN, they
On Mon, 4 Apr 2022, Kenneth Finnegan wrote:
Howdy All,
While I agree that it might be politically entertaining to let this
one blow up as a demonstration of how ARIN conducts business, this
list of networks includes too many small networks who likely don't
have a savy networking engineering
Howdy All,
While I agree that it might be politically entertaining to let this
one blow up as a demonstration of how ARIN conducts business, this
list of networks includes too many small networks who likely don't
have a savy networking engineering team.
In my opinion, they are not acceptable
Dear all,
On Sat, Apr 02, 2022 at 09:09:58PM +, John Curran wrote:
> As previously reported here, ARIN will be shutting down the
> ARIN-NONAUTH IRR database on Monday, 4 April 2022 at 12:00 PM ET.
>
> It is quite likely that some network operators will see different
> route processing as a
22 matches
Mail list logo
