1 / 6

Routing Proximity Services IETF 73 Minneapolis, November 2008

Routing Proximity Services IETF 73 Minneapolis, November 2008. Stefano Previdi - sprevidi@cisco.com. Introduction. Routing Layer for Proximity/Localization services What ? Why ? Need ?. Architecture. Routing Layer for Proximity/Localization services. What ?

maeve
Download Presentation

Routing Proximity Services IETF 73 Minneapolis, November 2008

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Routing Proximity ServicesIETF 73Minneapolis, November 2008 Stefano Previdi - sprevidi@cisco.com

  2. Introduction • Routing Layer for Proximity/Localization services • What ? • Why ? • Need ?

  3. Architecture • Routing Layer for Proximity/Localization services. What ? • Leverage Routing databases (ISIS/OSPF/BGP) in order to compute proximity/localization services • Interface to routing layer is well known: routing adjacencies. No need to define anything new • OSPF/ISIS and BGP Data has very good proximity/localization properties • Includes protocol extensions/features for policy management BGP Communities Route Tags ...

  4. Architecture • Routing Layer for Proximity/Localization services. Why ? • Consistency between Routing/forwarding decisions Proximity decisions • Use same topology information as used for routing Not derived from third parties • Information is kept up to date by routing layer: adapt to network events • Leverage existing (and future) IGP/BGP protocol enhancements Examples: RFC 5029 - ISIS Link Attribute RFC 5130 - ISIS Route Tags draft-ietf-isis-genapp - ISIS Generic Application TLV BGP Community / Extended Community ...

  5. Architecture • Standardization effort - Need • Need for a protocol supporting routing-based proximity • ALTO is chartered to standardize a signaling protocol between clients and servers according to draft-kiesel-alto-reqs • Routing Proximity can be based on IP addresses, Prefixes, AS numbers, BGP Communities, ... any routing information type • Protocol extensibility and backward compatibility Protocol objects and signaling messages will probably ‘grow’ over time

  6. References • Peer Selection Guidance Bruce Davie, Stefano Previdi, Jan Medved, Albert Tian - Cisco Systems {bdavie,sprevidi,jmedved,atian}@cisco.com - May 1, 2008 • Application-Layer Traffic Optimization (ALTO) Requirements draft-kiesel-alto-reqs-00 S. Kiesel (NEC), L. Popkin Pando Networks), S. Previdi (Cisco Systems), R. Woundy (Comcast), Y R. Yang (Yale University) • Application-Layer Traffic Optimization (ALTO) Problem Statement draft-marocco-alto-problem-statement-02 - July 10, 2008E. Marocco (Telecom Italia), V. Gurbani (Bell Laboratories, Alcatel-Lucent) • Improving User and ISP Experience through ISP-aided P2P Locality. Vinay Aggarwal Deutsche Telekom Labs/TU Berlin Anja Feldmann Deutsche Telekom Labs/TU Berlin Obi Akonjang TU Berlin {vinay,obi,anja}@net.t-labs.tu-berlin.de • IDIPS : ISP-Driven Informed Path Selection draft-saucez-idips-00.txt - February 18, 2008D. Saucez, B. Donnet, O. Bonaventure (Universite catholique de Louvain)

More Related