nanog: by thread

• RSS Feed
• About List
• All Lists

Previous period

Next period

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

• Re: CenturyLink RCA? William Allen Simpson (Jan 01)
  • <Possible follow-ups>
  • Re: CenturyLink RCA? Tom Beecher (Jan 02)
• Re: IP Dslams Nick Edwards (Jan 01)
  • Re: IP Dslams Brandon Martin (Jan 01)
  • Re: IP Dslams Nick Edwards (Jan 01)
    • Re: IP Dslams Colton Conor (Jan 01)
      • Re: IP Dslams Nick Edwards (Jan 02)
      • Re: IP Dslams Brandon Martin (Jan 02)
      • Re: IP Dslams Nick Edwards (Jan 04)
      • Re: IP Dslams Shawn L via NANOG (Jan 04)
      • Re: IP Dslams Blake Hudson (Jan 04)
      • Re: IP Dslams Shawn L via NANOG (Jan 04)
      • Re: IP Dslams Brandon Martin (Jan 04)
      • Re: IP Dslams Jeff Shultz (Jan 04)
  • <Possible follow-ups>
  • Re: IP Dslams Mikael Abrahamsson (Jan 04)
  • Re: IP Dslams Rob Pickering (Jan 04)
  • RE: IP Dslams Payam Poursaied (Jan 04)
    • Re: IP Dslams Sander Steffann (Jan 05)
      • RE: IP Dslams Payam Poursaied (Jan 05)
      • Re: IP Dslams Sander Steffann (Jan 06)
• Re: CenturyLink valdis . kletnieks (Jan 01)
  • Re: CenturyLink Saku Ytti (Jan 01)
• Re: Service Provider NetFlow Collectors H I Baysal (Jan 02)
  • Re: Service Provider NetFlow Collectors Tim Raphael (Jan 02)
    • Re: Service Provider NetFlow Collectors Saku Ytti (Jan 02)
      • Re: Service Provider NetFlow Collectors Tim Raphael (Jan 02)
    • Re: Service Provider NetFlow Collectors H I Baysal (Jan 02)
      • Re: Service Provider NetFlow Collectors Saku Ytti (Jan 02)
      • Re: Service Provider NetFlow Collectors H I Baysal (Jan 02)
      • Re: Service Provider NetFlow Collectors Tim Raphael (Jan 02)
  • <Possible follow-ups>
  • RE: Service Provider NetFlow Collectors Phil Lavin (Jan 02)
    • Re: Service Provider NetFlow Collectors Daniel Rohan (Jan 02)
  • Re: Service Provider NetFlow Collectors Nick Peelman (Jan 02)
    • Re: Service Provider NetFlow Collectors Mark Tinka (Jan 15)
  • Re: Service Provider NetFlow Collectors Aaron (Jan 03)
  • Re: Service Provider NetFlow Collectors jim deleskie (Jan 16)
    • Re: Service Provider NetFlow Collectors James Breeden (Jan 16)
• Re: Auto-configuring IPv6 transition mechanisms on customer devices Brandon Martin (Jan 02)
  • Re: Auto-configuring IPv6 transition mechanisms on customer devices Mikael Abrahamsson (Jan 02)
    • Re: Auto-configuring IPv6 transition mechanisms on customer devices Brandon Martin (Jan 02)
      • Re: Auto-configuring IPv6 transition mechanisms on customer devices Mikael Abrahamsson (Jan 02)
      • Re: Auto-configuring IPv6 transition mechanisms on customer devices Lee Howard (Jan 02)
      • Re: Auto-configuring IPv6 transition mechanisms on customer devices Brandon Martin (Jan 02)
• Re: How to choose a transport(terrestrial/subsea) Alfie Pates (Jan 02)
  • RE: How to choose a transport(terrestrial/subsea) Naslund, Steve (Jan 02)
    • Re: How to choose a transport(terrestrial/subsea) Mike Hammett (Jan 02)
      • Re: How to choose a transport(terrestrial/subsea) Tom Beecher (Jan 02)
      • Re: How to choose a transport(terrestrial/subsea) Saku Ytti (Jan 02)
      • RE: How to choose a transport(terrestrial/subsea) Naslund, Steve (Jan 02)
      • Re: How to choose a transport(terrestrial/subsea) Jason Bothe via NANOG (Jan 02)
      • Re: How to choose a transport(terrestrial/subsea) Mehmet Akcin (Jan 04)
• Cleveland/Cincinnati Co-location Mitchell Lewis (Jan 02)
  • Re: Cleveland/Cincinnati Co-location Paul Timmins (Jan 02)
    • Re: Cleveland/Cincinnati Co-location Matt Erculiani (Jan 02)
      • Re: Cleveland/Cincinnati Co-location Jeff Waddell (Jan 02)
  • Re: Cleveland/Cincinnati Co-location Justin M. Streiner (Jan 02)
    • Re: Cleveland/Cincinnati Co-location Allen McKinley Kitchen (gmail) (Jan 03)
      • Re: Cleveland/Cincinnati Co-location Shawn Ritchie (Jan 03)
  • <Possible follow-ups>
  • Re: Cleveland/Cincinnati Co-location David Kehoe (Jan 04)
    • Re: Cleveland/Cincinnati Co-location Ross Tajvar (Jan 06)
      • Re: Cleveland/Cincinnati Co-location Crist Clark (Jan 06)
      • Re: Cleveland/Cincinnati Co-location David Kehoe (Jan 06)
• does emergency (911) dispatch uses IP ? Mankamana Mishra (mankamis) via NANOG (Jan 02)
  • RE: does emergency (911) dispatch uses IP ? Naslund, Steve (Jan 02)
  • Re: does emergency (911) dispatch uses IP ? Sean Donelan (Jan 02)
    • RE: does emergency (911) dispatch uses IP ? Naslund, Steve (Jan 02)
  • RE: does emergency (911) dispatch uses IP ? Naslund, Steve (Jan 02)
