Full Abstract

Speakers
Philip Smith, Cisco Systems

Full Abstract

Speakers
Danny McPherson, Arbor Networks

Full Abstract

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.

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.

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.

The following topics will be covered as part of this tutorial:

• QoS Techniques
  • Classification/Marking
  • Shaping/Policing
  • Queuing/Scheduling
  • Congestion Avoidance
• QoS in IP/MPLS Edge
• IP Diffserv (DSCP)
• MPLS Diffserv (EXP)
• Diffserv Tunneling Modes (RFC 3270)
• QoS in MPLS Core
• MLPS QoS and Path selection schemes: MPLS TE / FRR / DS-TE

Speakers
Utpal Mukhopadhyaya, Cisco Systems
Arun Sathiamurthi, Cisco Systems
Paresh Shah, Cisco Systems

Full Abstract

Speakers
Steve Feldman, CNET.
Brokaw Price, Yahoo!

Full 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.

Speakers
Duane Wessels, Measurement Factory/CAIDA.

Full 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.

Speakers
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.

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.

Full 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.

Speakers
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.

Full 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.

Speakers
Moderator - 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.

Panelist - Wes George, Sprint
Panelist - 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.

Panelist - Jared Mauch, NTT America.
Panelist - 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.

Full 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.

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.

The solution has the following benefits:

• Reduces operating expenses (OpEx) and capital expenditures (CapEx)
• 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
• L2VPN can be combined with Quality of Service and Traffic Engineering to build new revenue-generating services
• VPLS is a service targeted for enterprise networks to connect geographically separate LAN segments together across a WAN.
  
  

In this tutorial we will walk through the following topics:

• Virtual Private Wire Service (VPWS): like-to-like and interworking attachment circuits
• VPLS (Virtual Private Lan Service): point-to-multipoint
• Guaranteed Quality of Service
• Traffic Engineering and fast reroute for L2VPN
• MPLS OAM L2VPN circuits
• Pseudowire redundancy & tunnel stitching
• High availability and reliability
• Convergence
• L2VPN troubleshooting

L2VPN (interworking & VPLS) demo

Speakers
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.

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.

Full 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: Paid Peering as an Adjunct to Settlement Free Interconnect (15 min). 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 AS7018 & AS7132 Discussion (15 min). 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. Emerging Content Provider Peering Approach (15 min). 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 Peering Contact Database (peeringdb.com) Update (10 min). 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 The Great Peering Debate (30 min). "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. Other Topics. 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.

Speakers
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.