January 2019 - Test - lists.nanog.org

Re: BGP Experiment
by hank＠interall.co.il 31 Jan '19

31 Jan '19

On 23/01/2019 19:40, Job Snijders wrote: I agree with Job. Continue the experiment and warn us in advance. -Hank > Dear Ben, all, > > I'm not sure this experiment should be canceled. On the public Internet > we MUST assume BGP speakers are compliant with the BGP-4 protocol. > Broken BGP-4 speakers are what they are: broken. They must be fixed, or > the operator must accept the consequences. > > "Get a sandbox like every other researcher" is not a fair statement, one > can also posit "Get a compliant BGP-4 implementation like every other > network operator". > > When bad guys explicitly seek to target these Asian and Australian > operators you reference (who apparently have not upgraded to the vendor > recommended release), using *valid* BGP updates, will a politely emailed > request help resolve the situation? Of course not! > > Stopping the experiment is only treating symptoms, the root cause must > be addressed: broken software. > > Kind regards, > > Job

1 0

Re: DNS Flag Day, Friday, Feb 1st, 2019
by Mark Andrews 31 Jan '19

31 Jan '19

Don’t forget the reverse tree as well. > On 31 Jan 2019, at 5:40 pm, Hank Nussbacher <hank(a)efes.iucc.ac.il> wrote: > > On 31/01/2019 07:18, Mark Andrews wrote: > > There is some secret, silent block on my postings to NANOG that the admins have not yet discovered. In the interim can one of you please proxy to the list that people should not forget about testing their inverse as well - *.in-addr.arpa via https://ednscomp.isc.org/ednscomp > > Regards, > Hank -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka(a)isc.org

1 0

Calling Jason Lixfeld @ DE-CIX NY
by Marijana Novakovic 30 Jan '19

30 Jan '19

Greetings Jason, Do you see your new IPv4 session UP at DE-CIX NY with LinkedIn? Thanks ! Kind regards, Mara

1 0

Amazon Peering
by Darin Steffl 30 Jan '19

30 Jan '19

Hey all, Does anyone have a direct contact to get a peering session established with Amazon at an IX? I sent a peering request Dec 2017 and two more times this Sept and Nov with no response. I sent to peering(a)amazon.com and received one automated response back so I know they received my email but nothing since. -- Darin Steffl Minnesota WiFi www.mnwifi.com 507-634-WiFi <http://www.facebook.com/minnesotawifi> Like us on Facebook <http://www.facebook.com/minnesotawifi>

11 18

Call for Presentations - CHI-NOG 09 (May 23rd)
by Tom Kacprzynski 29 Jan '19

29 Jan '19

CHI-NOG 09 - (Chicago Network Operators Group) May 23rd, 2019, Chicago, IL The Chicago Network Operators Group (CHI-NOG) is a vendor neutral organization. Our goal is to create a regional community of network professionals by presenting the latest technology trends, enabling collaboration and providing networking opportunities. CHI-NOG will be hosting its ninth annual conference on May 23rd, 2019 in downtown Chicago. For more information on the conference please see event's page ( http://chinog.org/chi-nog-09/) The CHI-NOG Program Committee is seeking proposals for presentations on relevant networking technologies with the focus on the following topics: * Network Automation / DevOps / CI-CD * Edge Computing and Networking * Interconnection/Peering * 5G Mobile * Open Networking * Overlay Networking Technologies * Low Latency Networks/Financial Networks * Network Security / DDoS * Academic Research in Networking and Related Infrastructure Fields. * Internet Monitoring * AI in Network Analytics * Advanced BGP/MPLS Technologies * Optical Networking/Data Center Interconnect * Content Delivery Networks (CDNs) * Software Defined Networking (SDN) * Network Traffic Engineering (TE) * Data Center Fabric * Tutorials Session Format Each presentation is 30 minutes, which includes a question and answer time. The duration can be extended per individual request to 60 minutes and will be considered by the program committee. Presentations should not contain any marketing material and should avoid discussion of commercial products but rather focus on the underlying technology. Key Dates 3/25/2019 - Presentation Abstract Submission Deadline 4/02/2019 - Program Committee's Selection Decision 4/15/2019 - Full Presentation Slides Submission Deadline 5/23/2019 - Conference Submission Please submit presentation’s abstract proposal by filling out the submission form at http://chinog.org/chi-nog-09/abstract-submission/ . Once your presentation is selected please provide the program committee with your photo and a short bio for web publication. All accepted speakers will receive complimentary tickets to the conference. For past presentation please see the archives at http://chinog.org/presentation-archive/. The program committee is looking forward to your submission and attendance.

1 0

AT&T Fiber Outage in Holmdel, NJ
by Amauris Rodriguez Martinez 29 Jan '19

29 Jan '19

Did anybody here have fiber issues yesterday night about 9:30 pm? Best Regards, Amauris Get Outlook for iOS<https://aka.ms/o0ukef>

2 2

NIST looking for comments on "Secure Interdomain Traffic Exchange – BGP Robustness and DDoS Mitigation: NIST Releases Draft NIST SP 800-189"
by Warren Kumari 29 Jan '19

29 Jan '19

