nanog: by date

699 messages starting Jan 01 19 and ending Jan 31 19
Date index | Thread index | Author index


Tuesday, 01 January

Re: CenturyLink Saku Ytti
Re: CenturyLink RCA? William Allen Simpson
Re: IP Dslams Nick Edwards
Re: IP Dslams Brandon Martin
Re: IP Dslams Nick Edwards
Re: CenturyLink valdis . kletnieks
Re: IP Dslams Colton Conor

Wednesday, 02 January

Re: IP Dslams Nick Edwards
Re: Service Provider NetFlow Collectors H I Baysal
Re: Auto-configuring IPv6 transition mechanisms on customer devices Brandon Martin
Re: Service Provider NetFlow Collectors Tim Raphael
Re: Service Provider NetFlow Collectors Saku Ytti
Re: Service Provider NetFlow Collectors H I Baysal
Re: Auto-configuring IPv6 transition mechanisms on customer devices Mikael Abrahamsson
Re: Service Provider NetFlow Collectors Tim Raphael
Re: IP Dslams Brandon Martin
Re: Auto-configuring IPv6 transition mechanisms on customer devices Brandon Martin
Re: Service Provider NetFlow Collectors Saku Ytti
Re: Auto-configuring IPv6 transition mechanisms on customer devices Mikael Abrahamsson
Re: Service Provider NetFlow Collectors Tim Raphael
RE: Service Provider NetFlow Collectors Phil Lavin
Re: Auto-configuring IPv6 transition mechanisms on customer devices Lee Howard
Re: Auto-configuring IPv6 transition mechanisms on customer devices Brandon Martin
Re: Service Provider NetFlow Collectors Daniel Rohan
Re: How to choose a transport(terrestrial/subsea) Alfie Pates
RE: How to choose a transport(terrestrial/subsea) Naslund, Steve
Re: How to choose a transport(terrestrial/subsea) Mike Hammett
Re: CenturyLink RCA? Tom Beecher
Re: How to choose a transport(terrestrial/subsea) Tom Beecher
Re: How to choose a transport(terrestrial/subsea) Saku Ytti
RE: How to choose a transport(terrestrial/subsea) Naslund, Steve
Re: How to choose a transport(terrestrial/subsea) Jason Bothe via NANOG
Cleveland/Cincinnati Co-location Mitchell Lewis
does emergency (911) dispatch uses IP ? Mankamana Mishra (mankamis) via NANOG
Re: Service Provider NetFlow Collectors H I Baysal
Re: Cleveland/Cincinnati Co-location Paul Timmins
Re: Cleveland/Cincinnati Co-location Matt Erculiani
RE: does emergency (911) dispatch uses IP ? Naslund, Steve
Re: does emergency (911) dispatch uses IP ? Sean Donelan
RE: does emergency (911) dispatch uses IP ? Naslund, Steve
RE: does emergency (911) dispatch uses IP ? Naslund, Steve
Re: Cleveland/Cincinnati Co-location Jeff Waddell
Re: Service Provider NetFlow Collectors Nick Peelman
Re: Cleveland/Cincinnati Co-location Justin M. Streiner

Thursday, 03 January

Re: Cleveland/Cincinnati Co-location Allen McKinley Kitchen (gmail)
Re: Service Provider NetFlow Collectors Aaron
Re: Cleveland/Cincinnati Co-location Shawn Ritchie
Re: Announcing Peering-LAN prefixes to customers Andy Davidson
Report on Legal Barriers to RPKI Adoption Christopher S. Yoo
192.208.19.0/24 hijack transiting 209, 286, 3320, 5511, 6461, 6762, 6830, 8220, 9002, 12956 Dominik Bay
Re: 192.208.19.0/24 hijack transiting 209, 286, 3320, 5511, 6461, 6762, 6830, 8220, 9002, 12956 Jeff Shultz
Astronaut accidently calls 911 from space Sean Donelan
Re: Cellular backup connections Dovid Bender

Friday, 04 January

Re: 192.208.19.0/24 hijack transiting 209, 286, 3320, 5511, 6461, 6762, 6830, 8220, 9002, 12956 Job Snijders
Re: IP Dslams Nick Edwards
Re: IP Dslams Shawn L via NANOG
Re: IP Dslams Jeff Shultz
Re: IP Dslams Mikael Abrahamsson
(FIXED) Re: 192.208.19.0/24 hijack transiting 209, 286, 3320, 5511, 6461, 6762, 6830, 8220, 9002, 12956 Dominik Bay
Re: IP Dslams Blake Hudson
Re: IP Dslams Shawn L via NANOG
Re: IP Dslams Brandon Martin
Weekly Routing Table Report Routing Analysis Role Account
Re: How to choose a transport(terrestrial/subsea) Mehmet Akcin
Changing upstream providers, opinions/thoughts on 123.net and cogent Aaron Henderson
Re: Cleveland/Cincinnati Co-location David Kehoe
Re: IP Dslams Rob Pickering
Re: Changing upstream providers, opinions/thoughts on 123.net and cogent Ben Cannon
Re: Changing upstream providers, opinions/thoughts on 123.net and cogent William Herrin
Re: Changing upstream providers, opinions/thoughts on 123.net and cogent Brandon Martin
RE: IP Dslams Payam Poursaied

