October 2018 - Test - lists.nanog.org

Hurricane Michael: Communication Service Provider status
by Sean Donelan 16 Oct '18

16 Oct '18

Electric power outages (percentage out of service) Florida Bay County - 98% Calhoun County - 100% Franklin County - 97% Gadsden County - 100% Gulf County - 99% Holmes County - 99% Jackson County - 100% Leon County - 91% Wakulla County - 97% Washington County - 98% I haven't found power outage reports from other states yet. 1 Public Safety Answering Point out of service Jackson County FL 15 Public Safety Answering Points re-routed Counties with over 60% cell sites out of service Florida Bay County - 78.3% Gulf County - 69.6% Holmes County - 74.1% Jackson County - 77.1% Liberty County - 88.9% Washington County - 69.2% Georgia Schley County - 66.7% Webster County - 64.7% Cable and Wireline subscribers reported out of service (likely more out of service than reported) Alabama - 14,855 Florida - 185,841 Georgia - 63,473 Radio and Television 4 TV stations out of service 30 FM stations out of service 4 AM stations out of service

2 5

SAFNOG-4/EANOG/tzNOG: Thank You & Survey
by Mark Tinka 16 Oct '18

16 Oct '18

Hello all. On behalf of the SAFNOG Management Committee, EANOG and tzNOG, I'd like to extend my sincere thanks to all of you that attended this year's meeting in Dar Es Salaam, physically and remotely. To our host (TISPA), our sponsors, our speakers and of course, you, our delegates, that supported this year's meeting... we would not have been able to do it without you. We look forward to seeing you again in 2019, details of which will be communicated in the coming months. I would like to ask you to take a few minutes and complete the 10-question survey at the link below, so that we know where to improve for future meetings: https://www.surveymonkey.com/r/JQTKVVF Thank you all, and see you in 2019. Mark Tinka

1 0

It's been 20 years today (Oct 16, UTC). Hard to believe.
by Rodney Joffe 15 Oct '18

15 Oct '18

At NANOG two weeks ago, we had an interesting discussion at one of the lunch tables. One of the subjects we discussed was the original IANA, and RFC Editor, Jon Postel. Seven of the ten people at the table had never heard of him. Maybe these days it no longer matters who he was, and what he meant to where we are today. <Sigh> For those who care about the history of the Internet, and routing and addressing. And protocols… https://tools.ietf.org/html/rfc2468 Oct 16, 1998.

4 3

ARIN TAL copyright
by Baldur Norddahl 15 Oct '18

15 Oct '18

Hi, The URL to the ARIN TAL nor the ARIN TAL document itself is not copyrightable. The ARIN TAL document contains a URL and a key, which is a machine generated random number. Neither is based on any creative work whatsoever, and so can not be copyrighted. Also would be protected by free speech and fair use. The service itself can have terms and conditions, but access the the TAL document is not an effective enforcement. Bundlers of software can include this information at will. No need to download it. I understand the issue is that ARIN wants protection from being sued, should I somehow harm myself with this service. However ARIN already offers a similar service without any terms and conditions: The reverse DNS. As reverse DNS is often used by SMTP mail servers and mail clients to stop spam, I might not receive an important mail due to the failure of the ARIN reverse DNS service. And then sue ARIN for my financial loss. As a compromise, I suggest that ARIN outsource the service to somewhere with a less hostile legal environment. For example, maybe RIPE could mirror the ARIN service. The ARIN service may still require terms and conditions, while automatically installed software would use the RIPE mirror. Regards, Baldur

2 1

some shallow statistics about finding the name/netname for IP address using RDAP and WHOIS
by Martin T 15 Oct '18

15 Oct '18

Hi! For testing a script I generated 10000 random IPv4 and global unicast IPv6 addresses. For all those addresses I tried to find the netname/name attribute value from WHOIS servers using the latest version of https://github.com/rfc1036/whois and RDAP servers using the curl. Basically 'whois -H <ip>' and 'curl -L "https://rdap.db.ripe.net/ip/<ip>"'. Out of those 10000 random IPv4 and IPv6 addresses, 7351 gave the same name/netname using RDAP and WHOIS. In case of 2285 addresses, the RDAP was able to find the name while WHOIS was not. Probably thanks to bootstrap feature. In case of 364 addresses, the WHOIS found a different netname than RDAP. Those cases can be seen here: http://termbin.com/p6u7 Left column is the RDAP and the right one is the WHOIS. If "IANA-BLK" WHOIS results for IPv6 are excluded, then only <1% of queries did not return a result using RDAP while they did return a result using WHOIS. In short, based on this small test, the RDAP is much more reliable than WHOIS for finding the name/netname for an IP address. Maybe those results are interesting or useful for somebody. PS. IPv4 and IPv6 addresses were generated like this: if (( $(($RANDOM % 2)) == 0 )); then # Generate random IPv4 address. printf -v ip '%d.%d.%d.%d' \ "$(($RANDOM % 256))" \ "$(($RANDOM % 256))" \ "$(($RANDOM % 256))" \ "$(($RANDOM % 256))" else # Gnerate random IPv6 global unicast address. hex_digit=( 0 1 2 3 4 5 6 7 8 9 a b c d e f ) ip= for i in {1..7}; do nibble= for i in {1..4}; do nibble="$nibble""${hex_digit[$(($RANDOM % 16))]}" done ip="$ip":"$nibble" done ip=2001"$ip" fi Martin

