[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

BCP38 is hard, was TWC (AS11351) blocking all NTP?

Subject: BCP38 is hard, was TWC (AS11351) blocking all NTP?
From: johnl at iecc.com (John Levine)
Date: 5 Feb 2014 00:29:05 -0000
In-reply-to: <CAP-guGWhdpt3s_m1VqAjh6YYx3u22jEAnFNju-69YM6xX5EeEg@mail.gmail.com>

>Why does it have to be hard? Restricting the filter to addresses which
>(A) the customer asserts are theirs 

How does the customer do that in a way that scales?

I don't think any of this is rocket science, but it apparently is a
real block to BCP38/84 implementatin.

R's,
John

Follow-Ups:
- BCP38 is hard, was TWC (AS11351) blocking all NTP?
  - From: marka at isc.org (Mark Andrews)
- BCP38 is hard, was TWC (AS11351) blocking all NTP?
  - From: jra at baylink.com (Jay Ashworth)
- BCP38 is hard, was TWC (AS11351) blocking all NTP?
  - From: saku at ytti.fi (Saku Ytti)

References:
- BCP38 is hard, was TWC (AS11351) blocking all NTP?
  - From: bill at herrin.us (William Herrin)

Prev by Date: BCP38 is hard, was TWC (AS11351) blocking all NTP?
Next by Date: Cogent <-> Verizon peering congestion
Previous by thread: BCP38 is hard, was TWC (AS11351) blocking all NTP?
Next by thread: BCP38 is hard, was TWC (AS11351) blocking all NTP?
Index(es):
- Date
- Thread