QUICK LINKS

SHARE THIS PAGE

You are here

NANOG Meeting Presentation Abstract

Newcomer Orientation and Reception

Meeting:

NANOG36

Date / Time:

2006-02-12 3:30pm - 5:00pm

Room:

Gold Room

Presenters:

Moderators:Steve Feldman, CNET.

Abstract:

Welcome! If you\'re new to NANOG, or if you\'re an experienced attendee and just feel like hanging out, this orientation session and reception are for you. Join us to meet other newcomers as well as members of the NANOG Steering Committee, Program Committee, and List-admin team. We\'ll demystify the goings-on at NANOG, and also tell you a bit about the birth of the organization way back in the mists of time.
We\'ll meet from 3:30-5:00 p.m. on Sunday, June 5. Light refreshments will be served—and be sure to join us immediately after the reception for the Community Meeting at 5:00 p.m.

Files:

None.

Sponsors:

None.

Searching for DNS Cache Poisoners—Lazy, Stupid, or Evil?

Meeting:

NANOG36

Date / Time:

2006-02-13 9:15am - 9:45am

Room:

Regency Ballroom

Presenters:

Speakers:Duane Wessels, Measurement Factory/CAIDA.

Abstract:

In response to reports of DNS cache poisoning early in 2005, we performed a number of surveys of authoritative DNS servers. Our survey looks for sources of DNS cache poisoning. We found about 170 potential sources of \"poison.\" Based on what we can determine about the organizations related to and responsible for the poisoning, we try to infer whether they have malicious intentions or are being stupid and lazy.

Tsuyoshi Toyono, NTT Labs

Tsuyoshi Toyono joined NTT Laboratories in 2003, and is engaged in DNS traffic measurement and analysis. He is a member of the Information Processing Society of Japan (IPSJ) and the WIDE Project.

Katsuyasu Toyama, NTT Labs

Katsuyasu Toyama is a senior research engineer at NTT Laboratories. He was involved with the establishment of the first Japanese datacenter company, Internet Multifeed Co., in 1997, and there he designed JPNAP\'s network and services in 2000. His current interests focus on bridging network operations and network research, especially the core technologies of the Internet, such as interdomain routing, name resolution, and security.

Abstract:

Current major operating systems that support IPv6 send AAAA queries for any name resolution prior to resolving A records, which doubles the number of queries and increases user response time. Because Windows Vista, which will be released in 2006, enables IPv6 by default, operators of DNS cache servers should prepare for this increase. In addition, many OSes may send multiple queries for single name resolution when the record is not found, by completing local domain names. While the completion is useful, it increases the load of DNS cache servers.
We show how the combination of AAAA query and domain name completion increases the number of queries. We will also discuss the effects of this increase on cache server operation and user response time, and explain how to decrease the needless queries.

Steve Gibbard, PCH

Steve Gibbard is Network Architect for Packet Clearing House (www.pch.net), a non-profit based in Berkeley, California. He runs an anycast DNS network which hosts the top level domains for several countries and several of the \"I\" root anycast DNS servers, maintains PCH\'s network of route collectors and route servers at exchange points around the world, and does research on the interconnection of Internet networks. In addition, Steve carries out network architecture and peering work as a consultant for several ISPs in the Bay Area and elsewhere. Steve is a former Senior Network Engineer at Cable & Wireless, and has held network engineering positions at Digital Island and World Wide Net.

Abstract:

The domain name system, without which most Internet applications don\'t work, depends on reliable access to DNS information. Failure scenarios therefore exist where two Internet hosts may have connectivity to each other, but can\'t communicate because they lack a path to a DNS server in another location. A talk at last year\'s APRICOT touched on this problem in the general case. This talk will look at the DNS in greater detail, and how the placement of DNS servers for various top level domains affects their reliability in different parts of the world.

Daniel Golding, Burton Group