• Re: Announcing Peering-LAN prefixes to customers Andy Davidson (Jan 03)
  • Re: Announcing Peering-LAN prefixes to customers Mark Tinka (Jan 15)
    • Re: Announcing Peering-LAN prefixes to customers Job Snijders (Jan 16)
      • Re: Announcing Peering-LAN prefixes to customers Mark Tinka (Jan 16)
    • Re: Announcing Peering-LAN prefixes to customers Christoffer Hansen (Jan 16)
      • Re: Announcing Peering-LAN prefixes to customers Job Snijders (Jan 16)
      • Re: Announcing Peering-LAN prefixes to customers Siyuan Miao (Jan 16)
      • Re: Announcing Peering-LAN prefixes to customers Mark Tinka (Jan 16)
      • Re: Announcing Peering-LAN prefixes to customers Job Snijders (Jan 16)
      • Re: Announcing Peering-LAN prefixes to customers Amreesh Phokeer (Jan 16)
      • Re: Announcing Peering-LAN prefixes to customers Matthias Waehlisch (Jan 16)
      • Re: Announcing Peering-LAN prefixes to customers Randy Bush (Jan 16)
      • Re: Announcing Peering-LAN prefixes to customers Job Snijders (Jan 16)
    • Re: Announcing Peering-LAN prefixes to customers Randy Bush (Jan 16)
    • Message not available
      • Re: Announcing Peering-LAN prefixes to customers John Kristoff (Jan 16)
      • Re: Announcing Peering-LAN prefixes to customers Christoffer Hansen (Jan 16)
      • Re: Announcing Peering-LAN prefixes to customers Job Snijders (Jan 16)
      • Re: Announcing Peering-LAN prefixes to customers Arnold Nipper (Jan 16)
      • Message not available
      • Re: Announcing Peering-LAN prefixes to customers John Kristoff (Jan 16)
      • Re: Announcing Peering-LAN prefixes to customers Randy Bush (Jan 16)
  • <Possible follow-ups>
  • RE: Announcing Peering-LAN prefixes to customers adamv0025 (Jan 17)
• Report on Legal Barriers to RPKI Adoption Christopher S. Yoo (Jan 03)
  • Re: Report on Legal Barriers to RPKI Adoption Job Snijders (Jan 06)
    • Re: Report on Legal Barriers to RPKI Adoption Nathalie Trenaman (Jan 08)
      • Re: Report on Legal Barriers to RPKI Adoption Ben Maddison via NANOG (Jan 09)
• 192.208.19.0/24 hijack transiting 209, 286, 3320, 5511, 6461, 6762, 6830, 8220, 9002, 12956 Dominik Bay (Jan 03)
  • Re: 192.208.19.0/24 hijack transiting 209, 286, 3320, 5511, 6461, 6762, 6830, 8220, 9002, 12956 Jeff Shultz (Jan 03)
  • Re: 192.208.19.0/24 hijack transiting 209, 286, 3320, 5511, 6461, 6762, 6830, 8220, 9002, 12956 Job Snijders (Jan 04)
  • (FIXED) Re: 192.208.19.0/24 hijack transiting 209, 286, 3320, 5511, 6461, 6762, 6830, 8220, 9002, 12956 Dominik Bay (Jan 04)
• Astronaut accidently calls 911 from space Sean Donelan (Jan 03)
  • Re: Astronaut accidently calls 911 from space Wes Hardaker (Jan 07)
• Re: Cellular backup connections Dovid Bender (Jan 03)
  • <Possible follow-ups>
  • Re: Cellular backup connections Ian Henderson (Jan 07)
• Weekly Routing Table Report Routing Analysis Role Account (Jan 04)
  • <Possible follow-ups>
  • Weekly Routing Table Report Routing Analysis Role Account (Jan 11)
  • Weekly Routing Table Report Routing Analysis Role Account (Jan 18)
  • Weekly Routing Table Report Routing Analysis Role Account (Jan 25)
• Changing upstream providers, opinions/thoughts on 123.net and cogent Aaron Henderson (Jan 04)
  • Re: Changing upstream providers, opinions/thoughts on 123.net and cogent Ben Cannon (Jan 04)
  • Re: Changing upstream providers, opinions/thoughts on 123.net and cogent William Herrin (Jan 04)
  • Re: Changing upstream providers, opinions/thoughts on 123.net and cogent Brandon Martin (Jan 04)
  • RE: Changing upstream providers, opinions/thoughts on 123.net and cogent Aaron Gould (Jan 08)
  • <Possible follow-ups>
  • Re: Changing upstream providers, opinions/thoughts on 123.net and cogent Neader, Brent (Jan 07)
• Verizon IDE Mitchell Lewis (Jan 05)
  • Re: Verizon IDE Justin M. Streiner (Jan 05)
    • Re: Verizon IDE Mel Beckman (Jan 05)
• attempted archive.is hijacking Dan Hollis (Jan 05)
  • Re: attempted archive.is hijacking Alfie Pates (Jan 07)
  • Re: attempted archive.is hijacking Ops One AG | Markus Ritzmann (Jan 07)
• Google Fiber v6 PD only giving /64 Chris Adams (Jan 05)
  • Re: Google Fiber v6 PD only giving /64 Sander Steffann (Jan 06)
  • Re: Google Fiber v6 PD only giving /64 Heather Schiller via NANOG (Jan 10)
