- NANOG - lists.nanog.org

Call for Participation -- ICANN DNSSEC Workshop at ICANN61 San Juan, Puerto Rico
by Jacques Latour 12 Dec '17

12 Dec '17

Hi All! The next ICANN DNSSEC Workshop will be on Wednesday, March 14, in San Juan, Puerto Rico. If you are interested in participating, please send a brief (1-2 sentence) description of your proposed presentation to dnssec-sanjuan(a)isoc.org by **03 January 2017** Thanks, Jack Call for Participation -- ICANN DNSSEC Workshop at ICANN61 San Juan, Puerto Rico The DNSSEC Deployment Initiative and the Internet Society Deploy360 Programme, in cooperation with the ICANN Security and Stability Advisory Committee (SSAC), are planning a DNSSEC Workshop during the ICANN61meeting held from 10-15 March 2018 in San Juan, Puerto Rico. The DNSSEC Workshop has been a part of ICANN meetings for several years and has provided a forum for both experienced and new people to meet, present and discuss current and future DNSSEC deployments. For reference, the most recent session was held at the ICANN Annual General Meeting in Abu Dhabi, UAE, https://schedule.icann.org/event/CbKE/dnssec-workshop-part-ii[schedule.ican…<https://urldefense.proofpoint.com/v2/url?u=https-3A__schedule.icann.org_eve…>, and https://schedule.icann.org/event/CbKF/dnssec-workshop-part-iii[schedule.ica…<https://urldefense.proofpoint.com/v2/url?u=https-3A__schedule.icann.org_eve…>. At ICANN61 we are particularly interested in live demonstrations of uses of DNSSEC or DANE. Examples might include: * Innovative uses of APIs to do something new and different using DNSSEC/DANE. * Email clients and servers using DNSSEC, OPENPGPKEY, or S/MIME for secure email. * DNSSEC automation and deployment using CDS, CDNSKey, and CSYNC. * DNSSEC signing solutions and innovation. * Tools for automating the generation of DNSSEC/DANE records. * Services for monitoring or managing DNSSEC signing or validation. * Tools or services for using DNSSEC/DANE along with other existing protocols and services such as SSH, XMPP, SMTP, S/MIME or PGP/GPG. Our interest is to provide current examples of the state of development and to show real-world examples of how DNSSEC and DANE related innovation can be used to increase the overall security of the Internet. We are open to presentations and demonstrations related to any topic associated with DNSSEC and DANE. Examples of the types of topics we are seeking include: 1. DNSSEC Activities For this panel we are seeking participation from those who have been involved in DNSSEC deployment and also from those who have not deployed DNSSEC but who have a keen interest in the challenges and benefits of deployment. In particular, we will consider the following questions: Are you interested in reporting on DNSSEC validation of your ISPs? What can DNSSEC do for you? What doesn't it do? What are the internal tradeoffs to implementing DNSSEC? What did you learn in your deployment of DNSSEC? We are interested in presentations from both people involved with the signing of domains and people involved with the deployment of DNSSEC-validating DNS resolvers. 2. Impact of Root Key Rollover We would like to bring together a panel of people who can talk about the impacts to ISPs, equipment providers and end users, and also what could be done to mitigate those issues. In particular, we are seeking participation from vendors, ISPs, and the community that could be affected by distribution of new root keys. If you have a specific concern about the Root Key Rollover we would like to hear from you. 3. Implementing next generation DNSSEC signing at Registries and DNS Operators Now that DNSSEC technology has matured many Registries, and DNS Operators have upgraded their legacy DNSSEC signing services with innovative solutions. * Real world use cases of HSMs and key management. * Signing at the edge. We would be interested in seeing presentations or demonstrations on those topics. 4. The operational realities of running DNSSEC Now that DNSSEC has become an operational norm for many registries, registrars, and ISPs, what have we learned about how we manage DNSSEC? What is the best practice around key rollovers? How often do you review your disaster recovery procedures? Is there operational familiarity within your customer support teams? What operational statistics have we gathered about DNSSEC? Are there experiences being documented in the form of best practices, or something similar, for transfer of signed zones? 5. Innovation around DANE and DNSSEC application automation For DNSSEC to reach massive deployment levels it is clear that a higher level of automation is required than is currently available. There also is strong interest for DANE usage within web transactions as well as for securing email and Voice-over-IP (VoIP). We are seeking presentations on topics such as: * How can the industry use DANE and other DNSSEC applications as a mechanism for creating a more secure Internet? * What tools, systems and services are available to help automate DNSSEC key management? * Can you provide an analysis of current tools/services and identify gaps? * What are some of the new and innovative uses of DANE and other DNSSEC applications in new areas or industries? * What tools and services are now available that can support DANE usage? We would be particularly interested in any live demonstrations of DNSSEC / DANE application automation and services. Demonstrations of new tools that make the setup of DNSSEC or DANE more automated would also be welcome. 6. DNSSEC and DANE in the enterprise and in the enterprise tool set Enterprises and enterprise software can play a critical role in both providing DNSSEC validation to their internal networks and also through signing of the domains owned by the enterprise. We are seeking presentations from enterprises and enterprise software providers that have implemented DNSSEC on validation and/or signing processes and can address questions such as: * What enterprise software support or plan do you have to support DNSSEC? * What are the benefits to enterprises of rolling out DNSSEC validation? And how do they do so? * What are the challenges to deployment for these organizations and how could DANE and other DNSSEC applications address those challenges? * How should an enterprise best prepare its IT staff and network to implement DNSSEC? * What enterprise tools and systems are available to assist enterprises in the deployment of DNSSEC? * How can the DANE protocol be used within an enterprise to bring a higher level of security to transactions using SSL/TLS certificates? 7. Implementing DNSSEC validation at Internet Service Providers (ISPs) Internet Service Providers (ISPs) play a critical role by enabling DNSSEC validation for the caching DNS resolvers used by their customers. We have now seen massive rollouts of DNSSEC validation within large North American ISPs and at ISPs around the world. We are interested in presentations on topics such as: * Can you describe your experiences with negative Trust Anchors and operational realities? * What does an ISP need to do to prepare its network for implementing DNSSEC validation? * How does an ISP need to prepare its support staff and technical staff for the rollout of DNSSEC validation? * Can you provide results and/or impacts of the impact of root key rollover? * What rollover technique do you use, i.e., RFC 5011 or other? In addition, we welcome suggestions for additional topics. If you are interested in participating, please send a brief (1-2 sentence) description of your proposed presentation to dnssec-sanjuan(a)isoc.org<mailto:dnssec-sanjuan@isoc.org> by **03 January 2017** We hope that you can join us. Thank you, Kathy Schnitt On behalf of the DNSSEC Workshop Program Committee: Jean Robert Hountomey, AfricaCERT Jacques Latour, .CA Xiaodong Lee, CNNIC Russ Mundy, Parsons Ondřej Filip, CZ.NIC Yoshiro Yoneya, JPRS Dan York, Internet Society Mark Elkins, DNS/ZACR Jacques Latour, CTO Canadian Internet Registration Authority (CIRA) cira.ca<http://www.cira.ca/> Tel.: (613) 237-5335 x294

