June 2015 - Test - lists.nanog.org

Good contact at Megapath wanted
by Lou Katz 11 Jun '15

11 Jun '15

regarding DDoS. Please contact me off-list. -- -=[L]=- Reassembled from random thought waves "We have a saying here on Jupiter -- everybody talks about the Great Red Spot but nobody does anything about it." - Lauren Weinstein

1 0

Re: eBay is looking for network heavies...
by Larry Sheldon 11 Jun '15

11 Jun '15

On 6/6/2015 05:43, shawn wilson wrote: > My first thought on reading that was "who the hell cares if a person > knows about internet culture". But than I had to reconsider - it's a > very apt way of telling if someone read the right books :) > > I would also add Ritchie, Thompson, and Diffie to that list (since you > ask about Larry, it's only appropriate). I find it interesting that I have not note a mention of people like Radia Pearlman and [name advancing years have stolen from me] that wrote a 3 volume set (I think it was) (that I can not find in the post-great-downsizing-bookshelves-disarray at the moment*). *did a little Binging--Not W. Richard Stevens although the subconscious thinks "steven" might have been the first name. NO! Douglas E. Comer "Internetworking with TCP/IP" (Nice try subconscious! Volume 3 is co-authored by David L. Stevens.) -- sed quis custodiet ipsos custodes? (Juvenal)

19 25

PPPoE/IPoE, any recommendations for upgrade?
by Nasser Heidari 11 Jun '15

11 Jun '15

Hi, We are currently using PPPoE in our network. I have seen some articles regarding migration of so-called legacy PPPoE to IPoE. After reviewing some of them and implementing IPoE in lab environment using Cisco ASR I didn't fine it that much beneficial to migrate whole system as I need to change a lot of things. For example: - I need to add it's support to our radius and obviously BSS system (E.g. using NAS-PORT-ID instead of username). - For the addressing part, as I have already using distributed BNG's, I need to change some of our policies. (For example assigning address blocks is much easier in PPPoE using framed-route) - I need to change our customers CPE configuration to use Ethernet encapsulation. - I haven't used DHCP in large scale environment. - I don't have any clear Idea/understanding regarding its maintainability/troubleshooting and also security. (Please add if I'm missing any other issue which may run into if I migrate to IPoE) Although it has some benefits, I'm not sure if it's that essential to migrate. Would you please kindly? - Share your Ideas/experiences/best practices in this regard? - If you are already using IPoE, tell more why should I upgrade? - Considering a DSL network with more than 800K customers using PPPoE, do you recommend this migration? Kind Regards, Nasser

6 7

RFP for Internet Transit for ARIN ASN 394018 (1GB Wowrack’s datacenter located in Tukwila, Seattle)
by John Curran 10 Jun '15

10 Jun '15

Hello NANOG Folks - Apologies for the distraction, but ARIN needs some transit providers and I thought there may be one or two on this list... We need 1 GB via standard multi-mode fiber in Wowrack/Seattle - ISP must provide native IPv4 and IPv6 connectivity, provide full view of the IPv4 and IPv6 routing table, support 32-bit ASNs, etc. If interested, please review the full RFP for details and response information. Thanks! /John John Curran President and CEO ARIN Begin forwarded message: From: ARIN <info(a)arin.net<mailto:info@arin.net>> Subject: [arin-announce] RFP for Internet Transit for ARIN ASN 394018 Date: June 9, 2015 at 8:59:07 AM PDT To: <arin-announce(a)arin.net<mailto:arin-announce@arin.net>> ARIN is soliciting proposals from Internet Service Providers (ISPs) to bid on the delivery of Internet transit to ARIN's network, ASN 394018. This network is part of ARIN's provisioning network and is a part of critical Internet infrastructure. ARIN is looking for qualified providers that are able to provide service to its rack within Wowrack's datacenter located in Tukwila, Seattle. All contractual terms and conditions related to the work performed, nondisclosure of information, or liability issues must be detailed. ARIN will require that the vendor performing this service sign a nondisclosure agreement due to the proprietary nature of the information ARIN retains for its subscribers. All proposals must be submitted no later than 5:00 p.m. EDT on 22 June 2015. ARIN will evaluate the properly submitted proposals and will select a winning bidder or bidders no later than 30 June 2015. Full text of the RFP is available at: http://www.arin.net/about_us/contracts/201506-westcoast-transit-rfp-sea.pdf Send proposals to rfp-transit-sea(a)arin.net or by mail to: Matt Rowley Infrastructure Manager ARIN 3635 Concorde Parkway, Suite 200 Chantilly, VA. 20151 ATTN: Proposal for Internet Transit Services Technical questions may be directed to: rfp-transit-sea(a)arin.net ARIN is operated as a nonprofit 501(c)(6) corporation which is chartered for educational, charitable, and scientific purposes. It is a membership organization with an official IRS designation as a business league. ___________