Saturday, 05 January

Re: IP Dslams Sander Steffann
Verizon IDE Mitchell Lewis
Re: Verizon IDE Justin M. Streiner
attempted archive.is hijacking Dan Hollis
Re: Verizon IDE Mel Beckman
Google Fiber v6 PD only giving /64 Chris Adams
RE: IP Dslams Payam Poursaied

Sunday, 06 January

Re: Google Fiber v6 PD only giving /64 Sander Steffann
Re: IP Dslams Sander Steffann
Re: Report on Legal Barriers to RPKI Adoption Job Snijders
Re: Cleveland/Cincinnati Co-location Ross Tajvar
Re: Cleveland/Cincinnati Co-location Crist Clark
Re: Cleveland/Cincinnati Co-location David Kehoe

Monday, 07 January

Re: attempted archive.is hijacking Alfie Pates
Re: Changing upstream providers, opinions/thoughts on 123.net and cogent Neader, Brent
Re: Cellular backup connections Ian Henderson
Re: attempted archive.is hijacking Ops One AG | Markus Ritzmann
Re: Astronaut accidently calls 911 from space Wes Hardaker

Tuesday, 08 January

RE: Changing upstream providers, opinions/thoughts on 123.net and cogent Aaron Gould
Re: BGP Experiment Italo Cunha
Re: BGP Experiment niels=nanog
Re: BGP Experiment Tom Ammon
Re: Report on Legal Barriers to RPKI Adoption Nathalie Trenaman
Re: BGP Experiment Italo Cunha
Re: BGP Experiment Saku Ytti
Re: BGP Experiment valdis . kletnieks
Re: BGP Experiment Nick Hilliard
Re: BGP Experiment niels=nanog
Re: BGP Experiment niels=nanog
Re: BGP Experiment Job Snijders
Re: BGP Experiment Jared Mauch
Re: BGP Experiment niels=nanog
Re: BGP Experiment Jared Mauch
Re: BGP Experiment Töma Gavrichenkov
Re: BGP Experiment Steve Noble
Re: BGP Experiment Randy Bush
Re: BGP Experiment Stephen Satchell
RE: BGP Experiment adamv0025
Re: BGP Experiment Eric Kuhnke
Re: BGP Experiment Randy Bush
Re: BGP Experiment Job Snijders
Re: BGP Experiment Tore Anderson

Wednesday, 09 January

Re: BGP Experiment Owen DeLong
Re: BGP Experiment Töma Gavrichenkov
Re: BGP Experiment Saku Ytti
Spoofer Report for NANOG for Dec 2018 CAIDA Spoofer Project
DNS Hijacking? - FiOS Northeast Blake Mckeeby
Re: Report on Legal Barriers to RPKI Adoption Ben Maddison via NANOG
Re: BGP Experiment Töma Gavrichenkov
RE: DNS Hijacking? - FiOS Northeast Phil Lavin
RE: DNS Hijacking? - FiOS Northeast Chris Kimball
Re: BGP Experiment Owen DeLong
Re: BGP Experiment Saku Ytti
Re: BGP Experiment Töma Gavrichenkov
Centurylink/Level3 WDM? James Breeden
Re: BGP Experiment Töma Gavrichenkov
Re: BGP Experiment Saku Ytti
Re: BGP Experiment Töma Gavrichenkov
Re: BGP Experiment Saku Ytti
Re: BGP Experiment Töma Gavrichenkov
Re: BGP Experiment Owen DeLong
Re: BGP Experiment Owen DeLong
Re: BGP Experiment Töma Gavrichenkov
Re: BGP Experiment Töma Gavrichenkov
Re: Centurylink/Level3 WDM? James Breeden
RE: BGP Experiment adamv0025
Re: BGP Experiment Töma Gavrichenkov

Thursday, 10 January

Call for presentations RIPE 78 Benno Overeinder
Proofpoint Mail Delivery Issues Tim Donahue
Re: DNS Hijacking? - FiOS Northeast Jim Popovitch via NANOG
Re: Proofpoint Mail Delivery Issues Mike Hammett
Re: Proofpoint Mail Delivery Issues Brian Kantor
Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Rich Kulawiec
Re: Proofpoint Mail Delivery Issues Dan White
Re: Proofpoint Mail Delivery Issues Jaren Angerbauer
RE: Proofpoint Mail Delivery Issues David McCabe
Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues J. Hellenthal via NANOG
Re: BGP Experiment Italo Cunha
RE: Proofpoint Mail Delivery Issues Tony Wicks
Re: Google Fiber v6 PD only giving /64 Heather Schiller via NANOG
Switch.com AS23005 John Von Essen

