May 2016 - Test - lists.nanog.org

IPv6 Residential Deployment Survey
by JORDI PALET MARTINEZ 22 May '16

22 May '16

Definitively, please respond to the survey. The point here is to be able to tell the ISPs, “hey why are you using /64 instead of /48 (or /56). You know that with /64, your customers can’t have different subnets in their network, for example an /64 in the SSID for guest, or different /64 for the home office and the kids ? You know that homenet will not work if you provide something smaller than /56 ? You know that only x% of ISP are using /64“, etc. … Ideally the survey should be responded by the ISPs, but we know that many of them (even if they don’t need to provide personal data) will not do it, so customers are able to respond as well. We will then manually try to avoid duplicate data from the same ISP, to avoid having a distorsion in the stats, or clarify the data if there are inconsistencies, etc. At the moment we got 225 responses (57 complete), most of them right now from RIPE NCC. Some people is not filling the “complete” survey, they can come back later to complete it and click “submit”, otherwise, we will manually “close” the incomplete surveys and account only for the fields that have been submitted. Hopefully this community can help to increase the responses from ARIN members ! Thanks a lot ! Regards, Jordi > On May 22, 2016, at 9:04 AM, Majdi S. Abbas <msa at latt.net> wrote: > > On Sun, May 22, 2016 at 04:32:11AM +0000, John Curran wrote: >> NANOGers - >> >> If you are providing residential Internet service with IPv6 (or >> are a customer of same), please take a moment to complete >> Jordi’s survey - this will help provide insight into the actual >> technical practices being used in residential IPv6 deployment. > > John, > > Allow me to suggest an additional survey: > > If you're a customer of a provider that currently provides > IPv6, and are not using it, please tell us why. > > In my case, on my consumer connection at home, I cannot utilize > IPv6 because my provider does not wish to provide more than a /64 to > a subscriber, and my equipment vendor (Juniper) does not support DHCPv6 > PD delegation hints, so I'll always get a /64 that does not scale well > to the >1 subnet I have internally. (4: Managment, Media, Guest, & > Internal.) Majdi - You should definitely complete the survey accordingly… that’s the kind of technical feedback that I believe Jordi is trying to collect! /John

1 0

Weekly Routing Table Report
by Routing Analysis Role Account 20 May '16

