- Test - lists.nanog.org

Call For Presentations - DNS-OARC Workshop 27, San Jose, CA, USA, 29-30 September 2017
by Jacques Latour 05 Jul '17

05 Jul '17

[with apologies to those who see this on multiple lists] Call For Presentations The DNS-OARC 27th Workshop will take place in San Jose, CA, USA on September 29th and 30th 2017, the Friday and Saturday preceding NANOG 71. The Workshop's Program Committee is now requesting proposals for presentations. All DNS-related subjects are welcome. If you are an OARC member, and have a sensitive topic you would like to present for members-only, we can accommodate those talks during the Members Only session on the morning of September 29th. A timeslot will also be available for lightning talks (5-10 minutes) on Saturday September 30th, for which submissions will be accepted during Friday 29th. Workshop Milestones: 26 May 2017, Call for Presentations posted and open for submissions 28 July 2017, Deadline for submission 11 August 2017, Draft Programme published 01 September 2017, Final Program published 15 September 2017, Final deadline for slideset submission Details for presentation submission will be published here: https://indico.dns-oarc.net/event/27/call-for-abstracts/ The workshop presentations will be organized by common themes, depending on the topics and the timing of each presentation. There are 30-minute and 15-minute slots, let us know your preference in your submission. To allow the Programme Committee to make objective assessments of submissions, so as to ensure the quality of the workshop, submissions SHOULD include slides. Draft slides are acceptable on submission. If you have questions or concerns you can contact the Programme Committee: https://www.dns-oarc.net/oarc/programme via <submissions(a)dns-oarc.net> Ray Bellis, for the OARC Programme Committee OARC depends on sponorship to fund its workshops and associated social events. Please contact <sponsor(a)dns-oarc.net> if your organization is interested in becoming a sponsor. (Please note that OARC is run on a non-profit basis, and is not in a position to reimburse expenses or time for speakers at its meetings.)

1 1

Call for presentations EPF12, 18th - 20th September, Lisbon sent to NANOG
by Arnold Nipper 05 Jul '17

05 Jul '17

Dear all, AMS-IX, DE-CIX, LINX, Netnod are happy to host the 12th European Peering Forum (EPF) in Lisbon, Portugal from the 18th - 20st September 2017. The event will welcome up to 300 peering managers and coordinators from networks connected to the host Internet exchanges. Besides an interesting topical agenda, the three-day event accommodates room for attendees to meet on a one-to-one basis to discuss bilateral peering business opportunities. The programme committee will be looking for presentations and lightning talks related to peering and technical topics of interconnection. Your presentation should address * Interconnection Automation * Regional Peering * Interconnection and Peering Internet Governance and Regulatory TopicS * Economic and Product Trends * Peering/Interconnection Strategy * Interesting findings about peering * 100GE and beyond Submissions =========== Presentations must be of a non-commercial nature. Product or marketing heavy talks are strongly discouraged. Submissions of presentations should be made to the programme committee <epf-pc(a)peering-forum.eu>. Please include: * Author's name and e-mail * Presentation title * Abstract * Slides (if available) * Time requested Deadlines ========= Presentation Abstract Deadline 17/07/2017 12:00 UTC Final Selection of Speakers 28/07/2017 Presentation Slides Submission Deadline 04/09/2017 12:00 UTC More information about the event and other activities around EPF12 may be found at https://peering-forum.eu/ Best regards, Arnold On behalf of the EPF hosts -- Arnold Nipper email: arnold(a)nipper.de mobile: +49 172 2650958

1 1

Call for presentations RIPE 75 and DCTM info
by Benno Overeinder 03 Jul '17

03 Jul '17