Daniel Golding is an industry analyst at the Burton Group, where his customer base consists of a number of enterprises with large global networks. His primary areas of coverage are internetworking, routing and switching, DNS/IP addressing, and large-scale IP network design. Prior to joining Burton Group, Daniel worked as a network architect and peering manager for a variety of large access ISPs. Daniel is a longtime attendee and frequent presenter at industry conferences including NANOG, ARIN, and MPLSCon.Panelists:

Joe Houle, AT&T

Joe Houle has been with AT&T for over 20 years. He has extensive experience in data communication, with a background in both equipment design and service definition/design. Joe has done: technical marketing for Frame Relay and ATM Equipment, Service and Network Planning for Frame Relay, customer network designs in AT&T Solutions (the consulting arm of AT&T), and Service and Network Planning for IP business services. One of Joe\'s present responsibilities is IP Service and Network Planning to support IPv6. He is a member of the North American IPv6 Task Force and is a steering committee member of the recently formed Mid-Atlantic IPv6 Task Force. Joe has an M.S. in Computer Science from Johns Hopkins University and a B.S. in IE/OR from Rutgers University.Jared Mauch, NTT America.Wes George, Sprint.

Jason Schiller, UUNET/Verizon

Jason Schiller is a Senior Internet Network Engineer in the IP Network Engineering Department at UUNET / Verizon. He has been with the company for over seven years. His current role includes architecting, designing, evaluating, and qualifying networks for deployment in the UUNET network. Jason also completes field trials and acts as highest level of escalation for issues in the Americas continental networks and for multicast issues globally. He is also responsible for defining and maintaining global standards for each of the continental UUNET networks. Previous projects include designing the UUCast multicast network and the Latin American network. Current interests include Internet routing, multicast, and IPv6.

Fred Wettling, Bechtel

Fred Wettling manages technology standards and strategies for Bechtel Corporation, He is one of 18 Bechtel Fellows out of an enterprise population of 40,000, and is sponsoring the enterprise IPv6 initiative within Bechtel. Fred is active within and outside of Bechtel promoting standards-based technology interoperability that support global enterprise business needs. He is a member of the North American IPv6 Task Force and IPv6 Business Council, has been active in the Network Applications Consortium (NAC) since 1997, and has served as the NAC¹s chairman for the past four years. Network World selected Fred as of the 50 most powerful people in networking in 2003, 2004, and 2005. He is a senior member of Cisco¹s Enterprise and Federal Technical Advisory Boards.

Abstract:

Discussion of IPv6 seems to be increasing in industry forums and publications. The US Federal Government has recently thrown its weight behind an IPv4-to-IPv6 transition. Some claim that our reserves of IPv4 address space are dwindling rapidly.
Is it time to roll out IPv6 in service provider networks and start offering services to consumers and enterprises? Is there really a demand? Is this just OSI networking all over again, or is there something more substantial here? IPv6 supporters from the IPv6 Business Council come together with IPv6 skeptics from Service Providers to clear the air on what may be an unneeded and massively disruptive transition or an amazingly enabling technological evolution—or both.

Philip Smith, Cisco Systems

