- Test - lists.nanog.org

unsubscribe
by Steve Lerner 23 Aug '17

23 Aug '17

On Wed, Aug 23, 2017 at 8:00 AM, <nanog-request(a)nanog.org> wrote: > Send NANOG mailing list submissions to > nanog(a)nanog.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.nanog.org/mailman/listinfo/nanog > or, via email, send a message with subject or body 'help' to > nanog-request(a)nanog.org > > You can reach the person managing the list at > nanog-owner(a)nanog.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of NANOG digest..." > > > Today's Topics: > > 1. Re: Creating a Circuit ID Format (Tassos Chatzithomaoglou) > 2. Re: Creating a Circuit ID Format (Jared Mauch) > 3. 2017 NANOG Elections General Information (Dave Temkin) > 4. Re: Creating a Circuit ID Format (Justin M. Streiner) > 5. Re: Creating a Circuit ID Format (Nick Hilliard) > 6. Spectrum web cache engineer (Andrew Kirch) > 7. RE: Creating a Circuit ID Format (Timothy Creswick) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 22 Aug 2017 19:01:56 +0300 > From: Tassos Chatzithomaoglou <achatz(a)forthnet.gr> > To: NANOG <nanog(a)nanog.org> > Subject: Re: Creating a Circuit ID Format > Message-ID: <6b76d308-1a55-af42-c7cd-195d77147a3b(a)forthnet.gr> > Content-Type: text/plain; charset=UTF-8 > > I don't know if it has any relation to your issue, but we use Circuit-ID > to uniquely identify the access node plus the customer's access loop > logical port on the access node. > Access node can be either a DSLAM, a switch, an OLT, etc. > > You may have a look at BBF's TR-101 (section 3.9.3) or TR-156 (section > 5.7) for syntax guide . > > -- > Tassos > > Colton Conor wrote on 21/8/17 23:26: > > We are building a new fiber network, and need help creating a circuit ID > > format to for new fiber circuits. Is there a guide or standard for fiber > > circuit formats? Does the circuit ID change when say a customer upgrades > > for 100Mbps to 1Gbps port? > > > > What do the larger carriers do? Any advice on creating a circuit ID > format > > for a brand new fiber network? > > > > > > Originally we ran a CLEC using a LECs copper, and our circuit ID was > > historically a telephone number for DSL circuits. The ILEC had a complex > > method for assigning circuit IDs. > > > > I am sure anything will work as long as you keep track of it, but any > > advice would be great! > > > > > > ------------------------------ > > Message: 2 > Date: Tue, 22 Aug 2017 12:37:08 -0400 > From: Jared Mauch <jared(a)puck.nether.net> > To: Tassos Chatzithomaoglou <achatz(a)forthnet.gr> > Cc: NANOG <nanog(a)nanog.org> > Subject: Re: Creating a Circuit ID Format > Message-ID: <2AF810AB-E963-4CD4-867C-3D96B73A4C8C(a)puck.nether.net> > Content-Type: text/plain; charset=us-ascii > > > > On Aug 22, 2017, at 12:01 PM, Tassos Chatzithomaoglou < > achatz(a)forthnet.gr> wrote: > > > > I don't know if it has any relation to your issue, but we use Circuit-ID > to uniquely identify the access node plus the customer's access loop > logical port on the access node. > > Access node can be either a DSLAM, a switch, an OLT, etc. > > > > You may have a look at BBF's TR-101 (section 3.9.3) or TR-156 (section > 5.7) for syntax guide . > > > My favorite circuit-ids were those from MFS where it had the service type > (2 chars i think) + a pop-code + z pop-code + service count number. > > We could then tell what pop/facility everything was handed off at easily > enough. I think my house even got a MFS pop code at one time due to the T1 > which was there. > > - Jared > > ------------------------------ > > Message: 3 > Date: Tue, 22 Aug 2017 10:21:32 -0700 > From: Dave Temkin <dave(a)temk.in> > To: "North American Network Operators' Group" <nanog(a)nanog.org> > Subject: 2017 NANOG Elections General Information > Message-ID: > <CAFJiuFq5=iAiRBxjbaKmZDvG=04bgdbpnXM1H-7v=dP1vWNZEA@ > mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hello NANOGers! > > We are once again approaching the annual NANOG election > <http://nanog.org/elections/2017/general> and appointment time. Board > candidate nominations open August 7th and the complete Election timeline > can be found here <http://nanog.org/elections/2017/general>. We encourage > those in the community who are not currently NANOG members to consider > becoming members of NANOG and to consider standing for a position in our > leadership. Through membership and voting, you will be an active > participant in directing all NANOG activities. > > Only NANOG members are eligible to nominate, be a candidate, vote, and > serve in the NANOG Board of Directors and Committees. Click here > <https://www.nanog.org/membership> to become a member today! **If you are > not a member and wish to vote in this election, your membership must be > received by 9:00 a.m. Pacific Time on Wednesday, October 4, 2017.** > > Why? > > NANOG is at its strongest and best when there is an engaged group of > members. If you care about NANOG and would like to take a turn at > volunteering your time, please consider becoming part of the team by taking > part in the nomination and election process. If you know someone else that > you believe would be interested in serving on the Board of Directors, > nominate them by completing the Online Process > <https://www.bigpulse.com/138028/signin> beginning August 7, 2017. Any > questions should be submitted to elections(a)nanog.org. > > As I spoke about during my opening at NANOG 70, diversity is key to the > viability of the NANOG community. Personally, it concerns me that our only > non-white, non-male elected member of the Board is leaving the board this > year, having served the maximum allowable number of terms. While everyone > is welcome, it is important that we represent our community well at all > levels and so if you or someone you know could help improve that > representation, please consider the nomination process. > > As NANOG continues to evolve, our Board of Directors and Committees will > continue to play an increasingly important role in our success. By joining > now, you can be an integral part of the process. > > For more information about the role of a Board of Director or any Committee > Member, or to find out more about what's involved in serving, please > consult the current NANOG Bylaws > <https://nanog.org/sites/default/files/sites/default/files/NANOG-Bylaws- > October2016.pdf> > or follow the links to the Board and Committee pages from the General 2017 > NANOG Elections Page <https://www.nanog.org/elections/2017/general>. > > > Best regards, > > Dave Temkin > On behalf of the NANOG Board of Directors > > > ------------------------------ > > Message: 4 > Date: Tue, 22 Aug 2017 16:50:40 -0400 (EDT) > From: "Justin M. Streiner" <streinerj(a)gmail.com> > To: James Bensley <jwbensley(a)gmail.com> > Cc: NANOG <nanog(a)nanog.org> > Subject: Re: Creating a Circuit ID Format > Message-ID: <Pine.LNX.4.64.1708221608470.25675(a)whammy.cluebyfour.org> > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > On Tue, 22 Aug 2017, James Bensley wrote: > > > In my opinion the circuit ID should be an abitrary (but unique) value > > and nothing more. As Nick suggested start at 1 and go up. If your > > company is called ABC Ltd then maybe have your first circuit ID as > > ABC00000001 and count up from there, it's as simple as that. > > > > For me, all the circuit ID should be is a record number/ID of a > > database entry and nothing more (or a search string). Some people like > > to have circuit IDs which include circuit types, or circuit speeds, or > > interface type, but as you asked, do you then change the circuit ID if > > the circuit speed changes, or the interface types changes, or the > > medium etc? > > Agreed. I designed something similar at a previous employer, and it just > used a date-coded ID with sequence number (ex: UOP 20170822.0001), and > then all of the cross-connect details were recorded in a place that was > better suited to capturing that sort of information. That would also > allow us to re-use fiber paths when we upgraded 1G links to 10G, etc. > > This also included IDs that could reference other circuit IDs - including > circuit IDs from other providers - so we could tie non-dark elements > together, such as waves through DWDM gear end up riding on separate dark > fiber paths on either side of the mux. > > The biggest obstacle was getting people to label fiber jumpers in the > field, but that obstacle went away as people get a better understanding of > it and having all of the cross-connects documented saved lots of time and > frustration when having to search through a large patch field at 3 AM... > > jms > > > ------------------------------ > > Message: 5 > Date: Tue, 22 Aug 2017 22:20:20 +0100 > From: Nick Hilliard <nick(a)foobar.org> > To: James Bensley <jwbensley(a)gmail.com> > Cc: NANOG <nanog(a)nanog.org> > Subject: Re: Creating a Circuit ID Format > Message-ID: <599CA014.5020704(a)foobar.org> > Content-Type: text/plain; charset=UTF-8 > > James Bensley wrote: > > In my opinion the circuit ID should be an abitrary (but unique) value > > and nothing more. As Nick suggested start at 1 and go up. If your > > company is called ABC Ltd then maybe have your first circuit ID as > > ABC00000001 and count up from there, it's as simple as that. > > there are a lot of ways of handling this, which broadly speaking break > down into whether you want to encode data in your circuit ID or whether > you want it to act as nothing more than an index on a database table. > > Regardless of what way you go about things, there are some parallel > issues, including whether you want inline checksumming, whether you want > random value increases or +1 increases, and whether you want an > alphanumeric or strictly numeric ID. Alphanumeric can allow unique > prefixes or suffixes to help identify who owns a circuit ID or what type > it is, at the complexity of adding identifiers which can be > misinterpreted over the phone. > > There are differing opinions on whether other information such as > service type, node location, speed, etc should be encoded in the service > name. > > Things that most people generally agree on include: > > - carefully splitting out service types. E.g. a fibre cable to a > location is one ID; a wavelength on that service is another ID of > another type; an IP transit service on that wave is a third ID, etc. > > - don't reuse IDs, ever. There are plenty of numbers out there. > > - don't change from one ID mechanism to another, if possible. > > Otherwise, for every well-reasoned suggestion to use a specific format, > there are other well-reasoned arguments to do things in a different way. > Choose one and stick with it. > > Nick > > > ------------------------------ > > Message: 6 > Date: Tue, 22 Aug 2017 21:44:24 -0400 > From: Andrew Kirch <trelane(a)trelane.net> > To: NANOG list <nanog(a)nanog.org> > Subject: Spectrum web cache engineer > Message-ID: > <CALA5tJLpNQBpE0gJne6VrPy7FPLfQjm5GMYwSj9Zr+=ZgaEHzg@mail. > gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Would a Spectrum engineer please contact me off list? It appears you're > caching an expired certificate for https://www.icei.org. > > The issue is tested/working everywhere else. > > Thanks! > > Andrew > > > ------------------------------ > > Message: 7 > Date: Wed, 23 Aug 2017 08:18:52 +0000 > From: Timothy Creswick <timothy(a)creswick.eu> > To: NANOG <nanog(a)nanog.org> > Subject: RE: Creating a Circuit ID Format > Message-ID: > <HE1PR05MB15644799780F432E10AC93ADAF850@HE1PR05MB1564. > eurprd05.prod.outlook.com> > > Content-Type: text/plain; charset="utf-8" > > > Things that most people generally agree on include: > > > > - carefully splitting out service types. E.g. a fibre cable to a > > location is one ID; a wavelength on that service is another ID of > > another type; an IP transit service on that wave is a third ID, etc. > > Definitely. We have one digit in our circuit ID which denotes the type to > aid with quick identification. > > We also use a luhn-10 checksum digit at the end, which is optional on > re-entry. This is really helpful when getting references over the phone. > When written, it's with a hyphen so that it's clear that it's able to be > dropped. > > A few things we also decided on: > > - Circuit references are purely numerical (although we prefix them with > letters when written, those letters are not part of what makes the numbers > unique in our business). The main reason for this is that they can easily > be entered in a variety of *compact* barcode formats. Most label printers > support this, and it saves loads of time in the datacentre when you can > just scan the label on a circuit on a handheld PC. > > - Circuit references are always the same length. This way, if the checksum > digit is being dropped (e.g. because it's coming from a non-human source > like a barcode), we know that the checksum digit is missing. > > - The first digit is never a zero, to avoid silly mistakes if you're > sorting them in Excel etc. > > - The first four digits are a simple date code of YYMM that the ID was > generated. This is surprisingly handy when you're looking for a specific > circuit reference in a list, and it sort of helps to spread the dataset out > a bit. This is what ensures that it's a non-zero first digit for the next > 80 years or so. The date code isn't a *requirement* of our format, however. > Should we need more than 10,000 circuits per month, we'll just abandon the > date coding. > > For those interested, our system looks like this: > > VCI-150600019-7 > > Any non [0-9] characters (including symbols) can be omitted. > > VCI : denotes that this circuit identifier corresponds to our business > 1506 : date code > 0001 : sequence number, incremented per circuit, per month > 9 : circuit type > 7 : checksum (optional) > > T > > > End of NANOG Digest, Vol 115, Issue 21 > ************************************** > -- -Steve Lerner (m) 212-495-9212