Dear colleagues, Please find the CFP for RIPE 75 below or at: https://ripe75.ripe.net/submit-topic/cfp/. The deadline for submissions is *20 August 2017*. Note: due to UAE law, confirmed speakers will need to submit a copy of their passport and contact information in advance of the meeting. More details are available here: https://ripe75.ripe.net/attend/dctm-requirements Kind regards, Benno Overeinder RIPE PC Chair https://ripe75.ripe.net/ripe-pc/ -------------------->>><<<-------------------- Call for Presentations A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. RIPE 75 will take place from 22-26 October in Dubai, UAE. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 75. See the full descriptions of the different presentation formats, https://ripe75.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than *20 August 2017*. Proposals submitted after this date will be considered depending on the remaining available space in the programme. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange - Connected Things (aka. Internet of Things - IoT) Speakers Due to UAE law, confirmed speakers will need to submit a copy of their passport and contact information in advance of the meeting. More details are available here: https://ripe75.ripe.net/attend/dctm-requirements Please also note that speakers do not receive any discount or funding towards the meeting fee at RIPE Meetings. Submissions RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and not attempt a product demonstration. Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minutes presentation with 5-10 minutes discussion - Tutorials: up to two hours (Monday morning) - Workshops: one hour (during evening sessions) to two hours (Monday morning) - BoFs: approximately one hour - Lightning talks: 10 minutes total for both presentation and any discussion The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe75.ripe.net/submit-topic/ - Lightning talks should also be submitted using the meeting submission system (https://ripe75.ripe.net/submit-topic/) and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced on short notice, in some cases on the same day but often one day prior to the time slot allocated. - Presenters who propose a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panellists, presenters and moderators. If you have any questions or requests concerning content submissions, please email pc [at] ripe [dot] net. -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 0

IPv4 Hijacking For Idiots
by Ronald F. Guilmette 03 Jul '17

03 Jul '17

The more I know, the less I understand. Maybe some of you kind folks can help. Please explain for me the following scenario, and how this all actually works in practice. Let's say that you're a malevolent Bad Actor and all you want to do is to get hold of some ASN that nobody is watching too closely, and then use that to announce some routes to some IPv4 space that nobody is watching too closely, so that you can then parcel out that IP space to your snowshoe spammer pals... at least until somebody gets wise. OK, so you pull down a copy of, say, the RIPE WHOIS database, and you programatically walk your way through it, looking for contact email addresses on ASN records where the domain of the contact email address has become unregistered. Say for example the one for AS34991. So then you re-register that contact domain, fresh, and then you start telling all of your friends and enemies that you -are- AS34991. That part seems simple enough, and indeed, I've seen -this- part of the movie several times before. However once you have stepped into the identity of the former owners of the ASN, if you then want to actually proceed to -announce- some routes, and actually ave those routes make it out onto the Internet generally, then you still have to -peer- with somebody, right? So, I guess then, if you're clever, you look and see who the ASN you've just successfully hijacked has historically peered with, and then you somehow arrange to send route announcements to those guys, right? (I'm talking about AS206776 and AS57344 here, BTW.) But see, this is where I get lost. I mean how do you push your route announcements to these guys? (I don't actually know that much about how BGP actually works in practice, so please bear with me.) How do you know what IP address to send your announcements to? And if you are going to push your route announcements out to, say, the specific routers that are run by AS206776 and AS57344, i.e. the ones that will send your desired route announcements out to the rest of the Internet... well.. how do you find out the IP addresses of those routers on those other networks? Do you call up the NOCs at those other networks and do a bit of social engineering on them to find out the IP addresses you need to send to? And can you just send BGP messages to the routers on those other networks without -any- authentication or anything and have those routers just blindly accept them -and- relay them on to the whole rest of the Internet?? I've read article after article after article bemoanging the fact that "BGP isn't secure", but now I'm starting to wonder just how massively and unbelieveably unsecure it actually is. I mean would these routers being run by AS206776 and AS57344 just blindly accept -any- route announcements sent to them from literally -any- IP address? (That seems positively looney tunes to me! I mean things can't really be THAT colossally and unbelievably stupid, can they?) Thanks in advance for any enlightenment. Regards, rfg P.S. It would appear to be the case that since some time in April of this year the "Bulgarian" network, AS34991, had evinced a rather sudden and pronounced affinity for various portion of the IPv4 address space nominally associated with the nation of Columbia, including at least five /24 blocks within 168.176.0.0/16 which, from where I am sitting, would appear to belong to the National University of Columbia. Oh well. They apparently haven't been missing those five gaping holes in their /16 since the time the more specifics started showing up in April. And anyway, so far it looks like the new owners of AS34991 haven't actually sub-leased any of those /24s to any spammers yet. Only the 190.90.88.0/24 block seems to be filled, wall-to-all, with snowshoe spammers so far.

13 26

Transit Providers in Bracknell, UK
by Gary T. Giesen 03 Jul '17

03 Jul '17

