[afnog] afnog Digest, Vol 138, Issue 4
malabow at gmail.com
malabow at gmail.com
Fri Sep 4 18:25:41 UTC 2015
I think v6 is over stated, v4 is not going anywhere and we as people are not ready E2E v6. We have been told years that v4 is ending and the world is just fine. Now regarding EoMPLS or any mpls, what is the the % of customers running in Africa, rather ISP having mpls enables network. My advice is prepare ur network v6, but don't lose over sleep.
Sent from my iPhone
> On Sep 4, 2015, at 2:02 PM, afnog-request at afnog.org wrote:
>
> Send afnog mailing list submissions to
> afnog at afnog.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://www.afnog.org/mailman/listinfo/afnog
> or, via email, send a message with subject or body 'help' to
> afnog-request at afnog.org
>
> You can reach the person managing the list at
> afnog-owner at afnog.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of afnog digest..."
>
>
> Today's Topics:
>
> 1. Re: Four Misconceptions About IPv4 to IPv6 Migration
> (Andrew Alston)
> 2. Re: Four Misconceptions About IPv4 to IPv6 Migration (Mark Tinka)
> 3. Weekly Routing Table Report (Routing Analysis Role Account)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 4 Sep 2015 12:26:29 +0000
> From: Andrew Alston <Andrew.Alston at liquidtelecom.com>
> To: Mark Tinka <mark.tinka at seacom.mu>, Nabil Badri
> <shenzen.shen at gmail.com>, "afnog at afnog.org" <afnog at afnog.org>
> Subject: Re: [afnog] Four Misconceptions About IPv4 to IPv6 Migration
> Message-ID:
> <AMSPR03MB5341535D08DB2D9FB2F26EDEE570 at AMSPR03MB534.eurprd03.prod.outlook.com>
>
> Content-Type: text/plain; charset="windows-1252"
>
> HI Mark,
>
> I think this is a matter of terminology or definition though. The moment you are running v6 over EoMPLS, or v6 over VPLS, at the moment you *ARE* running v6 over v4, because the MPLS is built between v4 end points. Yes, technically you can argue its just a matter of the way the traffic is switched, I argue that it is still on top of v4.
>
> I also would hardly call EoMPLS / VPLS specific use case scenarios, they are INCREDIBLY heavily used. I point out that even LINX is running on a VPLS network, and TECHNICALLY the native v6 between members is therefore being carried with a v4 backend, because the VPLS is v4 end point based.
>
> Agreed, this shouldn't stop the rollout of v6, but if we want TRUE native v6 everywhere, we have to remove the reliance on v4 entirely, and that is still there. This is ENTIRELY the fault of vendors, and it has to change.
>
> Andrew
>
>
> From: Mark Tinka [mailto:mark.tinka at seacom.mu]
> Sent: 04 September 2015 14:18
> To: Andrew Alston <Andrew.Alston at liquidtelecom.com>; Nabil Badri <shenzen.shen at gmail.com>; afnog at afnog.org
> Subject: Re: [afnog] Four Misconceptions About IPv4 to IPv6 Migration
>
>
> On 4/Sep/15 13:04, Andrew Alston wrote:
>
> V6 is coming, there is no doubt about it. If we don't deploy it, we're gonna be in trouble. NAT is not a sustainable solution, never has been, never will be, and the world is running out of v4. But until there is what I refer to as protocol parity, the deployment will be hampered, and that protocol parity is still (sadly) very very far away. Right now, no matter how much you want to, you still have to build your v6 in a provider environment ON TOP of your v4, and you have to be VERY careful with your hardware purchasing decisions if you wish to avoid a situation where you will be stuck in this scenario for the long haul.
>
> (Please don't mistake what I am saying by the way, such things should not stop the deployment of V6 totally, and if you have to build v6 on top of v4 right now, its in your interests to do so, and that is what my employer has done, I am merely stating that it would make the case so much stronger if the protocols actually had parity in the functionality)
>
> I don't think it is necessary to lay IPv6 over IPv4, unless you're providing 6-in-4 services or some such.
>
> We run native IPv6 across the board, and they pretty much run ships in the night. IPv4 does what it does, IPv6 does what it does. They don't intersect in any way.
>
> Agree that the lack of MPLS parity between IPv4 and IPv6 makes it difficult to do away with IPv4 entirely, but this is a specific use-case which goes above and beyond the basics of rolling out IPv6, IMHO.
>
> Mark.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://www.afnog.org/pipermail/afnog/attachments/20150904/0a9e9866/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 4 Sep 2015 15:18:14 +0200
> From: Mark Tinka <mark.tinka at seacom.mu>
> To: Andrew Alston <Andrew.Alston at liquidtelecom.com>, Nabil Badri
> <shenzen.shen at gmail.com>, "afnog at afnog.org" <afnog at afnog.org>
> Subject: Re: [afnog] Four Misconceptions About IPv4 to IPv6 Migration
> Message-ID: <55E99A16.5070707 at seacom.mu>
> Content-Type: text/plain; charset="windows-1252"
>
>
>
>> On 4/Sep/15 14:26, Andrew Alston wrote:
>>
>>
>>
>>
>> I think this is a matter of terminology or definition though. The
>> moment you are running v6 over EoMPLS, or v6 over VPLS, at the moment
>> you **ARE** running v6 over v4, because the MPLS is built between v4
>> end points. Yes, technically you can argue its just a matter of the
>> way the traffic is switched, I argue that it is still on top of v4.
>
> To be honest, at this point I don't really care, since MPLS is, well,
> multi-protocol. When we deliver services to customers over an MPLS
> construct, we don't care about the payload. It could be IPv4, it could
> be Ethernet, it could IPv6, it could be AppleTalk.
>
> That the MPLS construct is nailed up via IPv4 does not concern me so
> much (a lot of networks do not run MPLS). What mostly concerns me is, as
> a service provider, is tunneling IPv6 natively in IPv4.
>
>>
>>
>>
>>
>> Agreed, this shouldn?t stop the rollout of v6, but if we want TRUE
>> native v6 everywhere, we have to remove the reliance on v4 entirely,
>> and that is still there. This is ENTIRELY the fault of vendors, and it
>> has to change.
>
> So this is where I think striving for perfection may derail good. Is it
> really necessary to get rid of IPv4? I don't think so, to be honest.
>
> Even without the lack of MPLS parity, there are still a number of basic
> features in IPv4 that aren't available in IPv6 - simple things like
> RADIUS, TACACS+, NTP, e.t.c., are only starting to appear in code now.
> And since a lot of networks run older code to maintain stability, it
> will be a while before they can bring IPv6 into all the features they
> currently support, let alone the ones they want to support.
>
> Personally, I would not spend any time getting rid of IPv4. I will,
> however, continue to expend energy getting IPv6 everywhere, because the
> presence of IPv4 does not hinder this, really.
>
> Mark.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://www.afnog.org/pipermail/afnog/attachments/20150904/8046d1dd/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 5 Sep 2015 04:02:07 +1000 (AEST)
> From: Routing Analysis Role Account <cscora at apnic.net>
> To: apops at apops.net, nanog at nanog.org, routing-wg at ripe.net,
> afnog at afnog.org, sanog at sanog.org, pacnog at pacnog.org, safnog at safnog.org
> Subject: [afnog] Weekly Routing Table Report
> Message-ID: <201509041802.t84I276Z001927 at thyme.rand.apnic.net>
>
> 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,
> CaribNOG and the RIPE Routing Working Group.
>
> Daily listings are sent to bgp-stats at lists.apnic.net
>
> For historical data, please see http://thyme.rand.apnic.net.
>
> If you have any comments please contact Philip Smith <pfsinoz at gmail.com>.
>
> Routing Table Report 04:00 +10GMT Sat 05 Sep, 2015
>
> Report Website: http://thyme.rand.apnic.net
> Detailed Analysis: http://thyme.rand.apnic.net/current/
>
> Analysis Summary
> ----------------
>
> BGP routing table entries examined: 30167
> Prefixes after maximum aggregation (per Origin AS): 12174
> Deaggregation factor: 2.48
> Unique aggregates announced (without unneeded subnets): 10608
> Total ASes present in the Internet Routing Table: 4848
> Prefixes per ASN: 6.22
> Origin-only ASes present in the Internet Routing Table: 3304
> Origin ASes announcing only one prefix: 2007
> Transit ASes present in the Internet Routing Table: 1198
> Transit-only ASes present in the Internet Routing Table: 707
> Average AS path length visible in the Internet Routing Table: 4.3
> Max AS path length visible: 36
> Max AS path prepend of ASN ( 55644) 31
> Prefixes from unregistered ASNs in the Routing Table: 63
> Unregistered ASNs in the Routing Table: 45
> Number of 32-bit ASNs allocated by the RIRs: 10864
> Number of 32-bit ASNs visible in the Routing Table: 346
> Prefixes from 32-bit ASNs in the Routing Table: 854
> Number of bogon 32-bit ASNs visible in the Routing Table: 0
> Special use prefixes present in the Routing Table: 0
> Prefixes being announced from unallocated address space: 9
> Number of addresses announced to Internet: 258338464
> Equivalent to 15 /8s, 101 /16s and 238 /24s
> Percentage of available address space announced: 7.0
> Percentage of allocated address space announced: 7.0
> Percentage of available address space allocated: 100.0
> Percentage of address space in use by end-sites: 97.6
> Total number of prefixes smaller than registry allocations: 8184
>
> APNIC Region Analysis Summary
> -----------------------------
>
> Prefixes being announced by APNIC Region ASes: 8544
> Total APNIC prefixes after maximum aggregation: 1854
> APNIC Deaggregation factor: 4.61
> Prefixes being announced from the APNIC address blocks: 8266
> Unique aggregates announced from the APNIC address blocks: 3049
> APNIC Region origin ASes present in the Internet Routing Table: 501
> APNIC Prefixes per ASN: 16.50
> APNIC Region origin ASes announcing only one prefix: 125
> APNIC Region transit ASes present in the Internet Routing Table: 195
> Average APNIC Region AS path length visible: 4.6
> Max APNIC Region AS path length visible: 36
> Number of APNIC region 32-bit ASNs visible in the Routing Table: 27
> Number of APNIC addresses announced to Internet: 45189632
> Equivalent to 2 /8s, 177 /16s and 138 /24s
> Percentage of available APNIC address space announced: 5.3
>
> 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: 12219
> Total ARIN prefixes after maximum aggregation: 5908
> ARIN Deaggregation factor: 2.07
> Prefixes being announced from the ARIN address blocks: 13925
> Unique aggregates announced from the ARIN address blocks: 3821
> ARIN Region origin ASes present in the Internet Routing Table: 1960
> ARIN Prefixes per ASN: 7.10
> ARIN Region origin ASes announcing only one prefix: 1187
> ARIN Region transit ASes present in the Internet Routing Table: 355
> Average ARIN Region AS path length visible: 3.4
> Max ARIN Region AS path length visible: 27
> Number of ARIN region 32-bit ASNs visible in the Routing Table: 52
> Number of ARIN addresses announced to Internet: 168019744
> Equivalent to 10 /8s, 3 /16s and 199 /24s
> Percentage of available ARIN address space announced: 8.9
>
> 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-395164
> 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: 8462
> Total RIPE prefixes after maximum aggregation: 3532
> RIPE Deaggregation factor: 2.40
> Prefixes being announced from the RIPE address blocks: 7958
> Unique aggregates announced from the RIPE address blocks: 3730
> RIPE Region origin ASes present in the Internet Routing Table: 1307
> RIPE Prefixes per ASN: 6.09
> RIPE Region origin ASes announcing only one prefix: 688
> RIPE Region transit ASes present in the Internet Routing Table: 548
> Average RIPE Region AS path length visible: 5.1
> Max RIPE Region AS path length visible: 27
> Number of RIPE region 32-bit ASNs visible in the Routing Table: 265
> Number of RIPE addresses announced to Internet: 45053568
> Equivalent to 2 /8s, 175 /16s and 118 /24s
> Percentage of available RIPE address space announced: 6.5
>
> 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: 67
> Total LACNIC prefixes after maximum aggregation: 53
> LACNIC Deaggregation factor: 1.26
> Prefixes being announced from the LACNIC address blocks: 9
> Unique aggregates announced from the LACNIC address blocks: 1
> LACNIC Region origin ASes present in the Internet Routing Table: 16
> LACNIC Prefixes per ASN: 0.56
> LACNIC Region origin ASes announcing only one prefix: 5
> LACNIC Region transit ASes present in the Internet Routing Table: 16
> Average LACNIC Region AS path length visible: 3.9
> Max LACNIC Region AS path length visible: 8
> Number of LACNIC region 32-bit ASNs visible in the Routing Table: 2
> Number of LACNIC addresses announced to Internet: 65536
> Equivalent to 0 /8s, 1 /16s and 0 /24s
> Percentage of available LACNIC address space announced: 0.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: 16
> Total AfriNIC prefixes after maximum aggregation: 10
> AfriNIC Deaggregation factor: 1.60
> Prefixes being announced from the AfriNIC address blocks: 0
> Unique aggregates announced from the AfriNIC address blocks: 0
> AfriNIC Region origin ASes present in the Internet Routing Table: 6
> AfriNIC Prefixes per ASN: 0.00
> AfriNIC Region origin ASes announcing only one prefix: 2
> AfriNIC Region transit ASes present in the Internet Routing Table: 3
> Average AfriNIC Region AS path length visible: 3.9
> Max AfriNIC Region AS path length visible: 5
> Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 0
> Number of AfriNIC addresses announced to Internet: 0
> Equivalent to 0 /8s, 0 /16s and 0 /24s
> Percentage of available AfriNIC address space announced: 0.0
>
> 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
> 7545 979 99 7 TPG Telecom Limited
> 45528 578 31 32 Tikona Digital Networks Pvt L
> 7552 310 256 1 Viettel Corporation
> 9605 265 200 96 NTT DoCoMo, Inc.
> 24378 264 32 1 Total Access Communication PL
> 17488 247 61 37 Hathway IP Over Cable Interne
> 4755 223 64 2 TATA Communications formerly
> 45769 210 13 73 D-Vois Broadband Pvt Ltd
> 45899 198 259 24 VNNIC
> 17841 171 12 11 MIC E-GOVERNMENT
>
> 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
> 3356 1310 8207 19 Level 3 Communications, Inc.
> 16625 485 282 347 Akamai Technologies, Inc.
> 20115 390 350 96 Charter Communications
> 11492 382 42 205 CABLE ONE, INC.
> 2386 325 48 282 AT&T Data Communications Serv
> 714 284 4096 1 Apple Inc.
> 22773 259 170 15 Cox Communications Inc.
> 62823 255 16 10 Puerto Rico Cable Acquisition
> 15003 179 228 27 Nobis Technology Group, LLC
> 10796 167 214 86 Time Warner Cable Internet LL
>
> 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
> 20940 987 469 689 Akamai International B.V.
> 8402 514 64 1 OJSC "Vimpelcom"
> 39891 514 32 2 SaudiNet, Saudi Telecom Compa
> 9198 234 103 9 JSC Kazakhtelecom
> 48159 228 131 108 Telecommunication Infrastruct
> 3257 181 105 145 Tinet SpA
> 12586 133 42 6 GHOSTnet GmbH
> 51074 120 76 24 GOSTARESH-E-ERTEBATAT-E MABNA
> 44244 99 256 6 Iran Cell Service and Communi
> 35819 94 125 35 Bayanat Al-Oula For Network S
>
> Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-RIPE
>
> LACNIC Region per AS prefix count summary
> -----------------------------------------
>
> ASN No of nets /20 equiv MaxAgg Description
> 8151 11 8 11 Uninet S.A. de C.V.
> 10318 9 16 1 CABLEVISION S.A.
> 28573 9 5 7 NET Serviços de Comunicação S
> 18734 6 4 5 Operbes, S.A. de C.V.
> 27810 5 2 5 MERCANET LTDA
> 6057 4 2 4 Administracion Nacional de Te
> 10481 4 2 4 Prima S.A.
> 11271 4 2 4 BT Latam Brasil Ltda
> 14178 4 2 3 Megacable Comunicaciones de M
> 27814 4 2 3 Aeprovi
>
> 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
> 3741 4 1 1 Internet Solutions
> 5713 4 1 1 Telkom SA Ltd.
> 24835 4 2 4 Vodafone Data
> 37457 2 1 2 Telkom SA Ltd.
> 8452 1 1 1 TE-AS
> 37284 1 0 1 Aljeel Aljadeed For Technolog
>
> 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
> 3356 1310 8207 19 Level 3 Communications, Inc.
> 20940 987 469 689 Akamai International B.V.
> 7545 979 99 7 TPG Telecom Limited
> 45528 578 31 32 Tikona Digital Networks Pvt L
> 8402 514 64 1 OJSC "Vimpelcom"
> 39891 514 32 2 SaudiNet, Saudi Telecom Compa
> 16625 485 282 347 Akamai Technologies, Inc.
> 20115 390 350 96 Charter Communications
> 11492 382 42 205 CABLE ONE, INC.
> 2386 325 48 282 AT&T Data Communications Serv
>
> Complete listing at http://thyme.rand.apnic.net/current/data-ASnet
>
> Global Per AS Maximum Aggr summary
> ----------------------------------
>
> ASN No of nets Net Savings Description
> 7545 979 972 TPG Telecom Limited
> 45528 578 546 Tikona Digital Networks Pvt L
> 8402 514 513 OJSC "Vimpelcom"
> 39891 514 512 SaudiNet, Saudi Telecom Compa
> 7552 310 309 Viettel Corporation
> 20940 987 298 Akamai International B.V.
> 20115 390 294 Charter Communications
> 714 284 283 Apple Inc.
> 24378 264 263 Total Access Communication PL
> 62823 255 245 Puerto Rico Cable Acquisition
>
> Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet
>
> List of Unregistered Origin ASNs (Global)
> -----------------------------------------
>
> Bad AS Designation Network Transit AS Description
> 30662 UNALLOCATED 8.2.129.0/24 3356 Level 3 Communicatio
> 47092 UNALLOCATED 8.8.204.0/24 16410 The Reynolds and Rey
> 53506 UNALLOCATED 8.17.102.0/23 2828 XO Communications
> 46467 UNALLOCATED 8.19.192.0/24 46887 Lightower Fiber Netw
> 18985 UNALLOCATED 8.21.68.0/22 3356 Level 3 Communicatio
> 46473 UNALLOCATED 8.27.122.0/24 12180 Internap Network Ser
> 46473 UNALLOCATED 8.27.124.0/24 12180 Internap Network Ser
> 27205 UNALLOCATED 8.38.16.0/21 6461 Abovenet Communicati
> 15347 UNALLOCATED 8.224.147.0/24 12064 Cox Communications I
> 33628 UNALLOCATED 12.0.239.0/24 1239 Sprint
>
> 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
> 23.249.144.0/21 40430 colo4jax, LLC
> 23.249.152.0/21 40430 colo4jax, LLC
> 27.50.8.0/24 55548 Ravibhawan
> 27.50.9.0/24 55548 Ravibhawan
> 27.50.10.0/23 55548 Ravibhawan
> 27.100.7.0/24 56096 >>UNKNOWN<<
> 31.170.96.0/23 23456 32bit Transition AS
>
> 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:8 /9:8 /10:0 /11:7 /12:20
> /13:53 /14:67 /15:101 /16:435 /17:313 /18:632
> /19:1181 /20:3313 /21:2434 /22:2977 /23:3260 /24:15338
> /25:8 /26:7 /27:3 /28:2 /29:0 /30:0
> /31:0 /32:0
>
> Advertised prefixes smaller than registry allocations
> -----------------------------------------------------
>
> ASN No of nets Total ann. Description
> 39891 512 514 SaudiNet, Saudi Telecom Compa
> 8402 509 514 OJSC "Vimpelcom"
> 11492 379 382 CABLE ONE, INC.
> 62823 255 255 Puerto Rico Cable Acquisition
> 22773 212 259 Cox Communications Inc.
> 20115 171 390 Charter Communications
> 9198 144 234 JSC Kazakhtelecom
> 40285 128 131 NORTHLAND CABLE TELEVISION IN
> 48159 125 228 Telecommunication Infrastruct
> 12586 107 133 GHOSTnet GmbH
>
> Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos
>
> Number of /24s announced per /8 block (Global)
> ----------------------------------------------
>
> 1:1574 2:688 4:97 5:1879 6:25 8:1400
> 11:1 12:1809 13:19 14:1414 15:17 16:2
> 17:49 18:22 20:49 23:1269 24:1752 27:2080
> 31:1192
>
> End of report
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> afnog mailing list
>
> ------------------------------
>
> End of afnog Digest, Vol 138, Issue 4
> *************************************
More information about the afnog
mailing list