• Re: BGP Experiment Italo Cunha (Jan 08)
  • Re: BGP Experiment niels=nanog (Jan 08)
    • Re: BGP Experiment Tom Ammon (Jan 08)
      • Re: BGP Experiment niels=nanog (Jan 08)
      • Re: BGP Experiment Jared Mauch (Jan 08)
      • Re: BGP Experiment Töma Gavrichenkov (Jan 08)
      • Re: BGP Experiment Steve Noble (Jan 08)
      • Message not available
      • RE: BGP Experiment adamv0025 (Jan 08)
      • Re: BGP Experiment Stephen Satchell (Jan 08)
      • Re: BGP Experiment Job Snijders (Jan 08)
    • Re: BGP Experiment Italo Cunha (Jan 08)
    • Re: BGP Experiment Saku Ytti (Jan 08)
      • Re: BGP Experiment niels=nanog (Jan 08)
    • Re: BGP Experiment valdis . kletnieks (Jan 08)
      • Re: BGP Experiment niels=nanog (Jan 08)
      • Re: BGP Experiment Jared Mauch (Jan 08)
      • Re: BGP Experiment Owen DeLong (Jan 09)
    • Re: BGP Experiment Nick Hilliard (Jan 08)
  • Re: BGP Experiment Randy Bush (Jan 08)
    • Re: BGP Experiment Eric Kuhnke (Jan 08)
      • Re: BGP Experiment Randy Bush (Jan 08)
      • Re: BGP Experiment Job Snijders (Jan 08)
      • Re: BGP Experiment Tore Anderson (Jan 08)
      • Re: BGP Experiment Töma Gavrichenkov (Jan 09)
      • Re: BGP Experiment Saku Ytti (Jan 09)
      • Re: BGP Experiment Töma Gavrichenkov (Jan 09)
      • Re: BGP Experiment Saku Ytti (Jan 09)
      • Re: BGP Experiment Töma Gavrichenkov (Jan 09)
      • Re: BGP Experiment Owen DeLong (Jan 09)
      • Re: BGP Experiment Töma Gavrichenkov (Jan 09)
      • Re: BGP Experiment Saku Ytti (Jan 09)
      • Re: BGP Experiment Töma Gavrichenkov (Jan 09)
      • Re: BGP Experiment Saku Ytti (Jan 09)
      • Re: BGP Experiment Töma Gavrichenkov (Jan 09)
      • RE: BGP Experiment adamv0025 (Jan 09)
      • Re: BGP Experiment Töma Gavrichenkov (Jan 09)
      • Re: BGP Experiment Owen DeLong (Jan 09)
      • Re: BGP Experiment Owen DeLong (Jan 09)
      • Re: BGP Experiment Töma Gavrichenkov (Jan 09)
      • Re: BGP Experiment Töma Gavrichenkov (Jan 09)
  • Re: BGP Experiment Italo Cunha (Jan 10)
  • <Possible follow-ups>
  • Re: BGP Experiment Italo Cunha (Jan 22)
    • Re: BGP Experiment Ben Cooper (Jan 24)
      • Re: BGP Experiment Italo Cunha (Jan 23)
      • Re: BGP Experiment Job Snijders (Jan 23)
      • Re: BGP Experiment Eric Kuhnke (Jan 23)
      • RE: BGP Experiment Naslund, Steve (Jan 23)
      • Re: BGP Experiment Aled Morris via NANOG (Jan 23)
      • Re: BGP Experiment Töma Gavrichenkov (Jan 23)
      • RE: BGP Experiment Naslund, Steve (Jan 23)
      • RE: BGP Experiment Naslund, Steve (Jan 23)
      • Re: BGP Experiment Töma Gavrichenkov (Jan 23)
      • Re: BGP Experiment Nick Hilliard (Jan 23)
      • Re: BGP Experiment Filip Hruska (Jan 23)
      • RE: BGP Experiment Naslund, Steve (Jan 23)
      • Re: BGP Experiment Owen DeLong (Jan 23)
      • Re: BGP Experiment William Herrin (Jan 23)
      • Re: BGP Experiment Christoffer Hansen (Jan 23)
      • Re: BGP Experiment Nikolas Geyer (Jan 23)
      • Re: BGP Experiment James Jun (Jan 23)
      • Re: BGP Experiment Christoffer Hansen (Jan 23)
      • Re: BGP Experiment Mark Tinka (Jan 23)
      • RE: BGP Experiment adamv0025 (Jan 24)
      • Re: BGP Experiment Brian Kantor (Jan 24)
      • RE: BGP Experiment adamv0025 (Jan 24)
      • Re: BGP Experiment Saku Ytti (Jan 24)
      • RE: BGP Experiment adamv0025 (Jan 24)
      • Re: BGP Experiment Saku Ytti (Jan 24)
      • RE: BGP Experiment adamv0025 (Jan 31)
      • Re: BGP Experiment Saku Ytti (Jan 31)
      • Re: BGP Experiment Randy Bush (Jan 31)
      • Re: BGP Experiment Christoffer Hansen (Jan 23)
      • Re: BGP Experiment Paul S. (Jan 23)
      • Re: BGP Experiment Töma Gavrichenkov (Jan 23)
      • Global statistics during the experiment (was Re: BGP Experiment) Mike Tancsa (Jan 24)
      • Re: Global statistics during the experiment (was Re: BGP Experiment) Töma Gavrichenkov (Jan 24)
      • Re: BGP Experiment Mike Hale (Jan 24)
      • Re: BGP Experiment valdis . kletnieks (Jan 24)
      • Re: BGP Experiment Tom Beecher (Jan 25)
      • Re: BGP Experiment Randy via NANOG (Jan 25)
      • Re: BGP Experiment Mark Tees (Jan 25)
      • Re: BGP Experiment Mark Tees (Jan 25)
      • Re: BGP Experiment Randy Bush (Jan 26)
      • Re: BGP Experiment Owen DeLong (Jan 26)
      • Re: BGP Experiment valdis . kletnieks (Jan 26)
      • Re: BGP Experiment Owen DeLong (Jan 26)
      • Re: BGP Experiment Randy Bush (Jan 26)
      • Re: BGP Experiment Eric Kuhnke (Jan 26)
      • Re: BGP Experiment Nick Hilliard (Jan 26)
      • Re: BGP Experiment Randy Bush (Jan 26)
      • Re: BGP Experiment William Allen Simpson (Jan 27)
      • [2019/01/27] Re: BGP Experiment Hansen, Christoffer (Jan 27)
      • Re: BGP Experiment Randy Bush (Jan 27)
      • Re: BGP Experiment Nick Hilliard (Jan 27)
      • Re: BGP Experiment Brian Kantor (Jan 28)
  • Re: BGP Experiment Jakob Heitz (jheitz) via NANOG (Jan 25)
  • Re: BGP Experiment hank (Jan 30)
• Spoofer Report for NANOG for Dec 2018 CAIDA Spoofer Project (Jan 09)
• DNS Hijacking? - FiOS Northeast Blake Mckeeby (Jan 09)
  • RE: DNS Hijacking? - FiOS Northeast Phil Lavin (Jan 09)
    • Re: DNS Hijacking? - FiOS Northeast Jim Popovitch via NANOG (Jan 10)
  • RE: DNS Hijacking? - FiOS Northeast Chris Kimball (Jan 09)
• Centurylink/Level3 WDM? James Breeden (Jan 09)
  • Re: Centurylink/Level3 WDM? James Breeden (Jan 09)
• Call for presentations RIPE 78 Benno Overeinder (Jan 10)
• Proofpoint Mail Delivery Issues Tim Donahue (Jan 10)
  • Re: Proofpoint Mail Delivery Issues Mike Hammett (Jan 10)
    • Re: Proofpoint Mail Delivery Issues Brian Kantor (Jan 10)
      • Re: Proofpoint Mail Delivery Issues Dan White (Jan 10)
      • RE: Proofpoint Mail Delivery Issues David McCabe (Jan 10)
  • Re: Proofpoint Mail Delivery Issues Jaren Angerbauer (Jan 10)
  • RE: Proofpoint Mail Delivery Issues Tony Wicks (Jan 10)
• Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Rich Kulawiec (Jan 10)
  • Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues J. Hellenthal via NANOG (Jan 10)
    • Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Rich Kulawiec (Jan 11)
    • Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Anne P. Mitchell, Esq. (Jan 11)
  • Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Yang Yu (Jan 11)
    • Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Ross Tajvar (Jan 11)
    • Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Mike Hammett (Jan 11)
      • Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Brian Kantor (Jan 11)
    • Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Rich Kulawiec (Jan 11)
      • Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Andreas Ott (Jan 11)
      • Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Rob McEwen (Jan 11)
      • Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Töma Gavrichenkov (Jan 11)
      • Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Mark Andrews (Jan 11)
      • Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Töma Gavrichenkov (Jan 11)
      • Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues cosmo (Jan 11)
      • Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Grant Taylor via NANOG (Jan 11)
      • Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Rob McEwen (Jan 11)
      • Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Bryan Holloway (Jan 11)
  • Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues Töma Gavrichenkov (Jan 11)
• Switch.com AS23005 John Von Essen (Jan 10)
• ARIN NS down? Suresh Ramasubramanian (Jan 11)
  • Re: ARIN NS down? John Curran (Jan 11)
    • Re: ARIN NS down? i3D.net - Martijn Schmidt (Jan 11)
    • Dnssec still inoperable on the internet ?— was ARIN NS down? Ca By (Jan 11)
      • Re: Dnssec still inoperable on the internet ?— was ARIN NS down? Stephane Bortzmeyer (Jan 11)
      • Re: Dnssec still inoperable on the internet ?— was ARIN NS down? Ca By (Jan 11)
      • Re: Dnssec still inoperable on the internet ?— was ARIN NS down? Max Tulyev (Jan 11)
      • Re: Dnssec still inoperable on the internet ?― was ARIN NS down? Randy Bush (Jan 11)
      • Re: Dnssec still inoperable on the internet ?— was ARIN NS down? Antonios Chariton (Jan 11)
      • Re: Dnssec still inoperable on the internet ?— was ARIN NS down? Mikael Abrahamsson (Jan 11)
      • Re: Dnssec still inoperable on the internet ?— was ARIN NS down? Ca By (Jan 11)
  • Re: ARIN NS down? Stephane Bortzmeyer (Jan 11)
    • Re: ARIN NS down? John Curran (Jan 11)
      • 2019-01-11 ARIN.NET DNSSEC Outage – Post-Mortem (was: Re: ARIN NS down?) John Curran (Jan 11)
      • Re: 2019-01-11 ARIN.NET DNSSEC Outage – Post-Mortem (was: Re: ARIN NS down?) Stephane Bortzmeyer (Jan 14)
• SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 11)
  • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Michael Thomas (Jan 11)
  • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Doug Royer (Jan 11)
    • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 11)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Suresh Ramasubramanian (Jan 11)
  • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] William Herrin (Jan 11)
    • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 11)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] William Herrin (Jan 11)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 11)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] William Herrin (Jan 11)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Brandon Martin (Jan 11)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 11)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Suresh Ramasubramanian (Jan 11)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 11)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] valdis . kletnieks (Jan 11)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] valdis . kletnieks (Jan 11)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 11)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Töma Gavrichenkov (Jan 12)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 12)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Robert Blayzor (Jan 14)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 14)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Constantine A. Murenin (Jan 11)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Suresh Ramasubramanian (Jan 11)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Constantine A. Murenin (Jan 11)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Tom Beecher (Jan 14)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Constantine A. Murenin (Jan 11)
  • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Seth Mattinen (Jan 12)
    • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 12)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] James Downs (Jan 12)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 12)
  • Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] John Levine (Jan 12)
    • Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 12)
      • Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Brian Kantor (Jan 12)
      • Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 12)
      • Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Eric Tykwinski (Jan 12)
      • Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] valdis . kletnieks (Jan 12)
      • Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 12)
      • Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Töma Gavrichenkov (Jan 12)
      • Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Suresh Ramasubramanian (Jan 12)
      • Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 12)
      • Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Cummings, Chris (Jan 12)
      • Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 12)
      • Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Jason Hellenthal via NANOG (Jan 12)
      • Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 12)
      • Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Jason Hellenthal via NANOG (Jan 12)
      • Enough port 26 talk... Richard (Jan 12)
      • Re: Enough port 26 talk... Bjørn Mork (Jan 13)
      • Re: Enough port 26 talk... John Levine (Jan 13)
      • Message not available
      • Re: the e-mail of the future is the e-mail oft the past, was Enough port 26 talk... John R. Levine (Jan 14)
      • Re: the e-mail of the future is the e-mail oft the past, was Enough port 26 talk... Miles Fidelman (Jan 14)
      • Re: the e-mail of the future is the e-mail oft the past, was Enough port 26 talk... Bjørn Mork (Jan 15)
      • Re: the e-mail of the future is the e-mail oft the past, was Enough port 26 talk... Stephen Satchell (Jan 15)
      • Re: the e-mail of the future is the e-mail oft the past, was Enough port 26 talk... Tei (Jan 15)
      • Re: the e-mail of the future is the e-mail oft the past, was Enough port 26 talk... James Downs (Jan 15)
      • RE: the e-mail of the future is the e-mail oft the past, was Enough port 26 talk... Keith Medcalf (Jan 15)
      • Re: the e-mail of the future is the e-mail oft the past, was Enough port 26 talk... Grant Taylor via NANOG (Jan 15)
      • Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 12)
      • Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] valdis . kletnieks (Jan 12)
      • Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 12)
      • Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Ross Tajvar (Jan 12)
      • Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 12)
      • Re: yet another round of SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] valdis . kletnieks (Jan 12)
  • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Owen DeLong (Jan 12)
    • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 12)
  • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Jimmy Hess (Jan 13)
    • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 13)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] William Anderson (Jan 14)
  • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Doug Royer (Jan 14)
    • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 14)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Viruthagiri Thirumavalavan (Jan 14)
      • Re: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request] Jon Lewis (Jan 14)
• Could Someone From Yahoo Mail Please Contact Me Matt Hoppes (Jan 12)
  • Re: Could Someone From Yahoo Mail Please Contact Me Mike Hammett (Jan 12)
  • Re: Could Someone From Yahoo Mail Please Contact Me Ross Tajvar (Jan 12)
  • Re: Could Someone From Yahoo Mail Please Contact Me Udeme Ukutt (Jan 14)
    • Re: Could Someone From Yahoo Mail Please Contact Me Matt Hoppes (Jan 12)
      • Re: Could Someone From Yahoo Mail Please Contact Me Tom Beecher (Jan 14)