Can anyone recommend a transit provider in Bracknell, UK? Not too picky on requirements, but IPv6 is a must; RTBH and good peering are a very good to have. We're looking to replace one of our current providers (Virgin Media - AS5089). I have no problem naming them as they treat prefix list updates like service changes (and charge £250 for the privilege). We gave in and paid it and and 2 weeks later they have still not processed the change. Cheers, GTG

3 3

RFC 8195 "Use of Large Communities"
by Job Snijders 01 Jul '17

01 Jul '17

Dear all, RFC 8195 "Use of BGP Large Communities" was just now published: https://tools.ietf.org/html/rfc8195 RFC 8195 presents examples and inspiration for the operational application of Large Communities. The document suggests logical categories of Large Communities and demonstrates an orderly manner of organizing community values within those categories to achieve typical goals in routing policy. Any network or route server operator can consider using the concepts presented as the basis for their own Large Communities repertoire. RFC 8195 is meant as a companion document in the same way that RFC 1998 provided a concrete real-world application for RFC1997 BGP Communities. The RFC draws on the experience of operator communities such as NANOG and NLNOG. A ton of open source implementations [1] with Large support are already available. And with more traditional vendors like IOS XR, Junos, Arista & Nokia having releases around the corner, I hope this will be useful when planning your Large Communities deployment later this year. Kind regards, Job [1]: http://largebgpcommunities.net/implementations/

1 0

Weekly Routing Table Report
by cscora＠apnic.net 30 Jun '17