Friday, 11 January

ARIN NS down? Suresh Ramasubramanian
Re: ARIN NS down? John Curran
Re: ARIN NS down? Stephane Bortzmeyer
Re: ARIN NS down? i3D.net - Martijn Schmidt
Re: ARIN NS down? John Curran
Dnssec still inoperable on the internet ?— was ARIN NS down? Ca By
Re: Dnssec still inoperable on the internet ?— was ARIN NS down? Stephane Bortzmeyer
Re: Dnssec still inoperable on the internet ?— was ARIN NS down? Ca By
Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Yang Yu
Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Ross Tajvar
Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Mike Hammett
Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Brian Kantor
Re: Dnssec still inoperable on the internet ?— was ARIN NS down? Max Tulyev
Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Rich Kulawiec
Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Rich Kulawiec
Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Töma Gavrichenkov
Weekly Routing Table Report Routing Analysis Role Account
Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Andreas Ott
Re: Dnssec still inoperable on the internet ?― was ARIN NS down? Randy Bush
Re: Dnssec still inoperable on the internet ?— was ARIN NS down? Antonios Chariton
Re: Dnssec still inoperable on the internet ?— was ARIN NS down? Mikael Abrahamsson
Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Rob McEwen
Re: Dnssec still inoperable on the internet ?— was ARIN NS down? Ca By
Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Töma Gavrichenkov
Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Grant Taylor via NANOG
Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Bryan Holloway
Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Anne P. Mitchell, Esq.
Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Mark Andrews
Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Töma Gavrichenkov
2019-01-11 ARIN.NET DNSSEC Outage – Post-Mortem (was: Re: ARIN NS down?) John Curran
Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues cosmo
SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Michael Thomas
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Doug Royer
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] William Herrin
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] William Herrin
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Suresh Ramasubramanian
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Constantine A. Murenin
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] William Herrin
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Brandon Martin
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Suresh Ramasubramanian
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Constantine A. Murenin
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Suresh Ramasubramanian
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] valdis . kletnieks
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] valdis . kletnieks
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Constantine A. Murenin
Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Rob McEwen

Saturday, 12 January

Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Töma Gavrichenkov
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Seth Mattinen
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] James Downs
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] John Levine
Could Someone From Yahoo Mail Please Contact Me Matt Hoppes
Re: Could Someone From Yahoo Mail Please Contact Me Mike Hammett
Re: Could Someone From Yahoo Mail Please Contact Me Ross Tajvar
Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Brian Kantor
Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Eric Tykwinski
Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] valdis . kletnieks
Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Töma Gavrichenkov
Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Suresh Ramasubramanian
Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Cummings, Chris
Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Ross Tajvar
Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] valdis . kletnieks
Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] valdis . kletnieks
Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Jason Hellenthal via NANOG
Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Jason Hellenthal via NANOG
Enough port 26 talk... Richard
Re: Could Someone From Yahoo Mail Please Contact Me Matt Hoppes
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Owen DeLong
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan

Sunday, 13 January

Re: Enough port 26 talk... Bjørn Mork
Re: Enough port 26 talk... John Levine
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Jimmy Hess
Fwd: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Christoffer Hansen
Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Mike Hammett
Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting valdis . kletnieks
Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Christoffer Hansen
Re: plaintext email? Brian Kantor
Re: plaintext email? Christoffer Hansen
Re: plaintext email? Mike Hammett
Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting valdis . kletnieks
RE: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Keith Medcalf
Re: plaintext email? Jason Hellenthal via NANOG
Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Christoffer Hansen
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Matt Hoppes
Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Bryce Wilson
Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Seth Mattinen
Re: plaintext email? James R Cutler
Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Jason Hellenthal via NANOG
Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting James Downs
Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Jared Mauch
Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Brian Kantor
Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting valdis . kletnieks
Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Brian Kantor

Monday, 14 January

