1 - 2 - 4 - 8 - A - B - C - D - E - F - G - H - I - L - M - N - O - P - Q - R - S - T - U - V - W - X
Address Prefix
Click on the red underlined text to get to the source
... Level 2 intermediate systems route based on address prefixes,
preferring the longest matching prefix, and preferring internal
routes ...
... routing domain boundary that have advertised external
address prefixes into the level 2 subdomain. A level 2 router may
also be operating as a level 1 router ...
... Level 2 routing acts on address prefixes, using the longest address
prefix that matches the destination address;
...
... Level 2 routing acts on address prefixes, using the longest address
prefix that matches the destination address;
...
... domain, level 2
routing routes according to address prefixes. In this case, there is
considerable potential advantage (in terms of reducing the amount of
routing information ...
... considerable potential advantage (in terms of reducing the amount of
routing information that is required) if the number of address
prefixes required to describe any particular set of external
destinations can be minimized. Efficient routing ...
... routing with IDRP similarly
also requires minimization of the number of address prefixes needed
to describe specific destinations. In other words, addresses ...
...
Level 2 routing is based upon address prefixes. Level 2 routers
(ISs) distribute, throughout the level 2 subdomain, the area
...
... addresses of the level 1 areas to which they are attached (and any
manually configured reachable address prefixes). Level 2 routers
compute next-hop ...
... routers
compute next-hop forwarding information to all advertised address
prefixes. Level 2 routing is determined by the longest advertised
address prefix ...
... address
prefixes. Level 2 routing is determined by the longest advertised
address prefix that matches the destination address.
...
... At routing domain boundaries, address prefix information is exchanged
with other routing domains ...
... Alternatively, should the routing domain "own" an address prefix and
assign area addresses based upon it, boundary routing information ...
... group
of subscribers each to be assigned an address prefix from a shorter
prefix assigned to their provider ...
... (inter-domain) traffic. A short address prefix may be assigned to
the provider, which then assigns slightly longer prefixes ...
... compared to the number of routing domains and address prefixes that
can conveniently and efficiently be handled via dynamic inter-domain
routing protocols. As the Internet ...
... assign RD identifiers underneath their unique address prefix (the
reserved field is left to accommodate future growth and to provide
...
...
In the second case, each other provider sees a single address prefix
for the local provider which encompasses the new subscriber ...
... routing information to identify the
new subscriber's address prefix. Thus, the advantages primarily
benefit other providers which maintain routing information about this
...
... subscriber domains, based on
a single (shorter length) address prefix assigned to the provider.
For example, given the GOSIP Version 2 ...
... NSAP formats. This
results in direct providers advertising to other providers (both
direct and indirect) a small fraction of the number of address
prefixes that would be necessary if they enumerated the individual
prefixes of the subscriber ...
... service from one or more indirect providers and exchanging routing
information with other direct providers. In general, providers will
want to handle as few address prefixes as possible to keep costs low.
In the Internet environment, subscriber ...
... provider, when announcing the addresses that it can reach to other
providers, to use a single address prefix to describe a large number
of NSAP addresses corresponding to multiple routing ...
... connection to a provider,
and to assign a single address prefix to each area within its routing
domain ...
... providers in Europe, and one in the far east, then MBII may make use
of six different address prefixes. Each area within MBII would be
assigned a single address prefix based on the nearest connection ...
... of six different address prefixes. Each area within MBII would be
assigned a single address prefix based on the nearest connection.
...
... provider announces that it can reach
all of the NSAPs based on its own address prefix, which only includes
some of the NSAPs within MBII. If the connection ...
...
There are other possible solutions as well. A third approach is to
assign each multi-homed organization a single address prefix, based
on one of its connections to a provider ...
... routing domains which are attached to both). Rather
than getting two address prefixes (such as two AA values assigned
under the GOSIP address space ...
... customers with addresses that are not based on
its own address prefix, and how such non-local addresses will be
...
... address allocations. In this case, all addresses reachable in the
XYZ Corporation can be described by a single address prefix (implying
that router M only needs to be configured with a single address
prefix ...
... address prefix (implying
that router M only needs to be configured with a single address
prefix to represent the addresses reachable over this point-to-point
link). All addresses ...
... point-to-point
link). All addresses reachable in MBII can be described by six
address prefixes (implying that router X needs to be configured with
six address prefixes ...
... address prefixes (implying that router X needs to be configured with
six address prefixes to represent the addresses reachable over the
point-to-point link ...
... address abstraction requirements
beyond those inherent in the address prefixes exchanged across the
private link.
...
... routing domain use a
single address prefix assigned to that domain. Specifically, this
allows the set of all NSAP addresses ...
... single-homed routing domains use an address prefix based on its
connectivity to a public service provider. We recommend that zero-
...
... NSAP addresses for use within the U.S. portion of the Internet are
expected to be based primarily on two address prefixes: the ICD=0005
format used by The U.S. Government, and the DCC ...
... provider. We therefore strongly
recommend that addresses be assigned hierarchically, based on address
prefixes assigned to individual providers.
...
... addresses that are not based on
the provider's own address prefix, and how such non-local addresses
...
... prefix for its own RDIs. In all other
cases a provider should use the address prefix that it uses for
assigning addresses to systems within the provider ...