1 0

Spectrum web cache engineer
by Andrew Kirch 23 Aug '17

23 Aug '17

Would a Spectrum engineer please contact me off list? It appears you're caching an expired certificate for https://www.icei.org. The issue is tested/working everywhere else. Thanks! Andrew

1 0

2017 NANOG Elections General Information
by Dave Temkin 22 Aug '17

22 Aug '17

Hello NANOGers! We are once again approaching the annual NANOG election <http://nanog.org/elections/2017/general> and appointment time. Board candidate nominations open August 7th and the complete Election timeline can be found here <http://nanog.org/elections/2017/general>. We encourage those in the community who are not currently NANOG members to consider becoming members of NANOG and to consider standing for a position in our leadership. Through membership and voting, you will be an active participant in directing all NANOG activities. Only NANOG members are eligible to nominate, be a candidate, vote, and serve in the NANOG Board of Directors and Committees. Click here <https://www.nanog.org/membership> to become a member today! **If you are not a member and wish to vote in this election, your membership must be received by 9:00 a.m. Pacific Time on Wednesday, October 4, 2017.** Why? NANOG is at its strongest and best when there is an engaged group of members. If you care about NANOG and would like to take a turn at volunteering your time, please consider becoming part of the team by taking part in the nomination and election process. If you know someone else that you believe would be interested in serving on the Board of Directors, nominate them by completing the Online Process <https://www.bigpulse.com/138028/signin> beginning August 7, 2017. Any questions should be submitted to elections(a)nanog.org. As I spoke about during my opening at NANOG 70, diversity is key to the viability of the NANOG community. Personally, it concerns me that our only non-white, non-male elected member of the Board is leaving the board this year, having served the maximum allowable number of terms. While everyone is welcome, it is important that we represent our community well at all levels and so if you or someone you know could help improve that representation, please consider the nomination process. As NANOG continues to evolve, our Board of Directors and Committees will continue to play an increasingly important role in our success. By joining now, you can be an integral part of the process. For more information about the role of a Board of Director or any Committee Member, or to find out more about what's involved in serving, please consult the current NANOG Bylaws <https://nanog.org/sites/default/files/sites/default/files/NANOG-Bylaws-Octo…> or follow the links to the Board and Committee pages from the General 2017 NANOG Elections Page <https://www.nanog.org/elections/2017/general>. Best regards, Dave Temkin On behalf of the NANOG Board of Directors