Re: 2019-01-11 ARIN.NET DNSSEC Outage – Post-Mortem (was: Re: ARIN NS down?) Stephane Bortzmeyer
Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Stephen Satchell
Re: Could Someone From Yahoo Mail Please Contact Me Tom Beecher
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Doug Royer
Re: Could Someone From Yahoo Mail Please Contact Me Udeme Ukutt
Tools for streaming analysis Ben Logan
Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Stacy W. Smith
Cable/Wireless-Tower Map for the San Francisco Bay Coastside? Yosem Companys
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] William Anderson
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Jon Lewis
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Robert Blayzor
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan
Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Tom Beecher
Re: plaintext email? Randy Bush
Re: plaintext email? Christopher Morrow
Re: plaintext email? Randy Bush
Re: plaintext email? Brian Kantor
Re: plaintext email? Steve Atkins
CAT-TP Protocol? Richard
Re: CAT-TP Protocol? Andrew Latham
Re: the e-mail of the future is the e-mail oft the past, was Enough port 26 talk... John R. Levine
Re: plaintext email? John Levine
Re: plaintext email? Christopher Morrow
Re: the e-mail of the future is the e-mail oft the past, was Enough port 26 talk... Miles Fidelman
Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Owen DeLong
Re: Cable/Wireless-Tower Map for the San Francisco Bay Coastside? Mike Hammett
RE: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Keith Medcalf
Top-quoting Was: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Stephen Satchell
Re: Cable/Wireless-Tower Map for the San Francisco Bay Coastside? Tim Pozar
Re: plaintext email? bzs
Re: plaintext email? valdis . kletnieks
Re: plaintext email? Richard
Re: plaintext email? Royce Williams

Tuesday, 15 January

Re: the e-mail of the future is the e-mail oft the past, was Enough port 26 talk... Bjørn Mork
Top Posting Was: Re: plaintext email? James R Cutler
Re: plaintext email? Grant Taylor via NANOG
Re: plaintext email? Tei
Re: Top Posting Was: Re: plaintext email? Tom Beecher
Re: plaintext email? Stephen Satchell
Re: the e-mail of the future is the e-mail oft the past, was Enough port 26 talk... Stephen Satchell
Re: Top Posting Was: Re: plaintext email? Brian Kantor
Re: Top Posting Was: Re: plaintext email? Stephen Satchell
Re: Top-quoting Was: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Winston Polhamus
ASNs decimation in ZW this morning C. A. Fillekes
Re: ASNs decimation in ZW this morning C. A. Fillekes
Re: ASNs decimation in ZW this morning Colin Johnston
Re: the e-mail of the future is the e-mail oft the past, was Enough port 26 talk... Tei
Re: Top Posting Was: Re: plaintext email? John Levine
Re: plaintext email? bzs
Re: plaintext email? bzs
Re: plaintext email? William Herrin
Your opinion on network analysis in the presence of uncertain events Vanbever Laurent
Re: the e-mail of the future is the e-mail oft the past, was Enough port 26 talk... James Downs
Re: plaintext email? valdis . kletnieks
Re: plaintext email? Brian J. Murrell
Re: plaintext email? Brian Kantor
Re: Your opinion on network analysis in the presence of uncertain events Mel Beckman
Re: plaintext email? Grant Taylor via NANOG
Re: the e-mail of the future is the e-mail oft the past, was Enough port 26 talk... Grant Taylor via NANOG
Re: Your opinion on network analysis in the presence of uncertain events Vanbever Laurent
Re: Top Posting Was: Re: plaintext email? James R Cutler
Re: plaintext email? James R Cutler
Re: plaintext email? Bryan Fields
Re: plaintext email? cosmo
dyn internet intelligence Mehmet Akcin
Re: plaintext email? Aled Morris via NANOG
Re: plaintext email? Christopher Morrow
Re: plaintext email? Bryan Fields
Re: Your opinion on network analysis in the presence of uncertain events Mel Beckman
RE: the e-mail of the future is the e-mail oft the past, was Enough port 26 talk... Keith Medcalf
Re: plaintext email? bzs
Re: plaintext email? John Levine
Re: plaintext email? cosmo
Re: plaintext email? bzs
Re: Service Provider NetFlow Collectors Mark Tinka
Re: Announcing Peering-LAN prefixes to customers Mark Tinka

Wednesday, 16 January

