Browse Prior Art Database

Aggregation Support in the NSFNET Policy-Based Routing Database (RFC1482)

IP.com Disclosure Number: IPCOM000002310D
Original Publication Date: 1993-Jun-01
Included in the Prior Art Database: 2000-Sep-12
Document File: 10 page(s) / 24K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Knopper: AUTHOR [+2]

Abstract

This document describes plans for support of route aggregation, as specified in the descriptions of Classless Inter-Domain Routing (CIDR) [1] and the BGP-4 protocol [2], by the NSFNET Backbone Network Service. Mechanisms for exchange of route aggregates between the backbone service and regional/midlevel networks are specified. Additionally, the memo proposes the implementation of an Aggregate Registry which can be used by network service providers to share information about the use of aggregation. Finally, the operational impact of incorporating CIDR and aggregation is considered, including an analysis of how routing table size will be affected. This impact analysis will be used to modify the deployment plan, if necessary, to maximize operational stability.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 12% of the total text.

Network Working Group Mark Knopper

Request for Comments: 1482 Steven J. Richardson

Merit/NSFNET

June 1993

Aggregation Support in the NSFNET Policy-Based Routing Database

Status of this memo

This memo provides information for the Internet community. It does

not specify an Internet standard. Distribution of this memo is

unlimited.

Abstract

This document describes plans for support of route aggregation, as

specified in the descriptions of Classless Inter-Domain Routing

(CIDR) [1] and the BGP-4 protocol [2], by the NSFNET Backbone Network

Service. Mechanisms for exchange of route aggregates between the

backbone service and regional/midlevel networks are specified.

Additionally, the memo proposes the implementation of an Aggregate

Registry which can be used by network service providers to share

information about the use of aggregation. Finally, the operational

impact of incorporating CIDR and aggregation is considered, including

an analysis of how routing table size will be affected. This impact

analysis will be used to modify the deployment plan, if necessary, to

maximize operational stability.

1. Introduction

The Internet network service provider community and router vendors

(as well as the IESG and various IETF working groups) have agreed

that the time for deployment of route aggregation is upon us. This

topic has been discussed in the BGP-D, NJM and ORAD working groups at

several IETF meetings; it was a discussion topic of the NSFNET

Regional Techs' Meetings in January and June, 1993; and it was also a

topic of several meetings of the Federal Engineering Planning Group

and Engineering and Operations Working Group of the Federal Network

Council.

All have generally agreed that Summer, 1993 is the time to enable

BGP-4 and CIDR aggregation. Each of the parties is responsible for

its own aspect of CIDR implementation and practice. This memo

describes Merit's plans for support of route aggregation on the

NSFNET, and a proposal for implementing a database of aggregation

information for use by network providers.

2. Aggregation Support by the Backbone Service

The NSFNET backbone service includes a Policy-Based Routing Database

system which currently holds the set of network numbers that are

accepted by the backbone service with a list of Autonomous System

numbers from which announcements of these network numbers are

expected. In order to implement CIDR, the database system will be

modified to allow aggregation of routing information to be

configured.

The NSFNET will (initially) not support de-aggregation on its

outbound announcements. See section 2.3.

2.1 Current Configuration Capabilities

2.1.1 Inbound Announcements

An example of the way a network number is currently configured is as

follows:

35 ...