t; Australia go effected by your “expirment” and had no idea what was
> happening or why.
>
> Get a sandbox like every other researcher, as of now we have black holed
> and filtered your whole ASN, and have reccomended others do the same.
>
> On Wed, 23 Jan 2019 at 1:19 am, Italo Cun
NANOG,
This is a reminder that this experiment will resume tomorrow
(Wednesday, Jan. 23rd). We will announce 184.164.224.0/24 carrying a
BGP attribute of type 0xff (reserved for development) between 14:00
and 14:15 GMT.
On Tue, Dec 18, 2018 at 10:05 AM Italo Cunha wrote:
>
> NANOG,
>
&
shorter timeline [A]. We will follow up with
FRR devs and mailing lists/users.
[A] https://goo.gl/nJhmx1
On Tue, Jan 8, 2019 at 11:41 AM Italo Cunha wrote:
>
> NANOG,
>
> We've performed the first announcement in this experiment yesterday,
> and, despite the announcement
Hi Niels, we did run the experiment in a controlled environment with
different versions of Cisco, BIRD, and Quagga routers and observed no
issues. We did add FRR to the test suite yesterday for future tests.
On Tue, Jan 8, 2019 at 11:49 AM wrote:
>
> * cu...@dcc.ufmg.br (Italo Cunha) [
. As always, we
welcome your feedback.
[A] https://goo.gl/nJhmx1
On Tue, Dec 18, 2018 at 10:05 AM Italo Cunha wrote:
>
> NANOG,
>
> We would like to inform you of an experiment to evaluate alternatives
> for speeding up adoption of BGP route origin validation (research
> paper wit
NANOG,
We would like to inform you of an experiment to evaluate alternatives
for speeding up adoption of BGP route origin validation (research
paper with details [A]).
Our plan is to announce prefix 184.164.224.0/24 with a valid
standards-compliant unassigned BGP attribute from routers operated b
6 matches
Mail list logo