30 Jun '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, AusNOG, SANOG, PacNOG, MENOG, SAFNOG, SdNOG, BJNOG, CaribNOG 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 01 Jul, 2017 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 653102 Prefixes after maximum aggregation (per Origin AS): 254091 Deaggregation factor: 2.57 Unique aggregates announced (without unneeded subnets): 314847 Total ASes present in the Internet Routing Table: 57642 Prefixes per ASN: 11.33 Origin-only ASes present in the Internet Routing Table: 49881 Origin ASes announcing only one prefix: 21993 Transit ASes present in the Internet Routing Table: 7761 Transit-only ASes present in the Internet Routing Table: 230 Average AS path length visible in the Internet Routing Table: 4.4 Max AS path length visible: 41 Max AS path prepend of ASN ( 55644) 36 Prefixes from unregistered ASNs in the Routing Table: 63 Numnber of instances of unregistered ASNs: 67 Number of 32-bit ASNs allocated by the RIRs: 19273 Number of 32-bit ASNs visible in the Routing Table: 14977 Prefixes from 32-bit ASNs in the Routing Table: 61008 Number of bogon 32-bit ASNs visible in the Routing Table: 64 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 360 Number of addresses announced to Internet: 2848137828 Equivalent to 169 /8s, 195 /16s and 34 /24s Percentage of available address space announced: 76.9 Percentage of allocated address space announced: 76.9 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 98.7 Total number of prefixes smaller than registry allocations: 217503 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 179085 Total APNIC prefixes after maximum aggregation: 51339 APNIC Deaggregation factor: 3.49 Prefixes being announced from the APNIC address blocks: 178234 Unique aggregates announced from the APNIC address blocks: 73760 APNIC Region origin ASes present in the Internet Routing Table: 8213 APNIC Prefixes per ASN: 21.70 APNIC Region origin ASes announcing only one prefix: 2298 APNIC Region transit ASes present in the Internet Routing Table: 1158 Average APNIC Region AS path length visible: 4.4 Max APNIC Region AS path length visible: 41 Number of APNIC region 32-bit ASNs visible in the Routing Table: 3052 Number of APNIC addresses announced to Internet: 763598436 Equivalent to 45 /8s, 131 /16s and 150 /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: 198988 Total ARIN prefixes after maximum aggregation: 94731 ARIN Deaggregation factor: 2.10 Prefixes being announced from the ARIN address blocks: 200843 Unique aggregates announced from the ARIN address blocks: 92112 ARIN Region origin ASes present in the Internet Routing Table: 17906 ARIN Prefixes per ASN: 11.22 ARIN Region origin ASes announcing only one prefix: 6620 ARIN Region transit ASes present in the Internet Routing Table: 1777 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: 2060 Number of ARIN addresses announced to Internet: 1108512928 Equivalent to 66 /8s, 18 /16s and 144 /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: 175225 Total RIPE prefixes after maximum aggregation: 85781 RIPE Deaggregation factor: 2.04 Prefixes being announced from the RIPE address blocks: 171043 Unique aggregates announced from the RIPE address blocks: 102902 RIPE Region origin ASes present in the Internet Routing Table: 24139 RIPE Prefixes per ASN: 7.09 RIPE Region origin ASes announcing only one prefix: 11100 RIPE Region transit ASes present in the Internet Routing Table: 3405 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 33 Number of RIPE region 32-bit ASNs visible in the Routing Table: 5956 Number of RIPE addresses announced to Internet: 712116864 Equivalent to 42 /8s, 114 /16s and 10 /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: 82725 Total LACNIC prefixes after maximum aggregation: 18405 LACNIC Deaggregation factor: 4.49 Prefixes being announced from the LACNIC address blocks: 84002 Unique aggregates announced from the LACNIC address blocks: 38760 LACNIC Region origin ASes present in the Internet Routing Table: 6079 LACNIC Prefixes per ASN: 13.82 LACNIC Region origin ASes announcing only one prefix: 1648 LACNIC Region transit ASes present in the Internet Routing Table: 1119 Average LACNIC Region AS path length visible: 5.4 Max LACNIC Region AS path length visible: 36 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 3592 Number of LACNIC addresses announced to Internet: 170756320 Equivalent to 10 /8s, 45 /16s and 136 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-266652 + 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: 16968 Total AfriNIC prefixes after maximum aggregation: 3779 AfriNIC Deaggregation factor: 4.49 Prefixes being announced from the AfriNIC address blocks: 18620 Unique aggregates announced from the AfriNIC address blocks: 6990 AfriNIC Region origin ASes present in the Internet Routing Table: 1042 AfriNIC Prefixes per ASN: 17.87 AfriNIC Region origin ASes announcing only one prefix: 326 AfriNIC Region transit ASes present in the Internet Routing Table: 204 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: 317 Number of AfriNIC addresses announced to Internet: 92728832 Equivalent to 5 /8s, 134 /16s and 238 /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 5552 4190 74 ERX-CERNET-BKB China Education and Rese 7545 3933 404 363 TPG-INTERNET-AP TPG Telecom Limited, AU 17974 2976 902 73 TELKOMNET-AS2-AP PT Telekomunikasi Indo 4766 2805 11134 756 KIXS-AS-KR Korea Telecom, KR 9829 2752 1499 540 BSNL-NIB National Internet Backbone, IN 9808 2175 8699 34 CMNET-GD Guangdong Mobile Communication 4755 2088 422 222 TATACOMM-AS TATA Communications formerl 45899 2019 1415 109 VNPT-AS-VN VNPT Corp, VN 7552 1632 1104 73 VIETEL-AS-AP Viettel Corporation, VN 9498 1594 360 139 BBIL-AP BHARTI Airtel Ltd., IN 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 22773 3814 2953 161 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 6327 3411 1333 81 SHAW - Shaw Communications Inc., CA 18566 2179 405 109 MEGAPATH5-US - MegaPath Corporation, US 6389 2064 3671 39 BELLSOUTH-NET-BLK - BellSouth.net Inc., 20115 2010 2172 417 CHARTER-NET-HKY-NC - Charter Communicat 209 1825 5068 640 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 16509 1815 3696 586 AMAZON-02 - Amazon.com, Inc., US 30036 1795 325 309 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 6983 1695 854 231 ITCDELTA - Earthlink, Inc., US 701 1562 10560 631 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 3338 187 22 ALJAWWALSTC-AS, SA 8551 2971 377 40 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 2904 963 2090 AKAMAI-ASN1, US 34984 2000 328 417 TELLCOM-AS, TR 9121 1955 1691 17 TTNET, TR 12479 1614 1044 53 UNI2-AS, ES 13188 1602 100 55 TRIOLAN, UA 12389 1524 1408 626 ROSTELECOM-AS, RU 6849 1225 355 21 UKRTELNET, UA 8402 1123 544 15 CORBINA-AS OJSC "Vimpelcom", RU 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 10620 3541 544 185 Telmex Colombia S.A., CO 8151 2518 3404 576 Uninet S.A. de C.V., MX 11830 2089 369 57 Instituto Costarricense de Electricidad 7303 1550 1010 243 Telecom Argentina S.A., AR 6503 1541 437 53 Axtel, S.A.B. de C.V., MX 6147 1299 377 27 Telefonica del Peru S.A.A., PE 3816 1026 501 94 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 28573 968 2301 177 CLARO S.A., BR 11172 915 126 82 Alestra, S. de R.L. de C.V., MX 18881 895 1052 23 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 1254 398 48 LINKdotNET-AS, EG 37611 724 91 8 Afrihost, ZA 36903 711 357 129 MT-MPLS, MA 36992 643 1375 26 ETISALAT-MISR, EG 24835 499 850 15 RAYA-AS, EG 37492 407 320 75 ORANGE-, TN 29571 401 36 10 CITelecom-AS, CI 8452 358 1730 17 TE-AS TE-AS, EG 15399 353 35 7 WANANCHI-, KE 2018 300 327 74 TENET-1, ZA 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 5552 4190 74 ERX-CERNET-BKB China Education and Rese 7545 3933 404 363 TPG-INTERNET-AP TPG Telecom Limited, AU 22773 3814 2953 161 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 10620 3541 544 185 Telmex Colombia S.A., CO 6327 3411 1333 81 SHAW - Shaw Communications Inc., CA 39891 3338 187 22 ALJAWWALSTC-AS, SA 17974 2976 902 73 TELKOMNET-AS2-AP PT Telekomunikasi Indo 8551 2971 377 40 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 2904 963 2090 AKAMAI-ASN1, US 4766 2805 11134 756 KIXS-AS-KR Korea Telecom, KR Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 22773 3814 3653 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7545 3933 3570 TPG-INTERNET-AP TPG Telecom Limited, AU 10620 3541 3356 Telmex Colombia S.A., CO 6327 3411 3330 SHAW - Shaw Communications Inc., CA 39891 3338 3316 ALJAWWALSTC-AS, SA 8551 2971 2931 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 17974 2976 2903 TELKOMNET-AS2-AP PT Telekomunikasi Indonesia, I 9829 2752 2212 BSNL-NIB National Internet Backbone, IN 9808 2175 2141 CMNET-GD Guangdong Mobile Communication Co.Ltd. 18566 2179 2070 MEGAPATH5-US - MegaPath Corporation, US 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 65000 PRIVATE 31.219.177.0/25 8966 ETISALAT-AS P.O. Box 1150, Dub 65000 PRIVATE 31.219.177.128/25 8966 ETISALAT-AS P.O. Box 1150, Dub 64525 PRIVATE 45.119.143.0/24 133275 GIGANTIC-AS Gigantic Infotel P 64525 PRIVATE 45.125.62.0/24 133275 GIGANTIC-AS Gigantic Infotel P 65010 PRIVATE 46.56.192.0/21 42772 VELCOM-AS, BY 65010 PRIVATE 46.56.224.0/21 42772 VELCOM-AS, BY 65001 PRIVATE 46.237.40.0/21 13118 ASN-YARTELECOM PJSC Rostelecom 65534 PRIVATE 58.68.109.0/24 10201 DWL-AS-IN Dishnet Wireless Lim 64513 PRIVATE 62.150.101.0/24 9155 QNET Kuwait, KW Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 14.192.48.0/24 134833 LIHGL-HK LANLIAN INTERNATIONAL HOLDING GROUP LIMITE 14.192.49.0/24 134833 LIHGL-HK LANLIAN INTERNATIONAL HOLDING GROUP LIMITE 14.192.50.0/24 134833 LIHGL-HK LANLIAN INTERNATIONAL HOLDING GROUP LIMITE 14.192.51.0/24 134833 LIHGL-HK LANLIAN INTERNATIONAL HOLDING GROUP LIMITE 23.226.112.0/20 62788 -Reserved AS-, ZZ 27.100.7.0/24 56096 UNKNOWN 36.255.250.0/24 64091 UNKNOWN 41.76.232.0/21 62878 XLITT - Xlitt, US 41.77.248.0/21 62878 XLITT - Xlitt, US 41.78.12.0/23 62878 XLITT - Xlitt, US 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:104 /12:280 /13:545 /14:1049 /15:1846 /16:13473 /17:7631 /18:13434 /19:24639 /20:38561 /21:41217 /22:77596 /23:64333 /24:366107 /25:871 /26:604 /27:642 /28:35 /29:23 /30:18 /31:3 /32:27 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6327 3214 3411 SHAW - Shaw Communications Inc., CA 22773 2977 3814 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 39891 2898 3338 ALJAWWALSTC-AS, SA 8551 2436 2971 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 18566 2072 2179 MEGAPATH5-US - MegaPath Corporation, US 30036 1587 1795 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 11830 1479 2089 Instituto Costarricense de Electricidad y Telec 10620 1469 3541 Telmex Colombia S.A., CO 11492 1382 1532 CABLEONE - CABLE ONE, INC., US 6389 1371 2064 BELLSOUTH-NET-BLK - BellSouth.net Inc., US Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1596 2:803 4:18 5:2432 6:34 8:1044 12:1833 13:123 14:1739 15:28 16:2 17:158 18:90 20:61 23:2384 24:1974 25:2 27:2454 31:1919 32:80 33:14 35:20 36:387 37:2347 38:1318 39:62 40:98 41:2928 42:485 43:1930 44:71 45:2848 46:2794 47:154 49:1236 50:985 51:18 52:830 54:363 55:6 56:4 57:42 58:1577 59:1053 60:388 61:1959 62:1604 63:1914 64:4587 65:2221 66:4566 67:2271 68:1244 69:3380 70:1149 71:586 72:2201 74:2692 75:387 76:423 77:1545 78:1457 79:2378 80:1404 81:1391 82:993 83:722 84:906 85:1748 86:481 87:1161 88:757 89:2102 90:175 91:6188 92:975 93:2384 94:2376 95:2683 96:628 97:353 98:1063 99:86 100:154 101:1201 103:15187 104:2961 105:182 106:508 107:1721 108:824 109:2863 110:1457 111:1725 112:1193 113:1251 114:1028 115:1721 116:1793 117:1701 118:2204 119:1608 120:1054 121:1111 122:2252 123:1831 124:1480 125:1888 128:774 129:652 130:434 131:1406 132:520 133:199 134:654 135:225 136:447 137:437 138:1933 139:490 140:394 141:600 142:766 143:893 144:796 145:182 146:1028 147:690 148:1446 149:579 150:705 151:973 152:694 153:304 154:776 155:753 156:610 157:649 158:450 159:1512 160:685 161:743 162:2530 163:535 164:804 165:1395 166:379 167:1244 168:2957 169:791 170:3454 171:318 172:1022 173:1947 174:811 175:750 176:1877 177:4080 178:2481 179:1180 180:2208 181:1881 182:2376 183:1000 184:866 185:10032 186:3207 187:2233 188:2709 189:1814 190:8252 191:1327 192:9499 193:5783 194:4682 195:3910 196:2080 197:1261 198:5500 199:5895 200:7456 201:4340 202:10368 203:10020 204:4486 205:2814 206:3016 207:3114 208:3985 209:3933 210:3974 211:2144 212:2855 213:2500 214:876 215:66 216:5771 217:2104 218:868 219:599 220:1692 221:931 222:781 223:1175 End of report

