[168864] in North American Network Operators' Group
Re: BCP38 [Was: Re: TWC (AS11351) blocking all NTP?]
daemon@ATHENA.MIT.EDU (Mark Tinka)
Wed Feb 5 23:39:19 2014
From: Mark Tinka <mark.tinka@seacom.mu>
To: Jay Ashworth <jra@baylink.com>
Date: Thu, 6 Feb 2014 06:38:08 +0200
In-Reply-To: <0e554157-b925-4a2a-9c0d-4f751c21302c@email.android.com>
Cc: nanog@nanog.org
Reply-To: mark.tinka@seacom.mu
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--nextPart1568261.XnfqbgMlTn
Content-Type: Text/Plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
On Thursday, February 06, 2014 06:34:16 AM Jay Ashworth=20
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=20
ones I buy, anyway), and certainly a good idea for operators=20
to make sure their favorite vendor can support this when=20
they run their next purchase cycle.
Mark.
--nextPart1568261.XnfqbgMlTn
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
iQIcBAABAgAGBQJS8xGwAAoJEGcZuYTeKm+G1h0P/2fxyIJwLAbLuwDaVvk++r3v
hDvJJb6NWe1/3rF4UTfvhp9rtdspfQjGCUSZnYyJjnmg/IoxA+jG3Ml67LqBt3S4
+WqjSoJ7eu69jVYw993X19q+whLft2VUqinbQ/SFFaSeOaWVfeuhqxTRYgTQe8zh
ExcXByu3tyNHKmtzRqunNXOwyTpPLIDCzZ+SIMVK0+RQaOQkbFbOVA/nkBez7dQg
lhhZz1POKvqUb/iYoHD3H9ISfgnaqAj0UWQDM4hEPwu45VoeXrhpuiKQerrpjFrq
PBeHPvVZSkmNNUzzOYgTZyKcqj53oNrG7x1ZG64PLKtGUaTtcUvF//UD4geL12iL
FN6srQlh/uKtYzCvHfHb5lB+/0P1JLmiOBtXFhqVU5CMHxK3wob44FKLf0tjUBiB
UURp2nejEXQnppl+vUNzFrVFJ1CRAYco2nNUaquVBsk27qGOXTPcAG4G8Hedf6or
PtzlDGeCjjtCsysXGituyXMVsx3fmI9PBYnsS55pdeBynEUsMr7T3hXkRycg7IlF
cWXmX/0vuZacYqddEUhYmaIs0hKOiQql3gcaIItZh7n/gKuCMZ8Csahi4ihZusJ2
EulH4+RAZSRo0wFVCYdu+64erk2b1Gej88UpQB4zhbV90KNcm3rsQ5e4/LqUOOJM
znFjJHhIWOLIWzla1Rwi
=RZ2K
-----END PGP SIGNATURE-----
--nextPart1568261.XnfqbgMlTn--