Hey all, NIST is looking for comments on "Secure Interdomain Traffic Exchange – BGP Robustness and DDoS Mitigation: NIST Releases Draft NIST SP 800-189" They recently extended the deadline for comments to March 15, 2019, and so it looks like they would really like feedback.... ----- From: NIST Computer Security Division <csrc.nist(a)service.govdelivery.com> Subject: Secure Interdomain Traffic Exchange – BGP Robustness and DDoS Mitigation: NIST Releases Draft NIST SP 800-189 NIST has released Draft NIST Special Publication (SP) 800-189, Secure Interdomain Traffic Exchange: BGP Robustness and DDoS Mitigation, which provides technical guidance and recommendations for deploying technologies that improve the security of interdomain traffic exchange. The document focuses on securing the interdomain routing control (i.e., Border Gateway Protocol) traffic as well as mitigating Distributed Denial of Service (DDoS) attacks. It is intended to guide information security officers and managers of federal enterprise networks. The guidance also applies to the network services of hosting providers (e.g., cloud-based applications and service hosting) and Internet Service Providers (ISPs) when they are used to support federal IT systems. The guidance will also be useful for enterprise and transit network operators and equipment vendors in general. A public comment period for this document is open until March 15, 2019. Email Comments to: sp800-189(a)nist.gov Publication Details: https://csrc.nist.gov/publications/detail/sp/800-189/draft CSRC Update: https://csrc.nist.gov/news/2018/nist-releases-draft-sp-800-189-for-comment Warren. -- I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf

1 0

NANOG 75
by Bradley Raymo 29 Jan '19

29 Jan '19

NANOG Community, The NANOG 75 Agenda is published at http://www.cvent.com/d/1bqspy/16K and available as an iCal Feed <https://pc.nanog.org/static/published/meetings/NANOG75/agenda.ics>. The Program Committee has worked closely with our speakers to develop a first-rate program and we encourage all attendees to enjoy the whole conference. As we review submitted content, minor changes to the agenda are possible and will be updated in the online feed. Thank you to the many members of our community who submitted interesting content for NANOG 75! Over 700 attendees have registered and the NANOG family looks forward to welcoming all of you to San Francisco. Useful Information - NANOG 75 General Information and Registration: http://www.cvent.com/d/1bqspy - NANOG 75 Agenda: http://www.cvent.com/d/1bqspy/16K - Hotel Room Block(s) Information: http://www.cvent.com/d/1bqspy/8K - Reminder, registration is required to participate in the NANOG 75 Hackathon: http://www.cvent.com/d/1bqspy/4K - A welcome message that will be sent to registered NANOG 75 attendees a week before the conference will provide more information on scheduled events and applications to help you to make the most of your time in San Francisco. Safe travels and see you soon. Sincerely, Brad Raymo NANOG PC

1 0

Re: Verizon(AS701) announcing Comcast(AS7922) subnet 68.80.240.0/24
by Smith, Courtney 28 Jan '19

28 Jan '19

On 1/28/19, 2:08 PM, "Job Snijders" <job(a)ntt.net> wrote: Can you create RPKI ROAs for the 68.80.0.0/13? That is the most unambiguous, programmatically verifiable statement Comcast can make about what the rouing intentions of its prefixes are. Job, Working on plans for 2019.

1 0

Verizon(AS701) announcing Comcast(AS7922) subnet 68.80.240.0/24
by Smith, Courtney 28 Jan '19

28 Jan '19

Verizon (AS701) is currently originating 68.80.240.0/24. This is part of 68.80.0.0/13 allocated to Comcast (AS7922). We have reached out to Verizon to stop the announcement. Until that occurs, we request you block the 68.80.240.0/24 announcement. Thanks. route-views>show clock 18:35:15.335 UTC Mon Jan 28 2019 route-views>show ip bgp 68.80.240.0/24 longer-prefixes BGP table version is 34517149, local router ID is 128.223.51.103 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter, x best-external, a additional-path, c RIB-compressed, Origin codes: i - IGP, e - EGP, ? - incomplete RPKI validation codes: V valid, I invalid, N Not found Network Next Hop Metric LocPrf Weight Path * 68.80.240.0/24 203.62.252.83 0 1221 4637 701 i * 162.250.137.254 0 4901 6079 3257 701 i * 207.172.6.1 0 0 6079 3257 701 i * 202.232.0.2 0 2497 701 i * 208.51.134.254 0 0 3549 3356 701 i * 89.149.178.10 10 0 3257 701 i * 144.228.241.130 80 0 1239 701 i * 212.66.96.126 0 20912 174 701 i * 132.198.255.253 0 1351 6939 701 i * 207.172.6.20 0 0 6079 1299 701 i * 202.93.8.242 0 24441 3491 3491 701 i * 208.74.64.40 0 19214 3257 701 i * 195.208.112.161 0 3277 3267 1299 701 i *> 137.39.3.55 0 701 i * 134.222.87.1 18750 0 286 701 i * 203.181.248.168 0 7660 2516 701 i * 217.192.89.50 0 3303 3320 701 i * 114.31.199.1 0 4826 1299 701 i * 209.124.176.223 0 101 101 2914 701 i * 193.0.0.56 0 3333 1273 701 i * 91.218.184.60 0 0 49788 174 701 i * 37.139.139.0 0 57866 701 i * 94.142.247.3 0 0 8283 57866 701 i * 12.0.1.63 0 7018 701 i * 194.85.40.15 0 0 3267 1299 701 i * 162.251.163.2 0 53767 3257 701 i * 198.58.198.255 0 1403 1299 701 i * 198.58.198.254 0 1403 1299 701 i * 154.11.12.212 0 0 852 1299 701 i * 173.205.57.234 0 53364 3257 701 i * 206.24.210.80 0 3561 209 701 i * 140.192.8.16 0 54728 20130 6939 701 i * 64.71.137.241 0 6939 701 i route-views> -- Courtney Smith Network Engineer Comcast TPX http://as7922.peeringdb.com https://www.comcasttechnologysolutions.com

3 3