Re: Announcing Peering-LAN prefixes to customers Job Snijders
Re: Announcing Peering-LAN prefixes to customers Christoffer Hansen
Re: Announcing Peering-LAN prefixes to customers Job Snijders
Re: Announcing Peering-LAN prefixes to customers Mark Tinka
Re: Announcing Peering-LAN prefixes to customers Mark Tinka
Re: Announcing Peering-LAN prefixes to customers Job Snijders
Re: Announcing Peering-LAN prefixes to customers Randy Bush
Re: Announcing Peering-LAN prefixes to customers Randy Bush
Re: Announcing Peering-LAN prefixes to customers Job Snijders
Re: ASNs decimation in ZW this morning Colin Johnston
Re: ASNs decimation in ZW this morning Mark Tinka
Re: Service Provider NetFlow Collectors jim deleskie
Re: Announcing Peering-LAN prefixes to customers John Kristoff
Call for Participation -- ICANN DNSSEC Workshop at ICANN64 Kobe, Japan Jacques Latour
Re: Announcing Peering-LAN prefixes to customers Siyuan Miao
Re: Announcing Peering-LAN prefixes to customers Amreesh Phokeer
Re: Announcing Peering-LAN prefixes to customers Matthias Waehlisch
Re: Announcing Peering-LAN prefixes to customers Christoffer Hansen
Re: Announcing Peering-LAN prefixes to customers John Kristoff
Re: Announcing Peering-LAN prefixes to customers Job Snijders
Network Speed Testing and Monitoring Platform Colton Conor
Re: Network Speed Testing and Monitoring Platform David Guo via NANOG
Re: Network Speed Testing and Monitoring Platform Mike Hammett
Re: dyn internet intelligence Mehmet Akcin
Re: Announcing Peering-LAN prefixes to customers Arnold Nipper
Re: Network Speed Testing and Monitoring Platform Christoffer Hansen
Re: Network Speed Testing and Monitoring Platform J. Hellenthal via NANOG
Re: ASNs decimation in ZW this morning John Von Essen
Re: Service Provider NetFlow Collectors James Breeden
Re: Network Speed Testing and Monitoring Platform Colton Conor
RE: Network Speed Testing and Monitoring Platform Chris Kimball
Re: Network Speed Testing and Monitoring Platform Casey Russell
Re: Network Speed Testing and Monitoring Platform Ryan Wilkins
RE: Network Speed Testing and Monitoring Platform Cummings, Chris
Re: Network Speed Testing and Monitoring Platform Blake Hudson
RE: Your opinion on network analysis in the presence of uncertain events adamv0025
Re: Network Speed Testing and Monitoring Platform valdis . kletnieks
Re: Announcing Peering-LAN prefixes to customers Randy Bush
Re: Network Speed Testing and Monitoring Platform valdis . kletnieks
Re: ASNs decimation in ZW this morning Scott Weeks
Re: Network Speed Testing and Monitoring Platform James R Cutler
Re: Your opinion on network analysis in the presence of uncertain events Mel Beckman
Fiber owners Mehmet Akcin

Thursday, 17 January

Re: Your opinion on network analysis in the presence of uncertain events Vanbever Laurent
Re: Network Speed Testing and Monitoring Platform James Bensley
Re: ASNs decimation in ZW this morning Mark Tinka
Re: ASNs decimation in ZW this morning Colin Johnston
Re: ASNs decimation in ZW this morning Mark Tinka
Re: Your opinion on network analysis in the presence of uncertain events James Bensley
Call for Nominees NANOG Program Committee L Sean Kennedy
Re: Network Speed Testing and Monitoring Platform Colton Conor
Re: Network Speed Testing and Monitoring Platform tgrand via NANOG
Re: Network Speed Testing and Monitoring Platform Eric Dugas
Re: Network Speed Testing and Monitoring Platform Alain Hebert
RE: ASNs decimation in ZW this morning Keith Medcalf
Re: Network Speed Testing and Monitoring Platform Aled Morris via NANOG
Re: Network Speed Testing and Monitoring Platform Livingood, Jason
RE: Network Speed Testing and Monitoring Platform Aaron Gould
Re: Network Speed Testing and Monitoring Platform Chris Boyd
RE: Network Speed Testing and Monitoring Platform Zach Puls
Re: Network Speed Testing and Monitoring Platform R. Scott Evans
Re: Network Speed Testing and Monitoring Platform rapier
Coloblox Atlanta down? Raleigh Apple
Re: Stupid Question maybe? Christian Meutes
Re: Network Speed Testing and Monitoring Platform Blake Hudson
RE: Announcing Peering-LAN prefixes to customers adamv0025
No IPv6 by design to increase reliability... John Von Essen
Re: No IPv6 by design to increase reliability... Blake Hudson
Re: No IPv6 by design to increase reliability... Owen DeLong
Re: No IPv6 by design to increase reliability... Ca By
Re: No IPv6 by design to increase reliability... John Levine
Re: No IPv6 by design to increase reliability... Carlos M. Martinez
Re: No IPv6 by design to increase reliability... Owen DeLong
RE: Network Speed Testing and Monitoring Platform Philip Loenneker
Re: Network Speed Testing and Monitoring Platform Mike Hammett
colocation in Kansas City Tom Ammon

Friday, 18 January

