[143181] in North American Network Operators' Group
=?iso-8859-1?Q?Community_troubleshooting_=E9tiquette/BCP_=28was?=
daemon@ATHENA.MIT.EDU (Jason Lixfeld)
Mon Aug 1 14:03:55 2011
From: Jason Lixfeld <jason@lixfeld.ca>
In-Reply-To: <Pine.LNX.4.61.1108011345560.3994@soloth.lewis.org>
Date: Mon, 1 Aug 2011 14:03:24 -0400
To: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 2011-08-01, at 1:48 PM, Jon Lewis wrote:
> Things seem to be moving again.
I happen to have an L3 link out of NYC, but unfortunately I don't have a =
list of on-net L3 prefixes in any of the reportedly affected regions, so =
I'm unable to provide any data from my vantage point up here. I'm sure =
others are in my position as well.
Is there any sort of etiquette/BCP for reporting issues like this to the =
community? Something that might specify a method of providing =
information a little more specific than just specifying the affected =
region(s)? Maybe a list of a few affected hosts/prefixes/URLS/etc?
(incidentally, images.apple.com also resolves to our local Akamai =
cluster)=
