Who is Your Gte Routing Number Customer?

Network Working Group D. Cansever
Request for Comments: 2333 GTE Laboratories, Inc.
Category: Standards Track April 1998

NHRP Protocol Applicability Statement

Status of this Memo

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. 2. Introduction

This document summarizes the key features of NHRP. Introduction

This document summarizes the key features of NHRP. 3. Key Features

NHRP provides a mechanism to obtain the NBMA network address of the
destination, or of a router along the path to the destination. When a source generates a setup packet, the first border router along the specified source route checks the setup request, and if accepted, installs routing information; this information includes a path ID, the previous and next hops, and whatever other accounting-related information the particular domain requires. LISs, the source station must
forward data packets to a router that is a member of multiple LISs,
even though the source and destination stations may be on the same
logical NBMA network. ᠎Th is a​rt​ic​le has been do᠎ne with GSA Conte nt᠎ Generator DE᠎MO .

Please note that you must have Direct Deposit going into the account you enroll in. Recipient bank account number. It can be found on the checks, and sometimes the bank or credit union has it on their website. NHRP can be used in host-host, host-router and router-host
communications. As such,
NHRP will be used in resolving the ATM addresses of MPOA packets
destined outside the originating subnet. NHRP is specified for resolving the destination NBMA addresses of IP
datagrams over IP subnets within a large NBMA cloud. To this goal, NHRP provides the
source with the NBMA address of the destination, if the destination
is directly attached to the NBMA. If source routing exhibits route locality, the source is more likely to use other routes going through the node in question; in any case the overhead of the information about other links will be minimal. Moreover, this is perhaps really not an important difference, since we are more concerned with the number of messages than with the number of bits (because of compression and greater link bandwidth, as well as the increased physical stability of links). Finally, some of the transit constraints (e.g., path sensitive constraints) can be expressed in a more concise form in PV (see aggregation discussion below).

In this case, NHRP would avoid intermediate routers in the
multicast path. RFC 2333 NHRP Protocol Applicability April 1998

with an inter-LIS address resolution mechanism at the end of which
both stations can exchange packets without having to use the services
of intermediate routers. Moreover, unless the architecture employs incremental updates, where only changes to the routing information are propagated, the storage overhead has direct impact on the bandwidth overhead of the architecture since the exchange of routing information constitutes most of the bandwidth overhead. Therefore, to allow faster adaptation to changes in the operational status of routing facilities, the SDR component allows the source domain to switch to a route computed by the NR component, if failure along the source- demand route is detected (either during the route installation phase, or after the route is installed), and if policy permits use of the NR route. If the destination station is not
attached to the NBMA, then NHRP provides the source with the NBMA
address of an exit router that has connectivity to the destination. The scalability of NHRP can be analyzed at
three distinct levels:

o Client level
o LIS level
o Domain level

At the the Client level, the scalability of NHRP is affected by the
processing and memory limitations of the NIC that provides interface
to the NBMA network.

If the destination station is not part of the
logical NBMA network, NHRP provides the source with the NBMA address
of the current egress router towards the destination. Footnote: Packet forwarding along routes produced by the NR component can be accomplished by either source routing or hop-by-hop routing. Firstly, NHRP avoids the need to go through extra hops of routers
when the Source and Destination belong to different Logical Internet
Subnets (LIS). NHRP for router-router
communication that avoids persistent forwarding loops will be
addressed in a separate document. This is further discussed in Section 5.

The most prominent feature of NHRP is that it avoids extra router
hops in an NBMA with multiple LISs. In general, the selection made by the routing protocol
would often reflect a desirable attribute, such as identifying the
exit router that induces the least number of hops in the original
routed path. RFC 2333 NHRP Protocol Applicability April 1998

NHRP is defined for avoiding extra hops in the delivery of IP packets
with a single destination.

Leave a Comment