On Sat, Feb 9, 2019 at 9:09 PM Christopher Morrow
wrote:
> I wonder if there's a lurking verizon/701 engineer on-list who may have a
> few moments to reach me out of band? :) I've got what looks like busted
> routing (or
>
howdy! actually 3 different vz folk found me, explained what I'm seeing
On 11/Feb/19 16:53, Jay Borkenhagen wrote:
> FYI:
>
> The AT/as7018 network is now dropping all RPKI-invalid route
> announcements that we receive from our peers.
>
> We continue to accept invalid route announcements from our customers,
> at least for now. We are communicating with our
Job Snijders writes:
> Dear Jay, AT,
>
> On Mon, Feb 11, 2019 at 09:53:45AM -0500, Jay Borkenhagen wrote:
> > The AT/as7018 network is now dropping all RPKI-invalid route
> > announcements that we receive from our peers.
>
> Thanks for filtering us! :-)
Any time! :-)
> If you can share
valdis.kletni...@vt.edu writes:
> On Mon, 11 Feb 2019 09:53:45 -0500, Jay Borkenhagen said:
> > The AT/as7018 network is now dropping all RPKI-invalid route
> > announcements that we receive from our peers.
>
> Congrats!
Thanks!
> Are you able to comment on what amount of routes are
Compton, Rich A writes:
> That's great! Do you guys have plans to publish ROAs for your own
> netblocks? If so, can you please share info on your process (tools,
> pitfalls, etc.)? Thanks!
>
Hi Rich,
We do have ROAs published for a not insignificant fraction of our
address space. For
On Mon, 11 Feb 2019 09:53:45 -0500, Jay Borkenhagen said:
> The AT/as7018 network is now dropping all RPKI-invalid route
> announcements that we receive from our peers.
Congrats!
Are you able to comment on what amount of routes are getting dropped?
This is the best news today! Great job!!
Cheers,
Melchior
On Mon, Feb 11, 2019 at 3:56 PM Jay Borkenhagen wrote:
>
> FYI:
>
> The AT/as7018 network is now dropping all RPKI-invalid route
> announcements that we receive from our peers.
>
> We continue to accept invalid route announcements from
That's great! Do you guys have plans to publish ROAs for your own netblocks?
If so, can you please share info on your process (tools, pitfalls, etc.)?
Thanks!
On 2/11/19, 7:55 AM, "NANOG on behalf of Jay Borkenhagen"
wrote:
FYI:
The AT/as7018 network is now dropping all
Jay & everyone AT: I just want to say thank you. Kudos to your team for
implementing and management for having the intestinal fortitude to do so.
--
TTFN,
patrick
> On Feb 11, 2019, at 09:53, Jay Borkenhagen wrote:
>
>
> FYI:
>
> The AT/as7018 network is now dropping all RPKI-invalid route
Dear Jay, AT,
On Mon, Feb 11, 2019 at 09:53:45AM -0500, Jay Borkenhagen wrote:
> The AT/as7018 network is now dropping all RPKI-invalid route
> announcements that we receive from our peers.
Thanks for filtering us! :-)
AT doing origin validation combined with the peerlock-style AS_PATH
filters
A round of applause to AT for leading the way!
Best regards,
Martijn
On 2/11/19 3:53 PM, Jay Borkenhagen wrote:
> FYI:
>
> The AT/as7018 network is now dropping all RPKI-invalid route
> announcements that we receive from our peers.
>
> We continue to accept invalid route announcements from our
On Mon, Feb 11, 2019 at 6:55 AM Jay Borkenhagen wrote:
>
> FYI:
>
> The AT/as7018 network is now dropping all RPKI-invalid route
> announcements that we receive from our peers.
>
> We continue to accept invalid route announcements from our customers,
> at least for now. We are communicating
FYI:
The AT/as7018 network is now dropping all RPKI-invalid route
announcements that we receive from our peers.
We continue to accept invalid route announcements from our customers,
at least for now. We are communicating with our customers whose
invalid announcements we are propagating,
On 11/Feb/19 16:21, Mikael Abrahamsson wrote:
>
> Speaking of an Asia-Pac example, Thailand, the government owned telco.
>
>
On Mon, 11 Feb 2019, Mark Tinka wrote:
We have the same problem here in Africa too (and I saw it in Asia-Pac
while I was there as well)... non-telco-centric companies that deployed
Speaking of an Asia-Pac example, Thailand, the government owned telco.
On 11/Feb/19 15:55, Mikael Abrahamsson wrote:
>
>
> If they had just stayed at the L1 level and provided dark fiber for
> the amount of money mentioned before (for instance 10-15 EUR a month)
> then a lot of the problems wouldn't be there. They could have used the
> same organisation as
On Mon, 11 Feb 2019, Mark Tinka wrote:
someone else" they will say "huh? what do you mean". There is an
unfortunate common conflation between the fiber optic cable and the
services offered on it.
I get what you're saying, but sadly, someone has to take the risk to
build out a network. Unless
On 11/Feb/19 12:49, Mikael Abrahamsson wrote:
>
> In Sweden it's very common that people who live in detached house
> areas have to pay 1500-3000EUR to get attached to the fiber network as
> it's being built out. There are even bank loans you can get to pay for
> this, and pay it off over
On Mon, 11 Feb 2019, Mark Tinka wrote:
In any case, we are now building out our own fiber to cover the gaps
left by TDC. Here the end user has to pay DKK 12,000 (USD 1,824 / EUR
1,608) one time fee and with that he gets everything including 5 years
of free internet. This works out at DKK 200 /
On 11/Feb/19 11:31, Thomas Bellman wrote:
> I assume this is targeted towards single-family detached houses, where
> the family owns the house themselves. Then they likely will view that
> as an investment in the house. If you want to sell your house a couple
> of years later, and it doesn't
On 2019-02-11 04:57 CET, Mark Tinka wrote:
> On 10/Feb/19 17:46, Baldur Norddahl wrote:
[...]
>> In any case, we are now building out our own fiber to cover the gaps
>> left by TDC. Here the end user has to pay DKK 12,000 (USD 1,824 / EUR
>> 1,608) one time fee and with that he gets everything
21 matches
Mail list logo