1 0

Fwd: Bonus support for Action for Children
by Colin Johnston 30 Jun '17

30 Jun '17

excuse the subject, relevant as IT techies like this. > > Bonus support for Action for Children > A BT senior manager is donating half of his bonus to Action for Children’s Byte Night North West event and encouraging others to do the same. > Colin Johnston is an IT technical manager who has supported Action for Children for several years. This year he and hundreds of other executives will be sleeping out for a night on 6 October as part of the charity’s annual Byte Night event. As well as raising money by taking part in this, Colin has decided to also donate 50% of his bonus payment (£2,482.00 / 2 = £1241(donation amount)) this year to Action for Children. > Colin said, “Being involved for a while with Action for Children, I’ve got to know about the amazing work they do with children and young people and families. I’m happy to be in a position where I can help support their services by fundraising and donating. If people can’t take part in Byte Night then they can still help out by donating what they can – if other executives decided to also give half of their bonus to Action for Children, it would be a simple but really effective way of helping young people to have a brighter future.” > > Byte Night is Action for Children's biggest annual fundraiser; a national ‘sleep-out’ event. Each year, hundreds of like-minded people from the technology and business arena give up their beds for one night to help change the lives of vulnerable young people. It all began in 1998 when 30 individuals slept out in London and raised £35,000. Since then Byte Night has grown to 10 UK locations and over 1,200 people slept out in 2016. Byte Night is one of the UK’s top 17 mass participation charity events and is the largest charity sleep-out having raised over £9.6 million since the first event. Byte Night is celebrating its 20th anniversary this year and its fifth year in the North West. > Colin is a board member of the North West Byte Night event. > BT Volunteering is a very worthwhile endeavour. > > See mydonate page linked to Byte Night https://mydonate.bt.com/fundraisers/colinjohnston1 <https://mydonate.bt.com/fundraisers/colinjohnston1> > > For more information go to www.bytenight.org.uk <http://www.bytenight.org.uk/> or to donate Text Byte17 and the amount to 70070. > > Colin > > Colin Johnston <https://myprofile.bt.com/Person.aspx?accountname=IUSER%5C600969844> > IT Support Senior Professional, Core IT Infrastructure > BT Technology Service & Operations <https://intra.bt.com/bt/tso/Pages/index.aspx> | Tel: 01313001324 <tel:01313001324> | MyProfile <https://myprofile.bt.com/Person.aspx?accountname=IUSER%5C600969844> | colin.johnstone(a)bt.com <mailto:colin.johnstone@bt.com> | http://fixit.bt.com/ <http://fixit.bt.com/> > > BT Group plc Registered office: 81 Newgate Street London EC1A 7AJ. Registered in England and Wales no. 4190816 This electronic message contains information from BT Group plc which may be privileged or confidential. The information is intended to be for the use of the individual(s) or entity named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please delete it and notify me immediately by telephone or email.

