July 2016 - Test - lists.nanog.org

25 Jul '16

Hello if this is not appropriate for this list please excuse me and disregard this email. I thought of no better place than this place however if there is a better place for this email please advise and I will direct the email and the student to the questions. I received an email form a student this morning asking the following questions. 1. Are there any email providers that market to professional but offer a student rate or are of good quality but inexpensive etc.. 2. I have looked at the Microsoft exchange server in the cloud while it looks promising it does not seems to fit my cost ratio 3. I would mainly like to be able to have a professional email address so when I apply for jobs and other business of that sort I can be seen as a professional and to gather my email from various sources i.e. Gmail, Hotmail etc. and to present a more professional appearance to my work and school work etc.. I responded that he should look at google apps, however his questions got me thinking and I google around for an answer to give him, however I am not as well versed as I should be in the cloud besides for backup service and active directory management. I would like to know if you guys have any places I own give the student. Thanks Samual Office of technology education Please excuse grammar and spelling errors as this was typed on a smartphone. -----BEGIN PGP MESSAGE----- Version: GnuPG v2 owFdVAtsFEUYbqkQvPQoGgpUHo5FzEHKUcqr2FCoILY8pFCQR1Jlbnf2brndnXVm t9fjFSOCFtBUimjBNtJCI5AIFOQhFbSgxAgURQIo8rKIaUTTVBERxH9274rlcpfb 2fn/b77/+79/yr1JCV0TScLQ81mX05oSv24JJMxZP+ZGPtE0ilQFWSGVI/ga1ELY NBk1mYotghTK3D1N5RYyNYI5QaRUsuFPJwgbMpJVzkgQM9kNJDpWNT8qgBW1gyEL UQVQUYBYFmGAgCUCW9hwo911iEZICew6RAgjggnumNJOxMGPM8FyicpdGgUoomoa sGFEsgRMLFLsiRW3bJkYsEOd5cs24ZZKDe73egoQ5BC1hMgQHUuD83Tg0J4ljtYp M1QjiDAPiz8Bo1AQMCJW9wGR1zPMj5xPHiOxirARjVNntESVCeNCBgvpmIWJQws2 FMI5YGANBWyhnAL13yfBREdABwx4oGqQUhmOxZpqRZ141SClJjE4VIKIJfmvvlLn 9WTFqBSgEIb3GqVhUacr0TRVYpRTxRI9haYEQSfCnFYYToCkUVtGkZCqQVMsJ5sL orrKRdHwSqbEtQ0nROeiDgXe6lEkUe5QVikIMrydRYTamgxVq4YWBVeFiUgJgEAB zXl0WOKOYsQ6KcsMXiFOgRAxAAucCiDCGgtpgDutpkJuUAPoiViquCpzyixIkKC/ AVEjpGP+4DGOVSgKYgdDjzdMgXJRCWYqtcXhNpOgYtVP/Og5sZ+B8qnlBArN4yAm UBU9w8I15IFzTJNghg3JKRjOiVAWdhK5FKJUc9cCDcyJkPsTJuUmNWQiuyUJT4cc MUVXREfBEEEQEeB5RvtMCeO2exNCLDG3Vuizo6rhuNidnXgqozashaKgFDZ4BBCE JMJSIVW/Dwvi6+5twVEEbhEEL7kwFoetGC9QuoONAoSD8bkDH8BS2DYdt6mSO8FY ssQx7gRTFgWTGDhIdJDR326cuGPCBo2I+yJKbRS0ozzmG5gy574QLGjEcIn/b/z9 MTVngdnByV5PEdZhguBhuqIIIsIwRAoZVKNBMIBsS8LBRiytsMMFGGRYh/F1O2eC CEJPwhiF2cbcvTMi4iFqgjIAAqMM8ZYZogZxmJR16vtQQmLXhC6dO4nrOMHzcPf4 HX1lZMrtpMXDM+ftvL7Oc7V7y5oF/sNjKk+l7Mr9nQQWdvlW2pmknlp+7vGc5rsZ plKfdP3MrDtZ4S8b7/0yUL634+OKtwu9F36aNzmw+c3GwP59Y+f6sof+NWtagnW6 fvvKaxNHlc2+lH/+yfU/D/lg8Onvvqqvz1g9s7ri2dTK6ak1ZxsSq349M6P12PSj Ff7RV7In59+yW58YtfiN6hHW9/4iVsX63t1mp51U01O+aPCkKgPeinqtCbt6k9oP UZ8B/RXfp59sKn5q0I4Zrd0KG7VFM7f3qBh7zB52ee+2C1OSD2x5/XgZe/Usa/ot reGdjNGh4p2Dt/zQduxE9b8NzX2Ti1bU7Njwnpl2boRP2tP0uS/vwv6LgTGD0s+Y f+fW6X/glpu9D437qLJ1LV7X3OtmwchFvjvrtFUvZC1flpgdJs3+rav6VfXvZmS3 bFx6Ut2aeevA8dZ/LvqkouKNNT2u8aljlz82aUVb79bnB/65enxyy5L9RnmS52DO o20r26bOn1t46GDpKPvI3vpb41bMTrd6NY+P1r2WenjRxEsvLqC1czOz5uyaXz0n r8f5JRs2bV3ax/dS3chlJ2xf9e5Ma3TnnH63NynXOl2sThzx7pArFXTg7mGD/Pt6 BtdWPpNXUj6pLP3p67Wh9xP31BypOlc8M6u0TfXmTkuxa298M6E0+Ui/NRWb0xt7 7mnKrWPlRWkHShf/+EjOlP8A =cNlY -----END PGP MESSAGE-----

