April 2013 - Test - lists.nanog.org

Hazmat at 400 N Tampa
by Jay Ashworth 09 Apr '13

09 Apr '13

WFLA TV reports that Tampa Fire is working a hazmat call at 400 N Tampa. http://www.wfla.com/story/21920646/hazmat-situation-in-downtown-tampa Park Tower is the carrier hotel for Tampa Bay; there are about 13 carriers in that building, at least 9 of which have major POPs and xconn there. Depending on what the actual problem is, Tampa Bay, Florida, or the Southeast may see repercussions from this. Followups to outages-discussion(a)outages.org, please (except for actual further outage data). (I would set followups, but Zimbra 6 sucks.) Cheers, -- jra -- Jay R. Ashworth Baylink jra(a)baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA #natog +1 727 647 1274

1 0

Closing the gap to improve the capacity of existing fiber optic networks
by Eugen Leitl 09 Apr '13

09 Apr '13

http://www.gizmag.com/cudos-fiber-optic-network-capacity/26969/ Closing the gap to improve the capacity of existing fiber optic networks By Darren Quick April 7, 2013 Researchers claim to have increased the data capacity of optical networks to the point that all of the world’s internet traffic could be transmitted via a single fiber (Photo: Shutterstock) A team of researchers working through Australia’s Centre for Ultrahigh Bandwidth Devices for Optical Systems (CUDOS) has developed data encoding technology that increases the efficiency of existing fiber optic cable networks. The researchers claim their invention increases the data capacity of optical networks to the point that all of the world’s internet traffic could be transmitted via a single fiber. Compatible with existing networks, the data encoding technology involves making more efficient use of available data channels. Where existing networks transmit data with gaps between the channels, the new approach packs the data channels closer together, thereby allowing more lanes on the same super-highway. To demonstrate the system, the researchers re-programmed a LCoS (liquid crystal on silicon) Wavelength Selective Switch (WSS) to make more efficient use of available data channels. A WWS is a network component that uses different wavelengths of laser light to combine (or multiplex) multiple digital data streams onto a single optical fiber. The research team, which included Professor Arthur Lowery and Dr Liang Du of the Monash Department of Electrical and Computer Systems Engineering and Jochen Schroeder, Joel Carpenter and Ben Eggleton from the University of Sydney, managed to transmit a signal of 10 terabits per second (Tb/s) more than 850 km (528 miles) using the new technology. That’s still well short of the 26 Tb/s data transmission speeds achieved by scientists at Germany's Karlsruhe Institute of Technology (KIT), but is over a far greater distance than the 50 km (31 miles) that team achieved. Professor Lowry said that the switch could be used to squeeze signals into the gaps in data traffic that flows around large optical-ring networks between cities. "Importantly, new traffic can be squeezed into the fiber at any location and added to any ‘lane’ of the fiber freeway even between existing lanes,” he said. "Rather than laying hundreds of new parallel optical fibers to boost network capacity, we can make more efficient use of the existing network by tweaking the way data is transmitted over long distances." “Our approach is so flexible, network operators could adjust capacity to respond to increased demand, for example from people following big sport events like the Olympics," added Dr Schröder. The team believes the technology would allow existing infrastructure to cope with the rising demand for internet, which is expected to increase 1,000 fold over the coming decade, with minimal investment. "Because we are have made use of equipment that is already on the market, this technology could be translated to the consumer quite quickly,” said Dr Du. The team’s findings were presented last month at the Optical Fiber Communication Conference in California. It was presented as a postdeadline paper, which are intended to give attendees the opportunity to hear breakthrough results in rapidly advancing areas. Source: CUDOS

2 1

NANOG 58 - New Orleans - Call For Presentations is open!
by David Temkin 09 Apr '13

09 Apr '13