• Fwd: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Christoffer Hansen (Jan 13)
  • Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Mike Hammett (Jan 13)
    • Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting valdis . kletnieks (Jan 13)
    • Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Christoffer Hansen (Jan 13)
      • Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting valdis . kletnieks (Jan 13)
      • Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Christoffer Hansen (Jan 13)
      • Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Owen DeLong (Jan 14)
      • RE: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Keith Medcalf (Jan 14)
      • Top-quoting Was: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Stephen Satchell (Jan 14)
      • Re: Top-quoting Was: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Winston Polhamus (Jan 15)
    • Re: plaintext email? Brian Kantor (Jan 13)
      • Re: plaintext email? Christoffer Hansen (Jan 13)
      • Re: plaintext email? Mike Hammett (Jan 13)
      • Re: plaintext email? Jason Hellenthal via NANOG (Jan 13)
      • Re: plaintext email? James R Cutler (Jan 13)
      • Re: plaintext email? Randy Bush (Jan 14)
      • Re: plaintext email? Christopher Morrow (Jan 14)
      • Re: plaintext email? Randy Bush (Jan 14)
      • Re: plaintext email? Brian Kantor (Jan 14)
      • Re: plaintext email? Steve Atkins (Jan 14)
      • Re: plaintext email? John Levine (Jan 14)
      • Re: plaintext email? Christopher Morrow (Jan 14)
      • Re: plaintext email? bzs (Jan 14)
      • Re: plaintext email? valdis . kletnieks (Jan 14)
      • Re: plaintext email? Richard (Jan 14)
      • Re: plaintext email? Royce Williams (Jan 14)
      • Top Posting Was: Re: plaintext email? James R Cutler (Jan 15)
      • Re: Top Posting Was: Re: plaintext email? Tom Beecher (Jan 15)
      • Re: Top Posting Was: Re: plaintext email? Brian Kantor (Jan 15)
      • Re: Top Posting Was: Re: plaintext email? Stephen Satchell (Jan 15)
      • Re: Top Posting Was: Re: plaintext email? John Levine (Jan 15)
      • Re: Top Posting Was: Re: plaintext email? James R Cutler (Jan 15)
      • Re: plaintext email? Tei (Jan 15)
      • Re: plaintext email? Stephen Satchell (Jan 15)
      • Re: plaintext email? bzs (Jan 15)
      • Re: plaintext email? William Herrin (Jan 15)
      • Re: plaintext email? James R Cutler (Jan 15)
      • Re: plaintext email? bzs (Jan 15)
      • Re: plaintext email? Grant Taylor via NANOG (Jan 15)
      • Re: plaintext email? Grant Taylor via NANOG (Jan 15)
      • Re: plaintext email? Brian J. Murrell (Jan 15)
      • Re: plaintext email? Bryan Fields (Jan 15)
      • Re: plaintext email? cosmo (Jan 15)
      • Re: plaintext email? Aled Morris via NANOG (Jan 15)
      • Re: plaintext email? Christopher Morrow (Jan 15)
      • Re: plaintext email? Bryan Fields (Jan 15)
      • Re: plaintext email? bzs (Jan 15)
      • Re: plaintext email? John Levine (Jan 15)
      • Re: plaintext email? cosmo (Jan 15)
      • Re: plaintext email? bzs (Jan 15)
    • RE: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Keith Medcalf (Jan 13)
    • Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Matt Hoppes (Jan 13)
      • Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Bryce Wilson (Jan 13)
      • Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Seth Mattinen (Jan 13)
      • Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Jason Hellenthal via NANOG (Jan 13)
      • Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting James Downs (Jan 13)
      • Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Brian Kantor (Jan 13)
      • Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting valdis . kletnieks (Jan 13)
      • Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Brian Kantor (Jan 13)
      • Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Stephen Satchell (Jan 14)
    • Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Jared Mauch (Jan 13)
  • Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting Stacy W. Smith (Jan 14)
• Tools for streaming analysis Ben Logan (Jan 14)
  • RE: Tools for streaming analysis Edwin Pers (Jan 21)
• Cable/Wireless-Tower Map for the San Francisco Bay Coastside? Yosem Companys (Jan 14)
  • Re: Cable/Wireless-Tower Map for the San Francisco Bay Coastside? Mike Hammett (Jan 14)
  • Re: Cable/Wireless-Tower Map for the San Francisco Bay Coastside? Tim Pozar (Jan 14)
• CAT-TP Protocol? Richard (Jan 14)
  • Re: CAT-TP Protocol? Andrew Latham (Jan 14)
• ASNs decimation in ZW this morning C. A. Fillekes (Jan 15)
  • Re: ASNs decimation in ZW this morning C. A. Fillekes (Jan 15)
    • Re: ASNs decimation in ZW this morning Colin Johnston (Jan 15)
      • Message not available
      • Re: ASNs decimation in ZW this morning Colin Johnston (Jan 16)
      • Re: ASNs decimation in ZW this morning Mark Tinka (Jan 16)
      • Re: ASNs decimation in ZW this morning John Von Essen (Jan 16)
      • Re: ASNs decimation in ZW this morning Mark Tinka (Jan 17)
      • Re: ASNs decimation in ZW this morning Colin Johnston (Jan 17)
      • Re: ASNs decimation in ZW this morning Mark Tinka (Jan 17)
      • RE: ASNs decimation in ZW this morning Keith Medcalf (Jan 17)
      • Re: ASNs decimation in ZW this morning Mark Tinka (Jan 18)
      • Re: ASNs decimation in ZW this morning Colin Johnston (Jan 18)
  • <Possible follow-ups>
  • Re: ASNs decimation in ZW this morning Scott Weeks (Jan 16)
• Your opinion on network analysis in the presence of uncertain events Vanbever Laurent (Jan 15)
  • Re: Your opinion on network analysis in the presence of uncertain events Mel Beckman (Jan 15)
    • Re: Your opinion on network analysis in the presence of uncertain events Vanbever Laurent (Jan 15)
      • Re: Your opinion on network analysis in the presence of uncertain events Mel Beckman (Jan 15)
      • RE: Your opinion on network analysis in the presence of uncertain events adamv0025 (Jan 16)
      • Re: Your opinion on network analysis in the presence of uncertain events Mel Beckman (Jan 16)
      • Message not available
      • RE: Your opinion on network analysis in the presence of uncertain events adamv0025 (Jan 18)
      • Re: Your opinion on network analysis in the presence of uncertain events Vanbever Laurent (Jan 17)
  • Re: Your opinion on network analysis in the presence of uncertain events James Bensley (Jan 17)