Philip Smith joined Cisco Systems in January 1998. He is a member of the Service Provider Architectures Group of Consulting Engineering, within Corporate Development. His role includes working with many ISPs in the Asia-Pacific region and the rest of the world, specifically in network strategies, design, technology, and operations, as well as helping with network configuration and scaling. Other areas of interest also include Internet routing, Internet protocols, IPv6, and encouraging the growth of the Internet around the world.
Prior to joining Cisco, he spent five years at PIPEX (now part of UUNET\'s global ISP business), the UK\'s first commercial Internet Service Provider. He was one of the first engineers working in the UK Internet, and played a fundamental role in building the modern Internet in the UK and Europe.
Philip is co-author of Cisco ISP Essentials, published by Cisco Press. He holds a Doctor of Philosophy and has a First Class Honours Degree in Physics. He lives in Brisbane, Australia.

Abstract:

This tutorial covers common problems ISPs have when deploying BGP within their network. It looks at problems with peer establishment, missing routes, inconsistent route selection, and convergence issues. It also looks at real-world examples of common errors which are made when deploying BGP, both as iBGP and eBGP, in service provider networks.

With the increased convergence of multi-services at the edge of the provider network, there is a greater need for effective bandwidth management and service differentiation essentially achieved through IP Quality of Service. In order to provide end-to-end scalable IP services, MPLS backbones are being used to achieve this. This has led to a wider deployment of MPLS-based backbones, enabling providers to have the capability to extend service differentiation using MPLS Diffserv techniques. This ability to provide traffic categorization along with traffic engineering and bandwidth management techniques, available through MPLS Traffic Engineering (TE) and Diffserv-Aware Traffic Engineering (DS-TE), allows the service provider an array of choices for end-to-end implementation of Quality of Service.
The five key components of QoS include delay, jitter, latency, bandwidth and fairness. Any QoS deployment requires attention to these components. This would be achieved at the edge by initially classifying traffic streams appropriately, then metering them towards providing service-level guarantees and, if needed, marking the streams as per-policy definitions. Subsequently, for effective bandwidth management, congestion avoidance and management techniques need to be implemented for better utilization of the links and for improved distribution of the available resources.
<BR><BR>
QoS in the MPLS core achieves differentiation using the MPLS EXP (experimental bit) and leverages the above-mentioned techniques. Additionally, there are benefits of providing congestion avoidance in the core by combining MPLS EXP-based classification with path selection and link and node protection schemes enabled by MPLS TE /FRR/ DS-TE.
<BR><BR>
This tutorial will begin by providing a background to the classical QoS techniques available for packet-based IP and MPLS networks. Subsequently it will introduce the concepts of MPLS Diffserv and briefly discuss the mapping between IP Diffserv and MPLS Diffserv at the edge. It will also briefly touch upon the concepts of MPLS QoS in conjunction with the path selection schemes through MPLS TE/FRR and DS-TE.
<BR><BR>
The following topics will be covered as part of this tutorial:
<UL>
<LI> QoS Techniques
<UL>
<LI> Classification/Marking</LI>
<LI> Shaping/Policing</LI>
<LI> Queuing/Scheduling</LI>
<LI> Congestion Avoidance</LI>
</UL>
</LI>
<LI> QoS in IP/MPLS Edge</LI>
<UL>
<LI> IP Diffserv (DSCP)</LI>
<LI> MPLS Diffserv (EXP)</LI>
<LI> Diffserv Tunneling Modes (RFC 3270)</LI>
</UL>
</LI>
<LI> QoS in MPLS Core</LI>
<LI> MLPS QoS and Path selection schemes: MPLS TE / FRR / DS-TE</LI>
</UL>

Richard Steenbergen, nLayer Communications

Richard Steenbergen is the Co-Founder of nLayer Communications, where he currently serves as Chief Technical Officer and devotes a significant amount of time to the strategic management of peering and transit relationships. Previously, he served as a Sr. Network Engineer for several large NSPs, and was the Sr. Software Engineer responsible for developing optimized routing technologies at netVmg, Inc.

Abstract:

IRR Power Tools is a useful new utility developed by the author for ISPs. Its capabilities include:
<UL>
<LI> Automated retrieval of prefixes registered behind an IRR Object.</LI>
<LI> Automatic exclusion of bogon or other configured undesirable routes.</LI>
<LI> Tracking and long-term recording of prefix changes through CVS.</LI>
<LI> Automatic aggregation to optimize data and reduce unnecessary changes.</LI>
<LI> E-mail updates, letting users know that their change was processed.</LI>
<LI> E-mail alerts to the ISP, letting them know of new routing changes.</LI>
<LI> Exporting of change data in e-mail form, for non-IRR using ISPs.
<LI> Router config generation, for easy automated config deployment.</LI>
</UL>

NVisionIP and VisFlowConnect-IP: Two Tools for Visualizing NetFlows for Security

Meeting:

NANOG36

Date / Time:

2006-02-14 9:30am - 10:00am

Room:

Regency Ballroom

Presenters:

Speakers:

Bill Yurcik, NCSA

Bill Yurcik is currently Manager, Security R&D, and Senior Systems Security Engineer at NCSA. Prior to this he was Head of Security Operations at NCSA, so he has both a theoretical and practical background in computer network security. Prior to joining NCSA, Bill had 12 years of professional experience as a Network Engineer for large networks (Naval Research Laboratory, NASA, Verizon, and MITRE). He is a graduate of Johns Hopkins University (MS Electrical Engineering 1990, MS Computer Science 1987), the University of Maryland (BS Electrical Engineering 1984), and is Ph.D. ABD from the University of Pittsburgh (1994-99).

Abstract:

We present two NetFlows visualization tools, (1) NVisionIP and (2) VisFlowConnect-IP. Both of these tools have been developed based on system administrator requirements, their design peer-reviewed in security research forums, and usability testing is in process. These tools both present large volume complex data transparently to system administrators in simple intuitive visual interfaces that support human cognitive processes.
NVisionIP visually represents the state of all IP addresses on large networks on a single screen window (we use a Class B address space as the default) with capabilities to filter and drill down to subnets and individual machines for details-on-demand. VisFlowConnect-IP visually represents flows between internal network IP hosts and the Internet, showing who is connecting with whom, with capabilities to filter and drill down to subnets and individual machines for details-on-demand. NVisionIP and VisFlowConnect-IP can be used individually or in unison for correlating events. This work is distinguished from others in that these are the first Internet security visualization tools to be freely available on the Internet and deployed in large production environments.

In this presentation we describe a set of visualization techniques that can help the task of operating and managing a network by representing network traffic information in a concise and intuitive manner. Our client/server tool is called Flamingo.
The Flamingo server is responsible for receiving raw NetFlow feeds from devices in the network that can sample traffic, and then sending processed information to the client for display. The Flamingo client receives data from the server and provides concise intuitive data visualizations, 3D space navigation, as well as filtering capabilities that can help the operator to extract or monitor specific information of interest. We illustrate, with the help of simple examples, how Flamingo can be used to perform network monitoring tasks as well as network security-related data forensics.

Jianhong Xia, University of Massachusetts

Jianhong Xia is a Ph.D. Candidate in the Department of Electrical and Computer Engineering at the University of Massachusetts at Amherst. He received his B.S. and M.S. degrees from the Department of Automation at the University of Science and Technology of China (USTC) in China in 1993 and 1996, respectively. Jianhong is expecting to receive his Ph.D. this summer. His research interests include Internet measurements and monitoring, analysis of Internet traffic dynamics, Internet infrastructure vulnerability, and network security.Lixin Gao, University of Massachusetts.Teng Fei, University of Massachusetts.

Abstract:

Persistent forwarding loops can be exploited by flooding attacks in the Internet. This happens because persistent forwarding loops may share one or more links with forwarding paths to reachable addresses. An attacker can exploit persistent forwarding loops to overload the shared links to disrupt Internet connectivity to those reachable addresses.
To understand the extent of this vulnerability, we perform extensive measurements to systematically study persistent forwarding loops and the number of network addresses that can be affected. We find that persistent forwarding loops do exist in the current Internet. About 2.47% of routable addresses experience persistent forwarding loops and 0.78% of routable addresses can be attacked by exploiting persistent forwarding loops.
In addition, 81.8% of the persistent forwarding loops appear within destination domains and they can be observed from various locations, which makes it possible to launch attacks from many vantage points. We also find that most persistent forwarding loops are just two hops long, which enables an attacker to amplify traffic to persistent forwarding loops significantly.
The possible causes of persistent forwarding loops could be misconfiguration of the common usages of default routes and static routes. In this talk, we show an example in whcih a network administrator neglects to configure a \"pull-up route\" at a border router to his/her upstream provider, which leads to persistent forwarding loop.
The complete paper is available at <A HREF=\"http://rio.ecs.umass.edu/mnilpub/papers/jxia-imc05.pdf\">http://rio.ecs.umass.edu/mnilpub/papers/jxia-imc05.pdf</A>

Speakers:Peter Boothe, University of Oregon.James Hiebert, University of Oregon.Randy Bush, IIJ.

Abstract:

We have monitored BGP announcements for one particular month, and then tried to automatically extract hijacking information. By the date of NANOG 36, we hope to have the whole process automated and to have completed a study spanning many months instead of just one. We\'d also like feedback as to whether a biweekly hijacking report would be useful to the community at large.

OpenBGPD is a new, multi-feature BGP-implentation that runs on OpenBSD. A novel approach to implementing BGP, the code is being mostly developed by Henning Brauer of the OpenBGPD/OpenBSD-Team. One aspect of the presentation will be the implementation of OpenBGPD as a route-server at the DE-CIX, a project currently in development.

Muhammad Waris Sagheer, Cisco Systems

Muhammad Waris Sagheer is a Senior Software Engineer for the High End Routing Organization in Cisco Systems, specializing in Advanced MPLS Technologies. He provides design, consulting, and escalation assistance to US, European, and Asian service providers for ATM and MPLS technologies. Muhammad has presented on various MPLS-related topics at the APRICOT 2005 and the Networkers conference, as well as MPLS Power Sessions to European Service Providers and Enterprise customers. He is the co-author of case studies and articles in the Cisco Press book MPLS Configuration on Cisco IOS Software, Packet magazine, and Techworld.

Syed Nawaz, Cisco Systems

Syed Natif Nawaz has more than seven years of experience in networking design, including five years of experience with Cisco IOS-XR software. He is currently the IOS-XR Software Development Manager at Cisco Systems, where he works on customer-focused IOS and IOS-XR defect resolution, feature integration, release processes, and general serviceability guidelines. He is the co-author of articles in Techworld and Packet magazines. Formerly, Syed worked as a Development engineer at Assured Access technologies and Alcatel, where he developed software for Access Concentrators. In addition to higher education in Electrical and Electronics from University of Madras, Syed holds an M.S. in Computer Science and Engineering from State University of New York at Buffalo.

Abstract:

Initially, Virtual Private Networks were built using leased lines. Service providers were offering VPNs based on point-to-point data link layer connectivity, using ATM or Frame Relay virtual circuits. Customers built their own Layer 3 networks to accommodate IP traffic. As a result, separate networks exist for Layer 2 and Layer 3 traffic, but maintaining separate networks for Layer 2 VPNs, Layer 3 VPNs and Internet traffic is difficult and very costly.
<BR><BR>
In order to maximize return on their assets and minimize their operating costs, service providers often look to consolidate the delivery of multiple service types onto a single networking technology. As packet traffic takes up a larger and larger portion of the available network bandwidth, it becomes increasingly useful to optimize public networks for IP. As a result, service providers are moving to converged IP/MPLS networks, and they need a single infrastructure for delivering Layer 2 (including transport) and Layer 3 services to their internal and external customers. L2VPN is the architectural framework for accomplishing this, regardless of whether the Layer 2 service is ATM, Frame Relay, Ethernet, PPP, or HDLC. L2VPN encapsulates packets at the provider edge router, transports them over the backbone to the provider edge router on the other side of the cloud, removes encapsulation, and sends them to their destination.
<BR><BR>
The solution has the following benefits:
<UL>
<LI> Reduces operating expenses (OpEx) and capital expenditures (CapEx)</LI>
<LI> Offers a new set of services, such as Metro Ethernet
MPLS uses frames or cells. L2VPN can work in IP over ATM networks and IP over MPLS networks</LI>
<LI> L2VPN can be combined with Quality of Service and Traffic Engineering to build new revenue-generating services</LI>
<LI> VPLS is a service targeted for enterprise networks to connect geographically separate LAN segments together across a WAN.
<BR><BR></LI>
</UL>
In this tutorial we will walk through the following topics:
<UL>
<LI> Virtual Private Wire Service (VPWS): like-to-like and interworking attachment circuits</LI>
<LI> VPLS (Virtual Private Lan Service): point-to-multipoint</LI>
<LI> Guaranteed Quality of Service</LI>
<LI> Traffic Engineering and fast reroute for L2VPN</LI>
<LI> MPLS OAM L2VPN circuits</LI>
<LI> Pseudowire redundancy & tunnel stitching</LI>
<LI> High availability and reliability</LI>
<LI> Convergence</LI>
<LI> L2VPN troubleshooting</LI>
</UL>
L2VPN (interworking & VPLS) demo</LI>

William B. Norton, Equinix

Bill Norton is Co-Founder and Chief Technical Liaison for Equinix. He focuses on research on large-scale interconnection and ISP peering, and in particular, scaling Internet operations using optical networking. Bill has published and presented his research in a variety of international forums. From 1987 to 1998, he served in several staff and managerial roles at Merit Network, directing national and international network research and operations activities and serving as NANOG coordinator. Bill received a B.A. in Computer Science and an M.B.A. from the Business School at the University of Michigan, and has been an active member of the Internet Engineering Task Force for the past 15 years.

Abstract:

I have been working with the Peering Coordinator Community to identify emerging peering and ISP cooperation issues that should be aired and discussed for the good of the community. Here is a draft list of issues the community has volunteered so far:
<STRONG>Paid Peering as an Adjunct to Settlement Free Interconnect (15 min)</STRONG>. As a perennial topic over the last ten years or so, the topic of settlement-based peering has come up as a solution for peering partners who do not meet the Settlement Free Interconnect (SFI) requirements. This paid peering approach, however, has not been widely adopted for a variety of reasons that we would like to discuss and understand. Speaker: TBD
<STRONG>AS7018 & AS7132 Discussion (15 min)</STRONG>. With the merger of two of the largest peering companies in the U.S. Peering Ecosystem there are questions in the Peering Community about the near and medium term impacts. The speaker (TBD) will share insights into the migration and schedule for integration, along with any peering changes that might ensue.
<STRONG>Emerging Content Provider Peering Approach (15 min)</STRONG>. Two competing forces are driving the peering debate at content companies: 1) lower transit prices and the ability to leverage marquee brand names make it difficult for content companies to justify the business case for peering, and 2) at the same time, the next generation content (video streaming, IPTV, IP for populating caches with 40G video files, etc.) is expected to increase the value of peering by at least a factor of 10. The more traffic that a content company can peer, the greater the benefits of peering to the entire peering community. Greater control over the end-user experience is a powerful motivation for the content company but needs to be balanced with the cost and overhead of running a backbone, managing spikes and transit commits. A leading content company will share its experience, its business motivations for peering, and provide lessons learned for other content companies looking to peering to distribute their content. Speaker: TBD
<STRONG>Peering Contact Database (peeringdb.com) Update (10 min)</STRONG>. This shared database provides contact info for the community, so we\'ll have a brief statistical update on the usage and some words to encourage continued population of community information into the DB. Speaker: TBD
<STRONG>The Great Peering Debate (30 min)</STRONG>. \"The Utility of MEDs\" will be the title of the Great Peering Debate. \"From a Practical Perspective, are MEDs useful for distributing the peering traffic load?\" is the question; \"MEDs are not a useful tool for Peering\" will be defended by Richard Steenbergen; and \"MEDs are a useful tool for Peering\" will be defended by Patrick Gilmore. The Peering Contact Debate will be presented by the peeringDB Admin Team.
<STRONG>Other Topics</STRONG>. We expect that between now and February there will be a variety of emerging issues so we will use the flexibility of the BOF format to include late breaking topics of interest to the community.

