IPng Technical Requirements Of the Nimrod Routing and Addressing Architecture (RFC1753)
Original Publication Date: 1994-Dec-01
Included in the Prior Art Database: 2000-Sep-12
Internet Society Requests For Comment (RFCs)
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 email@example.com mailing list.
Network Working Group N. Chiappa
Request for Comments: 1753 December 1994
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.
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 firstname.lastname@example.org 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.
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 Internet, the basic routing architecture of that
Internet will have requirements that, while differing in detail, will
almost inevitably be similar to these.
In a similar, but more general, context, note that, by and large, the
general analysis of sections 3.1 ("Interaction Architectural Issues")
and 3.2 ("State and Flows in the Interne...