1 0

Hulu / ESPN: Commercial IP Address
by Jason Canady 15 Oct '18

15 Oct '18

Hello, I have a customer that is using Hulu Live to stream ESPN, however it isn't showing up in their Channel list. They reached out to Hulu and it's because their IP address is 'commercial'. We have many customers using Hulu without problems, but it seems specific to ESPN. Anyone else have this issue? Do you reach out to ESPN or Hulu? If anyone has any information, please share it. Appreciate your help in advance! Best Regards, Jason Canady Unlimited Net, LLC Responsive, Reliable, Secure

8 7

ARIN RPKI TAL deployment issues
by Job Snijders 15 Oct '18

15 Oct '18

Dear NANOG, I'd like to draw attention to a very concerning development: it appears that the ARIN TAL is not as widely deployed as other RPKI TALs (such as RIPE or APNIC's TAL). This means that ARIN members are needlessly put at higher risk. Ben Cartwright-Cox performed RPKI research a few weeks ago where he compared the (un)reachability of RPKI Invalid announcements using ARIN, RPKI, APNIC and JPNIC space. The full write-up is available here: https://blog.benjojo.co.uk/post/are-bgps-security-features-working-yet-rpki I quote Ben's assessment: """Using the data, we can also see that the providers that have not downloaded the ARIN TAL. Either because they were not aware that they needed to, or could not agree to the agreement they have with it. This is frustrating to watch. Since it means that ROA signing ARIN prefixes will be less secure than ROA signing others, until these restrictions are abolished. Even after that it will have a long term knock on effect as software updates take a long time to propagate to end networks.""" In other words, when creating RPKI ROAs for your resources, ARIN members are getting *LESS* in return compared to say RIPE members. As ARIN member I'd hope and expect the ARIN organisation to go above and beyond to distribute their RPKI TAL as widely as possible. (Think: proactively submitting the ARIN TAL to relevant open source projects, making the TAL available for download without restrictions or limitations). At the NANOG 74 meeting David Whisnick will talk about legal barriers to RPKI adoption and he'll offer suggestions for reform. I think Ben's observation that the ARIN TAL is less widely deployed is a direct result from the legal barriers that David identified. https://pc.nanog.org/static/published/meetings//NANOG74/daily/day_2.html#ta… I fear that if no action is taken (e.g. when none of the RPKI Cache Validators can include the ARIN TAL in their software distribution [1]), we'll continue to see the gap between ARIN and the other RIRs widen. Software developers have indicated that the RPA is problematic and prevents BGP implementations from shipping "secure by default" software: https://lists.arin.net/pipermail/arin-consult/2018-April/001087.html When ARIN members create ROAs, I assume those members would also like networks *outside* the ARIN region to honor those ROAs and help prevent propagation of incorrect BGP announcements. The ARIN member and the operator of the foreign network may not even have any languages in common! I fear that limited deployment of the ARIN TAL is detrimental to the business interests of resource holders in the ARIN region. Kind regards, Job [1]: https://github.com/NLnetLabs/routinator/commit/b1e70746bb3768554fa439c5ced4…

19 53

Fwd: [apops] APRICOT 2019 Call for Presentations
by Mark Tinka 15 Oct '18

15 Oct '18