Files:

None.

Sponsors:

None.

v6fix: Wiping the Slate Clean for IPv6

Meeting:

NANOG36

Date / Time:

2006-02-15 9:00am - 9:30am

Room:

Regency Ballroom

Presenters:

Speakers:

Kenjiro Cho, WIDE Project/IIJ

Kenjiro Cho is a senior researcher at Internet Initiative Japan, Inc. He received an M.Eng. degree in computer science from Cornell University, and a Ph.D. degree in media and governance from Keio University. Cho-san is currently an adjunct professor at Japan Advanced Institute of Science and Technology, and a board member of the WIDE project. His current research interests include traffic measurement and management, and operating system support for networking.

Ruri Hiromi, WIDE Project/Intec NetCore

Ruri Hiromi is a researcher at Intec Netcore, Inc. She is a streering members of WIDE\'s R&D activity. Hiromi-san works on the IPv6Fix project, fixing relatively small but important technical issues on implementation, configuration, and operation with IPv6.

Abstract:

IPv6 is now available for major types of equipment, OSes, and applications, and is also deployed in major ISP backbones. However, there are a small number of erroneous implementations that do not work in IPv4/IPv6 dual-stack environments. When an IPv6 user encounters a problem, a frustrated user often hastily concludes that the problem lies with IPv6. We are concerned that such situations could lead to agitation among IPv6 users.
The IPv6-fix project aims to identify and document issues and pitfalls in IPv6 deployment. Such problems are often found at boundaries of specifications, implementations, and operation. The project covers a wide range of real-world topics, including on-link assumptions, DNS servers and resolvers, TCP connection establishment, quality of the IPv6 Internet, and firewalls. In this talk, we will describe IPv6-fix activities, illustrate issues by examples, and introduce our tools and measurement results.