• Re: plaintext email? valdis . kletnieks (Jan 15)
  • Re: plaintext email? Brian Kantor (Jan 15)
• dyn internet intelligence Mehmet Akcin (Jan 15)
  • Re: dyn internet intelligence Mehmet Akcin (Jan 16)
• Call for Participation -- ICANN DNSSEC Workshop at ICANN64 Kobe, Japan Jacques Latour (Jan 16)
• Network Speed Testing and Monitoring Platform Colton Conor (Jan 16)
  • Re: Network Speed Testing and Monitoring Platform David Guo via NANOG (Jan 16)
    • Re: Network Speed Testing and Monitoring Platform Mike Hammett (Jan 16)
    • Re: Network Speed Testing and Monitoring Platform Colton Conor (Jan 16)
      • RE: Network Speed Testing and Monitoring Platform Chris Kimball (Jan 16)
      • Re: Network Speed Testing and Monitoring Platform Casey Russell (Jan 16)
      • Re: Network Speed Testing and Monitoring Platform Ryan Wilkins (Jan 16)
      • Re: Network Speed Testing and Monitoring Platform Blake Hudson (Jan 16)
      • Re: Network Speed Testing and Monitoring Platform Alain Hebert (Jan 17)
      • RE: Network Speed Testing and Monitoring Platform Zach Puls (Jan 17)
      • Re: Network Speed Testing and Monitoring Platform Blake Hudson (Jan 17)
      • RE: Network Speed Testing and Monitoring Platform Cummings, Chris (Jan 16)
      • Re: Network Speed Testing and Monitoring Platform valdis . kletnieks (Jan 16)
      • Re: Network Speed Testing and Monitoring Platform Aled Morris via NANOG (Jan 17)
      • Re: Network Speed Testing and Monitoring Platform Livingood, Jason (Jan 17)
  • Re: Network Speed Testing and Monitoring Platform Christoffer Hansen (Jan 16)
  • Re: Network Speed Testing and Monitoring Platform J. Hellenthal via NANOG (Jan 16)
  • Re: Network Speed Testing and Monitoring Platform valdis . kletnieks (Jan 16)
    • Re: Network Speed Testing and Monitoring Platform James R Cutler (Jan 16)
  • Re: Network Speed Testing and Monitoring Platform James Bensley (Jan 17)
    • Re: Network Speed Testing and Monitoring Platform Colton Conor (Jan 17)
      • Re: Network Speed Testing and Monitoring Platform tgrand via NANOG (Jan 17)
      • Re: Network Speed Testing and Monitoring Platform Eric Dugas (Jan 17)
      • Re: Network Speed Testing and Monitoring Platform Chris Boyd (Jan 17)
      • RE: Network Speed Testing and Monitoring Platform Philip Loenneker (Jan 17)
      • Re: Network Speed Testing and Monitoring Platform Mike Hammett (Jan 17)
      • Re: Network Speed Testing and Monitoring Platform Colton Conor (Jan 18)
      • Re: Network Speed Testing and Monitoring Platform Mike Hammett (Jan 18)
      • Re: Network Speed Testing and Monitoring Platform Colton Conor (Jan 18)
      • RE: Network Speed Testing and Monitoring Platform Philip Loenneker (Jan 20)
  • RE: Network Speed Testing and Monitoring Platform Aaron Gould (Jan 17)
    • Re: Network Speed Testing and Monitoring Platform Colton Conor (Jan 18)
      • RE: Network Speed Testing and Monitoring Platform Aaron Gould (Jan 18)
      • RE: Network Speed Testing and Monitoring Platform Luke Guillory (Jan 18)
      • Message not available
      • RE: Network Speed Testing and Monitoring Platform Luke Guillory (Jan 18)
      • RE: Network Speed Testing and Monitoring Platform Aaron Gould (Jan 18)
      • Message not available
      • Re: Network Speed Testing and Monitoring Platform Colton Conor (Jan 18)
  • Re: Network Speed Testing and Monitoring Platform R. Scott Evans (Jan 17)
  • Re: Network Speed Testing and Monitoring Platform Mark Tinka (Jan 22)
  • <Possible follow-ups>
  • Re: Network Speed Testing and Monitoring Platform rapier (Jan 17)
• Fiber owners Mehmet Akcin (Jan 16)
• Call for Nominees NANOG Program Committee L Sean Kennedy (Jan 17)
• Coloblox Atlanta down? Raleigh Apple (Jan 17)
• Re: Stupid Question maybe? Christian Meutes (Jan 17)
• No IPv6 by design to increase reliability... John Von Essen (Jan 17)
  • Re: No IPv6 by design to increase reliability... Blake Hudson (Jan 17)
  • Re: No IPv6 by design to increase reliability... Owen DeLong (Jan 17)
    • Re: No IPv6 by design to increase reliability... John Levine (Jan 17)
      • Re: No IPv6 by design to increase reliability... Owen DeLong (Jan 17)
  • Re: No IPv6 by design to increase reliability... Ca By (Jan 17)
  • Re: No IPv6 by design to increase reliability... Carlos M. Martinez (Jan 17)
• colocation in Kansas City Tom Ammon (Jan 17)
  • Re: colocation in Kansas City James Breeden (Jan 18)
• AT&T starting to charge for RFOs on ASE tail circuits? Victor Breen (Jan 18)
  • Re: AT&T starting to charge for RFOs on ASE tail circuits? Kaiser, Erich (Jan 18)
    • Re: AT&T starting to charge for RFOs on ASE tail circuits? Victor Breen (Jan 18)
      • Re: AT&T starting to charge for RFOs on ASE tail circuits? Mel Beckman (Jan 18)
  • Message not available
    • RE: AT&T starting to charge for RFOs on ASE tail circuits? Tony Patti (Jan 18)
• RE: Anyone using AT&T's ECOMP/ONAP? adamv0025 (Jan 18)
• contact from AS3 Ricardo Patara (Jan 18)
  • Re: contact from AS3 Michael Still (Jan 18)
    • Re: contact from AS3 Ricardo Patara (Jan 18)
• Waves between Buffalo and Manhattan Jason Lixfeld (Jan 18)
  • Re: Waves between Buffalo and Manhattan Mehmet Akcin (Jan 18)
    • Re: Waves between Buffalo and Manhattan Jason Lixfeld (Jan 18)
    • Re: Waves between Buffalo and Manhattan Benjamin Hatton (Jan 18)
      • Re: Waves between Buffalo and Manhattan Tom Beecher (Jan 18)