Re: ASNs decimation in ZW this morning Mark Tinka
Re: ASNs decimation in ZW this morning Colin Johnston
RE: Your opinion on network analysis in the presence of uncertain events adamv0025
Re: Network Speed Testing and Monitoring Platform Colton Conor
Re: Network Speed Testing and Monitoring Platform Colton Conor
Re: Network Speed Testing and Monitoring Platform Colton Conor
Re: Network Speed Testing and Monitoring Platform Mike Hammett
AT&T starting to charge for RFOs on ASE tail circuits? Victor Breen
RE: Anyone using AT&T's ECOMP/ONAP? adamv0025
Re: AT&T starting to charge for RFOs on ASE tail circuits? Kaiser, Erich
Re: colocation in Kansas City James Breeden
contact from AS3 Ricardo Patara
Re: contact from AS3 Michael Still
RE: Network Speed Testing and Monitoring Platform Aaron Gould
RE: Network Speed Testing and Monitoring Platform Luke Guillory
Re: AT&T starting to charge for RFOs on ASE tail circuits? Victor Breen
Re: AT&T starting to charge for RFOs on ASE tail circuits? Mel Beckman
Re: contact from AS3 Ricardo Patara
RE: AT&T starting to charge for RFOs on ASE tail circuits? Tony Patti
RE: Network Speed Testing and Monitoring Platform Luke Guillory
Waves between Buffalo and Manhattan Jason Lixfeld
Re: Waves between Buffalo and Manhattan Mehmet Akcin
Weekly Routing Table Report Routing Analysis Role Account
Re: Waves between Buffalo and Manhattan Jason Lixfeld
Re: Waves between Buffalo and Manhattan Benjamin Hatton
Re: Waves between Buffalo and Manhattan Tom Beecher
Re: Network Speed Testing and Monitoring Platform Colton Conor
RE: Network Speed Testing and Monitoring Platform Aaron Gould
Looking for a network operations/security contact at BNSF railway Eric Kuhnke
Contact for BART Ben Cannon
Charter Porting Mike Hammett
Re: Contact for BART William Herrin
Re: Contact for BART Ben Cannon
Re: Contact for BART Larry LaBas
Re: Contact for BART William Herrin
Re: Contact for BART Ben Cannon

Saturday, 19 January

Re: Contact for BART Owen DeLong
Re: Contact for BART Owen DeLong

Sunday, 20 January

Re: Contact for BART Scott Christopher
Re: Contact for BART Mike Hale
DANOS - The Linux Foundation - AT&T Ramy Hashish
Re: Contact for BART Owen DeLong
Re: Contact for BART Ben Cannon
RE: Network Speed Testing and Monitoring Platform Philip Loenneker

Monday, 21 January

RE: Tools for streaming analysis Edwin Pers
Re: Contact for BART Scott Christopher
do we not get agenda of nanog meeting in advance ? Mankamana Mishra (mankamis) via NANOG
Re: do we not get agenda of nanog meeting in advance ? Dan Halperin via NANOG

Tuesday, 22 January

Re: Network Speed Testing and Monitoring Platform Mark Tinka
RE: Contact for BART Marshall, Quincy
Re: BGP Experiment Italo Cunha
Re: Charter Porting Mike Hammett

Wednesday, 23 January

PREPA Mehmet Akcin
Re: BGP Experiment Italo Cunha
Re: BGP Experiment Job Snijders
Re: BGP Experiment Eric Kuhnke
RE: BGP Experiment Naslund, Steve
Re: BGP Experiment Töma Gavrichenkov
Re: BGP Experiment Aled Morris via NANOG
Re: BGP Experiment Töma Gavrichenkov
Re: BGP Experiment Nick Hilliard
Re: BGP Experiment Filip Hruska
RE: BGP Experiment Naslund, Steve
RE: BGP Experiment Naslund, Steve
RE: BGP Experiment Naslund, Steve
Re: BGP Experiment Christoffer Hansen
Re: BGP Experiment Nikolas Geyer
Re: BGP Experiment Christoffer Hansen
Re: BGP Experiment James Jun
Re: BGP Experiment Christoffer Hansen
IPv6 NAT64 Art Stephens
Re: IPv6 NAT64 Brandon Martin
Re: IPv6 NAT64 Ca By
Re: BGP Experiment Owen DeLong
DNS Flag Day, Friday, Feb 1st, 2019 Brian Kantor
Re: BGP Experiment Paul S.
Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews
Re: BGP Experiment Töma Gavrichenkov
Re: BGP Experiment Mark Tinka
Re: DNS Flag Day, Friday, Feb 1st, 2019 Christopher Morrow
Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews
Re: DNS Flag Day, Friday, Feb 1st, 2019 Christopher Morrow
Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews
Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews
Re: DNS Flag Day, Friday, Feb 1st, 2019 Christopher Morrow
Re: BGP Experiment William Herrin
Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews
Re: IPv6 NAT64 William Herrin

Thursday, 24 January

