nanog mailing list archives
Community troubleshooting étiquette/BCP (was: L3 Issues)
From: Jason Lixfeld <jason () lixfeld ca>
Date: Mon, 1 Aug 2011 14:03:24 -0400
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)
Current thread:
- L3 Issues Khurram Khan (Aug 01)
- Re: L3 Issues Thomas Donnelly (Aug 01)
- Re: L3 Issues Brent Jones (Aug 01)
- Re: L3 Issues Vasil Kolev (Aug 01)
- Re: L3 Issues Jon Lewis (Aug 01)
- Community troubleshooting étiquette/BCP (was: L3 Issues) Jason Lixfeld (Aug 01)
- RE: Community troubleshooting étiquette/BCP (was: L3 Issues) Scott Berkman (Aug 01)
- Community troubleshooting étiquette/BCP (was: L3 Issues) Jason Lixfeld (Aug 01)
- <Possible follow-ups>
- RE: L3 Issues David Hubbard (Aug 01)
- RE: L3 Issues Scott Berkman (Aug 01)
- Re: L3 Issues Michael J McCafferty (Aug 01)