Goals and functional requirements for inter-autonomous system routing
RFC 1126

Document Type RFC - Unknown (October 1989; No errata)
Author Mike Little
Last updated 2013-03-02
Stream Legacy
Formats plain text html pdf htmlized bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 1126 (Unknown)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          M. Little
Request for Comments:  1126                                         SAIC
                                                            October 1989

                 Goals and Functional Requirements for
                    Inter-Autonomous System Routing

Status of this Memo

   This document describes the functional requirements for a routing
   protocol to be used between autonomous systems.  This document is
   intended as a necessary precursor to the design of a new inter-
   autonomous system routing protocol and specifies requirements for the
   Internet applicable for use with the current DoD IP, the ISO IP, and
   future Internet Protocols.  It is intended that these requirements
   will form the basis for the future development of a new inter-
   autonomous systems routing architecture and protocol.  This document
   is being circulated to the IETF and Internet community for comment.
   Comments should be sent to: "open-rout-editor@bbn.com".  This memo
   does not specify a standard.  Distribution of this memo is unlimited.

1.  Introduction

   The development of an inter-autonomous systems routing protocol
   proceeds from those goals and functions seen as both desirable and
   obtainable for the Internet environment.  This document describes
   these goals and functional requirements.  The goals and functional
   requirements addressed by this document are intended to provide a
   context within which an inter-autonomous system routing architecture
   can be developed which will meet both current and future Internet
   routing needs.  The goals presented indicate properties and general
   capabilities desired of the Internet routing environment and what the
   inter-autonomous system routing architecture is to accomplish as a
   whole.

   The goals are followed by functional requirements, which address
   either detailed objectives or specific functionality to be achieved
   by the architecture and resulting protocol(s).  These functional
   requirements are enumerated for clarity and grouped so as to map
   directly to areas of architectural consideration.  This is followed
   by a listing and description of general objectives, such as
   robustness, which are applicable in a broad sense.  Specific
   functions which are not reasonably attainable or best left to future
   efforts are identified as non-requirements.

   The intent of this document is to provide both the goals and
   functional requirements in a concise fashion.  Supporting arguments,

Little                                                          [Page 1]
RFC 1126            Inter-Autonomous System Routing         October 1989

   tradeoff considerations and the like have been purposefully omitted
   in support of this.  An appendix has been included which addresses
   this omission to a limited extent and the reader is directed there
   for a more detailed discussion of the issues involved.

   The goals and functional requirements contained in this document are
   the result of work done by the members of the Open Routing Working
   Group.  It is our intention that these goals and requirements reflect
   not only those foreseen in the Internet community but are also
   similar to those encountered in environments proposed by ANSI, ECMA
   and ISO.  It is expected that there will be some interaction and
   relationship between this work and the product of these groups.

2.  Overall Goals

   In order to derive a set functional requirements there must be one or
   more principals or overall goals for the routing environment to
   satisfy.  These high level goals provide the basis for each of the
   functional requirements we have derived and will guide the design
   philosophy for achieving an inter-autonomous system routing solution.
   The overall goals we are utilizing are described in the following
   sections.

2.1  Route to Destination

   The routing architecture will provide for the routing of datagrams
   from a single source to one or more destinations in a timely manner.
   The larger goal is to provide datagram delivery to an identifiable
   destination, one which is not necessarily immediately reachable by
   the source.  In particular, routing is to address the needs of a
   single source requiring datagram delivery to one or more
   destinations.  The concepts of multi-homed hosts and multicasting
   routing services are encompassed by this goal.  Datagram delivery is
   to be provided to all interconnected systems when not otherwise
   constrained by autonomous considerations.

2.2  Routing is Assured

   Routing services are to be provided with assurance, where the
   inability to provide a service is communicated under best effort to
   the requester within an acceptable level of error.  This assurance is
   not to be misconstrued to mean guaranteed datagram delivery nor does
   it imply error notification for every lost datagram.  Instead,
Show full document text