Re: DNS Flag Day, Friday, Feb 1st, 2019 Mike Meredith
Re: DNS Flag Day, Friday, Feb 1st, 2019 Niels Bakker
Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews
Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews
Re: DNS Flag Day, Friday, Feb 1st, 2019 Bjørn Mork
Global statistics during the experiment (was Re: BGP Experiment) Mike Tancsa
Re: Global statistics during the experiment (was Re: BGP Experiment) Töma Gavrichenkov
Cloud networking technologies landscape Rich Edwards
DWDM 10ms failover David Williams
A survey about networking incidents Yu, Minlan
Re: BGP Experiment Ben Cooper
Contact at Google - Security Reliability Engineering Gavin Schoch
Cloud based Network monitoring service Shivaram Mysore
Re: DNS Flag Day, Friday, Feb 1st, 2019 Eric Brander
Any way to collect network usage data for dial-up subscriber aun Joe
Re: DNS Flag Day, Friday, Feb 1st, 2019 Stephen Satchell
RE: BGP Experiment adamv0025
Re: BGP Experiment Brian Kantor
RE: BGP Experiment adamv0025
Re: BGP Experiment Saku Ytti
RE: BGP Experiment adamv0025
Re: Any way to collect network usage data for dial-up subscriber Christopher Morrow
Re: BGP Experiment Mike Hale
RE: A survey about networking incidents Aaron Gould
RE: Any way to collect network usage data for dial-up subscriber Tony Wicks
Re: DNS Flag Day, Friday, Feb 1st, 2019 Christopher Morrow
Re: Amazon Peering Tom Beecher
Re: Amazon Peering Jason Lixfeld
Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews
Re: Amazon Peering Tom Beecher
Re: Amazon Peering Mike Hammett
Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews
Re: Amazon Peering Darin Steffl
Re: DNS Flag Day, Friday, Feb 1st, 2019 Stephen Satchell
Re: BGP Experiment valdis . kletnieks
Los Angeles Meet Up Mehmet Akcin
Re: BGP Experiment Saku Ytti

Friday, 25 January