9 8

Call for presentations RIPE 73
by Benno Overeinder 25 Jul '16

25 Jul '16

Dear colleagues, Please find the CFP for RIPE 73 below or at https://ripe73.ripe.net/submit-topic/cfp/. The deadline for submissions is 28 August 2016. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. Kind regards, Benno Overeinder RIPE PC Chair https://www.ripe.net/participate/meetings/ripe-meetings/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 73 will take place from 24-28 October 2016 in Madrid, Spain. 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 73. See the full descriptions of the different presentation formats, https://ripe73.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 28 August 2016. 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 in operations - Commercial transactions of IPv4 addresses - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange - Internet of Things (IoT) 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 The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe73.ripe.net/submit-topic/submission-form/. - Lightning talks should also be submitted using the meeting submission system (https://ripe73.ripe.net/submit-topic/submission-form/) 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. - Due to potential technical issues, presenters/panellists should be physically present at the RIPE Meeting. 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

number of characters in a domain?
by Ryan Finnesey 24 Jul '16

24 Jul '16

I was hoping someone can help me confirm my research. I am correct that domains are now limited to 67 characters in length including the extension? Cheers Ryan

8 7

MTU
by Baldur Norddahl 23 Jul '16

23 Jul '16

Hi What is best practice regarding choosing MTU on transit links? Until now we have used the default of 1500 bytes. I now have a project were we peer directly with another small ISP. However we need a backup so we figured a GRE tunnel on a common IP transit carrier would work. We want to avoid the troubles you get by having an effective MTU smaller than 1500 inside the tunnel, so the IP transit carrier agreed to configure a MTU of 9216. Obviously I only need to increase my MTU by the size of the GRE header. But I am thinking is there any reason not to go all in and ask every peer to go to whatever max MTU they can support? My own equipment will do MTU of 9600 bytes. On the other hand, none of my customers will see any actual difference because they are end users with CPE equipment that expects a 1500 byte MTU. Trying to deliver jumbo frames to the end users is probably going to end badly. Regards, Baldur

12 17

IPv6 Deployment for Mobile Subscribers
by Ricardo Ferreira 23 Jul '16

23 Jul '16