20 May '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 21 May, 2016 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 593812 Prefixes after maximum aggregation (per Origin AS): 217438 Deaggregation factor: 2.73 Unique aggregates announced (without unneeded subnets): 291167 Total ASes present in the Internet Routing Table: 53819 Prefixes per ASN: 11.03 Origin-only ASes present in the Internet Routing Table: 36588 Origin ASes announcing only one prefix: 15681 Transit ASes present in the Internet Routing Table: 6448 Transit-only ASes present in the Internet Routing Table: 168 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 39 Max AS path prepend of ASN ( 55644) 31 Prefixes from unregistered ASNs in the Routing Table: 960 Unregistered ASNs in the Routing Table: 360 Number of 32-bit ASNs allocated by the RIRs: 13944 Number of 32-bit ASNs visible in the Routing Table: 10783 Prefixes from 32-bit ASNs in the Routing Table: 42394 Number of bogon 32-bit ASNs visible in the Routing Table: 28 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 383 Number of addresses announced to Internet: 2810367044 Equivalent to 167 /8s, 130 /16s and 204 /24s Percentage of available address space announced: 75.9 Percentage of allocated address space announced: 75.9 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 98.1 Total number of prefixes smaller than registry allocations: 193857 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 151956 Total APNIC prefixes after maximum aggregation: 42399 APNIC Deaggregation factor: 3.58 Prefixes being announced from the APNIC address blocks: 163075 Unique aggregates announced from the APNIC address blocks: 66721 APNIC Region origin ASes present in the Internet Routing Table: 5180 APNIC Prefixes per ASN: 31.48 APNIC Region origin ASes announcing only one prefix: 1179 APNIC Region transit ASes present in the Internet Routing Table: 916 Average APNIC Region AS path length visible: 4.4 Max APNIC Region AS path length visible: 39 Number of APNIC region 32-bit ASNs visible in the Routing Table: 2087 Number of APNIC addresses announced to Internet: 754229060 Equivalent to 44 /8s, 244 /16s and 159 /24s Percentage of available APNIC address space announced: 88.1 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, 131072-135580 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: 180969 Total ARIN prefixes after maximum aggregation: 89100 ARIN Deaggregation factor: 2.03 Prefixes being announced from the ARIN address blocks: 186372 Unique aggregates announced from the ARIN address blocks: 88141 ARIN Region origin ASes present in the Internet Routing Table: 16361 ARIN Prefixes per ASN: 11.39 ARIN Region origin ASes announcing only one prefix: 5842 ARIN Region transit ASes present in the Internet Routing Table: 1716 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: 1221 Number of ARIN addresses announced to Internet: 1101448512 Equivalent to 65 /8s, 166 /16s and 197 /24s Percentage of available ARIN address space announced: 58.3 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: 142433 Total RIPE prefixes after maximum aggregation: 70409 RIPE Deaggregation factor: 2.02 Prefixes being announced from the RIPE address blocks: 151690 Unique aggregates announced from the RIPE address blocks: 94010 RIPE Region origin ASes present in the Internet Routing Table: 18083 RIPE Prefixes per ASN: 8.39 RIPE Region origin ASes announcing only one prefix: 7903 RIPE Region transit ASes present in the Internet Routing Table: 3012 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 36 Number of RIPE region 32-bit ASNs visible in the Routing Table: 4773 Number of RIPE addresses announced to Internet: 704402560 Equivalent to 41 /8s, 252 /16s and 84 /24s Percentage of available RIPE address space announced: 102.4 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: 61841 Total LACNIC prefixes after maximum aggregation: 12235 LACNIC Deaggregation factor: 5.05 Prefixes being announced from the LACNIC address blocks: 76253 Unique aggregates announced from the LACNIC address blocks: 36154 LACNIC Region origin ASes present in the Internet Routing Table: 2482 LACNIC Prefixes per ASN: 30.72 LACNIC Region origin ASes announcing only one prefix: 577 LACNIC Region transit ASes present in the Internet Routing Table: 570 Average LACNIC Region AS path length visible: 4.7 Max LACNIC Region AS path length visible: 23 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 2493 Number of LACNIC addresses announced to Internet: 171197760 Equivalent to 10 /8s, 52 /16s and 69 /24s Percentage of available LACNIC address space announced: 102.0 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: 14112 Total AfriNIC prefixes after maximum aggregation: 3258 AfriNIC Deaggregation factor: 4.33 Prefixes being announced from the AfriNIC address blocks: 16039 Unique aggregates announced from the AfriNIC address blocks: 5798 AfriNIC Region origin ASes present in the Internet Routing Table: 737 AfriNIC Prefixes per ASN: 21.76 AfriNIC Region origin ASes announcing only one prefix: 180 AfriNIC Region transit ASes present in the Internet Routing Table: 169 Average AfriNIC Region AS path length visible: 4.7 Max AfriNIC Region AS path length visible: 26 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 209 Number of AfriNIC addresses announced to Internet: 78707968 Equivalent to 4 /8s, 176 /16s and 253 /24s Percentage of available AfriNIC address space announced: 78.2 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 5556 4192 76 China Education and Research 7545 3334 356 220 TPG Telecom Limited 4766 3170 11144 1123 Korea Telecom 17974 2946 914 96 PT Telekomunikasi Indonesia 9829 2459 1467 464 National Internet Backbone 4755 2096 432 243 TATA Communications formerly 9808 1940 8717 30 Guangdong Mobile Communicatio 4808 1659 2299 549 CNCGROUP IP network China169 9583 1513 122 558 Sify Limited 38197 1497 93 215 Sun Network (Hong Kong) Limit 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 3242 2947 138 Cox Communications Inc. 6389 2299 3671 41 BellSouth.net Inc. 18566 2195 394 275 MegaPath Corporation 20115 1921 1937 404 Charter Communications 30036 1696 337 401 Mediacom Communications Corp 6983 1689 849 232 EarthLink, Inc. 209 1669 4968 770 Qwest Communications Company, 4323 1517 985 376 tw telecom holdings, inc. 701 1296 10718 704 MCI Communications Services, 11492 1290 236 586 CABLE ONE, INC. 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 2901 151 11 SaudiNet, Saudi Telecom Compa 20940 2557 985 1837 Akamai International B.V. 34984 1965 326 358 TELLCOM ILETISIM HIZMETLERI A 12479 1221 997 83 France Telecom Espana SA 8551 1203 376 55 Bezeq International-Ltd 6849 1148 355 21 JSC "Ukrtelecom" 13188 1078 98 65 TOV "Bank-Inform" 8402 1065 544 15 OJSC "Vimpelcom" 31148 1027 47 45 Freenet Ltd. 6830 890 2719 463 Liberty Global Operations B.V 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 3477 541 152 Telmex Colombia S.A. 8151 2259 3411 563 Uninet S.A. de C.V. 7303 1510 940 234 Telecom Argentina S.A. 6503 1477 437 55 Axtel, S.A.B. de C.V. 11830 1477 368 52 Instituto Costarricense de El 6147 1160 377 27 Telefonica del Peru S.A.A. 26615 1005 2325 34 Tim Celular S.A. 3816 999 478 186 COLOMBIA TELECOMUNICACIONES S 7738 994 1882 40 Telemar Norte Leste S.A. 11172 907 125 77 Alestra, S. de R.L. de C.V. 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 1082 402 44 Link Egypt (Link.NET) 37611 650 48 2 Afrihost-Brevis Computer Serv 36903 626 315 103 Office National des Postes et 36992 509 1359 27 ETISALAT MISR 8452 490 1472 15 TE-AS 37492 395 234 68 Orange Tunisie 29571 301 37 13 Cote d'Ivoire Telecom 24835 294 466 14 Vodafone Data 15399 284 35 10 Wananchi Group (Kenya) Limite 2018 257 327 74 TENET (The UNINET Project) 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 5556 4192 76 China Education and Research 10620 3477 541 152 Telmex Colombia S.A. 7545 3334 356 220 TPG Telecom Limited 22773 3242 2947 138 Cox Communications Inc. 4766 3170 11144 1123 Korea Telecom 17974 2946 914 96 PT Telekomunikasi Indonesia 39891 2901 151 11 SaudiNet, Saudi Telecom Compa 20940 2557 985 1837 Akamai International B.V. 9829 2459 1467 464 National Internet Backbone 6389 2299 3671 41 BellSouth.net Inc. Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 10620 3477 3325 Telmex Colombia S.A. 7545 3334 3114 TPG Telecom Limited 22773 3242 3104 Cox Communications Inc. 39891 2901 2890 SaudiNet, Saudi Telecom Compa 17974 2946 2850 PT Telekomunikasi Indonesia 6389 2299 2258 BellSouth.net Inc. 4766 3170 2047 Korea Telecom 9829 2459 1995 National Internet Backbone 18566 2195 1920 MegaPath Corporation 9808 1940 1910 Guangdong Mobile Communicatio 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 OJSC Rostelecom 30662 UNALLOCATED 8.2.129.0/24 3356 Level 3 Communicatio 53506 UNALLOCATED 8.17.102.0/23 3356 Level 3 Communicatio 46467 UNALLOCATED 8.19.192.0/24 46887 Lightower Fiber Netw 16589 UNALLOCATED 8.20.247.0/24 35838 CCANET Limited 16589 UNALLOCATED 8.26.56.0/24 35838 CCANET Limited 46473 UNALLOCATED 8.27.122.0/24 3356 Level 3 Communicatio 46473 UNALLOCATED 8.27.124.0/24 3356 Level 3 Communicatio 27205 UNALLOCATED 8.38.16.0/21 3356 Level 3 Communicatio 27205 UNALLOCATED 8.38.20.0/24 32787 Prolexic Technologie Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 23.226.112.0/20 62788 >>UNKNOWN<< 23.249.144.0/20 40430 colo4jax, LLC 27.100.7.0/24 56096 >>UNKNOWN<< 41.73.1.0/24 37004 >>UNKNOWN<< 41.73.2.0/24 37004 >>UNKNOWN<< 41.73.3.0/24 37004 >>UNKNOWN<< 41.73.4.0/24 37004 >>UNKNOWN<< 41.73.5.0/24 37004 >>UNKNOWN<< 41.73.6.0/24 37004 >>UNKNOWN<< 41.73.7.0/24 37004 >>UNKNOWN<< 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:101 /12:266 /13:511 /14:1035 /15:1761 /16:13039 /17:7614 /18:12699 /19:25925 /20:37931 /21:39674 /22:65485 /23:57409 /24:328597 /25:556 /26:598 /27:420 /28:46 /29:33 /30:14 /31:1 /32:32 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 39891 2664 2901 SaudiNet, Saudi Telecom Compa 22773 2471 3242 Cox Communications Inc. 18566 2097 2195 MegaPath Corporation 30036 1511 1696 Mediacom Communications Corp 6389 1477 2299 BellSouth.net Inc. 10620 1373 3477 Telmex Colombia S.A. 6983 1338 1689 EarthLink, Inc. 34984 1249 1965 TELLCOM ILETISIM HIZMETLERI A 11492 1193 1290 CABLE ONE, INC. 6849 968 1148 JSC "Ukrtelecom" Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1584 2:746 4:20 5:2066 6:31 8:958 12:1781 13:39 14:1695 15:45 16:2 17:84 18:90 20:48 22:1 23:1495 24:1775 27:2278 31:1771 32:59 33:2 34:2 35:5 36:287 37:2305 38:1219 39:25 40:91 41:2867 42:395 43:1738 44:43 45:1896 46:2494 47:77 49:1174 50:868 51:33 52:188 54:329 55:5 56:7 57:42 58:1538 59:874 60:343 61:1825 62:1509 63:1922 64:4452 65:2164 66:4248 67:2153 68:1089 69:3291 70:1103 71:476 72:1989 74:2547 75:344 76:345 77:1382 78:1248 79:820 80:1276 81:1338 82:945 83:700 84:824 85:1611 86:473 87:1086 88:561 89:1993 90:174 91:6047 92:896 93:2331 94:2332 95:2309 96:486 97:359 98:935 99:46 100:75 101:1047 103:10824 104:2415 105:124 106:400 107:1175 108:671 109:2191 110:1256 111:1651 112:1006 113:1143 114:1052 115:1615 116:1578 117:1429 118:2054 119:1624 120:934 121:1178 122:2177 123:2009 124:1569 125:1726 128:719 129:419 130:412 131:1326 132:622 133:176 134:454 135:127 136:374 137:353 138:1709 139:277 140:543 141:458 142:638 143:939 144:688 145:160 146:873 147:608 148:1481 149:508 150:649 151:882 152:618 153:281 154:623 155:938 156:499 157:432 158:337 159:1119 160:484 161:709 162:2322 163:546 164:900 165:1047 166:320 167:1148 168:1849 169:660 170:1578 171:263 172:561 173:1638 174:743 175:723 176:1740 177:3986 178:2208 179:1137 180:2060 181:1789 182:1850 183:951 184:800 185:6434 186:2990 187:2119 188:2125 189:1708 190:7749 191:1238 192:8937 193:5740 194:4389 195:3770 196:1710 197:1073 198:5549 199:5699 200:7010 201:3766 202:10115 203:9645 204:4511 205:2732 206:2981 207:3120 208:4049 209:3861 210:3877 211:2053 212:2696 213:2232 214:856 215:70 216:5782 217:1947 218:797 219:607 220:1683 221:869 222:665 223:1222 End of report

