Browse Prior Art Database

IPng Technical Requirements Of the Nimrod Routing and Addressing Architecture (RFC1753)

IP.com Disclosure Number: IPCOM000004003D
Original Publication Date: 1994-Dec-01
Included in the Prior Art Database: 2000-Sep-12
Document File: 15 page(s) / 44K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

N. Chiappa: AUTHOR

Abstract

This document was submitted to the IETF IPng area in response to RFC 1550. Publication of this document does not imply acceptance by the IPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.

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

Network Working Group N. Chiappa

Request for Comments: 1753 December 1994

Category: Informational

IPng Technical Requirements

Of the Nimrod Routing and Addressing Architecture

Status of this Memo

This memo provides information for the Internet community. This memo

does not specify an Internet standard of any kind. Distribution of

this memo is unlimited.

Abstract

This document was submitted to the IETF IPng area in response to RFC

1550. Publication of this document does not imply acceptance by the

IPng area of any ideas expressed within. Comments should be

submitted to the big-internet@munnari.oz.au mailing list.

This document presents the requirements that the Nimrod routing and

addressing architecture has upon the internetwork layer protocol. To

be most useful to Nimrod, any protocol selected as the IPng should

satisfy these requirements. Also presented is some background

information, consisting of i) information about architectural and

design principles which might apply to the design of a new

internetworking layer, and ii) some details of the logic and

reasoning behind particular requirements.

1. Introduction

It is important to note that this document is not "IPng Requirements

for Routing", as other proposed routing and addressing designs may

need different support; this document is specific to Nimrod, and

doesn't claim to speak for other efforts.

However, although I don't wish to assume that the particular designs

being worked on by the Nimrod WG will be widely adopted by the

Internet (if for no other reason, they have not yet been deployed and

tried and tested in practise, to see if they really work, an

absolutely necessary hurdle for any protocol), there are reasons to

believe that any routing architecture for a large, ubiquitous global

Internet will have many of the same basic fundamental principles as

the Nimrod architecture, and the requirements that these generate.

While current day routing technologies do not yet have the

characteristics and capabilities that generate these requirements,

they also do not seem to be completely suited to routing in the

next-generation Internet. As routing technology moves towards what is

needed for the next generation Internet, the underlying fundamental

laws and principles of routing will almost inevitably drive the

design, and hence the requirements, toward things which look like the

material presented here.

Therefore, even if Nimrod is not the routing architecture of the

next-generation ...