• Looking for a network operations/security contact at BNSF railway Eric Kuhnke (Jan 18)
• Contact for BART Ben Cannon (Jan 18)
  • Re: Contact for BART William Herrin (Jan 18)
    • Re: Contact for BART Ben Cannon (Jan 18)
      • Re: Contact for BART Larry LaBas (Jan 18)
      • Re: Contact for BART William Herrin (Jan 18)
      • Re: Contact for BART Ben Cannon (Jan 18)
      • Re: Contact for BART Owen DeLong (Jan 19)
      • Re: Contact for BART Scott Christopher (Jan 20)
      • Re: Contact for BART Mike Hale (Jan 20)
      • Re: Contact for BART Owen DeLong (Jan 20)
      • Re: Contact for BART Ben Cannon (Jan 20)
      • Re: Contact for BART Scott Christopher (Jan 21)
      • Re: Contact for BART Owen DeLong (Jan 19)
      • RE: Contact for BART Marshall, Quincy (Jan 22)
• Charter Porting Mike Hammett (Jan 18)
  • Re: Charter Porting Mike Hammett (Jan 22)
• DANOS - The Linux Foundation - AT&T Ramy Hashish (Jan 20)
• do we not get agenda of nanog meeting in advance ? Mankamana Mishra (mankamis) via NANOG (Jan 21)
  • Re: do we not get agenda of nanog meeting in advance ? Dan Halperin via NANOG (Jan 21)
• PREPA Mehmet Akcin (Jan 23)
• IPv6 NAT64 Art Stephens (Jan 23)
  • Re: IPv6 NAT64 Brandon Martin (Jan 23)
  • Re: IPv6 NAT64 Ca By (Jan 23)
  • Re: IPv6 NAT64 William Herrin (Jan 23)
• DNS Flag Day, Friday, Feb 1st, 2019 Brian Kantor (Jan 23)
  • Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews (Jan 23)
    • Re: DNS Flag Day, Friday, Feb 1st, 2019 Mike Meredith (Jan 24)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews (Jan 24)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews (Jan 24)
    • Re: DNS Flag Day, Friday, Feb 1st, 2019 Bjørn Mork (Jan 24)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews (Jan 24)
    • Re: DNS Flag Day, Friday, Feb 1st, 2019 Eric Brander (Jan 24)
  • Re: DNS Flag Day, Friday, Feb 1st, 2019 Christopher Morrow (Jan 23)
    • Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews (Jan 23)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Christopher Morrow (Jan 23)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews (Jan 23)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews (Jan 23)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Christopher Morrow (Jan 23)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews (Jan 23)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Niels Bakker (Jan 24)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Christopher Morrow (Jan 24)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Stephen Satchell (Jan 24)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews (Jan 24)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Stephen Satchell (Jan 24)
  • Re: DNS Flag Day, Friday, Feb 1st, 2019 Matthew Petach (Jan 30)
    • Re: DNS Flag Day, Friday, Feb 1st, 2019 Jim Popovitch via NANOG (Jan 30)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Christopher Morrow (Jan 30)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Jim Popovitch via NANOG (Jan 30)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews (Jan 30)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Christopher Morrow (Jan 30)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Jimmy Hess (Jan 30)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews (Jan 30)
      • Message not available
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews (Jan 30)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Radu-Adrian Feurdean (Jan 31)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews (Jan 31)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Matthew Petach (Jan 31)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Jimmy Hess (Jan 31)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Stephen Satchell (Jan 31)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews (Jan 31)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews (Jan 31)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 James Stahr (Jan 31)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Tinka (Jan 31)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews (Jan 31)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Jimmy Hess (Jan 31)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Doug Barton (Jan 31)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews (Jan 31)
      • RE: DNS Flag Day, Friday, Feb 1st, 2019 Keith Medcalf (Jan 30)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Christopher Morrow (Jan 30)
      • Re: DNS Flag Day, Friday, Feb 1st, 2019 Owen DeLong (Jan 31)
    • Re: DNS Flag Day, Friday, Feb 1st, 2019 Mark Andrews (Jan 30)
• Cloud networking technologies landscape Rich Edwards (Jan 24)
• DWDM 10ms failover David Williams (Jan 24)
• A survey about networking incidents Yu, Minlan (Jan 24)
  • RE: A survey about networking incidents Aaron Gould (Jan 24)
• Contact at Google - Security Reliability Engineering Gavin Schoch (Jan 24)
• Cloud based Network monitoring service Shivaram Mysore (Jan 24)
• Any way to collect network usage data for dial-up subscriber aun Joe (Jan 24)
  • Re: Any way to collect network usage data for dial-up subscriber Christopher Morrow (Jan 24)
  • RE: Any way to collect network usage data for dial-up subscriber Tony Wicks (Jan 24)
• Re: Amazon Peering Tom Beecher (Jan 24)
  • Re: Amazon Peering Jason Lixfeld (Jan 24)
    • Re: Amazon Peering Tom Beecher (Jan 24)
      • Re: Amazon Peering Mike Hammett (Jan 24)
      • Re: Amazon Peering Darin Steffl (Jan 24)
      • Re: Amazon Peering Anurag Bhatia (Jan 28)
      • Re: Amazon Peering Tom Beecher (Jan 28)
      • Re: Amazon Peering Brooks Swinnerton (Jan 29)
      • Re: Amazon Peering Luca Salvatore via NANOG (Jan 30)
      • Re: Amazon Peering Mike Hammett (Jan 30)
      • Re: Amazon Peering Luca Salvatore via NANOG (Jan 30)
      • RE: Amazon Peering Naslund, Steve (Jan 30)
      • Re: Amazon Peering Denis Fondras (Jan 30)
      • Re: Amazon Peering Tom Beecher (Jan 30)