Paula Rhea, Verizon

Paula Rhea is a Senior Consultant in MPLS and IP-VPN networking and product management for Verizon Business. She has over 15 years experience in wide area networking and large-scale network and system migrations, with positions and pre- and post-sales product development for Sprint and Hewlett-Packard. Paula\'s current professional interests include convergence, network-based security, and service level management and agreements. She is a Certified Information Systems Security Professional (CISSP). Paula holds a BBA from Texas Tech University and an MBA from Northwestern University.

Abstract:

Hurricane Katrina wreaked havoc on a three-state telecommunications infrastructure, leaving 3 million users without dial tone and taking thirty eight 9-1-1 Centers out of operation as well as 1,000 cell phone towers in the most widespread natural disaster to hit the U.S. This session focuses on the crisis management and emergency preparedness for the city of New Orleans in case study format, details the telecom infrastructure impacts/outages, and highlights how telecom operators such as ISPs, landline, wireless, and cable all teamed up to aggressively and creatively restore service to mission critical telecom infrastructure.
Specific examples in retail, healthcare, and an ISP will be highlighted. The presentation will provide insight into how the public Internet successfully served first responders such as the Police and Fire Departments as well as businesses and residents. The Internet provided the lifeline for tracking relatives, locating dispersed employees, submitting emergency claims to FEMA, and publicizing much-needed weather and recovery details with 100 broadcast stations initially off the air. Recent actions and proposals by the FCC and Department of Homeland Security will be shared. An assessment and vendor-neutral recommendation will be provided along with resources and references.

We propose an isolation layer—a shim—between inter-domain routing and packet forwarding. The job of this layer is to coordinate between Autonomous Systems on when and how to modify the forwarding state as to ensure inter-domain routing loops do not cause forwarding loops. The benefits of a consistency layer are two-fold. First, it prevents the creation of transient inter-domain forwarding loops and the resulting packet loss, high latency, and connection failures.
Second, by taking the burden of forwarding consistency off the inter-domain routing protocol, it enables inter-domain routing protocols with more complex convergence characteristics than BGP, such as protocols that optimize route selection based on performance.
We show that inter-domain routing loops cause real performance problems, and we offer two possible designs for the consistency layer. We prove that both designs are free of forwarding loops and show they are easy to deploy in the current Internet.