1 1

OT Fiber contractors?
by Jay Ashworth 10 Jun '15

10 Jun '15

I have a client needs a couple outside under-parkinglot runs installed*, and I'm so long out of that market I have no idea where to go. Offlist recs for Tampa metro cheerfully accepted. :-) Cheers, -- jra [ * Pulled and terminated; we'll supply the switches and do the interconnect ] -- Jay R. Ashworth Baylink jra(a)baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274

1 0

most accurate geo-IP source to build country-based access lists
by Martin T 10 Jun '15

10 Jun '15

Hi, let's say that I need to build an ACL where I block all the IPv4 traffic from Sweden. I considered following solutions: 1) RIR statistics files(ftp://ftp.ripe.net/ripe/stats/RIR-Statistics-Exchange-Format.txt) accessible for example at ftp://ftp.apnic.net/pub/stats/. However, those files contain allocations and assignment made by the registry producing the file and not any sub-assignments by other agencies(for example NIR, LIR). This means that this information is not very accurate. Another problem which I found out is that in case of inetnum object has many country fields, the first one is used. In addition, even the RIR statistics exchange format document says that: cc = ISO 3166 2-letter country code, and the enumerated variances of {AP,EU,UK} These values are not defined in ISO 3166 but are widely used. The cc value identifies the country. However, it is not specified if this is the country where the addresses are used. There are no rules defined for this value. It therefore cannot be used in any reliable way to map IP addresses to countries 2) MaxMind products. Those should rely on user input(for example MaxMind purchases user data from ISP's or content providers) and based on personal experience defaults to RIR data if no other more accurate source is available. If anyone has something to specify here, then please do so. 3) Use iptables geoip module, but turned out, that it uses MaxMind database: root@VM-host:~# grep -Hsi maxmind $(dpkg -L xtables-addons-common) /usr/lib/xtables-addons/xt_geoip_build:# Converter for MaxMind CSV database to binary, for xt_geoip /usr/lib/xtables-addons/xt_geoip_dl: http://geolite.maxmind.com/download/geoip/database/GeoIPv6.csv.gz \ /usr/lib/xtables-addons/xt_geoip_dl: http://geolite.maxmind.com/download/geoip/database/GeoIPCountryCSV.zip; root@VM-host:~# 4) In theory geofeeds(http://tools.ietf.org/html/draft-google-self-published-geofeeds-02) would be a nice solution, but as I understand the RFC, it would work for my example only in case all the IP address users would provide their geofeed and there is a centralized database to query. 5) Use prefix AS path. However, there seems to be no reliable way to determine source country based on information in BGP routing tables. Are there any other possibilities to geolocate IPv4 addresses with higher accuracy? regards, Martin

10 11

grepcidr 2.99
by John Levine 10 Jun '15

10 Jun '15

I've updated grepcidr again, adding some code contributed by a user. (This open source thing may actually have a future.) grepcidr is what it sounds like, you give it a bunch of CIDR ranges, and files to read, and it prints out the lines in the files that contain addresses that match any of the CIDR ranges. The new feature lets it match CIDR ranges in the input files as well as IP addresses. It handles both IPv4 and IPv6. It maps each file into memory and runs a state machine over the file in one pass so it's quite fast. There should be no limits on line length, file size, or number of patterns other than running out of memory. Find it here: http://www.taugh.com/grepcidr-2/ Regards, John Levine, johnl(a)iecc.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. http://jl.ly

2 2

Fwd: PeeringDB 2.0 Rollout And Governance Announcement
by Job Snijders 09 Jun '15

09 Jun '15

