[169407] in North American Network Operators' Group
Re: Filter NTP traffic by packet size?
daemon@ATHENA.MIT.EDU (Royce Williams)
Sun Feb 23 15:12:35 2014
In-Reply-To: <CA+E3k92tSRhzBbu5gEAAyfg63cq-2Et7BdKX6CHU9nL7ms53+w@mail.gmail.com>
From: Royce Williams <royce@techsolvency.com>
Date: Sun, 23 Feb 2014 11:11:50 -0900
To: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Sun, Feb 23, 2014 at 10:48 AM, Royce Williams <royce@techsolvency.com> w=
rote:
> Newb question ... other than retrofitting, what stands in the way of
> making BCP38 a condition of peering?
In other words ... if it's a problem of awareness, could upstreams
automate warning their downstreams? What about teaching RADb to
periodically test for BCP38 compliance, send soft warnings (with links
to relevant pages on www.bcp38.info), and publish stats?
Continuing my na=EFvet=E9 ...what if upstreams required BCP38 compliance
before updating BGP filters? This would require a soft rollout --
we'd have to give them a few months' warning to not interfere with
revenue streams -- but it sounds like nothing's going to change until
it starts hitting the pocketbooks.
Royce
