prefix
Click on the red underlined text to get to the source
...
This document refers to the term "prefix" throughout. In the current
classless Internet (see [CIDR ...
... class A, B, or C networks
may be referred to by merely a prefix and a mask, so long as such a
block of networks begins and ends on a power-of-two boundary. For
...
...
The term "prefix" as it is used here is equivalent to "CIDR block",
and in simple terms may be thought of as a group of one ...
... AS is a connected group of one or more IP prefixes run by one
or more network operators which has a SINGLE and CLEARLY DEFINED
...
...
ASX knows how to reach a prefix called NET1. It does not matter
whether NET1 belongs to ASX or to some other AS which exchanges
...
... The term AS is often confused or even misused as a convenient way of
grouping together a set of prefixes which belong under the same
administrative umbrella, even if within that group of prefixes ...
... prefixes which belong under the same
administrative umbrella, even if within that group of prefixes there
are various different routing policies. Without exception, an AS ...
... AS per classful network (the IDEAL situation is to have one
prefix, containing many longer prefixes, per AS). This may mean that
...
... network (the IDEAL situation is to have one
prefix, containing many longer prefixes, per AS). This may mean that
some re-engineering may be required in order to apply the criteria
...
... registration authority in order to minimize the number of advertised
prefixes from your AS. In the perfect world that number can, and
should, be as low as one.
...
... AS
As a general rule, one should try to place as many prefixes as
possible within a given AS, provided all of them conform to the
...
... AS of the provider. The site's prefix has exactly the same rout-
ing policy as the other customers of the site's service
provider ...
... rate AS must be created for the affected prefixes. This situa-
tion is rare and should almost never happen. Very few stub sites
require different routing policies ...
...
Again, a separate AS is not needed; the prefixes should be
placed in an AS of the site's provider ...
... Here multi-homed is taken to mean a prefix or group of prefixes
which connects to more than one service provider (i.e. more than
...
...
An AS is required; the site's prefixes should be part of a
single AS, distinct from the ASes ...
... decisions. Nevertheless, it may occasionally be necessary to split
up an AS or a prefix into two ASes for policy reasons. Those making
external policy may request the network operators ...
... changes, but the final decision is up to those network operators
who manage the prefixes in question, as well as the ASes containing
them. This is, of course, a trade off -- it will not always be
...
...
Generally, a prefix can should belong to only one AS. This is a
direct consequence of the fact that at each point in the Internet ...
... routing policy for traffic destined to each
prefix. In the case of an prefix which is used in neighbor peering
...
... traffic destined to each
prefix. In the case of an prefix which is used in neighbor peering
between two ASes ...
...
With the introduction of aggregation it should be noted that a prefix
may be represented as residing in more than one AS, however, this is
...