1 0

Virtual or Remote Peering
by Rod Beck 22 Aug '17

22 Aug '17

How well does this service work? I understand it usually involves point-to-multipoint Switched Ethernet with VLANs and resold IX ports. Sounds like a service for ISP that would like to peer, but have relatively small volumes for peering purposes or lopsided volumes. Roderick Beck Director of Global Sales United Cable Company DRG Undersea Consulting Affiliate Member www.unitedcablecompany.com<http://www.unitedcablecompany.com> 85 Király utca, 1077 Budapest rod.beck(a)unitedcablecompany.com 36-30-859-5144 [1467221477350_image005.png]

7 8

Re: US/Canada International border concerns for routing
by Dave Cohen 22 Aug '17

22 Aug '17

It seems to me the original question was asking about it more from a legal perspective, in other words does Canadian traffic have to stay in Canada. IANAL (or a Canadian), but the answer is "mostly, no, especially as related to publicly routed traffic" as should be evidenced based on what's already been discussed here. In other words, there is restricted traffic but unless you're making a play for MAN/WAN type service on owned infrastructure, those requirements are unlikely to arise. To support the macro point, there is some big-boy level peering in Toronto but not really much else outside that, but there are plenty of routes that don't cross the border if you don't have to jump networks to your destination, for example going to an AWS on ramp in Canada using a native partner network, especially in the Toronto-Ottawa-Montreal. Dave Cohen craetdave(a)gmail.com > On Aug 8, 2017, at 8:41 PM, Bill Woodcock <woody(a)pch.net> wrote: > > > --Apple-Mail=_8DA28412-F6D0-43D8-A90F-5E151E54468E > Content-Transfer-Encoding: quoted-printable > Content-Type: text/plain; > charset=us-ascii > > >> On Aug 8, 2017, at 5:33 PM, Clayton Zekelman <clayton(a)MNSi.Net> wrote: >> =20 >> =20 >> =20 >> With the peering policies of the major Canadian ISPs, you're virtually = > guaranteed to hairpin through the US on most paths. >> =20 >> Robellus (Rogers, Bell & Telus) will peer with you at any of their = > major Canadian peering points, such as NYC, Chicago or LA. > > To be fair, Rogers does peer in Toronto. Along with New York, Chicago, = > Seattle, and Ashburn. > > -Bill > > > > > > --Apple-Mail=_8DA28412-F6D0-43D8-A90F-5E151E54468E > Content-Transfer-Encoding: 7bit > Content-Disposition: attachment; > filename=signature.asc > Content-Type: application/pgp-signature; > name=signature.asc > Content-Description: Message signed with OpenPGP > > -----BEGIN PGP SIGNATURE----- > > iQIcBAEBCAAGBQJZilooAAoJEG+kcEsoi3+HgNsQAIPkgL/lVL/j1sdPyiyQsepE > TCyHm4bsAq6m085kXoRj/IWn+KsVwmAq8ZGKnKEAiozmrSeyxAa2vmw5Kfs57l1/ > crBima+EOOlPT4VcD7tv9e8yEiVdjDuMp5tnLI238qCfIlHeHRtuU7CClzWPv6uD > 3jCNIBEcScrLWz37Ofm/D2AkYRAhhK5H8I417Y/39TH4MIoIKFsGbvWwpl30Fv8r > 5phO0MrTP6mB8niHne6HTxyMED5TGQpVEL2Qgh6qgaI9vzAs5/47KwwY57tZpxaL > v9GjkPJ4Ql7QVWbsSkXnFmHxXzqaHXAfg8SR+gsCN42Jyn99AIyAAwdALhqc4RuZ > ydi+lOlEutAMndA01CnrI81Eu/RpWrN+q/vi37W2rb6EPTPcCz2196JDlpC6VVW6 > tJOMNuP6Pa/ee52Cxu6RWwA4QZ6QVIT9fbDcRFXTGNuohwP8XVpujcsPLChzsFXA > Y2nt+TliL697lTZNbTZEzQ0f9w2rpCDpcLjTMCR8MNWZ4MjQHL3eDgO5ZIWHPTQf > ggR1Dz2EhPSXXZdvN7KPh1q9rhRb2VUPSn3EeEDo2TjgUVeUlunsDg/ILpf8lxUY > RTsXe5Nky7YqXKDG4HSlLF3R/RtfaVqKJfjljYg351cs40rzivzjD2TJ8r35RQeW > btKUtEvrcU28g15nOhLG > =MTUG > -----END PGP SIGNATURE----- > > --Apple-Mail=_8DA28412-F6D0-43D8-A90F-5E151E54468E-- >

