Hi,
On Thu, Jun 18, 2020, at 04:01, Jon Lewis wrote:
>
> Just like I said, if you create an ROA for an aggregate, forgetting that
> you have customers using subnets of that aggregate (or didn't create ROAs
> for customer subnets with the right origin ASNs), you're literally telling
> those
Mark Tinka wrote on 18/06/2020 11:56:
Invalid routes being dropped creates downtime. People respond to
downtime a lot more eagerly.
humanity is a crisis-driven species.
Nick
On 18/Jun/20 12:51, Nick Hilliard wrote:
>
> The customer monitoring system is very reliable and often superior to
> in-house solutions.
What really made the experience great for us is that directly contacting
the remote network (somewhere in Eastern Europe) and getting them to fix
the issue
Mark Tinka wrote on 18/06/2020 11:16:
On 17/Jun/20 21:16, Tim Warnock wrote:
How did you know? Is there some monitoring system available to let
you know or do you have your own?
The usual way - a customer complained :-).
The customer monitoring system is very reliable and often superior to
On 17/Jun/20 21:16, Tim Warnock wrote:
> How did you know? Is there some monitoring system available to let you know
> or do you have your own?
The usual way - a customer complained :-).
Mark.
On Wed, 17 Jun 2020, Richa wrote:
Job,
RPKI ROA creation is a big hammer. Everyone needs to think carefully
about each ROA they create and if it will positively or negatively
impact their network.
Could you please shed some more light on the above?
How would ROA negatively impact if
>> Do you remember the old BSD paradigm? ... "less is more"
> s/bsd/mies/ credit where due.
recant. it was well before mies. i was just raised by and architect,
and had uni roomies who were in the architecture school mies founded.
so my own narrow vision. sorry.
randy
> Do you remember the old BSD paradigm? ... "less is more"
s/bsd/mies/ credit where due.
> We are now in a time where a *smaller* routing table entry list count
> is preferable to a 'full' table, because the fullest table is likely
> to also include problematic BGP routing information.
do
Dear Jon, group,
On Wed, Jun 17, 2020 at 10:25:14AM -0400, Jon Lewis wrote:
> On Mon, 15 Jun 2020, Mike Leber via NANOG wrote:
>
> > I'm pleased to announce Hurricane Electric has completed our RPKI
> > INVALID filtering project and we now have 0 RPKI INVALIDs in our routing
> > table.
> >
> >
> On 17/Jun/20 16:25, Jon Lewis wrote:
> > The flip side of this though is that every time an IP space owner
> > publishes an ROA for an aggregate IP block and overlooks the fact that
> > they have customers BGP originating a subnet of the aggregate with an
> > ASN not permitted by an ROA, HE has
On 17/Jun/20 16:25, Jon Lewis wrote:
>
> The flip side of this though is that every time an IP space owner
> publishes an ROA for an aggregate IP block and overlooks the fact that
> they have customers BGP originating a subnet of the aggregate with an
> ASN not permitted by an ROA, HE has
On Wed, 17 Jun 2020 at 17:28, Jon Lewis wrote:
> The flip side of this though is that every time an IP space owner
> publishes an ROA for an aggregate IP block and overlooks the fact that
> they have customers BGP originating a subnet of the aggregate with an ASN
> not permitted by an ROA, HE
On Mon, 15 Jun 2020, Mike Leber via NANOG wrote:
I'm pleased to announce Hurricane Electric has completed our RPKI
INVALID filtering project and we now have 0 RPKI INVALIDs in our routing
table.
Hurricane Electric has 29021 BGP sessions with 22109 prefix filters with
7191 networks directly and
On Tue, 16 Jun 2020 at 07:51, Mike Leber via NANOG wrote:
Hey,
> These prefix filters are updated automatically both through a system of
> daily updates and real time updates to prevent RPKI INVALID routes from
> being carried in our routing table.
What does real time mean in this context?
congratulations HE team!.
On Mon, Jun 15, 2020 at 9:56 PM TJ Trout wrote:
> absolutely awesome Mike!
>
> Can you put on the roadmap to enable irr based filters for customers with
> bgp communities?
>
> On Mon, Jun 15, 2020 at 9:48 PM Mike Leber via NANOG
> wrote:
>
>> I'm pleased to announce
absolutely awesome Mike!
Can you put on the roadmap to enable irr based filters for customers with
bgp communities?
On Mon, Jun 15, 2020 at 9:48 PM Mike Leber via NANOG
wrote:
> I'm pleased to announce Hurricane Electric has completed our RPKI
> INVALID filtering project and we now have 0 RPKI
I'm pleased to announce Hurricane Electric has completed our RPKI
INVALID filtering project and we now have 0 RPKI INVALIDs in our routing
table.
Hurricane Electric has 29021 BGP sessions with 22109 prefix filters with
7191 networks directly and 8239 networks including Internet exchanges.
We
17 matches
Mail list logo
