[168850] in North American Network Operators' Group
Re: BCP38 is hard; let's go shopping!
daemon@ATHENA.MIT.EDU (joel jaeggli)
Wed Feb 5 17:02:51 2014
Date: Wed, 05 Feb 2014 14:02:30 -0800
From: joel jaeggli <joelja@bogus.com>
To: Jay Ashworth <jra@baylink.com>, NANOG <nanog@nanog.org>
In-Reply-To: <7852910.7306.1391636764901.JavaMail.root@benjamin.baylink.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--VK8W1ocUsNDjSJHMIEFxAnX8JvqOh1l9M
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 2/5/14, 1:46 PM, Jay Ashworth wrote:
> ----- Original Message -----
>> From: "joel jaeggli" <joelja@bogus.com>
>=20
>>> As I've noted, I'm not sure I believe that's true of current generati=
on
>>> gear, and if it *is*, then it should cost manufacturers business.
>>
>> There are boxes that haven't aged out of the network yet where that's =
an
>> issue, some are more datacenter-centric than others. force10 e1200 was=
>> one platform that had this limitation for example.
>=20
> So making sure manufacturers are producing gear that's BCP38-compliant,=
> and buyers have it on their tick-list, is still a productive goal, too.=
it is... The products are probably close to the end of their sales
life, but they'll likely be around for a while.
> Cheers,
> -- jra
>=20
--VK8W1ocUsNDjSJHMIEFxAnX8JvqOh1l9M
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlLytPYACgkQ8AA1q7Z/VrKdBQCggdJaaE2T9rVfVNS+QY6FtT8f
7NwAn24zdKAo/1whpZSBk228McTs17Dn
=VNq3
-----END PGP SIGNATURE-----
--VK8W1ocUsNDjSJHMIEFxAnX8JvqOh1l9M--
