Hi Steve,
On 10/28, s...@iu.edu wrote:
> Greetings,
>
> We seek input on best practices for implementing RPKI ROV in a transit
> (partial transit) network. The Internet2 network provides partial
> transit for many of the K-12 and higher education institutions in the
> US. Our customer routes numb
On Fri, Oct 29, 2021 at 01:20:33AM +0400, Musa Stephen Honlue wrote:
> Personally I recommend dropping them invalids.
100%
> However, you could set local preferences as follows:
> - Valids routes get the highest local pref
> - unknown routes get a medium local pref
> - Invalids routes get the lo
Randy Bush wrote on 29/10/2021 02:03:
received this vuln notice four days before these children intend to
disclose. so you can guess how inclined to embargo.
The position doesn't seem to be compatible with e.g.
https://www.first.org/global/sigs/vulnerability-coordination/multiparty/FIRST-Mul
Background:
Five and ten years ago PCH conducted comprehensive global surveys
characterizing Internet peering agreements. They are the only ones of their
kind, and are relied upon by legislators and regulators throughout the world to
understand the Internet interconnection landscape.
Our write
i would not be surprised if email to my previous addresses
...!uunet!m2xenix!randy
...!uunet!oresoft!randy
bounced, making it difficult for these kiddies to reach me.
https://en.wikipedia.org/wiki/Responsible_disclosure
randy
Hi,
On Fri, 29 Oct 2021 at 00:48, Amir Herzberg wrote:
> Hi NANOGers, for our research on ROV (and ROV++, our extension, NDSS'21),
> we need access to historical data of blacklisted prefixes (due to spam,
> DDoS, other), as well as suspect-hijacks list (beyond BGPstream which we
> already have).
> On Oct 29, 2021, at 5:26 PM, Nick Hilliard wrote:
>
> Because this didn't happen, we now get to look forward to a weekend of
> elevated risk, followed by people upending their calendars to handle
> un-coordinated upgrades on monday morning.
That only happens if the team has the time to ge
Barry Greene wrote on 29/10/2021 13:15:
That only happens if the team has the time to get the fix into the code,
tested, validated, regressed, and deployed. I would say this is a
classic example of “ego” to publish overruling established principles.
The University of Twente should explore requ
Hi Matthew,
What you seem to have failed to understand is that most traffic hijacks on
> the internet are not malicious in nature, they are "fat finger" incidents
> where someone has accidentally announced something they did not intend to,
> either because of faulty software (the infamous "BGP op
Barry Greene wrote on 29/10/2021 13:15:
"The NCSC will try to resolve the security problem that you have
reported in a system within 60 days. Once the problem has been resolved,
we will decide in consultation whether and how details will be published.”
I would have expected you to council the
Le Fri, Oct 29, 2021 at 01:47:37PM +0200, Bill Woodcock a écrit :
> If you’re peering with an MLPA route-server, you’re welcome to include just
> the route-server’s ASN, if that’s easiest, rather than trying to include each
> of the peer ASNs on the other side of the route-server. Either way is fin
> there's a public statement about this from NCSC-NL:
>> https://www.ncsc.nl/actueel/nieuws/2021/oktober/29/aanstaande-bekendmaking-cvd-procedure-rpki
blah blah blah
bottom line. they gave first notice to devs 4 days before threatened
disclosure. that they then asked to embargo was just adding
> On Oct 29, 2021, at 6:55 PM, Denis Fondras wrote:
> Le Fri, Oct 29, 2021 at 01:47:37PM +0200, Bill Woodcock a écrit :
>> If you’re peering with an MLPA route-server, you’re welcome to include just
>> the route-server’s ASN, if that’s easiest, rather than trying to include each
>> of the peer A
The link doesn't work. 404
https://www.ncsc.nl/actueel/nieuws/2021/oktober/29/aanstaande-bekendm
What are the specs of that possible dos vuln?
Is is reflection or amplification or something else?
Thanks
Jean
I looked on english.ncsc.nl's news section (it's the most recently published
article) and it seems to be referencing OpenBSD's security page as the reason
this "CVD" doesn't involve the developers and thus isn't really a CVD.
The link is over linelen characters long and it may have gotten trunca
* nanog@nanog.org (Jean St-Laurent via NANOG) [Fri 29 Oct 2021, 19:57 CEST]:
The link doesn't work. 404
https://www.ncsc.nl/actueel/nieuws/2021/oktober/29/aanstaande-bekendm
| X-Mailer: Microsoft Outlook 16.0
The posted link works fine here but your MUA mangled it so you'll have
to do some m
This is an automated weekly mailing describing the state of the Internet
Global IPv4 Routing Table as seen from APNIC's router in Japan.
The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG
TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG.
Daily listings are sent to
On Fri, 29 Oct 2021, 15:55 A Crisan, wrote:
> Hi Matthew,
> I was reading the above exchange, and I do have a question linked to your
> last affirmation. To give you some context, the last 2021 ENISA report seem
> to suggest that internet traffic is "casually registered" by X actors to
> apply po
Greetings Fellow Nanog'ers
Are there any Comcast engineers in the group that could help to sort out a
10GB layer2 ELAN issue in Florida?
We are short of cancelling this circuit that has been in for a couple of
days.
We cannot pass above 1GB on this circuit... 10GB SFPs on both ends, 10GB
price,
https://www.ncsc.nl/actueel/nieuws/2021/oktober/29/aanstaande-bekendmaking-cvd-procedure-rpki
-Original Message-
From: NANOG On Behalf Of Niels Bakker
Sent: October 29, 2021 2:01 PM
To: nanog@nanog.org
Subject: Re: possible rsync validation dos vuln
* nanog@nanog.org (Jean St-Laurent via
I’ll reply off-list in a sec
From: NANOG on
behalf of Joe Carroll
Date: Friday, October 29, 2021 at 14:16
To: nanog list
Subject: Comcast? Layer2 / ELAN
Greetings Fellow Nanog'ers
Are there any Comcast engineers in the group that could help to sort out a 10GB
layer2 ELAN issue in Florida?
(this is an answer to Matthew but also with a question to all NANOGers, see
below, under `is this true?')
Matthew, thanks for your feedback on our paper - always welcome - although
the email I sent wasn't about ROV++ but on our need for historical data on
blacklisted prefixes. (our use is not limi
I would request an on-site rfc test that should clear things up quickly
On Fri, Oct 29, 2021 at 11:17 AM Joe Carroll wrote:
> Greetings Fellow Nanog'ers
>
> Are there any Comcast engineers in the group that could help to sort out a
> 10GB layer2 ELAN issue in Florida?
>
> We are short of cancell
23 matches
Mail list logo