Looking for contact from AS24218 Grzegorz Dabrowski
[ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Steven Bahnsen
Re: [ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Tom Beecher
Re: [ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Tom Hill
Re: [ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Mel Beckman
Re: [ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Saku Ytti
RE: [ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Aaron Gould
Re: [ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Forrest Christian (List Account)
Weekly Routing Table Report Routing Analysis Role Account
Re: [ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Randy Bush
Re: [ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Tom Beecher
Re: [ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Randy Bush
RE: [ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Aaron Gould
Re: BGP Experiment Jakob Heitz (jheitz) via NANOG
Re: BGP Experiment Tom Beecher
Re: BGP Experiment Randy via NANOG
Quick Script to check the uptime of ASR920's Erik Sundberg
RE: Quick Script to check the uptime of ASR920's Erik Sundberg
Re: Quick Script to check the uptime of ASR920's Mel Beckman
RE: Quick Script to check the uptime of ASR920's Erik Sundberg
Re: Quick Script to check the uptime of ASR920's Jason Hellenthal via NANOG
Re: BGP Experiment Mark Tees
Re: BGP Experiment Mark Tees

Saturday, 26 January

Re: BGP Experiment Randy Bush
Re: BGP Experiment Owen DeLong
Re: BGP Experiment Eric Kuhnke
Re: BGP Experiment Nick Hilliard
Re: BGP Experiment Randy Bush
Re: BGP Experiment valdis . kletnieks
Re: BGP Experiment Owen DeLong
Re: BGP Experiment Randy Bush

Sunday, 27 January

Re: BGP Experiment William Allen Simpson
[2019/01/27] Re: BGP Experiment Hansen, Christoffer
Comcast email contact Josh Smith
Re: Quick Script to check the uptime of ASR920's Laurent Dumont
Process for deploying new BGP attributes (experimentally or otherwise) Amir Herzberg
Re: BGP Experiment Randy Bush
Re: BGP Experiment Nick Hilliard
Re: Comcast email contact Mike Hammett

Monday, 28 January

Re: BGP Experiment Brian Kantor
Verizon(AS701) announcing Comcast(AS7922) subnet 68.80.240.0/24 Smith, Courtney
Re: Verizon(AS701) announcing Comcast(AS7922) subnet 68.80.240.0/24 Christopher Morrow
Re: Verizon(AS701) announcing Comcast(AS7922) subnet 68.80.240.0/24 Job Snijders
Re: Amazon Peering Anurag Bhatia
Since today is a day ending in "Y" it's route hijack day? (Excelcom - as24203 please call) Christopher Morrow
Re: Verizon(AS701) announcing Comcast(AS7922) subnet 68.80.240.0/24 Smith, Courtney
Re: Verizon(AS701) announcing Comcast(AS7922) subnet 68.80.240.0/24 Smith, Courtney
Re: Amazon Peering Tom Beecher

Tuesday, 29 January

Re: Amazon Peering Brooks Swinnerton
NANOG 75 Bradley Raymo
AT&T Fiber Outage in Holmdel, NJ Amauris Rodriguez Martinez
Re: AT&T Fiber Outage in Holmdel, NJ Mehmet Akcin
NIST looking for comments on "Secure Interdomain Traffic Exchange – BGP Robustness and DDoS Mitigation: NIST Releases Draft NIST SP 800-189" Warren Kumari
Call for Presentations - CHI-NOG 09 (May 23rd) Tom Kacprzynski

Wednesday, 30 January

Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Jason Lixfeld
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Bryan Holloway
Re: AT&T Fiber Outage in Holmdel, NJ Amauris Rodriguez Martinez
Re: Amazon Peering Luca Salvatore via NANOG
Re: Amazon Peering Mike Hammett
Effects of Cold Front on Internet Infrastructure - U.S. Midwest Mark Tinka
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mike Hammett
Re: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Mel Beckman
Re: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Bryan Holloway
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mehmet Akcin
Re: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Christopher Morrow
RE: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Naslund, Steve
Re: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Tom Beecher
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Jared Mauch
RE: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Naslund, Steve
RE: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Naslund, Steve
Re: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Paul Zugnoni via NANOG
Re: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Mark Tinka
RE: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Naslund, Steve
RE: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Naslund, Steve
Re: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Tom Beecher
Re: Amazon Peering Luca Salvatore via NANOG
RE: Amazon Peering Naslund, Steve
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY James Stankiewicz
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Marijana Novakovic via NANOG
Re: Amazon Peering Denis Fondras
Re: Amazon Peering Tom Beecher
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Thomas King
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Ren Provo
RE: Effects of Cold Front on Internet Infrastructure - U.S. Midwest bzs
Re: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Matthew Petach
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Töma Gavrichenkov
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY i3D . net - Martijn Schmidt
Re: DNS Flag Day, Friday, Feb 1st, 2019 Matthew Petach
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY valdis . kletnieks
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mike Hammett
Re: DNS Flag Day, Friday, Feb 1st, 2019 Jim Popovitch via NANOG
Re: DNS Flag Day, Friday, Feb 1st, 2019 Christopher Morrow
Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews
Re: DNS Flag Day, Friday, Feb 1st, 2019 Jim Popovitch via NANOG
Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews
Re: DNS Flag Day, Friday, Feb 1st, 2019 Christopher Morrow
RE: DNS Flag Day, Friday, Feb 1st, 2019 Keith Medcalf
Calling Jason Lixfeld @ DE-CIX NY Marijana Novakovic via NANOG
Re: DNS Flag Day, Friday, Feb 1st, 2019 Christopher Morrow
Re: DNS Flag Day, Friday, Feb 1st, 2019 Jimmy Hess
Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews
Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews
Re: BGP Experiment hank
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Thomas King

Thursday, 31 January

Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mark Tinka
RE: BGP Experiment adamv0025
Re: BGP Experiment Saku Ytti
Re: DNS Flag Day, Friday, Feb 1st, 2019 Radu-Adrian Feurdean
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Julien Goodwin
Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews
Re: DNS Flag Day, Friday, Feb 1st, 2019 Matthew Petach
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mark Tinka
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mike Hammett
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mark Tinka
Re: DNS Flag Day, Friday, Feb 1st, 2019 Jimmy Hess
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mike Hammett
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mark Tinka
Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews
Re: DNS Flag Day, Friday, Feb 1st, 2019 Stephen Satchell
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mike Hammett
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mark Tinka
Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews
RE: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Hiers, David
Re: DNS Flag Day, Friday, Feb 1st, 2019 James Stahr
Re: DNS Flag Day, Friday, Feb 1st, 2019 Owen DeLong
Re: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Fletcher Kittredge
Latency between Dallas and west coast Nathanael Catangay Cariaga
Re: Latency between Dallas and west coast Mike Hammett
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Owen DeLong
Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Tinka
Re: DNS Flag Day, Friday, Feb 1st, 2019 Jimmy Hess
Re: Latency between Dallas and west coast Mark Tinka
Re: Latency between Dallas and west coast Tom Beecher
Re: Latency between Dallas and west coast Nathanael Catangay Cariaga
Re: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Mel Beckman
Re: BGP Experiment Randy Bush
Re: Latency between Dallas and west coast JASON BOTHE via NANOG
RTBH no_export Roel Parijs
RE: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Colin Stanners (lists)
Re: RTBH no_export Łukasz Bromirski
Re: RTBH no_export Nick Hilliard
Re: RTBH no_export Theodore Baschak
Re: DNS Flag Day, Friday, Feb 1st, 2019 Doug Barton
RE: RTBH no_export Michel Py
Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews
Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews
Google you have a problem. Mark Andrews
Re: Google you have a problem. Christopher Morrow
Re: Google you have a problem. Mark Andrews
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Bryan Holloway
Re: RTBH no_export Alejandro Acosta
Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Niels Bakker
RE: RTBH no_export Michel Py
Re: Google you have a problem. Christopher Morrow
Re: Google you have a problem. Mark Andrews
Re: Google you have a problem. Christopher Morrow