*Fresh off of a great NANOG 57 in Orlando, your program committee is already working hard to provide a world-class program for NANOG 58 in NOLA - New Orleans, Louisiana - one of my favorite destinations in the world.* * * *As a reminder, we will be following the same Monday-Wednesday program that we started at NANOG 57, with Tutorials beginning Monday morning and closing with the Peering Track (and potentially a social) on Wednesday evening. * * * *We look forward to seeing everyone in The Big Easy!* * -------------------- The North American Network Operators' Group (NANOG) will hold its 58th meeting in New Orleans on June 3rd - 5th, 2013 Verizon Terremark will host NANOG 58. The NANOG Program Committee is now seeking proposals for presentations, panels, tutorials, tracks sessions, keynote materials, and the NOGLab experience for the NANOG 58 program. We invite presentations highlighting issues relating to technology already deployed or soon-to-be deployed in the Internet. Vendors are encouraged to work with operators to present real-world deployment experiences with the vendor's products and interoperability via the program and as part of the NOGLab. NANOG 58 submissions are welcome at http://pc.nanog.org. About NANOG NANOG is the premier meeting for network operators in North America. Meetings provide a forum for information exchange among network operators, engineers, and researchers. NANOG meets three times each year, and includes panels, presentations, tutorial sessions, tracks, informal BOFs, and a NOGLab which features interoperability demonstrations. NANOG attendees include operators from networks of all sizes, enterprise operators, peering coordinators, transport and switching equipment vendors, and network researchers. NANOG attendees will share ideas and interact with leaders in the field of network operations, discuss current operational events and issues, and learn about state-of-the-art operational techniques. Materials from NANOG 58 will be archived at: http://www.nanog.org/meetings/nanog58/<http://www.nanog.org/meetings/nanog55/> <http://www.nanog.org/meetings/nanog55/> Key Dates for NANOG 58 • CFP Opens for NANOG 58: 25-February-2013 • CFP Deadline #1: Presentation Abstracts Due: 8-April-2013 • CFP Deadline #2: Presentation Slides Due: 29-April-2013 • NANOG Highlights Page Posted: 22-April-2013 • Preliminary Topic List Posted: 26-April-2013 • Meeting Agenda Published: 13-May-2013 • Meeting Agenda Final sent to printer: 20-May-2013 • Lightning Talk Submissions Open (Abstracts Only): 2-June-2013 • Speaker FINAL presentations to PCTool or speaker-support: 31-May-2013 • On-Site Registration: 31-May-2013 The NANOG Program Committee seeks proposals for presentations, panels, tutorial sessions, tracks, and BOFs in all areas of network operations, including (but not limited to): - Power and facilities - Topics may include power reliability and engineering, green power, power efficiency, cooling, and facilities management. - Interconnections - Topics may include IXes, intra-building, MMR, metro-wide connections, peering, and transit purchasing tactics and strategies. - Security - Topics may include routing security, route filtering of large peers/customers, and inter-AS security and cooperation. - DNS - Topics may include using DNS data for network metrics, botnet discovery, and geolocation. - IPv6 - Topics may include real-world deployment challenges, Carrier Grade NAT, NAT-PT implementations that work and scale, and allocation strategies. - Content - Topics may include Distribution (p2p, IPTV), content payment models, content distribution technologies and networks, and storage/archiving. - Disaster recovery - Topics may include risk analysis, training, agencies, planning methods, hardware portability, key tools, transport audits, and other lessons learned. In general, presentations are being sought by and for network operators of all sizes. Presentations about difficult problems (and interesting solutions) that you encounter in the course of your job are encouraged. In addition, the Program Committee, through participation with other organizations and vendor’s, will be programming a NOGLab experience. The topic of the NOGLab will be timely and feature real-world experiences faced by operators of today’s Internet. If you think you have an interesting topic but want some feedback or assistance working it into a presentation, please email the Program Committee chair (chair(a)pc.nanog.org) and a representative on the Program Committee will give you the feedback needed to work it into a presentation. Otherwise, don't delay in submitting your talk, keynote, track, or panel into the NANOG Program Committee tool, located at http://pc.nanog.org. For more information about talk types and format, please see http://nanog.org/presentations/guidelines/talktips.php<http://www.nanog.org/presentations/guidelines/talktips.php> <http://www.nanog.org/presentations/guidelines/talktips.php> How to Present The deadline for accepting abstracts and slides is April 8, 2013 . While the majority of speaking slots may be filled by that date, a limited number of slots may be available after that date for topics that are exceptionally timely, important, or critical to the operations of the Internet. Complete Presentation Guidelines can be found at http://nanog.org/presentations/ <http://www.nanog.org/presentations/> <http://www.nanog.org/presentations/> The primary speaker, moderator, or author should submit presentation information and an abstract online at: http://pc.nanog.org once you have done this, you will receive instructions for submitting your draft slides. - Author's name(s) - Preferred contact email address - A preferred phone number for contact - Submission category (General Session, Panel, Tutorial, or Research Forum) - Presentation title - Abstract - Slides (attachment or URL), in PDF (preferred) or PowerPoint format. We look forward to reviewing your submission. Talks Keynote Presentation: The Program Committee invites speakers to submit materials for up to one-hour keynote presentations. Speakers should indicate that their submission is for a keynote in their abstracts. Speaker must submit slides for a Keynote Presentation. General Session Talk: A General Session presentation should be on a topic of interest to the general NANOG audience, and may be up to 30-minutes long (including time for Q&A). Speakers must submit slides for a General Session presentation. General Session Panel: Panels are 60-90-minute discussion sessions between a moderator and a team of panelists. The panel moderator should submit an abstract on the panel topic, a list of panelists, and how the panel will be organized. Panel selection will be based on the importance, originality, focus and timeliness of the topic, expertise of proposed panelists, as well as the potential for informative and controversial discussion. After acceptance the panel leader will be given the option to invite panel authors to submit their presentations to the NANOG program Committee for review. Until then authors should not submit their individual presentations for the panel. Tracks: Tracks are 90-minute informal agenda blocks on topics, which are of interest to a portion of the NANOG community. The 90-minute block can be subdivided into a number of smaller, highly related presentations, panels or open discussion. A moderator coordinates content within the 90-minute block of time, and must submit a detailed outline to the Program Committee, including sub-topics and presenters Peering ISP Security Tools Typically two tracks or three tracks will be run concurrently. Tutorials: Tutorials are 90-minute sessions. A presentation from the introductory through advanced level on all related topics, including: Disaster Recovery Planning Troubleshooting BGP Best Practices for Determining Traffic Matrices Options for Blackhole and Discard Routing BGP/MPLS Layer 3 VPNs Peering business and engineering basics A tutorial submission should include an abstract and slides. BOFs: BOFs (Birds of a Feather sessions) are informal sessions on topics, which are of interest to a portion of the NANOG community. BOFs may be held in the hallways, breakout areas or in an unscheduled tutorial room. Requests for scheduled BOFs will be take place on site at the meeting. A typical BOF session may include some structure or presentations, but usually is focused on community discussion and interaction. Frequent BOF topics include: R&D collaboration Hot-topics in the media The less structured nature of BOF sessions allows for the greatest flexibility from a timing perspective. Lightning Talks: A lightning talk is a very short presentation or speech by any attendee on any topic relevant to the NANOG audience. These are limited to ten minutes; this will be strictly enforced. If you have a topic that's timely, interesting, or even a crackpot idea you want to share, we encourage you to consider presenting it. The Program Committee will vote on all Lightning Talk submissions onsite at the meeting, and a submitter will be notified about his or her submission one day prior to the scheduled talk time. Submit your lightning talk proposal at http://pc.nanog.org starting June 2, 2013. Research Forum: Researchers are invited to present short (10-minute) summaries of their work for operator feedback. Topics include routing, network performance, statistical measurement and analysis, and protocol development and implementation. Studies presented may be works in progress. Researchers from academia, government, and industry are encouraged to present. The NANOG registration fee is waived for: - For General Session presentations, the registration fee will be waived for a maximum of one speaker. - For General Session panels, fees will be waived for one panel moderator and all panelists. - For Tracks, fees will be waived for one moderator. - For Research Forum presentations, fees will be waived for one speaker. - For Tutorials, fees will be waived for one instructor. *

