[168865] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: BCP38 [Was: Re: TWC (AS11351) blocking all NTP?]

daemon@ATHENA.MIT.EDU (Jay Ashworth)
Wed Feb 5 23:42:56 2014

In-Reply-To: <201402060638.08567.mark.tinka@seacom.mu>
From: Jay Ashworth <jra@baylink.com>
Date: Wed, 05 Feb 2014 23:39:56 -0500
To: mark.tinka@seacom.mu,Mark Tinka <mark.tinka@seacom.mu>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

I'm going to be somewhat of a pain in everybody's ass this year, pounding on the drum whenever the topic pops up. :-)

On February 5, 2014 11:38:08 PM EST, Mark Tinka <mark.tinka@seacom.mu> wrote:
>On Thursday, February 06, 2014 06:34:16 AM Jay Ashworth 
>wrote:
>
>> Sure.  Part of the data collection task.  Making sure all
>> the current new gear knows how, still a good idea.
>
>Yep - like Joel said; current kit supports it (well, the 
>ones I buy, anyway), and certainly a good idea for operators 
>to make sure their favorite vendor can support this when 
>they run their next purchase cycle.
>
>Mark.

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

home help back first fref pref prev next nref lref last post