4 4

Cox in Omaha blackhole routing to Level 3
by david peahi 21 Aug '17

21 Aug '17

Can someone from Cox reply to me offline regarding a Cox routing issue in Omaha? Both ends of connection are on Cox network, but a traceroute shows packets being routed into Level 3 at 4.35.186.61 24 msec 24 msec 24 msec, and blackholed in Level 3 network. David Holmes

1 0

Network & Socialize @ SAFNOG-3
by Mark Tinka 19 Aug '17

19 Aug '17

Hello all. The Internet is built on mutually fulfilling human connections, and at this year's SAFNOG meeting, we look forward to further enhancing these opportunities. There are a number of networking and social engagements planned for you, our delegates, at SAFNOG-3 in Durban: a) SAFNOG-3 will be co-located with iWeek, at the very same venue. You will have the chance to interact with several Internet personalities attending iWeek to understand their perspective. b) Prior to the start of each day, as well as during the lunch and coffee breaks, you will be able to surround yourself with fellow delegates and exchange ideas about the topics that will have been presented, or your own personal and professional experiences working on the Internet. c) NAPAfrica, Africa's largest Internet exchange point, will hold a Beers for Peers event at the California Dreaming venue in Durban. You are all invited to attend, free of charge, upon presentation of a ticket which will be handed to you at the registration counter. d) SEACOM, Eastern Africa's first submarine cable system, will hold the Closing Social Dinner at the Joint Jazz Cafe in Durban. You are all invited to attend, free of charge, upon presentation of a ticket which will be handed to you at the registration counter. e) For a bit of fun, an iPhone 7 Plus Jet Black, 256GB and iPad Pro 12.9-inch Space Gray, 512GB, Wi-Fi + Cellular, will be up for grabs in a lucky draw at the NAPAfrica and SEACOM events, respectively. So please carry your business cards and stand a chance to win one of these cool devices. For more details on the agenda and timing listings, please see: http://safnog.org/#section-agenda Do register your attendance as soon as you can. We look forward to seeing you in Durban. Cheers, Mark Tinka On Behalf of the SAFNOG Management Committee