1 2

Verizon DSL moving to CGN
by cb.list6 09 Apr '13

09 Apr '13

Interesting. http://www22.verizon.com/support/residential/internet/highspeedinternet/net…

37 88

Re: cloudmark?
by Chris Conn 09 Apr '13

09 Apr '13

On 2013-04-09 10:27, Chris Conn wrote: > > Hi, > > <rant> > it seems that many large providers are using cloudmark services. As far as I can tell: their policy is unclear, they can hardly be reached, mails to support are bouncing (delayed, then bounce). > > yes, the mailserver from one of our customers was blocked and this was OK and rightful, because they had a problem (cracked account). After the problem was resolved we started removing their IPv4 address from blacklists and almost all lists removed the ban immediately. > > cloudmark CSI service (reset request form) wants a form to be filled ... and they claim that they send out an email ... but it doesn't make its way to my inbox (no, no filters ...) > > and support can't be reached. > > Where are the good old times when the 'net was controlled by techs and not by lawyers? > > I can't recommend cloudmark. > </rant> > > Your experience does not mirror mine at all. I have less than 30 minutes of wait time for any support case, and they are few and far between. Reliability is high and FP rate is low. I have no idea what your reference to lawyers pertains to, however the only issue we have ever had was for them to take our money when we renewed for the umpteenth time. Maybe they cater to smaller providers more efficiently. Chris

1 0

ipfix analyzers
by Saku Ytti 09 Apr '13

09 Apr '13

Can someone point me to IPFIX analysers that do automatic learning of traffic patterns, raise events as suspected dos, and when operator marked as false positive, won't trigger that pattern anymore? This should be without configuring any explicit network ranges anywhere. So when I do get new customer, I don't have to teach the system about it. At simplest, maybe it could be static n pps / n Mbps per IP, then keep hitting false positive button, until they disappear. Other thing I'm missing from Arbor, is as far as I can see, it does not really like IXP. I don't know how you can ask via webUI to show traffic from ASNX in IXP port Y. I can ask traffic in port X or traffic in ASNX, but not traffic in ASNX in port X. You can dig this out of IPFIX data really easily. Both of these seem really trivial issues, frankly not much more than full work day to produce in homegrown IPFIX analyzer if you don't have to worry about bigdata/scaling (which I do). But is there product I can buy, which satisfies these requirements? -- ++ytti