• Los Angeles Meet Up Mehmet Akcin (Jan 24)
• Looking for contact from AS24218 Grzegorz Dabrowski (Jan 25)
• [ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Steven Bahnsen (Jan 25)
  • Re: [ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Tom Beecher (Jan 25)
  • Re: [ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Tom Hill (Jan 25)
    • Re: [ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Mel Beckman (Jan 25)
  • Re: [ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Saku Ytti (Jan 25)
  • RE: [ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Aaron Gould (Jan 25)
  • Re: [ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Forrest Christian (List Account) (Jan 25)
  • Re: [ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Randy Bush (Jan 25)
    • Re: [ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Tom Beecher (Jan 25)
      • Re: [ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Randy Bush (Jan 25)
      • RE: [ROUTING] Settle a pointless debate - more commonly used routing protocol in total deployments - OSPF vs IS-IS Aaron Gould (Jan 25)
• Quick Script to check the uptime of ASR920's Erik Sundberg (Jan 25)
  • RE: Quick Script to check the uptime of ASR920's Erik Sundberg (Jan 25)
  • Re: Quick Script to check the uptime of ASR920's Mel Beckman (Jan 25)
    • RE: Quick Script to check the uptime of ASR920's Erik Sundberg (Jan 25)
      • Re: Quick Script to check the uptime of ASR920's Jason Hellenthal via NANOG (Jan 25)
      • Re: Quick Script to check the uptime of ASR920's Laurent Dumont (Jan 27)
• Comcast email contact Josh Smith (Jan 27)
  • Re: Comcast email contact Mike Hammett (Jan 27)
• Process for deploying new BGP attributes (experimentally or otherwise) Amir Herzberg (Jan 27)
• Verizon(AS701) announcing Comcast(AS7922) subnet 68.80.240.0/24 Smith, Courtney (Jan 28)
  • Re: Verizon(AS701) announcing Comcast(AS7922) subnet 68.80.240.0/24 Christopher Morrow (Jan 28)
  • Re: Verizon(AS701) announcing Comcast(AS7922) subnet 68.80.240.0/24 Job Snijders (Jan 28)
  • Re: Verizon(AS701) announcing Comcast(AS7922) subnet 68.80.240.0/24 Smith, Courtney (Jan 28)
  • <Possible follow-ups>
  • Re: Verizon(AS701) announcing Comcast(AS7922) subnet 68.80.240.0/24 Smith, Courtney (Jan 28)
• Since today is a day ending in "Y" it's route hijack day? (Excelcom - as24203 please call) Christopher Morrow (Jan 28)
• NANOG 75 Bradley Raymo (Jan 29)
• AT&T Fiber Outage in Holmdel, NJ Amauris Rodriguez Martinez (Jan 29)
  • Re: AT&T Fiber Outage in Holmdel, NJ Mehmet Akcin (Jan 29)
    • Re: AT&T Fiber Outage in Holmdel, NJ Amauris Rodriguez Martinez (Jan 30)
• NIST looking for comments on "Secure Interdomain Traffic Exchange – BGP Robustness and DDoS Mitigation: NIST Releases Draft NIST SP 800-189" Warren Kumari (Jan 29)
• Call for Presentations - CHI-NOG 09 (May 23rd) Tom Kacprzynski (Jan 29)
• Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Jason Lixfeld (Jan 30)
  • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Bryan Holloway (Jan 30)
  • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mike Hammett (Jan 30)
    • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Marijana Novakovic via NANOG (Jan 30)
  • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mehmet Akcin (Jan 30)
    • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Jared Mauch (Jan 30)
      • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY James Stankiewicz (Jan 30)
      • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Thomas King (Jan 30)
      • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Ren Provo (Jan 30)
      • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Töma Gavrichenkov (Jan 30)
      • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY i3D . net - Martijn Schmidt (Jan 30)
      • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY valdis . kletnieks (Jan 30)
      • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mike Hammett (Jan 30)
      • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Thomas King (Jan 30)
      • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mark Tinka (Jan 31)
      • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Julien Goodwin (Jan 31)
      • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mark Tinka (Jan 31)
      • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mike Hammett (Jan 31)
      • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mark Tinka (Jan 31)
      • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mike Hammett (Jan 31)
      • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mark Tinka (Jan 31)
      • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mike Hammett (Jan 31)
      • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Mark Tinka (Jan 31)
      • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Owen DeLong (Jan 31)
      • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Bryan Holloway (Jan 31)
      • Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY Niels Bakker (Jan 31)
• Effects of Cold Front on Internet Infrastructure - U.S. Midwest Mark Tinka (Jan 30)
  • Re: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Mel Beckman (Jan 30)
    • Re: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Bryan Holloway (Jan 30)
      • Re: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Christopher Morrow (Jan 30)
      • Re: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Matthew Petach (Jan 30)
    • Re: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Tom Beecher (Jan 30)
      • RE: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Naslund, Steve (Jan 30)
      • RE: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Naslund, Steve (Jan 30)
      • Re: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Mark Tinka (Jan 30)
      • Re: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Paul Zugnoni via NANOG (Jan 30)
      • RE: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Naslund, Steve (Jan 30)
      • Re: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Tom Beecher (Jan 30)
      • RE: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Naslund, Steve (Jan 30)
      • RE: Effects of Cold Front on Internet Infrastructure - U.S. Midwest bzs (Jan 30)
      • RE: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Hiers, David (Jan 31)
  • RE: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Naslund, Steve (Jan 30)
  • Re: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Fletcher Kittredge (Jan 31)
    • Re: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Mel Beckman (Jan 31)
      • RE: Effects of Cold Front on Internet Infrastructure - U.S. Midwest Colin Stanners (lists) (Jan 31)
• Calling Jason Lixfeld @ DE-CIX NY Marijana Novakovic via NANOG (Jan 30)
• Latency between Dallas and west coast Nathanael Catangay Cariaga (Jan 31)
  • Re: Latency between Dallas and west coast Mike Hammett (Jan 31)
    • Re: Latency between Dallas and west coast Mark Tinka (Jan 31)
      • Re: Latency between Dallas and west coast Tom Beecher (Jan 31)
      • Re: Latency between Dallas and west coast Nathanael Catangay Cariaga (Jan 31)
      • Re: Latency between Dallas and west coast JASON BOTHE via NANOG (Jan 31)
• RTBH no_export Roel Parijs (Jan 31)
  • Re: RTBH no_export Łukasz Bromirski (Jan 31)
  • Re: RTBH no_export Nick Hilliard (Jan 31)
  • Re: RTBH no_export Theodore Baschak (Jan 31)
    • Re: RTBH no_export Alejandro Acosta (Jan 31)
      • RE: RTBH no_export Michel Py (Jan 31)
  • RE: RTBH no_export Michel Py (Jan 31)
• Google you have a problem. Mark Andrews (Jan 31)
  • Re: Google you have a problem. Christopher Morrow (Jan 31)
    • Re: Google you have a problem. Mark Andrews (Jan 31)
      • Re: Google you have a problem. Christopher Morrow (Jan 31)
      • Re: Google you have a problem. Mark Andrews (Jan 31)
      • Re: Google you have a problem. Christopher Morrow (Jan 31)

Previous period

Next period