1 0

Weekly Routing Table Report
by cscora＠apnic.net 18 Aug '17

18 Aug '17

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG MENOG, BJNOG, SDNOG, CMNOG, IRNOG and the RIPE Routing WG. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 19 Aug, 2017 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 657966 Prefixes after maximum aggregation (per Origin AS): 256321 Deaggregation factor: 2.57 Unique aggregates announced (without unneeded subnets): 318644 Total ASes present in the Internet Routing Table: 58117 Prefixes per ASN: 11.32 Origin-only ASes present in the Internet Routing Table: 50261 Origin ASes announcing only one prefix: 22199 Transit ASes present in the Internet Routing Table: 7856 Transit-only ASes present in the Internet Routing Table: 219 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 56 Max AS path prepend of ASN ( 55644) 51 Prefixes from unregistered ASNs in the Routing Table: 65 Number of instances of unregistered ASNs: 69 Number of 32-bit ASNs allocated by the RIRs: 19739 Number of 32-bit ASNs visible in the Routing Table: 15504 Prefixes from 32-bit ASNs in the Routing Table: 63312 Number of bogon 32-bit ASNs visible in the Routing Table: 26 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 329 Number of addresses announced to Internet: 2852057444 Equivalent to 169 /8s, 254 /16s and 241 /24s Percentage of available address space announced: 77.0 Percentage of allocated address space announced: 77.0 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: 219103 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 179034 Total APNIC prefixes after maximum aggregation: 51785 APNIC Deaggregation factor: 3.46 Prefixes being announced from the APNIC address blocks: 178012 Unique aggregates announced from the APNIC address blocks: 74353 APNIC Region origin ASes present in the Internet Routing Table: 8286 APNIC Prefixes per ASN: 21.48 APNIC Region origin ASes announcing only one prefix: 2302 APNIC Region transit ASes present in the Internet Routing Table: 1174 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 56 Number of APNIC region 32-bit ASNs visible in the Routing Table: 3139 Number of APNIC addresses announced to Internet: 764417508 Equivalent to 45 /8s, 144 /16s and 21 /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: 200851 Total ARIN prefixes after maximum aggregation: 95479 ARIN Deaggregation factor: 2.10 Prefixes being announced from the ARIN address blocks: 202628 Unique aggregates announced from the ARIN address blocks: 93514 ARIN Region origin ASes present in the Internet Routing Table: 17958 ARIN Prefixes per ASN: 11.28 ARIN Region origin ASes announcing only one prefix: 6646 ARIN Region transit ASes present in the Internet Routing Table: 1775 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: 2155 Number of ARIN addresses announced to Internet: 1109948448 Equivalent to 66 /8s, 40 /16s and 120 /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: 176258 Total RIPE prefixes after maximum aggregation: 86469 RIPE Deaggregation factor: 2.04 Prefixes being announced from the RIPE address blocks: 172136 Unique aggregates announced from the RIPE address blocks: 104075 RIPE Region origin ASes present in the Internet Routing Table: 24295 RIPE Prefixes per ASN: 7.09 RIPE Region origin ASes announcing only one prefix: 11175 RIPE Region transit ASes present in the Internet Routing Table: 3439 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 32 Number of RIPE region 32-bit ASNs visible in the Routing Table: 6095 Number of RIPE addresses announced to Internet: 712878720 Equivalent to 42 /8s, 125 /16s and 170 /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: 84593 Total LACNIC prefixes after maximum aggregation: 18725 LACNIC Deaggregation factor: 4.52 Prefixes being announced from the LACNIC address blocks: 85858 Unique aggregates announced from the LACNIC address blocks: 39440 LACNIC Region origin ASes present in the Internet Routing Table: 6264 LACNIC Prefixes per ASN: 13.71 LACNIC Region origin ASes announcing only one prefix: 1742 LACNIC Region transit ASes present in the Internet Routing Table: 1161 Average LACNIC Region AS path length visible: 5.4 Max LACNIC Region AS path length visible: 24 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 3780 Number of LACNIC addresses announced to Internet: 171061472 Equivalent to 10 /8s, 50 /16s and 48 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-268700 + ERX transfers LACNIC Address Blocks 177/8, 179/8, 181/8, 186/8, 187/8, 189/8, 190/8, 191/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 17163 Total AfriNIC prefixes after maximum aggregation: 3807 AfriNIC Deaggregation factor: 4.51 Prefixes being announced from the AfriNIC address blocks: 19003 Unique aggregates announced from the AfriNIC address blocks: 6990 AfriNIC Region origin ASes present in the Internet Routing Table: 1063 AfriNIC Prefixes per ASN: 17.88 AfriNIC Region origin ASes announcing only one prefix: 333 AfriNIC Region transit ASes present in the Internet Routing Table: 208 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: 335 Number of AfriNIC addresses announced to Internet: 93287936 Equivalent to 5 /8s, 143 /16s and 118 /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 5438 4192 87 ERX-CERNET-BKB China Education and Rese 7545 4004 408 395 TPG-INTERNET-AP TPG Telecom Limited, AU 17974 2966 902 73 TELKOMNET-AS2-AP PT Telekomunikasi Indo 4766 2840 11124 749 KIXS-AS-KR Korea Telecom, KR 9829 2753 1498 549 BSNL-NIB National Internet Backbone, IN 9808 2358 8699 32 CMNET-GD Guangdong Mobile Communication 45899 2293 1453 111 VNPT-AS-VN VNPT Corp, VN 4755 2095 422 220 TATACOMM-AS TATA Communications formerl 7552 1686 1106 71 VIETEL-AS-AP Viettel Corporation, VN 9498 1625 361 144 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 3816 2952 159 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 6327 3456 1341 88 SHAW - Shaw Communications Inc., CA 18566 2205 405 109 MEGAPATH5-US - MegaPath Corporation, US 6389 2063 3671 39 BELLSOUTH-NET-BLK - BellSouth.net Inc., 20115 2026 2214 434 CHARTER-NET-HKY-NC - Charter Communicat 209 1859 5065 635 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 30036 1826 329 279 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 16509 1819 3862 538 AMAZON-02 - Amazon.com, Inc., US 701 1718 10559 628 UUNET - MCI Communications Services, In 6983 1693 854 229 ITCDELTA - Earthlink, 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 3387 186 23 ALJAWWALSTC-AS, SA 20940 2971 968 2135 AKAMAI-ASN1, US 8551 2546 377 41 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 34984 2057 332 424 TELLCOM-AS, TR 9121 1909 1691 17 TTNET, TR 12479 1653 1048 59 UNI2-AS, ES 12389 1607 1536 668 ROSTELECOM-AS, RU 13188 1602 100 55 TRIOLAN, UA 6849 1225 355 21 UKRTELNET, UA 8402 1169 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 3547 542 217 Telmex Colombia S.A., CO 8151 2843 3410 583 Uninet S.A. de C.V., MX 11830 2109 370 65 Instituto Costarricense de Electricidad 7303 1560 1018 247 Telecom Argentina S.A., AR 6503 1555 437 53 Axtel, S.A.B. de C.V., MX 6147 1214 377 27 Telefonica del Peru S.A.A., PE 3816 1026 504 95 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 28573 953 2278 185 CLARO S.A., BR 11172 917 126 86 Alestra, S. de R.L. de C.V., MX 18881 898 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 1198 398 48 LINKdotNET-AS, EG 37611 748 91 8 Afrihost, ZA 36903 711 357 130 MT-MPLS, MA 36992 679 1378 29 ETISALAT-MISR, EG 24835 499 850 15 RAYA-AS, EG 29571 421 36 10 CITelecom-AS, CI 37492 407 321 75 ORANGE-, TN 15399 357 35 7 WANANCHI-, KE 2018 305 327 74 TENET-1, ZA 23889 278 103 14 MauritiusTelecom, MU 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 5438 4192 87 ERX-CERNET-BKB China Education and Rese 7545 4004 408 395 TPG-INTERNET-AP TPG Telecom Limited, AU 22773 3816 2952 159 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 10620 3547 542 217 Telmex Colombia S.A., CO 6327 3456 1341 88 SHAW - Shaw Communications Inc., CA 39891 3387 186 23 ALJAWWALSTC-AS, SA 20940 2971 968 2135 AKAMAI-ASN1, US 17974 2966 902 73 TELKOMNET-AS2-AP PT Telekomunikasi Indo 8151 2843 3410 583 Uninet S.A. de C.V., MX 4766 2840 11124 749 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 3816 3657 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7545 4004 3609 TPG-INTERNET-AP TPG Telecom Limited, AU 6327 3456 3368 SHAW - Shaw Communications Inc., CA 39891 3387 3364 ALJAWWALSTC-AS, SA 10620 3547 3330 Telmex Colombia S.A., CO 17974 2966 2893 TELKOMNET-AS2-AP PT Telekomunikasi Indonesia, I 8551 2546 2505 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 9808 2358 2326 CMNET-GD Guangdong Mobile Communication Co.Ltd. 8151 2843 2260 Uninet S.A. de C.V., MX 9829 2753 2204 BSNL-NIB National Internet Backbone, IN 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 65532 PRIVATE 14.192.19.0/24 132717 NDCTPL-IN NxtGen Datacenter & 65001 PRIVATE 43.229.208.0/24 135334 NEO-AS-AP NetExpress Online, B 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 65530 PRIVATE 45.249.40.0/24 133720 SOFTCALLCOC-AS SOFT CALL CUST- 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 290012147 UNALLOCATED 63.65.43.0/24 7046 RFC2270-UUNET-CUSTOMER - MCI C 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 27.100.7.0/24 56096 UNKNOWN 41.76.232.0/21 62878 XLITT - Xlitt, US 41.77.248.0/21 62878 XLITT - Xlitt, US 41.78.180.0/23 37265 -Reserved AS-, ZZ 41.79.12.0/22 37306 -Reserved AS-, ZZ 43.228.144.0/22 9829 BSNL-NIB National Internet Backbone, IN Complete listing at http://thyme.rand.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:15 /9:13 /10:36 /11:104 /12:284 /13:554 /14:1051 /15:1852 /16:13432 /17:7672 /18:13425 /19:24703 /20:38890 /21:41705 /22:78620 /23:65002 /24:368360 /25:856 /26:634 /27:650 /28:37 /29:25 /30:17 /31:2 /32:27 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6327 3252 3456 SHAW - Shaw Communications Inc., CA 22773 3002 3816 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 39891 2946 3387 ALJAWWALSTC-AS, SA 18566 2089 2205 MEGAPATH5-US - MegaPath Corporation, US 8551 2011 2546 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 30036 1608 1826 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 11830 1499 2109 Instituto Costarricense de Electricidad y Telec 10620 1493 3547 Telmex Colombia S.A., CO 11492 1388 1567 CABLEONE - CABLE ONE, INC., US 6389 1371 2063 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:1572 2:832 4:18 5:2454 6:31 7:1 8:1052 12:1854 13:142 14:1709 15:27 16:2 17:193 18:90 20:61 23:2439 24:1914 25:2 27:2361 29:1 31:1920 32:84 33:18 35:21 36:393 37:2362 38:1330 39:65 40:97 41:2954 42:463 43:1966 44:78 45:3015 46:2793 47:163 49:1257 50:995 51:19 52:815 54:364 55:7 56:4 57:45 58:1569 59:1009 60:327 61:1922 62:1695 63:1907 64:4653 65:2208 66:4570 67:2282 68:1232 69:3360 70:1176 71:615 72:2226 74:2718 75:389 76:427 77:1469 78:1447 79:1944 80:1410 81:1393 82:1000 83:731 84:946 85:1823 86:467 87:1206 88:769 89:2181 90:166 91:6188 92:1005 93:2394 94:2343 95:2656 96:652 97:355 98:1067 99:98 100:153 101:1220 103:15646 104:3023 105:186 106:568 107:1753 108:820 109:2903 110:1457 111:1746 112:1252 113:1251 114:1059 115:1559 116:1660 117:1757 118:2163 119:1652 120:733 121:1060 122:2334 123:1824 124:1484 125:1785 128:886 129:665 130:440 131:1473 132:571 133:191 134:680 135:225 136:453 137:470 138:1924 139:505 140:399 141:642 142:778 143:878 144:809 145:184 146:1087 147:701 148:1482 149:570 150:722 151:981 152:727 153:297 154:883 155:758 156:660 157:663 158:479 159:1556 160:739 161:744 162:2520 163:503 164:950 165:1396 166:382 167:1291 168:2991 169:841 170:3481 171:335 172:1014 173:1992 174:813 175:747 176:1896 177:4002 178:2556 179:1128 180:2214 181:1962 182:2389 183:776 184:877 185:10473 186:3316 187:2199 188:2603 189:1798 190:8347 191:1342 192:9553 193:5802 194:4680 195:3919 196:2100 197:1325 198:5542 199:5900 200:7579 201:4299 202:10334 203:9994 204:4540 205:2850 206:3076 207:3156 208:3941 209:3995 210:3950 211:2061 212:2890 213:2520 214:860 215:66 216:5891 217:2130 218:897 219:601 220:1686 221:899 222:749 223:1193 End of report

1 0

For the Wireless Guys
by Rod Beck 17 Aug '17

17 Aug '17

https://phys.org/news/2017-08-transmission-terahertz-multiplexer.html Roderick Beck Director of Global Sales United Cable Company DRG Undersea Consulting Affiliate Member www.unitedcablecompany.com<http://www.unitedcablecompany.com> 85 Király utca, 1077 Budapest rod.beck(a)unitedcablecompany.com 36-30-859-5144 [1467221477350_image005.png]

7 7

Telekom Malaysia Contact
by Gabe Cole 17 Aug '17

17 Aug '17

I am working on some subsea cables that need to transit in Malaysia and need a contact at Telekom Malaysia. Thanks in advance! Gabe Cole +1-617-303-8707 gabe(a)rtegroup.com @datacenterguru

1 0