1 0

cloudmark?
by Martin Hotze 09 Apr '13

09 Apr '13

Hi, <rant> it seems that many large providers are using cloudmark services. As far as I can tell: their policy is unclear, they can hardly be reached, mails to support are bouncing (delayed, then bounce). yes, the mailserver from one of our customers was blocked and this was OK and rightful, because they had a problem (cracked account). After the problem was resolved we started removing their IPv4 address from blacklists and almost all lists removed the ban immediately. cloudmark CSI service (reset request form) wants a form to be filled ... and they claim that they send out an email ... but it doesn't make its way to my inbox (no, no filters ...) and support can't be reached. Where are the good old times when the 'net was controlled by techs and not by lawyers? I can't recommend cloudmark. </rant> greetings, martin

1 0

Re: Verizon DSL moving to CGN
by kpospisek＠bigpond.com 09 Apr '13

09 Apr '13

Quoting: > Date: Sun, 7 Apr 2013 09:31:22 +0200 (CEST) > From: Mikael Abrahamsson <swmike(a)swm.pp.se> > To: nanog list <nanog(a)nanog.org> > Subject: Re: Verizon DSL moving to CGN > On Sun, 7 Apr 2013, Fabien Delmotte wrote: >> CGN is just a solution to save time, it is not a transition mechanism >> through IPv6 >> At the end (IPv6 at home) you will need at list : >> Dual stack or NAT64/ DNS64 > CGN doesn't stop anyone deploying dual stack. NAT64/DNS64 is dead in the > water without other mechanisms (464XLAT or alike). Defusing the "dead-in-the-water" phrase: An IPv4 solution with NAT64/DNS64 will still enable pure IPv6 SS devices without built-in NAT46 to still access the majority of the IPV4 world. (There are few IPV4-over-IPv6 technologies that can make a similar claim so thats already one step ahead of the competition on the IPv4 sunset path) XLAT464 (CLAT46+PLAT64) is now published as RFC6877. It is the most mature sunset technology - Is a single vendor offering out there that either does not already have a NAT64 function or doesn't have it in their roadmaps ? Greets Karl Pospisek from Melbourne AU.

1 0

Announcing BGP-SRx 0.3.0 service release
by Borchert, Oliver 08 Apr '13

08 Apr '13

This is to announce the BGP Secure Router Extension (BGP-SRx) Version 0.3 Prototype Implementation. This release includes extensive performance and robustness improvements, multi router support, re-design/re-write of the Quagga integration, and many bug fixes. BGP-SRx is an open source reference implementation and research platform for investigating emerging BGP security extensions and supporting protocols. The BGP-SRx suite consists of three parts: (1) SRx Server, (2) SRx API, and (3) Quagga-SRx (which integrates the SRx API into the Quagga router). The focus is on origin validation, although it is designed to be extended to path validation. Stub functionality for path validation is included in this version. Additionally, this release contains an SRx client/server test harnesses and a simple RPKI validation cache simulator (VCS). The VCS allows to manually feed ROA information into BGP-SRx server using the RPKI to Router protocol (rfc6810) as well as WireShark modules for debugging. For more information on BGP-SRx, and to download the prototype and tools, see: http://www-x.antd.nist.gov/bgpsrx/ Comments and feedback about BGP-SRx are welcome. See the project page for details. Thanks, Oliver Borchert ------------------------------------------------------------- Oliver Borchert, Computer Scientist National Institute of Standards and Technology (Phone) 301.975.4856 , (Fax) 301.975.6238 ------------------------------------------------------------- Oliver Borchert, Computer Scientist National Institute of Standards and Technology (Phone) 301.975.4856 , (Fax) 301.975.6238

1 0

ICMP Redirect on Resolvers
by Shahab Vahabzadeh 08 Apr '13

08 Apr '13

Hello everybody, I have two DNS Server (resolver) running on FreeBSD 9.0, I always see in console messages like this: icmp redirect from 192.168.140.36: 192.168.179.80 => 192.168.140.254 and lots of messages like this, mostly ip addresses not belong to me, and some times these resolvers stop working. My question is what are these messages? why they only shown in console of these servers not others? And are they cause the problems like stopping working for server/services? Thanks -- Regards, Shahab Vahabzadeh, Network Engineer and System Administrator Cell Phone: +1 (415) 871 0742 PGP Key Fingerprint = 8E34 B335 D702 0CA7 5A81 C2EE 76A2 46C2 5367 BF90

7 9