1 0

RE: Need BGP route check (UPDATE)
by Matthew Huff 20 May '16

20 May '16

>From responses I received, I have gotten a number of different answers. Some are seeing our routes from 6128, some from 46887 and a few from both. The response from Eric though was typical. Showing the IPv4 prefix only from AS6128, but the IPv6 from both 6128 & 46887. I am guessing that 46887 might be set with a community to not export our IPv4 prefixes except to direct peers? Anyone directly peered with 46887 that could see the community for 129.77.0.0/16 and verify? ---- Matthew Huff | 1 Manhattanville Rd Director of Operations | Purchase, NY 10577 OTA Management LLC | Phone: 914-460-4039 aim: matthewbhuff | Fax: 914-694-5669 > -----Original Message----- > From: Eric Tykwinski [mailto:eric-list@truenet.com] > Sent: Friday, May 20, 2016 11:48 AM > To: Matthew Huff <mhuff(a)ox.com> > Subject: RE: Need BGP route check > > Matt, > > show ip bgp 129.77.0.0/16 > BGP routing table entry for 129.77.0.0/16, version 161696687 > Paths: (2 available, best #2, table Default-IP-Routing-Table) > Advertised to update-groups: > 1 > 3356 6128 14607 > 4.59.140.65 from 4.59.140.65 (4.69.183.7) > Origin IGP, metric 0, localpref 100, valid, external > 174 6128 14607 > 38.104.114.73 from 38.104.114.73 (154.26.5.244) > Origin IGP, metric 105030, localpref 100, valid, external, best > Community: 174:21000 174:22013 > > show bgp ipv6 unicast 2620:0:2810::/48 > BGP routing table entry for 2620:0:2810::/48, version 18004880 > Paths: (2 available, best #1, table Global-IPv6-Table) > Advertised to update-groups: > 2 > 3356 6128 14607 > 2001:1900:2100::A2D (FE80::219:7FF:FEDD:2800) from > 2001:1900:2100::A2D > (4.69.183.7) > Origin IGP, metric 0, localpref 100, valid, external, best > Community: 3356:3 3356:22 3356:100 3356:123 3356:575 3356:2039 > 6128:3000 6128:3091 6128:4000 6128:5003 6128:5046 64600:4000 > 64600:65002 > 174 46887 14607 14607 > 2001:550:2:4::B:1 (FE80::D66D:50FF:FE5E:1D3) from 2001:550:2:4::B:1 > (154.26.5.244) > Origin IGP, metric 105030, localpref 100, valid, external > Community: 174:21001 174:22013 > > Sincerely, > > Eric Tykwinski > TrueNet, Inc. > P: 610-429-8300 > > > -----Original Message----- > From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of Matthew Huff > Sent: Friday, May 20, 2016 11:32 AM > To: nanog(a)nanog.org > Subject: Need BGP route check > > One of our upstreams is apparently having problems, although they don't > appear to know about it. I've seen an alert at BGPmon.net about our > prefixes > being withdrawn, and I can't locate our prefixes through that provider > on > any routeviews. Can someone check to see what ASPATHS you are seeing > for our > prefixes? > > 129.77.0.0/16 > 2620:0:2810::/48 > > We should be advertised via AS6128 and AS46887 > > ---- > Matthew Huff | 1 Manhattanville Rd Director of > Operations | > Purchase, NY 10577 OTA Management LLC | Phone: 914-460-4039 > aim: matthewbhuff | Fax: 914-694-5669 > > >

2 1

Need BGP route check
by Matthew Huff 20 May '16

20 May '16

One of our upstreams is apparently having problems, although they don't appear to know about it. I've seen an alert at BGPmon.net about our prefixes being withdrawn, and I can't locate our prefixes through that provider on any routeviews. Can someone check to see what ASPATHS you are seeing for our prefixes? 129.77.0.0/16 2620:0:2810::/48 We should be advertised via AS6128 and AS46887 ---- Matthew Huff | 1 Manhattanville Rd Director of Operations | Purchase, NY 10577 OTA Management LLC | Phone: 914-460-4039 aim: matthewbhuff | Fax: 914-694-5669

4 3

Re: NANOG Digest, Vol 100, Issue 19
by Arthur Liew 20 May '16

20 May '16

Hi Guys, Just wondering if anyone knows equivalent of bgp.he.net for GRX/IPX world? Any good mailing list around targeting GRX/IPX? Thanks ! Rgds Arthur

1 0

Frontier Rep
by Chris McDonald 19 May '16

19 May '16

Could a frontier rep hit me up offlist for an on-net check? thanks chris

1 0

mail delivery delayed to gmail/gmail hosted domains
by Mathias Zimmermann 18 May '16

18 May '16

Dear Nanog'er, Since about 4 weeks or more we experience a mail delivery delay (always between 03:09 and 03:10) to gmail.com and gmail hosted domains. We already filled out the "delivery problem report" but never heard something from them. Are there any specs from google which explains when they delay mail acceptance? We are not listed in any blocklists and the SPF, PTR record is correctly set. Any ideas? Regards, Mathias

1 0

B5-Lite
by Jared Mauch 17 May '16

17 May '16

Anyone deployed this radio in production in the US? I’m curious to hear from people who are using it, looking at replacing some UBNT hardware with it on some PTP links, going from the M-series class devices to something more modern. Thanks, - Jared

10 17

Comcast DNS Contact
by rwebb＠ropeguru.com 17 May '16

17 May '16

Can one of the Comcast DNS guru's contact me reference an issue with a .gov resolution? Robert

2 3

Perspectives about customer M/A/C in triple play environments
by Jason Lixfeld 16 May '16

16 May '16

Hello, I think it’s fair to say that most broadband/FTTx customers don’t have to think very much or need to have a very high degree of understanding if they want to move their wired Internet device from one room or another in their house. Maybe to keep things simple, let’s assume that we’re talking about a relatively modern MDU unit where a customer has some sort of provider CPE in their in-suite telecom demark closet/box/what have you with some number of switched 'LAN’ ports on it, and each of those LAN ports would be wired to a wall jack somewhere. Mr. or Ms. User can move their Internet device anywhere there is a wall jack and Bob’s your uncle. My question is around how this landscape changes in triple play environments. As I understand it, most triple play deployments separate (in some cases VoIP,) TV and Internet traffic onto VLANs (Internet would be presented to the customer untagged). The CPE would then allow the ISP to switch the video traffic onto a coax port, or maybe onto the CPE’s embedded switch, or maybe both. For the sake of argument, let’s assume the provider is supplying an Ethernet based set-top-box, so customer should be able to connect the STB to any wall jack and it should just work. And they should be able to connect their provider supplied ATA to any wall jack, and it should just work. And they should be able to connect their Internet device to any wall jack and it should just work. Or should it? Are most CPEs that are provided by ISPs sophisticated enough to be able to put all service tags on all ports, and have those same ports act as untagged LAN ports as well? If not, how do providers deal with this? Do they dedicate one port for an IPTV STB? One port for an ATA (assuming no built-in POTS on the CPE)? And the rest of the ports for untagged Internet? What if the customer has 2+ TVs? Do they need to call in and have the provider remote in and provision another port for TV at the expense of some other service that might be running on that port already? Do they need to install a switch that does IGMP snooping? I feel like this all has the potential to become very complicated for the customer, and maybe the provider and their installers. To me, the customer should continue to be dumb and unassuming. They should be able to put whatever they want wherever they want and have it just work. Is that how things actually are in the real world or are customers and providers making silent sacrifices for the sake of all this new fangled technology?

4 3