FYI - APRICOT 2019 Call for Presentations. Thanks. Mark. -------- Forwarded Message -------- Subject: [apops] APRICOT 2019 Call for Presentations Date: Fri, 12 Oct 2018 14:43:08 +1000 From: Philip Smith <pfsinoz(a)gmail.com> To: apops(a)apops.net Hi everyone, The call for presentations for APRICOT 2019 has been published - we are all looking forward to receiving your presentation and tutorial proposals and welcoming you to APRICOT 2019 in Daejeon, Korea, in February. Thanks! Mark, Marijana, Philip APRICOT 2019 PC Chairs -- Asia Pacific Regional Internet Conference on Operational Technologies (APRICOT) 25th - 28th February 2019, Daejeon, Korea https://2019.apricot.net CALL FOR PAPERS =============== The APRICOT 2019 Programme Committee is now seeking contributions for Presentations and Tutorials for the APRICOT 2019 Conference. We are looking for presenters who would: - Offer a technical tutorial on an appropriate topic; - Participate in the technical conference sessions as a speaker; - Convene and chair panel sessions of relevant topics; - Lead informal Birds of Feather break out sessions. Please submit on-line at: http://papers.apricot.net/user/login.php?event=79 CONFERENCE MILESTONES --------------------- Call for Papers Opens: Now Draft Program Published: As Papers Confirmed Final Deadline for Submissions: 25 January 2019 Final Program Published: 1 February 2019 Final Slides Received: 15 February 2019 *NOTE THAT REGARDLESS OF DEADLINES, SLOTS ARE FILLED ON A FIRST COME, FIRST SERVED BASIS* PROGRAMME CONTENT ----------------- The APRICOT Conference Programme consists of three parts, these being the Peering Forum, Tutorials, and Conference Tracks. Topics proposed must be relevant to Internet Operations and Technologies: - IPv4 / IPv6 Routing and Operations - Internet backbone operations - Peering, Interconnects and IXPs - Content Distribution Network technology & operations - Research on Internet Operations and Deployment - Network security (NSP-SEC, DDoS, Anti-Spam, Anti-Malware) - IPv6 deployment on fixed and Wireless/Cellular networks - DNS / DNSSEC - Access and Transport Technologies, including Cable/DSL, LTE/5G, wireless, metro ethernet, fibre, segment routing - Software Defined Networking / Network Function Virtualisaton - Content & Service Delivery (Multicast, Voice, Video, "telepresence", Gaming) and Cloud Computing CfP SUBMISSION -------------- Draft slides for both tutorials and conference sessions MUST be provided with CfP submissions otherwise the submission will be rejected immediately. For work in progress, the most current information available at time of submission is acceptable. All draft and complete slides must be submitted in PDF format only. Slides must be of original work, with all company confidential marks removed. Final slides are to be provided by the specified deadline for publication on the APRICOT website. Prospective presenters should note that the majority of speaking slots will be filled well before the final submission deadline. The PC may, at their discretion, retain a limited number of slots up to the final submission deadline for presentations that are exceptionally timely, important, or of critical operational importance. Every year we turn away submissions, due to filling up all available programme slots before the deadline. Presenters should endeavour to get material into the PC sooner rather than later. Any questions or concerns should be addressed to the Programme Committee by e-mail at: pc-chairs at apricot.net We look forward to receiving your presentation proposals. Mark Tinka, Marijana Novakovic & Philip Smith Co-Chairs, APRICOT 2019 Programme Committee -- _______________________________________________ apops mailing list apops(a)apops.net https://mailman.apnic.net/mailman/listinfo/apops Website: www.apops.net .

1 0

Fwd: [apops] APRICOT 2019 PC call for volunteers
by Mark Tinka 15 Oct '18

15 Oct '18

FYI. Mark. -------- Forwarded Message -------- Subject: [apops] APRICOT 2019 PC call for volunteers Date: Mon, 8 Oct 2018 20:26:42 +1000 From: Philip Smith <pfsinoz(a)gmail.com> To: apops(a)apops.net Hi everyone, The APRICOT 2019 Programme Committee is responsible for the solicitation and selection of suitable presentation and tutorial content for the APRICOT 2019 conference (https://2019.apricot.net/) The APRICOT PC Chairs are now seeking nominations from the community to join the APRICOT 2019 PC to assist with the development of the programme for APRICOT 2019. Eligible PC candidates are those who have attended APRICOT conferences in the recent past, have broad technical knowledge of Internet operations, and have reasonable familiarity with the format of APRICOT conferences. Having constructive opinions and ideas about how the programme content might be improved is of high value too. PC members are expected to work actively to solicit content and review submissions for technical merit. The PC meets by conference call, weekly in frequency during the three months prior to APRICOT. If you are interested in joining the PC and meet the above eligibility criteria, please send a brief note to "pc-chairs at apricot.net". The note should include affiliation (if any) and contact details (including e-mail address), and a brief description of why you would make a good addition to the PC. PC members who are active, successfully solicit content, contribute to regular PC meetings and submit reviews receive complimentary registration for APRICOT 2019. The PC Chairs will accept nominations received by 17:00 UTC+8 on Monday 22nd October, 2018, and will announce the new PC shortly thereafter. Many thanks! Mark Tinka, Marijana Novakovic & Philip Smith APRICOT 2019 PC Chairs -- _______________________________________________ apops mailing list apops(a)apops.net https://mailman.apnic.net/mailman/listinfo/apops Website: www.apops.net .

1 0

ifIndex
by Randy Bush 13 Oct '18

13 Oct '18

do folk have experience with platforms where ifIndexes are not stable across reboots etc? how do you deal with it? do some of those platforms trap on change? randy, who hates ifIndex changes

7 9