network
Click on the red underlined text to get to the source
... (a) transit restrictions imposed by source, destination, and transit
networks, (b) different types of services offered and required, and
(c) the presence of multiple carriers with different charging
...
... architecture is capable of accommodating very large numbers of
datagram networks, it does not provide support for specialized
routing requirements ...
... can support unconstrained proliferation of user requirements and
network services. At the same time, this is not necessarily a
problem. The capabilities of the architecture may in fact exceed the
...
... limited. However, the possible use of data compression techniques
and the increasing speed of network links make this less important
than route ...
... TOS) routing. There is a great deal of research and development
activity currently underway to explore network architectures and
protocols for high-bandwidth ...
... deployed homogeneously across the internet (including all
metropolitan, regional, and backbone networks) that will support all
types of traffic uniformly. To support diverse traffic ...
... service guarantees will attempt to use the route (e.g., using an
explicit setup message if so required by the underlying networks).
In Section 4 we describe additional services that may be provided to
...
... routing loops may occur as a result of using an inconsistent map of
the network at different domains. Therefore, the use of
confederations with hop-by-hop ...
... comparison, PV can accommodate different confederation definitions
because looping is avoided by the use of full path information.
Consistent network maps are not needed at each route server, since
route ...
... number of domains requiring special routes simultaneously through the
same part of the network is small relative to the total population.
...
...
The essential dilemma is that networks are not organized in a nicely
geographical or topologically consistent manner (e.g., it is not
effective to ask for all networks ...
... networks are not organized in a nicely
geographical or topologically consistent manner (e.g., it is not
effective to ask for all networks going east-west that are within a
certain north-south region of the target), hence a source domain ...
... also want to provide more accurate route information for long
distance communications that entails more than a few network hops.
Reverse path update (RPU) is a mechanism for sending dynamic status
...
...
In this way, sources will receive status information from regions of
the network through which they maintain active routes, even if those
regions are more than k hops away. Using such a scheme, k could be
...
... NR and the SDR components, must
be able to determine what forwarding mechanism to use. That is, when
presented with a network layer PDU, such a BR should be able to make
...
... be handled by the NR or the SDR component. Discrimination mechanisms
are dependent on whether the new network layer introduced by the SDR
component is built on top of, or in parallel with, the network ...
... network layer introduced by the SDR
component is built on top of, or in parallel with, the network layers
supported by the NR component. Once the discrimination is made,
...
... 3. Packet Forwarding:
We should consider replacing the current IDPR-style network
layer (which contains a global path identifier ...
... Reachability Information:
Currently IDRP distributes network reachability information
within updates, whereas IDPR only distributes domain ...
... IDPR uses a domain name service
function to map network numbers to domain numbers; the latter
is needed to make the routing ...
... is needed to make the routing decision. We should consider
obtaining the network reachability and domain information in
a unified manner.
...
... Applicability to Various Network Layer Protocols ...
... The proposed architecture is designed to accommodate such existing
network layer protocols as IP ([Postel81]), CLNP ...
... ST2-90]). In addition, we intend for this architecture to
support future network layer mechanisms, e.g., Clark and Jacobson's
proposal or Braden and Casner's Integrated Services ...
... different types of services offered is matched by the ability of a
particular network layer protocol to unambiguously express requests
for such different types of services, the capability of the
...
... architecture will have equal importance for
different network layer protocols. On the other hand, this
architecture is designed to serve the future global internetworking
...
... architecture is designed to serve the future global internetworking
environment. The extensive research and development currently
underway to implement and evaluate network mechanisms for different
types of service suggests that future networks ...
... network mechanisms for different
types of service suggests that future networks will offer such
services.
...
... issue of single versus multiple protocols. The architecture does not
make any assumptions about whether each network layer is going to
have its own inter-domain routing ...
... have its own inter-domain routing protocol, or a single inter-domain
routing protocol will be able to cover multiple network layers
[Footnote: Similar issue already arose with respect to the intra-
domain ...
... domain routing protocol covering multiple network layers, or by
multiple inter-domain routing protocols (with the same architecture ...
... inter-domain routing protocols (with the same architecture)
tailored to a specific network layer [Footnote: If the single
protocol strategy is adopted, then it is likely that IDRP ...
... route
management protocols. In addition, a network management entity must
describe local configuration information ...
... Intra-Domain Routing Exchange Protocol for use in Conjunction with the protocol for providing the Connectionless-mode Network Service (ISO 8473)", ISO/IEC 10589. ...
... "Protocol for providing the connectionless-mode network service", ISO 8473, 1988. ...
... Jaffee, J., and F. Moss, "A Responsive Distributed Routing Algorithm for Computer Networks", IEEE Transactions on Communications, July 1982. ...