This page hosts and catalogues a reading list, which points to documents read by project partners.

Each document has its own comments done by the partner that has read such document.

Instructions to add/modify new items can be shown here.



To propose new documents to be included on this page please fill the following form.



 Background

Commented by Cesar Olvera. This is not a paper but a presentation. Anyway it contains a discussion on the growth of routing and addressing on the Internet. It reviews the attempts to accommodate that growth, examines the current trends, scaling constraints imposed by hardware/cost limitations, how the future might look if nothing changes, and finally explores an alternative approach. Along this, it has a basic set of references worth to read. We will include them in TO-READ section below.


 BGP

Commented by Cesar Olvera. This document reports how have been satisfied by Border Gateway Protocol version 4 (BGP-4) the requirements for publication of a routing protocol as an Internet Draft Standard. This report augments RFC 1774 and summarizes the main features of BGP-4, as well as analyzes the protocol regarding scaling and performance.


 Effects on Routing Hardware

Commented by Alessandro C. This document reports some test results related to the behavior of routers when receiving a number of BGP routes near or over the capacity of router memory. The main result is the oscillatory behavior of routers when the memory limit is reached: BGP sessions and related routes are cleared and then re-established in a periodic fashion. The main drawback of the article is that it is quite old and the results would need to be updated as BGP implementations have been improved a lot since 2002; for example, it is known that a major vendor did not support the packing of BGP prefixes in UPDATE messages before 2002 (a separate BGP UPDATE message was used for each prefix).


 Endpoints

Commented by Alvaro Vives. This documents contains early thinking on the topic of locator and identifier split. Experience with internetworking, along with further reflection on exactly what the fundamental objects in networking are, have resulted in two conclusions. First, early work on networking was not careful to distinguish between the concepts of an object and the name(s) of that object. Secondly, the set of fundamental objects recognized was not rich enough.
This paper discusses these issues in detail, and, as a result, defines, and proposes explicit recognition of, a new fundamental object in internetworking, the "endpoint". It further proposes the creation of an explicit naming space, the "endpoint name", for these objects.


 IDR Requirements

Commented by Cesar Olvera. This I-D historical perspective on the current state of IDR routing with respect to RFC1126 Goals and Functional Requirements for Inter-Autonomous System Routing. The I-D idea is to provides some insights into alternative approaches which may be help when building a new set of requirements. This I-D is the companion document to Requirements for Inter-Domain Routing (draft-irtf-routing-reqs-06.txt)
Commented by Cesar Olvera. This I-D is a discussion of requirements for the future routing architecture and future routing protocols. We can say this I-D is actually a recommendation to who is interested in create a routing architecture for the Internet in the future.


 Locator/ID Split

Commented by Alvaro Vives. A common observation is that a key issue in today's Internet is the overlapping semantics of IP addresses used as 'locators' and as 'identifiers'. A rather hasty conclusion from this is that the architectural solution is a 'identifier-locator split'. This document presents various general considerations about the mapping between identifiers and locators at the network and routing level in the Internet.
Specially useful seems the definitions included and the references to current work on the issue as well as an analysis of the current behaviour of locators and identifiers and if their split is of any help. Finally design goals are given for a mapping mechanism between Identifier namespace and locator namespace.

Previous Sets of Requirements

Commented by Alvaro Vives. It is commonly recognized that the Internet routing and addressing architecture is facing challenges in scalability, mobility, multi-homing, and inter-domain traffic engineering. The RRG is designing an alternate architecture to meet these challenges. This document consists of a prioritized list of design goals for the architecture that help on stablishing the criteria that will be used to evaluate different proposals but leaving open the possibility to make intelligent trade-offs between various metrics.
This said, the design goals are: Improved routing scalability, Scalable support for traffic engineering, Scalable support for multi-homing, Scalable support for mobility, Simplified renumbering, Decoupling location and identification, First-class elements, Routing quality, Routing security and Deployability.


 Problem Statements

Commented by Cesar Olvera. This paper states many of the problems in BGP concern route validity, path visibility and safety. The authors see two possible approaches to fixing BGP’s problems. 1st: to build fixes into the existing infrastructure by determining sufficient conditions (or what must be added to the infrastructure, separate from the protocol) for some property to be satisfied (e.g., [7, 9, 14, 15, 16, 22]). 2: to design for intrinsic robustness by redesigning the protocol to explicitly prevent the problem (e.g., [1, 8, 17]), which may provide more effective solutions in the long term. [Note: References in the same paper]


 Routing and Addressing

Commented by Cesar Olvera. This document reports the outcome of the Routing and Addressing Workshop, which the IAB held on October 18-19, 2006 in Amsterdam. The primary goal of this workshop was to develop a shared understanding of the problems that the large backbone operators are facing regarding the scalability of today's Internet routing system. The key workshop findings include an analysis of the major factors that are driving routing table growth, constraints in router technology, and the limitations of today's Internet addressing architecture. It is hoped that these findings will serve as input to the IETF community and help identify next steps towards effective solutions.



 TO-READ Section
 If you want you can get them for reading.

 Atomized Routing

 Background

 BGP Improvements

 Compact Routing

 Convergence
  • Towards harmless convergence in case of maintenance operations in IP networks

 Effects on Routing Hardware
  • D. Chang et al, An Empirical Study of Router Response to Large BGP Routing Table Load

 Endpoints

 Future Domain Routing
  • IRTF Routing Research Group's (RRG), Future Domain Routing (FDR), Scalability Research Subgroup (RR-FS) http://rr-fs.caida.org/

 IDR

 Internet Routing Protocol Standardization Criteria

 ISLAY

 Locator/ID Split

 Maths and Routing

 Multihoming

 Operational Global Routing

 Overlay Networks and Policy Distribution Networks

 Path-Vector Protocols

 Policy and Configuration Problems in BGP4
  • N. Feamster and H. Balakrishnan, Towards a Logic for WideArea Internet Routing

 Previous Sets of Requirements

 Problem Statements

 Renumbering

 Research Proposals

 Routing

 Routing Schemes

 SHIM6

 Surveys on Routing



 Other Documents

 Internet Topology Data

 State of the Routing World

 Routing and Addressing

 Workshops


Page last modified by August 10, 2007, at 09:25 AM