1 - 3 - 4 - 7 - 8 - A - B - C - D - E - F - G - H - I - L - M - N - O - P - Q - R - S - T - U - V - W
tunnel
Click on the red underlined text to get to the source
... node of the LSP, these paths can
be treated as tunnels, tunneling below normal IP routing and
...
... filtering mechanisms. When an LSP is used in this way we refer to it
as an LSP tunnel.
LSP tunnels ...
... LSP tunnel.
LSP tunnels allow the implementation of a variety of policies related
to network performance ...
... to network performance optimization. For example, LSP tunnels can be
automatically or manually routed away from network failures,
...
... network failures,
congestion, and bottlenecks. Furthermore, multiple parallel LSP
tunnels can be established between two nodes, and traffic between the
...
... traffic between the
two nodes can be mapped onto the LSP tunnels according to local
policy. Although traffic engineering (that is, performance ...
... The purpose of this document is to describe the use of RSVP to
establish LSP tunnels. The intent is to fully describe all the
objects, packet formats, and procedures required to realize
...
... interoperable implementations. A few new objects are also defined
that enhance management and diagnostics of LSP tunnels.
The document also describes a means of rapid node ...
... onto a label-switched path in this way, we call the LSP an "LSP
Tunnel". When labels are associated with traffic flows, it becomes
possible for a router ...
... signaling protocol model uses downstream-on-demand label
distribution. A request to bind labels to a specific LSP tunnel is
initiated by an ingress node through the RSVP ...
...
An advantage of using RSVP to establish LSP tunnels is that it
enables the allocation of resources along the path. For example,
bandwidth ...
... enables the allocation of resources along the path. For example,
bandwidth can be allocated to an LSP tunnel using standard RSVP
reservations and Integrated Services ...
... TUNNEL_IPv6 have been defined to support the
LSP tunnel feature. The semantics of these objects, from the
perspective of a node ...
... label switched path, is that traffic
belonging to the LSP tunnel is identified solely on the basis of
packets arriving from the PHOP or "previous hop" (see [1]) with the
...
... address. When we refer to these objects generically, we use the
qualifier LSP_TUNNEL.
In some applications it is useful to associate sets of LSP tunnels ...
... TUNNEL.
In some applications it is useful to associate sets of LSP tunnels.
This can be useful during reroute operations or to spread a traffic
trunk over multiple paths. In the traffic engineering ...
... traffic engineering application
such sets are called traffic engineered tunnels (TE tunnels). To
...
... traffic engineered tunnels (TE tunnels). To
enable the identification and association of such LSP tunnels ...
... tunnels). To
enable the identification and association of such LSP tunnels, two
identifiers are carried. A tunnel ID ...
... LSP tunnels, two
identifiers are carried. A tunnel ID is part of the SESSION object.
The SESSION ...
... Operation of LSP Tunnels ...
... This section summarizes some of the features supported by RSVP as
extended by this document related to the operation of LSP tunnels.
These include: (1) the capability to establish LSP tunnels with or
...
... extended by this document related to the operation of LSP tunnels.
These include: (1) the capability to establish LSP tunnels with or
without QoS requirements ...
... QoS requirements, (2) the capability to dynamically reroute
an established LSP tunnel, (3) the capability to observe the actual
route traversed by an established LSP tunnel ...
... LSP tunnel, (3) the capability to observe the actual
route traversed by an established LSP tunnel, (4) the capability to
identify and diagnose LSP tunnels, (5) the capability to preempt an
...
... route traversed by an established LSP tunnel, (4) the capability to
identify and diagnose LSP tunnels, (5) the capability to preempt an
established LSP tunnel under administrative policy control ...
... identify and diagnose LSP tunnels, (5) the capability to preempt an
established LSP tunnel under administrative policy control, and (6)
the capability to perform downstream ...
... node has knowledge of a route that has high likelihood
of meeting the tunnel's QoS requirements, or that makes efficient use
...
... node
can receive information about the actual route that the LSP tunnel
traverses. The sender node ...
... Resv message containing a LABEL object uses
that label for outgoing traffic associated with this LSP tunnel. If
the node is not the sender ...
... node will use to identify incoming
traffic associated with this LSP tunnel. This label also serves as
shorthand for the Filter Spec. The node ...
... requirements for Traffic Engineering is the capability to
reroute an established TE tunnel under a number of conditions, based
on administrative policy. For example, in some contexts, an
...
... on administrative policy. For example, in some contexts, an
administrative policy may dictate that a given TE tunnel is to be
rerouted when a more "optimal" route becomes available. Another
...
... route becomes available. Another
important context when TE tunnel reroute is usually required is upon
failure of a resource along the TE tunnel's established path. Under
...
... context when TE tunnel reroute is usually required is upon
failure of a resource along the TE tunnel's established path. Under
some policies, it may also be necessary to return the TE tunnel to
...
... failure of a resource along the TE tunnel's established path. Under
some policies, it may also be necessary to return the TE tunnel to
its original path when the failed resource becomes re-activated.
...
... traffic, or
adversely impact network operations while TE tunnel rerouting is in
progress. This adaptive and smooth rerouting ...
... rerouting requirement
necessitates establishing a new LSP tunnel and transferring traffic
from the old LSP tunnel ...
... LSP tunnel and transferring traffic
from the old LSP tunnel onto it before tearing down the old LSP
tunnel. This concept is called "make-before-break." A problem can
...
... traffic
from the old LSP tunnel onto it before tearing down the old LSP
tunnel. This concept is called "make-before-break." A problem can
arise because the old and new LSP tunnels ...
... LSP
tunnel. This concept is called "make-before-break." A problem can
arise because the old and new LSP tunnels might compete with each
other for resources on network segments ...
... Depending on availability of resources, this competition can cause
Admission Control to prevent the new LSP tunnel from being
established. An advantage of using RSVP to establish LSP tunnels ...
... LSP tunnel from being
established. An advantage of using RSVP to establish LSP tunnels is
that it solves this problem very elegantly.
...
... links that are common to the old and new LSPs, resources used
by the old LSP tunnel should not be released before traffic is
transitioned to the new LSP tunnel ...
... LSP tunnel should not be released before traffic is
transitioned to the new LSP tunnel, and reservations should not be
counted twice because this might cause Admission Control to reject
...
... counted twice because this might cause Admission Control to reject
the new LSP tunnel.
A similar situation can arise when one wants to increase the
...
... A similar situation can arise when one wants to increase the
bandwidth of a TE tunnel. The new reservation will be for the full
amount needed, but the actual allocation needed is only the delta
...
... bandwidth request without changing the
SENDER_TEMPLATE, could result in a tunnel being torn down, depending
upon local policy.
...
... bandwidth and routing. The idea is that the old and new LSP tunnels
share resources along links which they have in common. The
...
... links which they have in common. The
LSP_TUNNEL SESSION object is used to narrow the scope of the RSVP
...
... RSVP
session to the particular TE tunnel in question. To uniquely
identify a TE tunnel, we use the combination of the destination IP
address ...
... session to the particular TE tunnel in question. To uniquely
identify a TE tunnel, we use the combination of the destination IP
address (an address of the node ...
... destination IP
address (an address of the node which is the egress of the tunnel), a
Tunnel ID, and the tunnel ...
... node which is the egress of the tunnel), a
Tunnel ID, and the tunnel ingress node's IP address ...
... node's IP address, which is placed
in the Extended Tunnel ID field.
During the reroute or bandwidth ...
...
During the reroute or bandwidth-increase operation, the tunnel
ingress needs to appear as two different senders to the RSVP ...
... links that are not held in common, the new Path message
is treated as a conventional new LSP tunnel setup. On links held in
common, the shared SESSION ...
... LSP Tunnel related Message Formats ...
... LSP Tunnel related Objects ...
...
Indicates that a local repair mechanism is in use to
maintain this tunnel (usually in the face of an outage
of the link it was previously routed over).
...
...
Indicates that a local repair mechanism is in use to
maintain this tunnel (usually in the face of an outage
of the link it was previously routed over).
...
... notification
3 Tunnel locally repaired
...
... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 tunnel end point address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
...
... address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MUST be zero | Tunnel ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Extended Tunnel ID ...
... Tunnel ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Extended Tunnel ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
...
... identifier used in the SESSION that remains constant
over the life of the tunnel.
Extended Tunnel ID ...
... identifier used in the SESSION that remains constant
over the life of the tunnel. Normally set to all zeros.
Ingress nodes that wish to narrow the scope of a SESSION ...
... | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MUST be zero | Tunnel ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
...
... identifier used in the SESSION that remains constant
over the life of the tunnel.
Extended Tunnel ID ...
... identifier used in the SESSION that remains constant
over the life of the tunnel. Normally set to all zeros.
Ingress nodes that wish to narrow the scope of a SESSION ...
... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 tunnel sender address |
...
...
This section describes how to setup a tunnel that is capable of
maintaining resource reservations (without double counting) while it
...
... node forms a
SESSION object, assigns a Tunnel_ID, and places its IPv4 address in
the Extended_Tunnel ...
... Tunnel_ID, and places its IPv4 address in
the Extended_Tunnel_ID. It also forms a SENDER_TEMPLATE and assigns
a LSP ...
... SENDER_TEMPLATE and assigns
a LSP_ID. Tunnel setup then proceeds according to the normal
procedure.
...
... Path message as follows. The existing SESSION
object is used. In particular the Tunnel_ID and Extended_Tunnel_ID
are unchanged. The ingress node ...
... SESSION
object is used. In particular the Tunnel_ID and Extended_Tunnel_ID
are unchanged. The ingress node picks a new LSP ...
... RA C-Type includes all the same fields as the LSP_TUNNEL
C-Type. Additionally it carries resource affinity information. The
...
... SE Style desired
This flag indicates that the tunnel ingress node may
choose to reroute this tunnel ...
... tunnel ingress node may
choose to reroute this tunnel without tearing it down.
A tunnel egress node ...
... choose to reroute this tunnel without tearing it down.
A tunnel egress node SHOULD use the SE Style when
...
... set of attribute filters
associated with a tunnel any of which renders a link acceptable
(with respect to this test). A null set (all bits ...
... set of attribute filters
associated with a tunnel all of which must be present for a
link to be acceptable (with respect to this test). A null set
...
... SE Style desired
This flag indicates that the tunnel ingress node may
choose to reroute this tunnel ...
... tunnel ingress node may
choose to reroute this tunnel without tearing it down.
A tunnel egress node ...
... choose to reroute this tunnel without tearing it down.
A tunnel egress node SHOULD use the SE Style when
...
... of an incoming label. For this reason an administration may wish to
limit the domain over which LSP tunnels can be established. This can
be accomplished by setting filters on various ports ...