[ Forwarding today's announcement, apologies for duplicates ] --------------- Hi Everyone! PeeringDB is rolling our the first major revision since its inception, PeeringDB 2.0. This email will explain the basics, and how you can learn more information if you are interested. Future Communication ------------------------------------------------------------ Before we begin, we should note one of the major changes is the way in which PeeringDB will be announcing future enhancements, changes, maintenance windows, and other information. In the future, if you would like to be notified of certain events, or participate in discussions, please subscribe to one of the following email lists. The URL will be added to the main PeeringDB page in case you lose this email. * PeeringDB Announce (http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-announce) All PeeringDB administrative information, such as upgrades, maintenances, outages, etc. * PeeringDB Governance (http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-gov) Discussion list for PeeringDB governance issues. This is a community-based effort, the community’s input will help guide the future of the PeeringDB (as it has always done). * PeeringDB Technical (http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-tech) Discussion of the back end of PeeringDB & other technical topics. * PeeringDB User-Discuss (http://lists.peeringdb.com/cgi-bin/mailman/listinfo/user-discuss) All other list traffic. Our goal is to give you all the information you want, and no more. Please subscribe to any of these lists you feel are appropriate, or none. You will still be able to use the database even if you are not subscribed to any lists. PeeringDB 2.0 Beta! ------------------------------------------------------------ If you would like to try PeeringDB 2.0 now, please visit beta.peeringdb.com (https://beta.peeringdb.com/) . Documentation is available at beta.peeringdb.com/docs/ to assist with the transition and introduce you to the new API. Should you find bugs please report them on Github (https://github.com/peeringdb/1to2/issues) . PeeringDB Governance Announcement ------------------------------------------------------------ It has been suggested that the PeeringDB be moved under one of the existing community organizations currently in place. After some internal soul searching, discussion with some of those organizations, and discussion with PeeringDB users in person, at conferences, and over email, PeeringDB has decided to remain an independent entity. To ensure the DB’s continued operation with the community’s best interests squarely in mind and shepherd the future development of the DB, the PeeringDB is choosing a board of directors. The initial, interim board was announced during the Peering Track of NANOG 64, June 3, 2015. An election by the PeeringDB community to replace the initial board will be held prior to August 1st, 2016. If you are interested in governance, including running for the board, please join the PeeringDB Governance email list. The times and method of voting for the board as well as other governance topics will be announced on that list, and only on that list. PeeringDB 2.0 Rollout Timeline ------------------------------------------------------------ August 1, 2015: PeeringDB 2.0 will be brought online. The https://www.peeringdb.com/ URL will direct users to the new instance, and access to the old UI will be discontinued. The old SQL access and nightly dumps will continue for a month to ensure transition time for those using the old schema. September 1, 2015: SQL Access to the old PeeringDB 1.0 database will be discontinued. If you would like to be notified of each step as it is happening, as well as future changes to the DB, please subscribe to the PeeringDB Announce list. Questions & Comments ------------------------------------------------------------ If you have any questions, please email admin(a)PeeringDB.com Kind regards, The PeeringDB Admins

1 0

RE: 100G DWDM FEC standard
by Gert Grammel 09 Jun '15

09 Jun '15

Hi Mikael, >From a standards perspective keep in mind that http://www.stupi.se/Standards/100G-long-haul4.pdf is not approved - but we are working hard on it. OTOH having a reference implementation at hand, is an accelerator that helps a lot. Let me also add some color to your email as the current interoperability situation in WDM is quite funny. Sometimes transceivers of the same vendor can't talk to each other, as they are based on a different generation of ASICs and therefore FEC implementations. In other words, vendors typically have more than only one secret sauce they cook with, and different sauces do not blend well :-) . Perhaps transport folks are already too used to deal with such kind of issues that no one laments anymore. On the other hand perhaps, the networking industry is already so used to Ethernet where interoperability is a no-brainer, that it is difficult to imagine what it means to deal with a technology that prevents multi-vendor interop. To confirm your final point: Interoperability is on the top of the shopping lists for the networking industry. Gert email : ggrammel(a)juniper.net --------------------------------------- Date: Fri, 5 Jun 2015 17:53:58 +0200 (CEST) From: Mikael Abrahamsson <swmike(a)swm.pp.se> To: nanog(a)nanog.org Subject: 100G DWDM FEC standard Message-ID: <alpine.DEB.2.02.1506051741330.9487(a)uplift.swm.pp.se> Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Hi, I just watched the "evolution of ethernet speeds" presentation from NANOG meeting. There was a statement that there was "vendor secret sauce" in the 100G DWDM space. Yes, that is true, but: http://www.stupi.se/Standards/100G-long-haul4.pdf There actually is a standard for 100G DWDM that has support from multiple router vendors. When you buy new gear, make sure your vendors support the above standard, so we can connect our routers over longer distances between vendors, without needing transponders. We in the Deutsche Telecom Terastream project have Huawei, Cisco, Juniper and ALU routers that natively (DWDM colored interfaces in the routers) talk directly to each other over 1500 km amplified DWDM system (no transponders), and we can also talk from these routers interfaces to Cisco and ALU transponders if we want to. https://jeffloughridge.wordpress.com/2013/10/16/peter-lothbergs-terastream-… if you want to know more about the project. Next time you purchase 100G DWDM equipment, make sure you buy equipment that follows this standard to be certain that it interoperates to combat vendor "secret sauce". -- Mikael Abrahamsson email: swmike(a)swm.pp.se

2 1

Re: NANOG Digest, Vol 89, Issue 2
by Ramy Hashish 09 Jun '15

09 Jun '15

Does anybody knows anything about "AirTight networks" and "Meru"?

1 0