3 2

Point 2 point IPs between ASes
by Krunal Shah 30 Jun '17

30 Jun '17

Hello, What subnet mask you are people using for point to point IPs between two ASes? Specially with IPv6, We have a transit provider who wants us to use /64 which does not make sense for this purpose. isn’t it recommended to use /127 as per RFC 6164 like /30 and /31 are common for IPv4. I was thinking, if someone is using RFC7404 for point to point IP between two ASes and establish BGP over link local addresses. This way you have your own IP space on your router and transit provider does not have to allocate IP space for point to point interface between two ASes. In traceroutes you would see only loopback IP address with GUA assigned from your allocated routable address space. Remotely DDoS to this link isn’t possible this way. Thoughts? [Description: cid:image010.png@01D1ECB6.5D17D120]<https://primus.ca/> Krunal Shah Network Analyst, IP & Transport Network Engineering O: 416-855-1805 kshah(a)primustel.ca [Description: cid:image011.png@01D1ECB6.5D17D120]<https://primus.ca/> [Description: cid:image012.png@01D1ECB6.5D17D120] <https://twitter.com/Primus4Business> [Description: cid:image013.png@01D1ECB6.5D17D120] <https://www.facebook.com/primusforbusiness> [Description: cid:image014.png@01D1ECB6.5D17D120] <https://www.linkedin.com/company/primus-telecommunications-canada-inc-> ________________________________ This electronic message contains information from Primus Management ULC ("PRIMUS") , which may be legally privileged and confidential. The information is intended to be for the use of the individual(s) or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please notify us by telephone or e-mail (to the number or address above) immediately. Any views, opinions or advice expressed in this electronic message are not necessarily the views, opinions or advice of PRIMUS. It is the responsibility of the recipient to ensure that any attachments are virus free and PRIMUS bears no responsibility for any loss or damage arising in any way from the use thereof.The term "PRIMUS" includes its affiliates. ________________________________ Pour la version en français de ce message, veuillez voir http://www.primustel.ca/fr/legal/cs.htm