Is there anyone here working in an ISP where IPv6 is deployed? We are starting to plan the roll-out IPv6 to mobile subscribers (phones) I am interesting in knowing the mask you use for the assignment; whether it is /64 or /128. In RFC 3177, it says: 3. Address Delegation Recommendations The IESG and the IAB recommend the allocations for the boundary between the public and the private topology to follow those general rules: - /48 in the general case, except for very large subscribers. - /64 when it is known that one and only one subnet is needed by design. - /128 when it is absolutely known that one and only one device is connecting. Basically a sole device will be connecting to the internet so I am wondering if this rule is follwed. Cheers -- Ricardo Ferreira

9 9

Weekly Routing Table Report
by cscora＠apnic.net 22 Jul '16

22 Jul '16

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, SAFNOG, PaNOG, 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 23 Jul, 2016 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 605817 Prefixes after maximum aggregation (per Origin AS): 218806 Deaggregation factor: 2.77 Unique aggregates announced (without unneeded subnets): 294816 Total ASes present in the Internet Routing Table: 54378 Prefixes per ASN: 11.14 Origin-only ASes present in the Internet Routing Table: 36517 Origin ASes announcing only one prefix: 15523 Transit ASes present in the Internet Routing Table: 6452 Transit-only ASes present in the Internet Routing Table: 163 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 54 Max AS path prepend of ASN ( 55644) 51 Prefixes from unregistered ASNs in the Routing Table: 61 Unregistered ASNs in the Routing Table: 14 Number of 32-bit ASNs allocated by the RIRs: 14745 Number of 32-bit ASNs visible in the Routing Table: 11409 Prefixes from 32-bit ASNs in the Routing Table: 45128 Number of bogon 32-bit ASNs visible in the Routing Table: 15 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 359 Number of addresses announced to Internet: 2819713764 Equivalent to 168 /8s, 17 /16s and 106 /24s Percentage of available address space announced: 76.2 Percentage of allocated address space announced: 76.2 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 98.2 Total number of prefixes smaller than registry allocations: 197336 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 156415 Total APNIC prefixes after maximum aggregation: 42755 APNIC Deaggregation factor: 3.66 Prefixes being announced from the APNIC address blocks: 168745 Unique aggregates announced from the APNIC address blocks: 68054 APNIC Region origin ASes present in the Internet Routing Table: 5202 APNIC Prefixes per ASN: 32.44 APNIC Region origin ASes announcing only one prefix: 1183 APNIC Region transit ASes present in the Internet Routing Table: 934 Average APNIC Region AS path length visible: 4.4 Max APNIC Region AS path length visible: 54 Number of APNIC region 32-bit ASNs visible in the Routing Table: 2238 Number of APNIC addresses announced to Internet: 759062340 Equivalent to 45 /8s, 62 /16s and 95 /24s Percentage of available APNIC address space announced: 88.7 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: 182907 Total ARIN prefixes after maximum aggregation: 89306 ARIN Deaggregation factor: 2.05 Prefixes being announced from the ARIN address blocks: 188607 Unique aggregates announced from the ARIN address blocks: 88629 ARIN Region origin ASes present in the Internet Routing Table: 16283 ARIN Prefixes per ASN: 11.58 ARIN Region origin ASes announcing only one prefix: 5773 ARIN Region transit ASes present in the Internet Routing Table: 1703 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: 1345 Number of ARIN addresses announced to Internet: 1103342816 Equivalent to 65 /8s, 195 /16s and 172 /24s Percentage of available ARIN address space announced: 58.4 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: 145200 Total RIPE prefixes after maximum aggregation: 71268 RIPE Deaggregation factor: 2.04 Prefixes being announced from the RIPE address blocks: 154819 Unique aggregates announced from the RIPE address blocks: 95081 RIPE Region origin ASes present in the Internet Routing Table: 18096 RIPE Prefixes per ASN: 8.56 RIPE Region origin ASes announcing only one prefix: 7829 RIPE Region transit ASes present in the Internet Routing Table: 3002 Average RIPE Region AS path length visible: 4.4 Max RIPE Region AS path length visible: 27 Number of RIPE region 32-bit ASNs visible in the Routing Table: 4936 Number of RIPE addresses announced to Internet: 705966464 Equivalent to 42 /8s, 20 /16s and 49 /24s Percentage of available RIPE address space announced: 102.6 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, 196608-204287 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: 61695 Total LACNIC prefixes after maximum aggregation: 12258 LACNIC Deaggregation factor: 5.03 Prefixes being announced from the LACNIC address blocks: 76891 Unique aggregates announced from the LACNIC address blocks: 36669 LACNIC Region origin ASes present in the Internet Routing Table: 2485 LACNIC Prefixes per ASN: 30.94 LACNIC Region origin ASes announcing only one prefix: 568 LACNIC Region transit ASes present in the Internet Routing Table: 572 Average LACNIC Region AS path length visible: 4.8 Max LACNIC Region AS path length visible: 22 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 2653 Number of LACNIC addresses announced to Internet: 170131520 Equivalent to 10 /8s, 36 /16s and 0 /24s Percentage of available LACNIC address space announced: 101.4 LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-265628 + 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: 14410 Total AfriNIC prefixes after maximum aggregation: 3209 AfriNIC Deaggregation factor: 4.49 Prefixes being announced from the AfriNIC address blocks: 16396 Unique aggregates announced from the AfriNIC address blocks: 6052 AfriNIC Region origin ASes present in the Internet Routing Table: 733 AfriNIC Prefixes per ASN: 22.37 AfriNIC Region origin ASes announcing only one prefix: 170 AfriNIC Region transit ASes present in the Internet Routing Table: 172 Average AfriNIC Region AS path length visible: 4.6 Max AfriNIC Region AS path length visible: 19 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 237 Number of AfriNIC addresses announced to Internet: 80888832 Equivalent to 4 /8s, 210 /16s and 68 /24s Percentage of available AfriNIC address space announced: 80.4 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 5560 4191 75 ERX-CERNET-BKB China Education and Rese 7545 3425 384 253 TPG-INTERNET-AP TPG Telecom Limited, AU 4766 3177 11145 1126 KIXS-AS-KR Korea Telecom, KR 17974 2935 904 78 TELKOMNET-AS2-AP PT Telekomunikasi Indo 9829 2564 1487 522 BSNL-NIB National Internet Backbone, IN 1659 2493 1466 38 ERX-TANET-ASN1 Taiwan Academic Network 9808 2160 8761 40 CMNET-GD Guangdong Mobile Communication 4755 2078 431 243 TATACOMM-AS TATA Communications formerl 4808 1718 2318 556 CHINA169-BJ China Unicom Beijing Provin 38197 1493 92 275 SUNHK-DATA-AS-AP Sun Network (Hong Kong 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 3503 2965 144 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 18566 2195 405 110 MEGAPATH5-US - MegaPath Corporation, US 6389 2182 3671 41 BELLSOUTH-NET-BLK - BellSouth.net Inc., 20115 1931 1952 409 CHARTER-NET-HKY-NC - Charter Communicat 30036 1715 342 385 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 209 1708 5083 651 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 6983 1687 849 228 ITCDELTA - Earthlink, Inc., US 7018 1347 20075 1001 ATT-INTERNET4 - AT&T Services, Inc., US 11492 1339 239 558 CABLEONE - CABLE ONE, INC., US 16509 1332 2474 423 AMAZON-02 - Amazon.com, Inc., US 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 3329 169 15 ALJAWWALSTC-AS , SA 20940 2724 1054 1932 AKAMAI-ASN1 , US 34984 1974 327 358 TELLCOM-AS , TR 12479 1290 1002 46 UNI2-AS , ES 8551 1244 377 46 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 6849 1148 355 21 UKRTELNET , UA 13188 1074 97 86 BANKINFORM-AS , UA 8402 1032 544 15 CORBINA-AS Russia, RU 31148 1017 47 44 FREENET-AS , UA 6830 883 2752 462 LGI-UPC formerly known as UPC Broadband 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 3479 543 124 Telmex Colombia S.A., CO 8151 2265 3366 553 Uninet S.A. de C.V., MX 7303 1531 949 241 Telecom Argentina S.A., AR 11830 1493 369 66 Instituto Costarricense de Electricidad 6503 1418 437 54 Axtel, S.A.B. de C.V., MX 6147 1103 377 27 Telefonica del Peru S.A.A., PE 3816 998 478 181 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 7738 994 1882 40 Telemar Norte Leste S.A., BR 28573 910 2180 158 CLARO S.A., BR 11172 907 125 76 Alestra, S. de R.L. de C.V., MX 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 1163 402 48 LINKdotNET-AS, EG 36903 656 330 109 MT-MPLS, MA 37611 648 48 2 Afrihost, ZA 36992 537 1357 26 ETISALAT-MISR, EG 8452 504 1472 15 TE-AS TE-AS, EG 37492 373 234 68 ORANGE-TN, TN 24835 330 594 15 RAYA-AS, EG 29571 299 37 12 CITelecom-AS, CI 15399 289 35 6 WANANCHI-KE, KE 2018 264 327 73 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 5560 4191 75 ERX-CERNET-BKB China Education and Rese 22773 3503 2965 144 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 10620 3479 543 124 Telmex Colombia S.A., CO 7545 3425 384 253 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3329 169 15 ALJAWWALSTC-AS , SA 4766 3177 11145 1126 KIXS-AS-KR Korea Telecom, KR 17974 2935 904 78 TELKOMNET-AS2-AP PT Telekomunikasi Indo 20940 2724 1054 1932 AKAMAI-ASN1 , US 9829 2564 1487 522 BSNL-NIB National Internet Backbone, IN 1659 2493 1466 38 ERX-TANET-ASN1 Taiwan Academic Network 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 3503 3359 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 10620 3479 3355 Telmex Colombia S.A., CO 39891 3329 3314 ALJAWWALSTC-AS , SA 7545 3425 3172 TPG-INTERNET-AP TPG Telecom Limited, AU 17974 2935 2857 TELKOMNET-AS2-AP PT Telekomunikasi Indo 1659 2493 2455 ERX-TANET-ASN1 Taiwan Academic Network 6389 2182 2141 BELLSOUTH-NET-BLK - BellSouth.net Inc., 9808 2160 2120 CMNET-GD Guangdong Mobile Communication 18566 2195 2085 MEGAPATH5-US - MegaPath Corporation, US 4766 3177 2051 KIXS-AS-KR Korea Telecom, KR Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 65001 PRIVATE 5.143.176.0/20 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.192.0/20 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.192.0/21 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.200.0/21 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.208.0/21 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.216.0/21 15468 KLGELECS-AS 38, Teatralnaya st 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 65412 PRIVATE 41.89.7.0/24 36866 JTL, KE 65512 PRIVATE 45.252.244.0/24 45899 VNPT-AS-VN VNPT Corp, VN Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 23.249.144.0/20 40430 COLO4JAX-AS - colo4jax, LLC, US 27.100.7.0/24 56096 UNKNOWN 41.73.1.0/24 37004 -Reserved AS-, ZZ 41.73.2.0/24 37004 -Reserved AS-, ZZ 41.73.3.0/24 37004 -Reserved AS-, ZZ 41.73.4.0/24 37004 -Reserved AS-, ZZ 41.73.5.0/24 37004 -Reserved AS-, ZZ 41.73.6.0/24 37004 -Reserved AS-, ZZ 41.73.7.0/24 37004 -Reserved AS-, ZZ 41.73.8.0/24 37004 -Reserved AS-, ZZ 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:16 /9:13 /10:36 /11:100 /12:266 /13:518 /14:1049 /15:1766 /16:13169 /17:7816 /18:12749 /19:25323 /20:38278 /21:40173 /22:67117 /23:58796 /24:336973 /25:564 /26:587 /27:377 /28:49 /29:32 /30:16 /31:1 /32:33 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 39891 2896 3329 ALJAWWALSTC-AS , SA 22773 2732 3503 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 18566 2087 2195 MEGAPATH5-US - MegaPath Corporation, US 30036 1530 1715 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 6389 1414 2182 BELLSOUTH-NET-BLK - BellSouth.net Inc., 10620 1383 3479 Telmex Colombia S.A., CO 6983 1339 1687 ITCDELTA - Earthlink, Inc., US 34984 1257 1974 TELLCOM-AS , TR 11492 1235 1339 CABLEONE - CABLE ONE, INC., US 6849 968 1148 UKRTELNET , UA Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1577 2:747 4:21 5:2137 6:31 8:969 12:1779 13:43 14:1720 15:44 16:2 17:88 18:114 20:49 22:1 23:1635 24:1795 27:2293 31:1781 32:67 33:3 34:2 35:5 36:315 37:2271 38:1248 39:35 40:94 41:2959 42:457 43:1797 44:43 45:2079 46:2528 47:82 49:1159 50:902 51:12 52:517 54:340 55:9 56:7 57:42 58:1605 59:944 60:351 61:1815 62:1504 63:1929 64:4522 65:2177 66:4257 67:2201 68:1113 69:3286 70:1251 71:484 72:2027 74:2543 75:343 76:382 77:1427 78:1270 79:877 80:1244 81:1385 82:973 83:718 84:851 85:1606 86:486 87:1100 88:551 89:2098 90:211 91:6066 92:977 93:2397 94:2407 95:2501 96:513 97:370 98:945 99:41 100:76 101:1088 103:11639 104:2539 105:128 106:430 107:1410 108:663 109:2230 110:1286 111:1632 112:1037 113:1116 114:1089 115:1659 116:1614 117:1531 118:1988 119:1608 120:1260 121:1153 122:2189 123:2040 124:1589 125:1780 128:677 129:410 130:410 131:1339 132:619 133:175 134:466 135:139 136:382 137:394 138:1768 139:299 140:712 141:451 142:649 143:907 144:719 145:163 146:888 147:651 148:1383 149:534 150:659 151:1024 152:634 153:303 154:655 155:959 156:515 157:484 158:383 159:1137 160:513 161:720 162:2358 163:919 164:895 165:1061 166:318 167:1165 168:1961 169:669 170:1785 171:262 172:608 173:1638 174:752 175:743 176:1729 177:4109 178:2190 179:1140 180:2125 181:1812 182:1962 183:917 184:832 185:6991 186:3022 187:2086 188:2188 189:1749 190:7810 191:1277 192:9052 193:5730 194:4436 195:3830 196:1705 197:1136 198:5559 199:5739 200:7066 201:3771 202:10110 203:10075 204:4508 205:2723 206:2983 207:3102 208:4094 209:3872 210:4265 211:2041 212:2702 213:2326 214:869 215:70 216:5846 217:1982 218:800 219:623 220:1634 221:866 222:680 223:1263 End of report

1 0

Re: MTU
by Saad Abdullah 22 Jul '16

22 Jul '16

Worth reading this on choosing MTU on transit link. http://blog.apnic.net/2014/12/15/ip-mtu-and-tcp-mss-missmatch-an-evil-for-n… -Sad >> >> On Fri, Jul 22, 2016 at 10:01 PM, Baldur Norddahl < >> baldur.norddahl(a)gmail.com> wrote: >> >>> Hi >>> >>> What is best practice regarding choosing MTU on transit links? >>> >>> Until now we have used the default of 1500 bytes. I now have a project >>> were >>> we peer directly with another small ISP. However we need a backup so we >>> figured a GRE tunnel on a common IP transit carrier would work. We want >>> to >>> avoid the troubles you get by having an effective MTU smaller than 1500 >>> inside the tunnel, so the IP transit carrier agreed to configure a MTU of >>> 9216. >>> >>> Obviously I only need to increase my MTU by the size of the GRE header. >>> But >>> I am thinking is there any reason not to go all in and ask every peer to >>> go >>> to whatever max MTU they can support? My own equipment will do MTU of >>> 9600 >>> bytes. >>> >>> On the other hand, none of my customers will see any actual difference >>> because they are end users with CPE equipment that expects a 1500 byte >>> MTU. >>> Trying to deliver jumbo frames to the end users is probably going to end >>> badly. >>> >>> Regards, >>> >>> Baldur >>> >> >> >

1 0

Fwd: [ PRIVACY Forum ] Critical bug threatens to bite mobile phones and networks
by Jay R. Ashworth 20 Jul '16

20 Jul '16

Heap overflow bug in either a widely used ASN.1 library from Objective Systems, apparently popular with cell-radio industry people. Not sure if this will leak over into NANOG land -- but neither are you, and that's most of my point. DO *you* know if this library is used in your routers? Can you find out? How easily and quickly? Cheers, -- jra ----- Forwarded Message ----- > From: "PRIVACY Forum mailing list" <privacy(a)vortex.com> > To: privacy-list(a)vortex.com > Sent: Tuesday, July 19, 2016 7:12:47 PM > Subject: [ PRIVACY Forum ] Critical bug threatens to bite mobile phones and networks > Critical bug threatens to bite mobile phones and networks > > http://arstechnica.com/security/2016/07/software-flaw-puts-mobile-phones-an… > > A newly disclosed vulnerability could allow attackers to seize > control of mobile phones and key parts of the world's > telecommunications infrastructure and make it possible to > eavesdrop or disrupt entire networks, security experts warned > Tuesday. The bug resides in a code library used in a wide > range of telecommunication products, including radios in cell > towers, routers, and switches, as well as the baseband chips > in individual phones. Although exploiting the heap overflow > vulnerability would require great skill and resources, > attackers who managed to succeed would have the ability to > execute malicious code on virtually all of those devices. The > code library was developed by Pennsylvania-based Objective > Systems and is used to implement a telephony standard known as > ASN.1, short for Abstract Syntax Notation One. > > - - - > > --Lauren-- > Lauren Weinstein (lauren(a)vortex.com) http://www.vortex.com/lauren > Founder: > - Network Neutrality Squad: http://www.nnsquad.org > - PRIVACY Forum: http://www.vortex.com/privacy-info > Co-Founder: People For Internet Responsibility: http://www.pfir.org/pfir-info > Member: ACM Committee on Computers and Public Policy > Lauren's Blog: http://lauren.vortex.com > Google+: http://google.com/+LaurenWeinstein > Twitter: http://twitter.com/laurenweinstein > Tel: +1 (818) 225-2800 / Skype: vortex.com > I have consulted to Google, but I am not currently > doing so -- my opinions expressed here are mine alone. > _______________________________________________ > privacy mailing list > http://lists.vortex.com/mailman/listinfo/privacy -- Jay R. Ashworth Baylink jra(a)baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274

3 2

Re: [apops] BGP Update Report
by Martin Hannigan 19 Jul '16

19 Jul '16

On Fri, Jul 15, 2016 at 6:00 PM, <cidr-report(a)potaroo.net> wrote: > 15 - 104.111.200.0/21 6948 0.2% AS16625 -- AKAMAI-AS - Akamai Technologies, Inc., US > AS20940 -- AKAMAI-ASN1 , US This has been addressed. Appreciated Potaroo Team. Best, -M<

1 0

Re: akamai abnormal spike
by Clayton Zekelman 19 Jul '16

19 Jul '16

We noticed on the 12th and 13th there was a significant up tick in traffic served from our Akamai servers as well. At 05:37 PM 13/07/2016, eric c wrote: >Good afternoon, > >Has anyone notice any abnormal spike in Akamai trafic in the last 24-48 >hours compared to other days. I know it was black tuesday yesterday but >traffic from last month didn't even come close to what we saw from Akamai. > >We have some caching servers and even notice a spike to them as well. > >Limelight even showed up on our network. > >thanks >eric -- Clayton Zekelman Managed Network Systems Inc. (MNSi) 3363 Tecumseh Rd. E Windsor, Ontario N8W 1H4 tel. 519-985-8410 fax. 519-985-8409

4 3