A provider's success is increasingly being influenced by its ability to monitor and engineer its traffic performance - both within its domain and between its domain and other AS's. Key data required for both inter- and intra-domain traffic engineering (TE) include information on routing, traffic loads, bandwidth, and path performance.

This tutorial focuses on application of TE for inter-domain purposes. This includes short-term traffic management requirements such as debugging, congestion mitigation, and routing optimization; as well as long-term planning involving capacity planning, peering analysis, and load balancing.

The first half of this tutorial provides an overview of techniques that can be used by large, complex networks to expand their visibility into and control of traffic moving between their network and other domains (it recaps key points from the NANOG24 Inter-domain Traffic Engineering tutorial).

The second half of the tutorial provides specific examples and case studies of inter-domain TE from commercial networks, including MFN and Global Crossing. A case example from Exodus also demonstrates how data gathered for inter-domain TE can be used for intra-domain TE purposes, e.g., use of BGPNextHop in optimizing internal routing.

About the Presenters
Josh Wepman is an applications engineer at Ixia. He was a senior engineer at Caimis, Inc., responsible for BGP routing and traffic (flow) analyses and for design of several traffic engineering applications. Previously, Josh served as a backbone engineer at UUNET, managing intra-domain routing and traffic engineering efforts.

Joe Abley is a toolmaker at MFN, building tools to measure, manage, and document MFN's IP network. He has also worked at MFN as a backbone engineer. Before joining MFN, Joe worked as a consultant for various carriers and ISPs in New Zealand, where he provided operational and network design support for regional IP networks.

Andrew Lange is Principal Network Architect at Exodus, a Cable & Wireless Service. He designs and evaluates advanced network architectures and systems. Prior to joining Exodus, Andrew managed the Network Protocol Engineering and the QA/Test groups at GlobalCenter. These groups were responsible for the operations and future development of the GlobalCenter network.

Matthew Meyer is part of a team of network engineers evolving Global Crossing's multi-vendor MPLS-TE enabled network. He is team lead for a group that focuses on traffic engineering and network protocol design and analysis. Prior to working at GBLX, Matthew supported the NSFNET at Advanced Network Services (ANS), then shifted to backbone engineering and network optimization while at AOL and UUNET.