15 23

[NANOG-announce] NANOG 71 Call for Presentations is Open
by L Sean Kennedy 30 Jun '17

30 Jun '17

NANOG Community, The NANOG Program Committee is excited to announce that we are now accepting proposals for all sessions at NANOG 71 in San Jose, CA, October 2-4 2017. Below is a summary of key details from the Call for Presentations <http://www.cvent.com/events/nanog-71/custom-22-4f71b2f3181e49c1ab199f5d5d40…> from the NANOG 71 meeting page <http://www.cvent.com/events/nanog-71/event-summary-4f71b2f3181e49c1ab199f5d…> . We look forward to seeing you in San Jose! Sincerely, L Sean Kennedy NANOG Program Committee NANOG 71 Call for Presentations The North American Network Operators' Group (NANOG) will hold its 71st conference in San Jose, California. The conference takes place on October 2-4, 2017. The NANOG Program Committee seeks proposals for presentations, panels, tutorials, and track sessions for the NANOG 71 program. We welcome suggestions of potential speakers or new topic ideas. Presentations may cover technologies already deployed or soon-to-be deployed in the Internet. Vendors are welcome to submit talks which cover relevant technologies and capabilities, but presentations must not be promotional or discuss proprietary solutions. NANOG 71 submissions can be entered on the NANOG Program Committee Tool. <https://pc.nanog.org/> How To Submit The primary speaker, moderator, or author should submit a presentation proposal and an abstract on the Program Committee Tool <https://pc.nanog.org/>. - Select “Propose Talk” from the *Talks* menu - Select the NANOG 71 meeting in the *Meeting* menu - Select the appropriate *Session* the talk will be presented in (General Session 30-45 minutes; Tutorial 90-120 minutes; Track 90-120 minutes) - Provide the information requested below Upload draft slides as soon as possible so the Program Committee can understand the intended structure and level of detail covered by the talk. Draft slides are not required for a proposal to be initiated, but they are usually expected before the Program Committee can definitively accept a submission. The following information should be included in the proposal: - Author's name(s) - Professional or educational affiliation - A preferred contact email address - A preferred phone number for contact - Submission category (General Session, Panel, Tutorial, or Track) - Presentation title - Abstract - Slides in PowerPoint (preferred) or PDF format - Comments as desired including URL to materials or previous talk Timeline for submission and proposal review - Submitter enters abstract (and draft slides if possible) in Program Committee Tool <https://pc.nanog.org/>. - Any time following Call for Presentations and prior to CFP deadline for slide submission - PC performs initial review and assigns a “Shepherd” to help develop the submission. - Within 2 weeks - Submitter develops draft slides of talk - Please submit initial draft slides early - Panel and Track submissions should provide topic list and intended/confirmed participants - PC reviews slides and continues to work with Submitter as needed to develop topic - Draft presentation slides should be submitted prior to published deadline for slides - PC accepts or declines submission - Agenda assembled and posted - Submitters notified If you think you have an interesting topic but want feedback or suggestions for developing an idea into a presentation, please email the Program Committee <nanogpc(a)nanog.org>, and a representative of the Program Committee will respond. Otherwise, submit your talk, keynote, track, or panel proposal to the Program Committee Tool <https://pc.nanog.org/> without delay! We look forward to reviewing your submission. Key Dates for NANOG 71 Registration for NANOG 71 opens Thursday, 06/29/2017 Agenda Outline for NANOG 71 posted Thursday, 06/29/2017 CFP Deadline: Presentation Slides Due Monday, 07/24/2017 Topic List and NANOG Highlights Friday, 07/28/2017 Final presentation submission <https://pc.nanog.org/> Monday, 09/25/2017 Lightning Talk submissions open Sunday, 10/1/2017 General presentation advice is provided with our “Guidelines for Presenting at a NANOG Meeting <https://www.nanog.org/meetings/presentation/guidelines>”, "Present at a NANOG" <https://www.nanog.org/meetings/presentation> and “Tips on Giving a Talk <https://www.nanog.org/meetings/presentation/tips>”. The NANOG Program Committee seeks proposals for presentations, panels, tutorial sessions, and tracks in all areas of network operations, such as: - Network Connectivity, Interconnection, and Architecture - Network Management and Configuration including Automation - Network Performance, Measurement, and Telemetry - Data Center and Physical Plant including Cooling and Power Efficiency - Network Research - Internet Governance - Routing and Switching Protocols - Network Data and Control Plane Security - Optical and Transmission Technologies - Wireless Networks - DNS, Transport, and Applications - Network Operations and Engineering Professional Experiences Submissions are welcomed by and for network operators of all sizes. Presentations about difficult problems (and interesting solutions) that you encounter in the course of your job are encouraged. The NANOG registration fee is waived for: - General Session presentations: the conference registration fee will be waived for a maximum of one speaker. - General Session panels: conference registration fees will be waived for one panel moderator and all panelists. - Tracks: conference registration fees will be waived for one moderator. - Tutorials: conference registration fees will be waived for one instructor. _______________________________________________ NANOG-announce mailing list NANOG-announce(a)mailman.nanog.org http://mailman.nanog.org/mailman/listinfo/nanog-announce

1 0