IPv6 route annoucement

policy-wise, to accepting a /22 in v4? Thanks, John -- John York Information Technology | Network Administrator Phone: 615-399-7000 x:333 Griffin Technology 2030 Lindell Avenue Nashville, TN 37203 USA

RE: IPv6 route annoucement

John -Original Message- From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Justin M. Streiner Sent: Thursday, August 07, 2014 1:56 PM To: North American Network Operators' Group Subject: Re: IPv6 route annoucement On Thu, 7 Aug 2014, John York wrote: > Hoping to not start a

RE: where to go to understand DDoS attack vector

In this case, 17 is both the protocol and port number. Confusing coincidence :) > -Original Message- > From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Roland > Dobbins > Sent: Tuesday, August 26, 2014 8:32 AM > To: nanog@nanog.org > Subject: Re: where to go to understand DDoS att

Re: google troubles?

ne know what's up? Fiber cut? DC outages? > > -- blair > -- John York Information Technology | Network Administrator Phone: 615-399-7000 x:333 Griffin Technology 2030 Lindell Avenue Nashville, TN 37203 USA This message and any attachments should be treated as confidential information of Griffin Technology, Inc.

RE: BGPMON Alert Questions

We have a registered prefix that was affected. The RPKI may have helped though; only one BGPMON peer saw the mis-originated route. Much better than being on the 10+ list. -Original Message- From: Randy Bush [mailto:ra...@psg.com] Sent: Wednesday, April 02, 2014 7:23 PM To: North American N