1 0

Packets Broker (aka: WAN Accelerator (aka: Congestion Algorithms (aka: You call yourself a network engineer?) )
by Alain Hebert 12 Dec '17

12 Dec '17

Hi, We're used to fix Long Fat Network issues ourself... But I'm stuck in a case where we need to transparently proxy TCP connections to apply congestion algorithms (cubic, htcp, etc) since some of our newer customers are ... well ... refusing to acknowledge that reality. Any good lead for a 1U platform averaging ~10Gbps of throughput, that isn't some PC hack in a box? ( off-lists would be nice, unless you think that could be useful to others ) Thanks for your time. -- ----- Alain Hebert ahebert(a)pubnix.net PubNIX Inc. 50 boul. St-Charles P.O. Box 26770 Beaconsfield, Quebec H9W 6G7 Tel: 514-990-5911 http://www.pubnix.net Fax: 514-990-9443

2 1

quake3-master-getservers:
by Richard 11 Dec '17

11 Dec '17

NANOG group, at a client site who was complaining of having their Active Directory passwords changed every week. Found a PPTP which had been put in place by a ex employee. Fixed that. I have no idea what a master-get servers is. If anyone can ping me-off-list to educate me a bit more, please do. Sincerely, Richard

3 2

Survey about interconnection agreements
by Pedro de Botelho Marcos 11 Dec '17

11 Dec '17

Dear community, We are a group of researchers conducting a survey about the future of the interconnection agreements. Our goal is to understand the current process and reasons for establishing inter-domain interconnection agreements and how this ecosystem can be improved in the future. Can you please help us by answering a set few objective questions reflecting your views? This survey will take you less than 10 minutes, and you can earn a prize by doing it! Survey URL: https://goo.gl/bJxJzZ This survey is in the context of our proposal to create truly dynamic interconnection agreements. Please watch this short (3 minutes) introductory video. https://youtu.be/DVbjR7JQTvo We are offering a redeemable prize worth 25.00 USD (twenty-five United States Dollars) for the first 200 (two hundred) respondents that meet the following eligibility criteria: - You must be a peering coordinator or a network operator working with inter-domain interconnection aspects - Your organization must operate an autonomous system (AS) - You must be able to provide personal information that allows us to verify if you are eligible You can also participate in the survey without disclosing your identity. In this case, you are not eligible for the prize. Research records will be kept confidential. All data will be anonymous and collected and published in a manner that would not allow identification of your identity. A summary of the aggregate results will be made available to the community and used as a part of a scientific article. If you have any question, do not hesitate to contact us. Also, if you want to know more about our project, please visit our website: https://dynam-ix.github.io Thank you very much, -- Pedro Marcos Federal University of Rio Grande do Sul

1 0

Re: Static Routing 172.16.0.0/32
by Ryan Hamel 09 Dec '17

09 Dec '17

1. A single known ip address that redirects to the closest internal repo server. 172.16.0.0/32 redirects to a usable subnet ip in 172.16.xx.xx by static route. 2. Internal private network that is reachable by clients. -------- Original message -------- From: William Herrin <bill(a)herrin.us> Date: 12/8/17 1:34 PM (GMT-08:00) To: Ryan Hamel <Ryan.Hamel(a)quadranet.com> Cc: nanog(a)nanog.org Subject: Re: Static Routing 172.16.0.0/32 On Thu, Dec 7, 2017 at 10:13 PM, Ryan Hamel <Ryan.Hamel(a)quadranet.com<mailto:Ryan.Hamel@quadranet.com>> wrote: A colleague of mine has static routed 172.16.0.0/32<http://172.16.0.0/32> to a usable IP address, to have a single known IP address be static routed to a regions closest server. While I understand the IP address does work (pings and what not), I don't feel this should be the proper IP address used, but something more feasible like a usable IP in a dedicated range (172.31.0.0/24<http://172.31.0.0/24> for example). Hi Ryan, Some clarifications: 1. You say, "static routed to a regions closest server." What do you mean by that? A static-routed anycast address? 2. In what reachability context? Is this a private network? An ISP network where the reachability should be the ISP and its customers? Regards, Bill Herrin -- William Herrin ................ herrin(a)dirtside.com<mailto:herrin@dirtside.com> bill(a)herrin.us<mailto:bill@herrin.us> Dirtside Systems ......... Web: <http://www.dirtside.com/>

6 8

Re: Static Routing 172.16.0.0/32
by Ryan Hamel 08 Dec '17

08 Dec '17

> At some point, some chucklehead is going to look at that .0.0 and mentally think /16, and things will go pear-shaped pretty quickly.... Same for a /12, which is RFC1918. -------- Original message -------- From: valdis.kletnieks(a)vt.edu Date: 12/8/17 1:46 PM (GMT-08:00) To: Ryan Hamel <Ryan.Hamel(a)quadranet.com> Cc: nanog(a)nanog.org Subject: Re: Static Routing 172.16.0.0/32 On Fri, 08 Dec 2017 03:13:57 +0000, Ryan Hamel said: > Greetings, > A colleague of mine has static routed 172.16.0.0/32 to a usable IP address, > to have a single known IP address be static routed to a regions closest server. > While I understand the IP address does work (pings and what not), I don't feel > this should be the proper IP address used, but something more feasible like a > usable IP in a dedicated range (172.31.0.0/24 for example). Probably depends on what your colleague is trying to do. Nothing in the rules says the .0 address on a subnet is reserved (though you're in for a surprise if there's any gear still on the net with a 4.2BSD stack). > I would to hear everyone's thoughts on this, as this the first IP address in > an RFC1918 range. > At some point, some chucklehead is going to look at that .0.0 and mentally think /16, and things will go pear-shaped pretty quickly....

1 0

Weekly Routing Table Report
by cscora＠apnic.net 08 Dec '17

08 Dec '17

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG, CaribNOG TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG, IRNOG and the RIPE Routing WG. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 09 Dec, 2017 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 674032 Prefixes after maximum aggregation (per Origin AS): 262246 Deaggregation factor: 2.57 Unique aggregates announced (without unneeded subnets): 326110 Total ASes present in the Internet Routing Table: 59288 Prefixes per ASN: 11.37 Origin-only ASes present in the Internet Routing Table: 51190 Origin ASes announcing only one prefix: 22549 Transit ASes present in the Internet Routing Table: 8098 Transit-only ASes present in the Internet Routing Table: 243 Average AS path length visible in the Internet Routing Table: 4.4 Max AS path length visible: 30 Max AS path prepend of ASN ( 23679) 26 Prefixes from unregistered ASNs in the Routing Table: 89 Number of instances of unregistered ASNs: 89 Number of 32-bit ASNs allocated by the RIRs: 20830 Number of 32-bit ASNs visible in the Routing Table: 16674 Prefixes from 32-bit ASNs in the Routing Table: 68623 Number of bogon 32-bit ASNs visible in the Routing Table: 10 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 350 Number of addresses announced to Internet: 2861476514 Equivalent to 170 /8s, 142 /16s and 170 /24s Percentage of available address space announced: 77.3 Percentage of allocated address space announced: 77.3 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 98.8 Total number of prefixes smaller than registry allocations: 223308 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 185027 Total APNIC prefixes after maximum aggregation: 53147 APNIC Deaggregation factor: 3.48 Prefixes being announced from the APNIC address blocks: 184153 Unique aggregates announced from the APNIC address blocks: 76925 APNIC Region origin ASes present in the Internet Routing Table: 8526 APNIC Prefixes per ASN: 21.60 APNIC Region origin ASes announcing only one prefix: 2392 APNIC Region transit ASes present in the Internet Routing Table: 1230 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 29 Number of APNIC region 32-bit ASNs visible in the Routing Table: 3394 Number of APNIC addresses announced to Internet: 767380514 Equivalent to 45 /8s, 189 /16s and 76 /24s APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079, 55296-56319, 58368-59391, 63488-64098, 64297-64395, 131072-137529 APNIC Address Blocks 1/8, 14/8, 27/8, 36/8, 39/8, 42/8, 43/8, 49/8, 58/8, 59/8, 60/8, 61/8, 101/8, 103/8, 106/8, 110/8, 111/8, 112/8, 113/8, 114/8, 115/8, 116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8, 123/8, 124/8, 125/8, 126/8, 133/8, 150/8, 153/8, 163/8, 171/8, 175/8, 180/8, 182/8, 183/8, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, 223/8, ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 201752 Total ARIN prefixes after maximum aggregation: 97101 ARIN Deaggregation factor: 2.08 Prefixes being announced from the ARIN address blocks: 203119 Unique aggregates announced from the ARIN address blocks: 95080 ARIN Region origin ASes present in the Internet Routing Table: 18043 ARIN Prefixes per ASN: 11.26 ARIN Region origin ASes announcing only one prefix: 6673 ARIN Region transit ASes present in the Internet Routing Table: 1782 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 23 Number of ARIN region 32-bit ASNs visible in the Routing Table: 2276 Number of ARIN addresses announced to Internet: 1112345120 Equivalent to 66 /8s, 77 /16s and 10 /24s ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 2138-2584, 2615-2772, 2823-2829, 2880-3153 3354-4607, 4865-5119, 5632-6655, 6912-7466 7723-8191, 10240-12287, 13312-15359, 16384-17407 18432-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959, 46080-47103 53248-55295, 62464-63487, 64198-64296, 393216-397212 ARIN Address Blocks 3/8, 4/8, 6/8, 7/8, 8/8, 9/8, 11/8, 12/8, 13/8, 15/8, 16/8, 17/8, 18/8, 19/8, 20/8, 21/8, 22/8, 23/8, 24/8, 26/8, 28/8, 29/8, 30/8, 32/8, 33/8, 34/8, 35/8, 38/8, 40/8, 44/8, 45/8, 47/8, 48/8, 50/8, 52/8, 53/8, 54/8, 55/8, 56/8, 57/8, 63/8, 64/8, 65/8, 66/8, 67/8, 68/8, 69/8, 70/8, 71/8, 72/8, 73/8, 74/8, 75/8, 76/8, 96/8, 97/8, 98/8, 99/8, 100/8, 104/8, 107/8, 108/8, 128/8, 129/8, 130/8, 131/8, 132/8, 134/8, 135/8, 136/8, 137/8, 138/8, 139/8, 140/8, 142/8, 143/8, 144/8, 146/8, 147/8, 148/8, 149/8, 152/8, 155/8, 156/8, 157/8, 158/8, 159/8, 160/8, 161/8, 162/8, 164/8, 165/8, 166/8, 167/8, 168/8, 169/8, 170/8, 172/8, 173/8, 174/8, 184/8, 192/8, 198/8, 199/8, 204/8, 205/8, 206/8, 207/8, 208/8, 209/8, 214/8, 215/8, 216/8, RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 181863 Total RIPE prefixes after maximum aggregation: 88725 RIPE Deaggregation factor: 2.05 Prefixes being announced from the RIPE address blocks: 177773 Unique aggregates announced from the RIPE address blocks: 107176 RIPE Region origin ASes present in the Internet Routing Table: 24709 RIPE Prefixes per ASN: 7.19 RIPE Region origin ASes announcing only one prefix: 11307 RIPE Region transit ASes present in the Internet Routing Table: 3509 Average RIPE Region AS path length visible: 4.5 Max RIPE Region AS path length visible: 30 Number of RIPE region 32-bit ASNs visible in the Routing Table: 6465 Number of RIPE addresses announced to Internet: 713494912 Equivalent to 42 /8s, 135 /16s and 17 /24s RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-45055, 47104-52223, 56320-58367 59392-61439, 61952-62463, 64396-64495 196608-207259 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/8, 62/8, 77/8, 78/8, 79/8, 80/8, 81/8, 82/8, 83/8, 84/8, 85/8, 86/8, 87/8, 88/8, 89/8, 90/8, 91/8, 92/8, 93/8, 94/8, 95/8, 109/8, 141/8, 145/8, 151/8, 176/8, 178/8, 185/8, 188/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 87455 Total LACNIC prefixes after maximum aggregation: 19290 LACNIC Deaggregation factor: 4.53 Prefixes being announced from the LACNIC address blocks: 88717 Unique aggregates announced from the LACNIC address blocks: 39465 LACNIC Region origin ASes present in the Internet Routing Table: 6636 LACNIC Prefixes per ASN: 13.37 LACNIC Region origin ASes announcing only one prefix: 1817 LACNIC Region transit ASes present in the Internet Routing Table: 1234 Average LACNIC Region AS path length visible: 5.2 Max LACNIC Region AS path length visible: 26 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 4162 Number of LACNIC addresses announced to Internet: 172656352 Equivalent to 10 /8s, 74 /16s and 134 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-268700 + ERX transfers LACNIC Address Blocks 177/8, 179/8, 181/8, 186/8, 187/8, 189/8, 190/8, 191/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 17844 Total AfriNIC prefixes after maximum aggregation: 3918 AfriNIC Deaggregation factor: 4.55 Prefixes being announced from the AfriNIC address blocks: 19920 Unique aggregates announced from the AfriNIC address blocks: 7176 AfriNIC Region origin ASes present in the Internet Routing Table: 1102 AfriNIC Prefixes per ASN: 18.08 AfriNIC Region origin ASes announcing only one prefix: 359 AfriNIC Region transit ASes present in the Internet Routing Table: 220 Average AfriNIC Region AS path length visible: 4.8 Max AfriNIC Region AS path length visible: 21 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 377 Number of AfriNIC addresses announced to Internet: 95038976 Equivalent to 5 /8s, 170 /16s and 46 /24s AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/8, 102/8, 105/8, 154/8, 196/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4538 5257 4192 74 ERX-CERNET-BKB China Education and Rese 7545 4083 410 407 TPG-INTERNET-AP TPG Telecom Limited, AU 4766 2797 11128 758 KIXS-AS-KR Korea Telecom, KR 17974 2780 916 76 TELKOMNET-AS2-AP PT Telekomunikasi Indo 9829 2766 1499 540 BSNL-NIB National Internet Backbone, IN 45899 2481 1529 158 VNPT-AS-VN VNPT Corp, VN 7552 2359 1158 55 VIETEL-AS-AP Viettel Group, VN 9394 2169 4931 27 CTTNET China TieTong Telecommunications 4755 2081 421 211 TATACOMM-AS TATA Communications formerl 9808 2073 8699 32 CMNET-GD Guangdong Mobile Communication Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 6327 3366 1323 86 SHAW - Shaw Communications Inc., CA 22773 3303 2951 146 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 18566 2170 405 108 MEGAPATH5-US - MegaPath Corporation, US 20115 2060 2296 461 CHARTER-NET-HKY-NC - Charter Communicat 6389 1975 3671 39 BELLSOUTH-NET-BLK - BellSouth.net Inc., 16509 1950 4077 588 AMAZON-02 - Amazon.com, Inc., US 209 1931 5062 645 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 30036 1861 331 247 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 11492 1694 234 570 CABLEONE - CABLE ONE, INC., US 701 1547 10589 625 UUNET - MCI Communications Services, In Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 39891 3519 186 23 ALJAWWALSTC-AS, SA 20940 2863 853 2066 AKAMAI-ASN1, US 8551 2493 378 42 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2065 1795 696 ROSTELECOM-AS, RU 34984 2051 330 439 TELLCOM-AS, TR 12479 1963 1069 124 UNI2-AS, ES 9121 1898 1691 17 TTNET, TR 13188 1605 100 46 TRIOLAN, UA 8402 1233 544 14 CORBINA-AS OJSC "Vimpelcom", RU 6849 1227 355 21 UKRTELNET, UA Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 3651 3468 596 Uninet S.A. de C.V., MX 10620 3568 540 266 Telmex Colombia S.A., CO 11830 2646 370 66 Instituto Costarricense de Electricidad 6503 1628 437 53 Axtel, S.A.B. de C.V., MX 7303 1497 1022 194 Telecom Argentina S.A., AR 6147 1220 377 27 Telefonica del Peru S.A.A., PE 3816 1034 512 103 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 28573 997 2256 200 CLARO S.A., BR 11172 918 126 85 Alestra, S. de R.L. de C.V., MX 18881 904 1065 27 TELEFÔNICA BRASIL S.A, BR Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1075 398 48 LINKdotNET-AS, EG 37611 772 91 8 Afrihost, ZA 36903 737 370 135 MT-MPLS, MA 36992 677 1383 31 ETISALAT-MISR, EG 8452 524 1730 17 TE-AS TE-AS, EG 24835 516 850 15 RAYA-AS, EG 29571 436 36 10 CITelecom-AS, CI 37492 433 367 77 ORANGE-, TN 15399 350 35 7 WANANCHI-, KE 37342 343 32 1 MOVITEL, MZ Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 4538 5257 4192 74 ERX-CERNET-BKB China Education and Rese 7545 4083 410 407 TPG-INTERNET-AP TPG Telecom Limited, AU 8151 3651 3468 596 Uninet S.A. de C.V., MX 10620 3568 540 266 Telmex Colombia S.A., CO 39891 3519 186 23 ALJAWWALSTC-AS, SA 6327 3366 1323 86 SHAW - Shaw Communications Inc., CA 22773 3303 2951 146 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 20940 2863 853 2066 AKAMAI-ASN1, US 4766 2797 11128 758 KIXS-AS-KR Korea Telecom, KR 17974 2780 916 76 TELKOMNET-AS2-AP PT Telekomunikasi Indo Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 7545 4083 3676 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3519 3496 ALJAWWALSTC-AS, SA 10620 3568 3302 Telmex Colombia S.A., CO 6327 3366 3280 SHAW - Shaw Communications Inc., CA 22773 3303 3157 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 8151 3651 3055 Uninet S.A. de C.V., MX 17974 2780 2704 TELKOMNET-AS2-AP PT Telekomunikasi Indonesia, I 11830 2646 2580 Instituto Costarricense de Electricidad y Telec 8551 2493 2451 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 45899 2481 2323 VNPT-AS-VN VNPT Corp, VN Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 65602 UNALLOCATED 8.225.192.0/24 30372 SUNESYS2 - Sunesys, LLC, US 64710 PRIVATE 39.134.26.0/23 56042 CMNET-SHANXI-AP China Mobile c 64710 PRIVATE 39.134.28.0/23 56042 CMNET-SHANXI-AP China Mobile c 64710 PRIVATE 39.134.30.0/24 56042 CMNET-SHANXI-AP China Mobile c 64710 PRIVATE 39.134.31.0/24 56042 CMNET-SHANXI-AP China Mobile c 64710 PRIVATE 39.137.20.0/23 56042 CMNET-SHANXI-AP China Mobile c 64710 PRIVATE 39.137.22.0/24 56042 CMNET-SHANXI-AP China Mobile c 65001 PRIVATE 46.237.40.0/21 13118 ASN-YARTELECOM PJSC Rostelecom 64513 PRIVATE 62.150.101.0/24 9155 QNET Kuwait, KW 419333 UNALLOCATED 84.17.91.0/24 41933 IPRAGAZ-AS Istanbul/ TURKEY, T Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 100.64.0.0/15 4804 MPX-AS Microplex PTY LTD, AU Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 14.128.14.0/23 10247 NETLINE, ZA 14.192.50.0/23 10247 NETLINE, ZA 14.192.58.0/23 10247 NETLINE, ZA 27.100.7.0/24 56096 UNKNOWN 36.255.250.0/23 10247 NETLINE, ZA 41.78.180.0/23 37265 -Reserved AS-, ZZ 43.228.144.0/22 9829 BSNL-NIB National Internet Backbone, IN 43.251.20.0/22 9381 WTT-AS-AP WTT HK Limited, HK 43.251.84.0/22 133676 PNPL-AS Precious netcom pvt ltd, IN 43.251.84.0/23 133676 PNPL-AS Precious netcom pvt ltd, IN Complete listing at http://thyme.rand.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:15 /9:13 /10:36 /11:106 /12:285 /13:550 /14:1064 /15:1862 /16:13342 /17:7740 /18:13630 /19:25246 /20:38966 /21:44009 /22:81970 /23:66887 /24:376085 /25:827 /26:606 /27:655 /28:36 /29:21 /30:17 /31:4 /32:60 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6327 3158 3366 SHAW - Shaw Communications Inc., CA 39891 2946 3519 ALJAWWALSTC-AS, SA 22773 2547 3303 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 18566 2064 2170 MEGAPATH5-US - MegaPath Corporation, US 11830 1992 2646 Instituto Costarricense de Electricidad y Telec 8551 1957 2493 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 30036 1628 1861 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 10620 1560 3568 Telmex Colombia S.A., CO 11492 1502 1694 CABLEONE - CABLE ONE, INC., US 9121 1370 1898 TTNET, TR Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1567 2:818 4:18 5:2612 6:38 8:1087 9:1 12:1851 13:181 14:1742 15:29 16:3 17:183 18:76 20:53 21:1 23:2473 24:1929 25:2 27:2349 31:1968 32:87 35:22 36:452 37:2446 38:1443 39:156 40:101 41:3039 42:524 43:1952 44:88 45:3386 46:2857 47:191 49:1369 50:1043 51:35 52:912 54:354 55:5 56:7 57:42 58:1568 59:992 60:373 61:1999 62:1786 63:1832 64:4611 65:2240 66:4495 67:2296 68:1189 69:3178 70:1133 71:588 72:2090 74:2687 75:391 76:423 77:1545 78:1573 79:1891 80:1434 81:1418 82:1062 83:757 84:996 85:1925 86:484 87:1216 88:893 89:2307 90:174 91:6254 92:1036 93:2356 94:2424 95:2710 96:669 97:352 98:958 99:107 100:153 101:1480 102:9 103:16395 104:3200 105:211 106:517 107:1784 108:820 109:2926 110:1508 111:1729 112:1271 113:1374 114:1072 115:1602 116:1711 117:1632 118:2176 119:1649 120:734 121:1065 122:2403 123:1914 124:1474 125:1821 128:960 129:576 130:442 131:1563 132:605 133:194 134:975 135:229 136:446 137:456 138:1994 139:550 140:381 141:678 142:762 143:922 144:795 145:193 146:1146 147:706 148:1553 149:630 150:718 151:1003 152:738 153:303 154:971 155:738 156:736 157:755 158:597 159:1621 160:834 161:731 162:2543 163:530 164:939 165:1472 166:384 167:1343 168:3131 169:791 170:3624 171:402 172:1022 173:1895 174:838 175:771 176:1891 177:4014 178:2494 179:1177 180:2232 181:2114 182:2394 183:811 184:889 185:11722 186:3387 187:2353 188:2607 189:1935 190:8198 191:1348 192:9718 193:5853 194:4754 195:3967 196:2287 197:1468 198:5550 199:5877 200:7225 201:4862 202:10424 203:10004 204:4552 205:2871 206:3060 207:3087 208:3981 209:3880 210:3978 211:2072 212:2892 213:2586 214:869 215:65 216:5726 217:2098 218:892 219:624 220:1696 221:944 222:731 223:1206 End of report

1 0

FCC Seeks Comment on 2017 Hurricane Season Response Efforts
by Sean Donelan 08 Dec '17

08 Dec '17

PUBLIC SAFETY AND HOMELAND SECURITY BUREAU SEEKS COMMENT ON RESPONSE EFFORTS UNDERTAKEN DURING 2017 HURRICANE SEASON PS Docket No. 17-344 Comments Due: January 22, 2018 Reply Comments Due: February 21, 2018 https://www.fcc.gov/document/fcc-seeks-comment-2017-hurricane-season-respon… A. Questions Regarding Impacts to Communications Infrastructure B. Questions Regarding the FCC’s Response C. Questions Regarding Communications Service User Experience D. Questions Regarding Communications Service Provider Experience

1 0

Poor speed to AWS
by Eric Dugas 07 Dec '17

07 Dec '17

Anyone from AWS can contact me off-list? We peer with AS16509 in Montreal and Toronto and get really good speed to US-EAST-1, US-EAST-2 and of course CA-CENTRAL-1 but anything else outside the east coast (US-WEST-1 and US-WEST-2 more precisely) is about ten times slower even on multi-threaded HTTP(S) or SCP/SFTP transfers. Goes through two of our transit providers, Telia and Zayo. Thanks Eric

2 2

Suggestions for a more privacy conscious email provider
by Michael S. Singh 07 Dec '17

07 Dec '17

Hi all, I am in need of some suggestions for some privacy conscious email providers. I am currently using Migadu email hosting from Switzerland, basically they allow their users to have as many domains and mailboxes without storage limits without extra cost. However they only allow 10 messages to be sent per day on their free tier. -- Sincerely Michael S Singh, M: 914-266-0601 W: www.wadadli.me F: 5E0E FD46 4592 1682 A4B6 5F62 761E 4940 A177 3B38 Sent via Migadu.com, world's easiest email hosting

35 83