wdiff draft-ietf-mpls-ldp-state-01.txt draft-ietf-mpls-ldp-state-02.txt

MPLS Working Group Liwen Wu Christophe Boscher
Internet Draft Pierrick Cheval
Expiration Date: December 1999 Christophe Boscher April 2000 Alcatel USA France

Liwen Wu
Cisco

Eric Gray
Lucent

June

October 1999

LDP State Machine
draft-ietf-mpls-ldp-state-01.txt

0.
draft-ietf-mpls-ldp-state-02.txt

Status of this Memo

This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.

Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet- Drafts.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts Internet-Drafts as reference
material or to cite them other than as "work in progress."

The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt

The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.

Distribution of this memo is unlimited.

1. Abstract

In the current LDP draft [Ref5], specification [4], there is no state machine
specified for processing the LDP messages. We think that defining a
common state machine is very important for interoperability between
different ldp implementations.

This draft document provides state machine tables for ATM switch LSRs. We
begin in section 2 by defining a list of terminologies. Then in
section 3, we propose two sets of state machine tables for ATM switch
LSRs which use downstream-on-demand mode, one method can be used for
non-vc mergable merge-able ATM LSRs, while the other one can be used for the
vc-mergable
vc-merge-able ATM LSRs. In section 4, we provides a state machine
for downstream mode ATM LSR.

We focus on the LDP state machines and the associated control blocks.
We not describe the "LDP controller" which is in charge of LDP
session initialization, address mapping messages management, routing
interface, etc. Specifically, the LDP specification [4] defines the
state machine for session management.

Even though the state machines in this document are specific for
ATM-LSR, they can be easily adapted for other types of LSRs.

2. Terminologies

- LDP-REQUEST: LDP Label Request message

- LDP-MAPPING: LDP Label Mapping message

- LDP-WITHDRAW: LDP Label Withdraw message

- LDP-RELEASE: LDP Label Release message

- LDP-ABORT: It is a LDP Abort message which is used to abort a LSP setup.

- LDP-NAK: It is a LDP Notification msg which is message used to reject a an LDP message.

3. State Machine for Downstream-on-Demand Mode

This draft focuses on the LDP state machines and the associated
control blocks. It does not describe the "LDP controller" which is
in charge of LDP session initialization, address mapping messages
management, routing interface, etc.

In this draft, we provide two sets of state machines: one for the ATM
LSR which does not have VC-merge capability, and the other one for
the ATM LSR which does have VC-merge capability.

State machine descriptions are given in terms of control blocks,
states, events, response actions and state transitions. Control
blocks contain the information that is required to support handling
of events. A control block may also contain any additional
information that is required either of any specific implementation or
in support of other required functions. In every case, additional
information required to support the procedures defined in the LDP
specification [4] or management objects defined in the LDP MIB [3]
would be stored in a specific LDP implementation - either as part of
the control block structure or in some other way.

The state machines cover both independent LSP control and ordered LSP
control.

The loop

Loop detection and loop prevention message will be processed in
the way as
specified in [Ref5]. [4]. The impact of loop detection and loop prevention
messages on a state transition transitions is left for further study.

3.0 An LSR's Behavior in the Case of a Next Hop Change

When there is a topology change and an LSR detects a new better next
hop for an LSP, it may behave in 2 different ways:

1) It tries to do a "local repair". This means that it extends the
LSP through the new next hop, releases the old path from this LSR
forward and then splices into this newly extended LSP.

2) If the LSP is created with the "pinned" option[Ref7,CR-LDP], option (CR-LDP[5]), the
LSR ignores the new next hop change, and the LSP stays unchanged. The
LSR may decide to send an LDP-MAPPING which contains the attribute
about this New Next Hop (NH) change.

3.1. ATM Switch LSR with NO VC-merge

In an MPLS domain where some ATM LSRs do not have VC-merge
capability, downstream-on-demand mode is required for these ATM
LSRs[Ref1]. LSRs
[1]. Also, "conservative label retention mode" is required in this case[Ref1].
case [1].

For each LSP, there are 2 kinds of state machines involves:

1) the LSP Control Block and its state machine which can be used to
handle normal LSP setup. It is created when the LSR receives a new
LDP Request and it is deleted when the LSP of this request is torn
down.

2) the Next Hop Trigger Control Block and its state machine which is
used to handle switching over to a better LSP through a different
next hop. It is created when the LSR decides to switch over to a
better next hop and it is deleted when the LSR finishes switching
over to the better next hop. This state machine uses a timer (and
has corresponding states) to ensure that switch over occurs in a
timely fashion.

3.1.1 LSP Control Block

For each LSP, an LSP_Control_Block is defined which may contain the
following information:

- Upstream Label Request ID(assigned ID (assigned by the upstream LSR), which
is the 'Message Id' in the Label Request Message received from the
upstream LSR.

- Downstream Label Request ID (assigned by this LSR itself), which
is 'Message Id' in the Label Request Message sent to the
downstrearm downstream
LSR.

- Upstream LDP Identifier

- Downstream LDP Identifier

- State

- FEC

- Upstream Label(assigned Label (assigned by this LSR)

- Downstream Label(assigned Label (assigned by the downstream LSR)

- Trigger Control Block Pointer, (Only used at the ingress LSR of a
LSP)which points to the control block that triggers setting up this
LSP or tearing down this LSP.

- Next Hop Control Block Pointer, which points to the control block
which is used for switching over to a better LSP.

The following index combinations can be used to locate a unique
LSP_Control_Block:

- Downstream Label and Downstream LDP Identifier, or

- Upstream Label and Upstream LDP Identifier, or

- Downstream Label Request ID and Downstream LDP Identifier

- Upstream Label Request ID and Upstream LDP Identifier

Here is the relationship between different control blocks, the detail
definition of Next Hop Trigger Block is described in section 3.1.6.

For example, an LSP which transit through (LSR-A, LSR-B, LSR-C,LSR- LSR-C, LSR-
D):

LSR-A ----> LSR-B ---> LSR-C ---> LSR-D
The control blocks in LSR-A are:

+-----------------------+
| Trigger Control Block |
| (e.g, by config) |
+-----------------------+
^
|(Trigger Control block pointer) |
|
+-----------------------+
| LSP Control Block |
+-----------------------+

When LSR-B detects a better next hop to LSR-D through LSR-E, and it
decides to switch over to it, so control blocks in LSR-B are:

3.1.2 States

This section describes the various states that are used in the state
machine for the ATM non VC-merge LSR.

-- IDLE

This is the initial LSP state, when the LSP_Control_Block is created.

-- RESPONSE_AWAITED

This state means that the LSR has received and processed an LDP-
REQUEST from an upstream LSR, or it has received an internal set up
request. It has sent a new LDP-REQUEST towards a downstream LSR. The
LSR is waiting for the LDP-MAPPING message from the downstream LSR.

-- ESTABLISHED

This state means that the LSR has received the LDP-MAPPING message from the
downstream LSR and the LSP is up and operational.

-- RELEASE_AWAITED

This state means that the LSR has sent a LDP-WITHDRAW message upstream and is
waiting for the LDP-RELEASE before freeing up the label resource.

3.1.3 Events

-- LDP Request

The LSR receives an LDP-REQUEST from an upstream LSR.

-- LDP Mapping

The LSR receives an LDP-MAPPING from a downstream LSR.

-- LDP Release

The LSR receives an LDP-RELEASE from an upstream LSR.

-- LDP Withdraw

The LSR receives an LDP-WITHDRAW from a downstream LSR.

-- LDP Upstream Abort

The LSR receives an LDP-ABORT from an upstream LSR.

-- LDP Downstream Nak NAK The LSR receives an LDP-NAK(notification) LDP-NAK (notification) from
an downstream LSR.

-- Upstream Lost
The LSR loses its LDP session with an upstream LDP peer.

-- Downstream Lost

The LSR loses its LDP session with a downstream LDP peer.

-- Internal SetUp

For some reason, e.g. a configuration request of a traffic
engineering tunnel, or recognizing a new FEC could trigger an
Internal SetUp event to set up a new LSP from this node.

-- Internal Destroy

The LSR send an Internal Destroy event to tear down an LSP.

-- Internal Cross-Connect

The LSR send an Internal Cross-Connect to splice two LSPs into one
LSP. This happens when a LSR switchs over to a better next hop

-- Internal New NH

The LSR decides to switch over the better next hop.

3.1.4 State Transitions

The following diagram describes briefly the state transitions.

+-------------------+
| |
+-------->| IDLE |<--------------+
| | | |
| +-------------------+ |(LDP Release)
|(LDP Upstream | |
| Abort) |(LDP Request) |(LDP Upstream Abort)
|(Downstream Lost) |(Internal SetUp) |
|(Downstream Nak) NAK) | |(LDP Downstream Nak) NAK)
|(Upstream Lost) v |(Upstream Lost)
| +-------------------+ |
| | | |
+---------| RESPONSE_AWAITED | |
| | |
+-------------------+ |
| |
|(LDP Mapping) |
| |
v |
+-------------------+ |
| | |
| ESTABLISHED |------------>--+
| | |
+-------------------+ |
| |
| |
|(LDP Withdraw) |
|(Downstream Lost) |
| |
v |
+-------------------+ |
| | |
| RELEASE_AWAITED |------------>--+
| |
+-------------------+

3.1.5 State Machine

3.1.5.1 State -- "IDLE"

State: IDLE
Event: LDP Request

New States: State: Depends upon the action routine

Actions:

If this LSR is the LSP Egress or Proxy Egress [Ref2] [2]

Then:
Choose an upstream label, connect this upstream label to the local
IP forwarding module, allocate the resources, send the LDP-MAPPING
message
upstream with the upstream label, and go to the new state
`ESTABLISHED'.

else
Obtain a next hop (or interface) with the FEC specified in the
LDP-REQUEST message,
LDP-REQUEST, propagate the LDP-REQUEST message, LDP-REQUEST, with newly assigned Message
ID by this LSR, towards the obtained next hop, and go to the new
state `RESPONSE_AWAITED'.

If the LSR uses the independent control mode[Ref2], mode [2], choose an
upstream label, connect this upstream label to the local IP
forwarding module, and send an LDP-MAPPING message upstream with the
upstream label.

If unable to process the request for any reason, issue an LDP-NAK
message to
the sender with the appropriate error code and delete the control
block.

State: IDLE

Event: LDP Mapping

New State: IDLE

Actions:

Ignore the event. It is an internal implementation error.

State: IDLE

Event: LDP Release

New State: IDLE

Actions:

Ignore the event. It is an internal implementation error.

State: IDLE

Event: LDP Withdraw

New State: IDLE

Actions:

Ignore the event. It is an internal implementation error.

State: IDLE

Event: LDP Upstream Abort

New State: IDLE

Actions:

Ignore the event. It is an internal implementation error.

State: IDLE

Event: LDP Downstream Nak NAK

New State: IDLE

Actions:

Ignore the event. It is an internal implementation error.

State: IDLE

Event: Upstream Lost

New State: IDLE

Actions:

Ignore the event. It is an internal implementation error.

State: IDLE

Event: Downstream Lost

New State: IDLE
Actions:

Ignore the event. It is an internal implementation error.

State: IDLE

Event: Internal SetUp

New State: RESPONSE_AWAITED

Actions:

Set up the Trigger Control Block pointer,

Obtain a next hop (or interface) with the FEC specified in the
Internal SetUp message, send a LDP-REQUEST towards the obtained next
hop, and go to the new state 'RESPONSE_AWAITED'. `RESPONSE_AWAITED'.

State: IDLE

Event: Internal Destroy

New State: IDLE

Actions:

Ignore. It is an internal implementation error.

State: IDLE

Event: Internal Cross-Connect

New State: IDLE

Actions:

Ignore. It is an internal implementation error.

State: IDLE

Event: Internal New NH

New State: IDLE

Actions:

Ignore. It is an internal implementaion implementation error.

3.1.5.2 State -- "RESPONSE_AWAITED"

State: RESPONSE_AWAITED

Event: LDP Request

New State: RESPONSE_AWAITED

Actions:

Ignore the event. It is an internal implementation error. A non VC
merge ATM LSR must create a new LSP control block for a new LDP
request.

State: RESPONSE_AWAITED

Event: LDP Mapping

New State: ESTABLISHED

Actions:

1) If the LSP is triggered by the local router(Trigger router (Trigger Control Block
Pointer is not zero), send event "Internal `Internal LSP UP" UP' to the Trigger
control block.

2) Else If the LSR uses the ordered control mode, choose an upstream
label.

3) Connect the upstream label to the downstream label. Allocate the
resources. propagate Propagate the LDP-MAPPING message upstream with the upstream
label.

If unable to process the message, disconnect the upstream label from
the downstream label, free the upstream label, release the resources,
send an LDP-RELEASE message downstream and an LDP-Nak LDP-NAK upstream with status
(No Label Resources[ref-5]), Resources [4]), and delete the LSP_Control_Block.

State: RESPONSE_AWAITED

Event: LDP Release

New State: IDLE

Actions:

If the LSR uses the independent control mode, free the upstream
label.

Send an LDP-ABORT message downstream and delete the
LSP_Control_Block. LSP_Control_Block.

Note: This should only occur if the LSR uses the independent control
mode. In the ordered control mode, no upstream label mapping will
have been sent corresponding to this LSP while waiting for a label
mapping from downstream.

State: RESPONSE_AWAITED

Event: LDP Withdraw

New State: RESPONSE_AWAITED

Actions:

Ignore the event. It's a protocol error from the downstream LSR.

State: RESPONSE_AWAITED

Event: LDP Upstream Abort

New State: IDLE

Actions:

If the LSR uses the independent control mode, free the upstream
label.

Send an LDP-ABORT message downstream.

Delete the LSP_Control_Block.

State: RESPONSE_AWAITED

Event: LDP Downstream Nak NAK

New State: Depends on the action routine

Actions:

1. If the LSP is triggered by the local router(Trigger router (Trigger Control Block
Pointer is not zero), send event "Internal `Internal LSP DOWN" DOWN' to the Trigger
control block.

2. Else If the LSR uses the independent control mode, send an LDP-
WITHDRAW message upstream and go to state 'RELEASE_AWAITED'. `RELEASE_AWAITED'.

If the LSR uses the ordered control mode, send an LDP-NAK message upstream.
Then delete the control block.

State: RESPONSE_AWAITED

Event: Upstream Lost

New State: IDLE

Actions:

If the LSR uses the independent control mode, free the upstream
label.

Send an LDP-ABORT downstream and delete the LSP_Control_Block.

State: RESPONSE_AWAITED

Event: Downstream Lost

New State: Depends on the action routine

Actions:

1. If the LSP is triggered by the local router(Trigger router (Trigger Control Block
Pointer is not zero), send event "Internal `Internal LSP DOWN" DOWN' to the trigger
control block.

2. Else, If the LSR uses the independent control mode, free the
upstream label and send an LDP-WITHDRAW upstream and go to state
'RELEASE_AWAITED'.
`RELEASE_AWAITED'.

If the LSR uses the ordered control mode, send an LDP-NAK
upstream(with upstream
(with a status No Route[Ref-5]) `No Route' [4]) and then delete the control block.

State: RESPONSE_AWAITED

Event: Internal SetUp

New State: RESPONSE_AWAITED

Actions:

Ignore, it is an internal implementation error.

State: RESPONSE_AWAITED

Event: Internal Destroy

New State: IDLE

Actions:

Send an LDP-ABORT downstream and delete the LSP_Control_Block.

State: RESPONSE_AWAITED

Event: Internal Cross-Connect

New State: RESPONSE_AWAITED

Actions:

Ignore the event. It is an internal implementation error.

State: RESPONSE_AWAITED

Event: Internal New NH

New State: RESPONSE_AWAITED

Actions:

Send LDP-ABORT to the old downstream, and send LDP-REQUEST to the new
next hop.

3.1.5.3 State --"ESTABLISHED"

State: ESTABLISHED

Event: LDP Request

New State: ESTABLISHED

Actions:

Ignore the event. It's an internal implementation error. For non VC-
merge ATM LSR, a new LSP control block is always created for each LDP
request.

State: ESTABLISHED

Event: LDP Mapping
New State: ESTABLISHED

Actions:

Process the LDP-MAPPING message, LDP-MAPPING, which may contain the new attributes of the
label mapping and then propagate the LDP-MAPPING message upstream.

State: ESTABLISHED

Event: LDP Release

New State: IDLE

Actions:

Disconnect the upstream label from the downstream label.

Free the upstream label.

Free the resources.

Send event "Internal Destroy" `Internal Destroy' to the Next Hop Trigger Block if it was
in the middle of switching over to the better next hop.

Propagate the LDP-RELEASE message downstream if the LSR is not the end of LSP
and delete the LSP_Control_Block.

State: ESTABLISHED

Event: LDP Withdraw

New State: Depends on the action routine.

Actions:

1) Free the resources and send LDP-RELEASE downstream.

2) If it is independent control mode, set the state to 'IDLE', `IDLE', create
a internal LDP Request with the information in the LSP_Control_Block,
and pass event 'LDP `LDP Request' to its own state machine.

3) Else for the ordered control mode

3.1)If the LSP is triggerd triggered to be setup by itself(e.g itself (e.g it is the
ingress LSR of this LSP), send event "Internal `Internal LSP NAK" NAK' to the
trigger control block and delete the control block

3.2) else, if it is triggered by the incoming LDP Request,
Disconnect the upstream label from the downstream label. And Propagate
the LDP-WITHDRAW message upstream and go to state
'RELEASE_AWAITED'. `RELEASE_AWAITED'.

3.3) If the LSP is in the middle of switching over to a better LSP,
send event 'Internal `Internal Destroy' to the state machine of its New Next
Hop LSP Control Block.

State: ESTABLISHED

Event: LDP Upstream Abort

New State: IDLE

Actions:

Disconnect the upstream label from the downstream label.

Free the upstream label.

Send event "Internal Destroy" `Internal Destroy' if the LSR was in the middle of
switching over to the better next hop.

Propagate an LDP-RELEASE message downstream and delete the LSP_Control_Block.

State: ESTABLISHED

Event: LDP Downstream Nak NAK

New State: ESTABLISHED

Actions:

Ignore the event. It is a protocol error from the downstream LSR.
The downstream LSR should always LSP-WITHDRAW msg to tear down the LSP
when the LSP is established.

State: ESTABLISHED

Event: Upstream Lost

New State: IDLE

Actions:

Disconnect the upstream label from the downstream label.

Free the upstream label.

Send event "Internal Destroy" `Internal Destroy' to the Next Hop Trigger Control Block
if it was in the middle of switching over to the better next hop.

Free the resources.

Propagate an LDP-RELEASE message downstream and delete the LSP_Control_Block.

State: ESTABLISHED

Event: Downstream Lost

New State: Depends on the actions

Actions:

1) If the LSP is triggered by the local router(Trigger router (Trigger Control Block
Pointer is not zero), send event "Internal `Internal LSP NAK" NAK' to the Trigger
control block and delete the control block.

2) Else, disconnect the upstream label from the downstream label.
Propagate an LDP-WITHDRAW message upstream and go to state
'RELEASE_AWAITED' `RELEASE_AWAITED' state.

3) Send event "Internal Destroy" `Internal Destroy' to the Next Hop Trigger Control
Block if it was in the middle of switching over to the better next
hop.

State: ESTABLISHED

Event: Internal Setup

New State: ESTABLISHED

Actions:

Ignore, it is an internal implementation error.

State: ESTABLISHED

Event: Internal Destroy

New State: IDLE

Actions:

Disconnect the upstream label from the downstream label if it is not
the ingress of the LSP.

Free the resources.

Send an LDP-RELEASE message downstream and delete the LSP_Control_Block.

State: ESTABLISHED

Event: Internal Cross-Connect

New State: ESTABLISHED

Actions:

Connect the upstream label to the downstream label

May need to send a new LDP-MAPPING upstream with the attributes from
the new next hop.

Reset Trigger Control Block Pointer to zero.

State: ESTABLISHED

Event: Internal New NH

New State: ESTABLISHED

Actions:

1) If the LSR was in the middle of switching over to a better next
hop(Next
hop (Next Hop Trigger Control Block Pointer is not zero), it send
"Internal
`Internal New NH" NH' to that control block.

2) Else, create a new Next Hop Trigger Control Block, set Next Hop
Trigger Control Block pointer which points this control block. And
then pass "Internal `Internal New NH" NH' to this control block.

3.1.5.4 State --"RELEASE_AWAITED"

State RELEASE_AWAITED

Event LDP Request

New State: RELEASE_AWAITED

Actions:

Ignore the event. It is an internal implementation error.

State

State: RELEASE_AWAITED

Event

Event: LDP Mapping

New State: RELEASE_AWAITED

Actions:

It is an protocol error from the downstream LDP peer, but anyway send
a LDP-RELEASE downstream.

State

State: RELEASE_AWAITED

Event

Event: LDP Release

New State: IDLE

Actions:

1) Free the upstream label

2) Delete the control block.

State

State: RELEASE_AWAITED

Event

Event: LDP Withdraw

New State: RELEASE_AWAITED

Actions:

It is an protocol error from the downstream LDP peer, but send a
LDP-RELEASE anyway.

State

State: RELEASE_AWAITED

Event

Event: LDP Upstream Nak NAK

New State: IDLE

Actions:

1) Free the upstream label

2) Delete the control block.

State

State: RELEASE_AWAITED

Event

Event: LDP Downstream Nak NAK

New State: RELEASE_AWAITED

Actions:

Ignore the event. Continue waiting for the LDP-RELEASE from upstream.

State

State: RELEASE_AWAITED

Event

Event: Upstream Lost

New State: IDLE

Actions:

1) Free the upstream label

2) Delete the control block.

State

State: RELEASE_AWAITED

Event

Event: Downstream Lost

New State: RELEASE_AWAITED

Actions:

Ignore the event. Continue waiting for the LDP-RELEASE from upstream.

State

State: RELEASE_AWAITED

Event

Event: Internal SetUp

New State: RELEASE_AWAITED

Actions:

Ignore the event. It is an internal implementation error.

State

State: RELEASE_AWAITED

Event

Event: Internal Destroy
New State: RELEASE_AWAITED

Actions:

Ignore the event. It is an internal implementation error.

State

State: RELEASE_AWAITED

Event

Event: Internal Cross-Connect

New State: RELEASE_AWAITED

Actions:

Ignore the event. It is an internal implementation error.

3.1.6 Handling the Next Hop Change

When an LSR detects a better next hop, it may decides to establish a
new LSP through this next hop. For example, an LSR is configured as
"local repair", or the LSR is configured as "global repair" and it is
the ingress end of a LSP. It can then create a Next Hop Trigger
Control Block and use the state machine of Next Hop Trigger Control
Block to establish a new LSP through the better next hop.

3.1.6.1 Next Hop Trigger Control Block

-- State

-- LSP Control Block Pointer, which points to the original LSP
control block.

-- New Next Hop LSP Control Block Pointer, which points to the LSP
Control Block that is setting up an LSP through the new next hop.

3.1.6.2 States

-- IDLE

This is the initial LSP state, when the Trigger_Control_Block is
created.

-- NEW_NH_RETRY

This is the state where an LSR waits for a retry timer to expire and
then tries to establish an LSP through a new next hop.

-- NEW_NH_RESPONSE_AWAITED

This is the state where an LSR is in the middle of establishing a new
LSP through a new next hop. It has triggered a LSP control block to
send an LDP-REQUEST towards the new next hop and is waiting for the
LDP-MAPPING message.
LDP-MAPPING.

3.1.6.3 Events

-- Internal New NH

The LSR detects there is a new next hop for a FEC.

-- Internal Retry Timeout

The LSP retry timer expires.

-- Internal LSP UP

The LSP to the new Next Hop is UP

-- Internal LSP NAK

The LSP through the new next hop could not get set up

-- Internal Destroy

This event is triggered when the LSR lost the LDP session with its
upstream neighbor.

3.1.6.4 State Transition for next hop change

|
|
|
| Internal New NH
|
v
+---------------------+
| | Internal destroy
| NEW_NH_RETRY |--------------
| | |
+---------------------+ |
| |
| |
| (Internal retry timeout) |
| |
v |
+---------------------+ |
| | Internal |
| NEW_NH_RESPONSE | Destroy |
| _AWAITED |-------------|
| | |
+---------------------+ |
| |
| (Internal LSP UP) |
| (Internal LSP NAK) |
v v
the control block is deleted

3.01.3 State Machine

3.01.3.1 State -- "IDLE"

State: IDLE

Event: Internal New NH

New States: State: NEW_NH_RETRY

Actions:

Start the LSP retry timer and go to the 'NEW_NH_RETRY' `NEW_NH_RETRY' state.

State: IDLE

Event: Internal retry timeout
New States: State: IDLE

Actions:

Ignore. It is an internal implementation error.

State: IDLE

Event: Internal LSP UP

New States: State: IDLE

Actions:

Ignore. It is an internal implementation error.

State: IDLE

Event: Internal LSP NAK

New States: State: IDLE

Actions:

Ignore. It is an internal implementation error.

State: IDLE

Event: Internal destroy

New States: State: IDLE

Actions:

Ignore. It is an internal implementation error.

3.01.3.2 State -- "NEW_NH_RETRY"

State: NEW_NH_RETRY

Event: Internal New NH

New States: State: NEW_NH_RETRY

Actions:

Restart the LSP retry timer.

State: NEW_NH_RETRY

Event: Internal retry timeout

New States: State: NEW_NH_RESPONSE_AWAITED

Actions:

If the new next hop is the same one as the old next hop, delete the
control block.

Otherwise, create an LSP control block which will try to establish a
new LSP through the new next hop. And send event "Internal Setup" `Internal Setup' to
its state machine.

State: NEW_NH_RETRY

Event: Internal LSP UP

New States: State: NEW_NH_RETRY

Actions:

Ignore. It is an internal implementation error.

State: NEW_NH_RETRY

Event: Internal LSP NAK

New States: State: NEW_NH_RETRY

Actions:

Ignore. It is an internal implementation error.

State: NEW_NH_RETRY

Event: Internal destroy

New States: State: IDLE

Actions:

Stop the timer and delete the control block.

3.01.3.3 State -- "NEW_NH_RESPONSE_AWAITED"
State: NEW_NH_RESPONSE_AWAITED

Event: Internal New NH

New States: State: NEW_NH_RETRY

Actions:

Restart the LSP retry timer, send "Internal destroy" `Internal destroy' to the control
block of the LSP for the new next hop and go to the 'NEW_NH_RETRY' `NEW_NH_RETRY'
state.

State: NEW_NH_RESPONSE_AWAITED

Event: Internal retry timeout

New States: State: NEW_NH_RESPONSE_AWAITED

Actions:

Ignore. It is an internal implementation error.

State: NEW_NH_RESPONSE_AWAITED

Event: Internal LSP UP

New States: State: IDLE

Actions:

Send event "Internal cross-connect" `Internal cross-connect' event to the LSP control block of
the new next hop.

Send event "Internal destroy" `Internal destroy' event to the original LSP control
block.

Then delete the control block.

State: NEW_NH_RESPONSE_AWAITED

Event: Internal LSP NAK

New States: State: IDLE

Actions:

Delete the control block.

State: NEW_NH_RESPONSE_AWAITED

Event: Internal destroy

New States: State: IDLE

Actions:

Send event "Internal destroy" `Internal destroy' the control block for the new LSP
through the new next hop.

3.1.7 LDP Related Message Handling

- If an LSR receives an LDP-REQUEST from an upstream LSR:

a) If this is a duplicate request, discard the msg. message. A duplicate
request means that there is a LSP_Control_Block which has same FEC,
same Upstream Label Request ID and same Upstream LDP Session
Identifier.

b) Otherwise, create a new LSP_Control_Block, store the relevant
information from the message into the control block, then pass the
event `LDP Request' to its state machine.

- If an LSR receives an LDP-MAPPING from a downstream LSR:

a) Extract the 'Label Request Message ID' field and from the LDP-
MAPPING message.
MAPPING.

b) Find an LSP_Control_Block which has the same Downstream Label
Request ID and the same Downstream LDP Session Identifier.

c) If an LSP_Control_Block is found, pass the event `LDP Mapping' to
its state machine.

d) If there is no matching LSP_Control_Block found, then try to find
an LSP_Control_Block which has the same Downstream Lable Label and the same
Downstream LDP Session Identifier.

e) If an LSP_Control_Block is found, pass the event 'LDP `LDP Mapping' to
its state machine.

f) Otherwise, ignore the LDP-MAPPING message and send a LDP-RELEASE
message
downstream.

- If an LSR receives an LDP-RELEASE from an upstream LSR:

a) Find an LSP_Control_Block which has the same Upstream Label and
the same Upstream LDP Session Identifier.

b) If an LSP_Control_Block is found, pass the event 'LDP `LDP Release' to
its state machine.

c) Otherwise, ignore the message.

- If an LSR receives an LDP-WITHDRAW from a downstream LSR:

a) Find an LSP_Control_Block which has the same Downstream Label and
the same Downstream LDP Session Identifier.

b) If an LSP_Control_Block is found, pass the event 'LDP `LDP Withdraw' to
its state machine.

c) Otherwise, ignore the LDP-WITHDRAW message and send a LDP-RELEASE
message
downstream.

- If an upstream LDP peer is lost:

a) Find all the LSP_Control_Blocks whose upstream LDP peer is that
LSR.

b) Then pass the event 'Upstream `Upstream Lost' to their state machines.

- If a downstream LDP peer is lost:

a) Find all the LSP_Control_Blocks whose downstream LDP peer is that
LSR.

b) Then pass the event 'Downstream `Downstream Lost' to their state machines.

- If the LSR detects a new next hop for an FEC:

For each LSP which needs "local repair", or it needs "global repair"
and it is the ingress of the LSP, pass event "Internal New NH" to its
state machine.

- If an LSR receives an LDP-Abort from an upstream LSR:

a) Extract the LDP Request ID value from the LDP-Abort message.

b) Find an LSP_Control_Block which has the same Upstream Label
Request ID and the same Upstream LDP Session Identifier.

c) If an LSP_Control_Block is found, pass the event 'LDP `LDP Upstream
Abort' to its state machine.

d) Otherwise, ignore the message.

- If the LSR receives an LDP-NAK from a downstream LSR:

a) Extract the LDP Request ID value from the LDP-NAK.

b) Find an LSP_Control_Block which has the same Downstream Label
Request ID and the same Downstream LDP Session Identifier.

c) If an LSP_Control_Block is found, pass the event `LDP Downstream
NAK' to its state machine.

d) Otherwise, ignore the message.

3.2. ATM Switch LSR with VC-merge

3.2.1 VC-merge

A VC-merge capable LSR can map multiple incoming labels(VPI/VCI) labels (VPI/VCI)
into one outgoing label. It is possible that this LSR can only merge
a limited number of incoming labels into a single outgoing label. As
described in [Ref2], [2], suppose, for example, that due to some hardware
limitation a node is capable of merging four incoming labels into a
single outgoing label. Suppose however, that this particular node has
six incoming labels arriving at it for a particular FEC. In this
case, this node may merge these into two outgoing labels.

When an upstream LSR has a limited merging capability, it is
difficult for a downstream LSR to know how many labels should be
assigned to each FEC. In this case, downstream-on-demand is
recommended.

3.2.2 Control Block

There are 3 types of control blocks involved:
Upstream_LSP_Control_Block, Downstream_LSP_Control_Block, and Next
Hop Trigger Control Block.

There is one Upstream_LSP_Control_Block for each LDP-REQUEST
received.

There is one Downstream_LSP_Control_Block for each unique LDP-
REQUEST LDP-REQUEST
sent to a downstream LSR. There can be multiple
Downstream_LSP_Control_Blocks per FEC in an LSR. This can be the
result of an upstream LSR asking for a label of for an FEC. This LSR
must assign a unique upstream label and it can not merge this
upstream label into an existing downstream label of for this FEC.

There is one Next Hop Trigger Control Block for each FEC for which was
detected with a
better next hop has been detected and the LSR decides has decided to switch over
to this better next hop. It could be the result of "local repair" or
"global repair" if the LSR is the ingress LSR of the LSP.

A Downstream_LSP_Control_Block contains a list of pointers to
Upstream_LSP_Control_Blocks or the Next Hop Trigger Control Block.
This means that this LSR has decided to map the multiple labels
listed in the Upstream_LSP_Control_Blocks and the Next Hop Trigger
Control Block into a single label listed in the
Downstream_LSP_Control_Block.

An Upstream_LSP_Control_Block may contain the following information:

- Upstream LDP Session Identifier

- State

- Upstream Label(assigned Label (assigned by this LSR)

- Downstream_LSP_Control_Block pointer

- Upstream LDP Request ID (assigned by the Upstream upstream LSR in
downstream-on-demand mode)

- Next_Hop_Trigger_Block pointer

Upstream Label and Upstream LDP Session Identifier can be used to
locate a unique Upstream_LSP_Control_Block.

If an LSR is using downstream-on-demand mode, it can use the Upstream
LDP Request ID and the Upstream LDP Session Identifier to locate a
unique Upstream_LSP_Control_Block.

An Next_Hop_Trigger_LSP_Control_Block may contain the following
information:

- Upstream_LSP_Control_Block pointer, which points to the one
which is needed to switch over to the better next hop

- State

- Downstream_LSP_Control_Block pointer

A Downstream_LSP_Control_Block may contain the following information:

- FEC
- State

- Downstream LDP Session Identifier

- list of pointers to the Upstream_LSP_Control_Blocks or the
Trigger_Control_Blocks which are merged at this LSR for this
FEC

- Downstream Label(assigned Label (assigned by the downstream LSR)

- Downstream Label Request ID (assigned by the LSR itself if
it is using downstream-on-demand mode)

Downstream Label, Downstream LDP Session Identifier can be used to
locate a unique Downstream_LSP_Control_Block.

If an LSR is using downstream-on-demand mode, it can also use the
Downstream Label Request ID and the Downstream LDP Session Identifier
to locate a unique Downstream_LSP_Control_Block.

The following diagram details the relationship between these 2 types
of control blocks:

For example, the LSR has decided to merge 3 LDP-REQUESTs of a FEC
from upstream LSR1,LSR2,LSR3 LSR1, LSR2, LSR3 into one LDP-REQUEST and sent it to a
downstream LSR4.

+---------------------+
| |
| Upstream_LSP_Control|
| _Block for Upstream|-------+ Upstream|------+
| LSR1 | |
+---------------------+ |
|
|
|
|
|
+---------------------+ |
| | |
| Upstream_LSP_Control| | (merged into)
| _Block for Upstream |-------+ |------+
| LSR2 | |
+---------------------+ |
|
|
|
| +------------------------------+
| | |
+-->|
+---------------------+ +--->| Downstream_LSP_Control_Block |
| Next_Hop_Trigger_ | | | for Downstream LSR4 |
| | |
| +------------------------------+
|
+---------------------+ |
| Next_Hop_Trigger_ | |
| LSP_Control_Block |------+ | |
| |-------+
| | +------------------------------+
+---------------------+

3.2.3 State Machines for Downstream-on-demand Mode

The following sections describe the state machines used in
downstream-on-demand mode.

3.2.3.1 State of the Upstream_LSP_Control_Block's State Machine
for Downstream-on-demand Mode

-- IDLE

This is the initial LSP state.

-- RESPONSE_AWAITED

This state means that the LSR has received and processed an LDP-
REQUEST from an upstream LSR, and has sent a new LDP-REQUEST towards
a downstream LSR. The LSR is waiting for the LDP-MAPPING message from the
downstream LSR.

-- ESTABLISHED

This state means that the LSR has received the LDP-MAPPING message from the
downstream LSR and the LSP is up and operational.

-- RELEASE_AWAITED

This state means that the LSR has sent a LDP-WITHDRAW message upstream and is
waiting for the LDP-RELEASE before freeing up the label resource.

3.2.3.2 Events of the Upstream_LSP_Control_Block's State Machine
for Downstream-on-demand Mode

-- LDP Request

The LSR receives an LDP-REQUEST from an upstream LSR.

-- Internal Downstream Mapping

This event is sent by one Downstream_LSP_Control_Block's state
machine. This Downstream_LSP_Control_Block is the merged
Downstream_LSP_Control_Block of this Upstream_LSP_Control_Block. The
event is the result of receiving an LDP-MAPPING message by the
Downstream_LSP_Control_Block's state machine.

-- LDP Release
The LSR receives an LDP-RELEASE from an upstream LSR.

-- Internal Downstream Withdraw

This event is sent by one Downstream_LSP_Control_Block's state
machine. This Downstream_LSP_Control_Block is the merged
Downstream_LSP_Control_Block of this Upstream_LSP_Control_Block. The
event is the result of receiving an LDP-WITHDRAW message by the
Downstream_LSP_Control_Block's state machine.

-- LDP Upstream Abort

The LSR receives an LDP-ABORT from an upstream LSR.

-- Internal Downstream Nak NAK

This event is sent by one Downstream_LSP_Control_Block's state
machine. This Downstream_LSP_Control_Block is the merged
Downstream_LSP_Control_Block of this Upstream_LSP_Control_Block. The
event is the result of receiving an LDP-NAK message by the
Downstream_LSP_Control_Block's state machine, or it detects an error.

-- Upstream Lost

The LSR loses the LDP session with its upstream LDP peer.

-- Internal New NH

The LSR detects there is better next hop and decides to establish the
lsp through this better next hop

-- Internal Re-Cross-Connect

This event is used to trigger splicing into a different downstream
LSP. This can happens when it is switched over to a better LSP
through the new next hop.

3.2.3.3 State Transitions of the Upstream_LSP_Control_Block's State
Machine for Downstream-on-demand Mode

+-------------------+
| |
+-------->| IDLE |<------------+
| | | |
| +-------------------+ |
|(LDP Abort) | |
|(Internal |(LDP Request) |
| Downstream Nak) NAK) | |
|(Upstream Lost) | |
| v |
| +-------------------+ |
| | | |
+---------| RESPONSE_AWAITED | |
| | |(Upstream Lost)
+-------------------+ |
| |
|(Internal Downstream |
| mapping) |(LDP Release)
| |
v |
+-------------------+ |
| | |(LDP Abort)
| ESTABLISHED |------->-----+
| | |
+-------------------+ |
| |
| |
|(Internal Downstream Withdraw)
|(Internal Downstream Nak) NAK)
v
+-------------------+ |
| | |
|RELEASE_AWAITED |------->-----+
| |
+-------------------+

3.2.3.4 Upstream_LSP_Control_Block's State Machine
for Downstream-on-demand Mode

3.2.3.4.1 State -- "IDLE"
State: IDLE

Event: LDP Request

New State: Depends upon the action routine.

Actions:

If this LSR is the LSP Egress or Proxy Egress [Ref2], [2],

Then:

choose an upstream label, allocate the resources, connect this
upstream label to the local IP forwarding module, send an LDP-
MAPPING upstream with the upstream label and go to the state
'ESTABLISHED'.
`ESTABLISHED'.

else

Obtain a next hop(or hop (or interface). Find a
Downstream_LSP_Control_Block which has the same FEC and the same
next hop and also is able to merge more input labels. If not found,
create a new Downstream_LSP_Control_Block with the state 'IDLE'. `IDLE'.

If the state of the Downstream_LSP_Control_Block is `ESTABLISHED',
choose an upstream label, connect the upstream label with the
downstream label and send an LDP-MAPPING message upstream with the upstream
label, and go to the state `ESTABLISHED'.

If the state of Downstream_LSP_Control_Block is not `ESTABLISHED',
set the state of the Upstream_LSP_Control_Block to
'RESPONSE_AWAITED'.
`RESPONSE_AWAITED'. If the LSR use the independent control
mode[Ref2], mode
[2], choose an upstream label, and send an LDP-MAPPING
message upstream.

Pass the event `Internal AddUpstream' to the
Downstream_LSP_Control_Block's state machine.

If unable to process the request for any reason, issue an LDP-NAK
message to
the sender with the appropriate error code and delete the control
block.

State: IDLE

Event: Internal Downstream Mapping

New State: IDLE

Actions:

Ignore the event. It is an internal implementation error.

State: IDLE

Event: LDP Release

New State: IDLE

Actions:

Ignore the event. It is an internal implementation error.

State: IDLE

Event: Internal Downstream Withdraw

New State: IDLE

Actions:

Ignore the event. It is an internal implementation error.

State: IDLE

Event: LDP Upstream Abort

New State: IDLE

Actions:

Ignore the event. It is an internal implementation error.

State: IDLE

Event: Internal Downstream Nak NAK

New State: IDLE

Actions:

Ignore the event. It is an internal implementation error.

State: IDLE

Event: Upstream Lost

New State: IDLE
Actions:

Ignore the event. It is an internal implementation error.

State: IDLE

Event: Internal Re-Cross-Connect

New State: IDLE

Actions:

Ignore the event. It is an internal implementation error.

State: IDLE

Event: Internal New NH

New State: IDLE

Actions:

Ignore the event. It is an internal implementation error.

3.2.3.4.2 State -- "RESPONSE_AWAITED"

State: RESPONSE_AWAITED

Event: LDP Request

New State: RESPONSE_AWAITED

Actions:

Ignore the event. It is an internal implementation error.

State: RESPONSE_AWAITED

Event: Internal Downstream Mapping

New State: Depends on the action routine

Actions:

If the LSR uses the ordered control mode, assign an upstream label.

Connect the upstream label to the downstream label and allocate the
resources.

Send an LDP-MAPPING message upstream with the upstream label.

Then go to the state 'ESTABLISHED'. `ESTABLISHED'.

If unable to process the message for any reason, issue an LDP-NAK
message
upstream and an LDP-RELEASE message downstream and delete the control block.

State: RESPONSE_AWAITED

Event: LDP Release

New State: RESPONSE_AWAITED

Actions

Ignore the event. It is an protocol error from the upstream peer.

State: RESPONSE_AWAITED

Event: Internal Downstream Withdraw

New State: RESPONSE_AWAITED

Actions

Ignore the event. It is an internal implementation error.

State: RESPONSE_AWAITED

Event: LDP Upstream Abort

New State: IDLE

Actions

If the LSR uses the independent control mode, free the upstream label
and the resources.

Send the event 'Internal `Internal DeleteUpstream' to its
Downstream_LSP_Control_Block's state machine.

Delete the control block.

State: RESPONSE_AWAITED
Event: Internal Downstream Nak NAK

New State: IDLE

Actions:

If the LSR uses the independent control mode, free the upstream label
and the resources. Then, send an LDP-WITHDRAW message upstream.

If the LSR uses the ordered control mode, propagate the LDP-NAK
message
upstream.

Delete the control block.

State: RESPONSE_AWAITED

Event: Upstream Lost

New State: IDLE

Actions

If the LSR uses the independent control mode, free the upstream label
and the resources.

Send the event 'Internal `Internal DeleteUpstream' to its
Downstream_LSP_Control_Block's state machine.

Delete the control block.

State: RESPONSE_AWAITED

Event: Internal Re-Cross-Connect

New State: RESPONSE_AWAITED

Actions:

Ignore the event. It is an internal implementation error.

State: RESPONSE_AWAITED

Event: Internal New NH

New State: depends on the actions

Actions:

Send event "Internal DeleteUpstream" `Internal DeleteUpstream' to its old downstream control
block.

Find a Downstream_LSP_Control_Block which has the same FEC and the
same next hop and also is able to merge more input labels. If not
found, create a new Downstream_LSP_Control_Block with the state
'IDLE'.
`IDLE'.

If the state of Downstream_LSP_Control_Block is not `ESTABLISHED',
set the state of the Upstream_LSP_Control_Block to
'RESPONSE_AWAITED'.
`RESPONSE_AWAITED'.

Pass the event `Internal AddUpstream' to the new
Downstream_LSP_Control_Block's state machine.

3.2.3.4.3 State -- "ESTABLISHED"

State: ESTABLISHED

Event: LDP Request

New State: ESTABLISHED

Actions

Ignore the event. It is an internal implementation error.

State: ESTABLISHED

Event: Internal Downstream Mapping

New State: ESTABLISHED

Actions

Process the new attributes of the mapping and then propagate the
LDP-MAPPING message upstream.

State: ESTABLISHED

Event: LDP Release
New State: IDLE

Actions

Disconnect the upstream label from the downstream label, free the
upstream label and resources.

Send the event 'Internal `Internal DeleteUpstream' to its
Downstream_LSP_Control_Block's state machine.

Send the event "Internal `Internal Destroy' to the Next_Hop_Trigger_Block's
state machine if the LSR was in the middle of switching over to the
better next hop.

Delete the control block.

State: ESTABLISHED

Event: Internal Downstream Withdraw

New State: Depends on the action routine

Actions

If it uses independent mode,set mode, set its state to 'IDLE' `IDLE' and create a
internal 'LDP `LDP Request' and send to its own state machine.

Else
Disconnect the upstream label from the downstream label.

Propagate the LDP-WITHDRAW upstream and go to state
'RELEASE_AWAITED'.
`RELEASE_AWAITED'.

Send the event "Internal `Internal Destroy' to the Next_Hop_Trigger_Block's
state machine if the LSR was in the middle of switching over to the
better next hop.

State: ESTABLISHED

Event: LDP Upstream Abort

New State: IDLE

Actions

Disconnect the upstream label from the downstream label, free the
upstream label and the resources.

Send the event 'Internal `Internal DeleteUpstream' to its
Downstream_LSP_Control_Block's state machine.

Send the event "Internal `Internal Destroy' to the Next_Hop_Trigger_Block's
state machine if the LSR was in the middle of switching over to the
better next hop.

Delete the control block.

State: ESTABLISHED

Event: Internal Downstream Nak NAK

New State: Depends on the actions

Actions:

If it uses independent mode,set mode, set its state to 'IDLE' `IDLE' and create a
internal 'LDP `LDP Request' and send to its own state machine.

Else
Disconnect the upstream label from the downstream label

Send an LDP-WITHDRAW upstream and go to state 'RELEASE_AWAITED'. `RELEASE_AWAITED'.

Send the event "Internal `Internal Destroy' to the Next_Hop_Trigger_Block's
state machine if the LSR was in the middle of switching over to the
better next hop.

State: ESTABLISHED

Event: Upstream Lost

New State: IDLE

Actions:

Disconnect the upstream label from the downstream label, free the
upstream label and the resources.

Send the event 'Internal `Internal DeleteUpstream' to its
Downstream_LSP_Control_Block's state machine.

Send the event "Internal `Internal Destroy' to the Next_Hop_Trigger_Block's
state machine if the LSR was in the middle of switching over to the
better next hop.

Delete the control block.

State: ESTABLISH

Event: Internal Re-Cross-Connect

New State: ESTABLISH

Actions:

Reconnect the upstream lable label to the new downstream lable. label.

Send the event 'Internal `Internal DeleteUpstream' to its old
Downstream_LSP_Control_Block's state machine.

State: ESTABLISH

Event: Internal New NH

New State: ESTABLISH

Actions:

Create a new Next_Hop_Trigger_Control_Block and pass event `Internal
New NH' to its state machine.

3.2.3.4.4 State -- "RELEASE_AWAITED"

State: RELEASE_AWAITED

Event: LDP Request

New State: RELEASE_AWAITED

Actions:

Ignore the event. It is a protocol error from the upstream LSR.

State: RELEASE_AWAITED

Event: Internal Downstream Mapping

New State: RELEASE_AWAITED

Actions:

Ignore the event. It is an internal implementatin implementation error.

State: RELEASE_AWAITED
Event: LDP Release

New State: IDLE

Actions:

Free the upstream lable resource. label resource and delete the control block.

State: RELEASE_AWAITED

Event: Internal Downstream Withdraw

New State: RELEASE_AWAITED

Actions:

Ignore the event. It is a protocol error from the downstream LSR.

State: RELEASE_AWAITED

Event: LDP Upstream Abort

New State: IDLE

Actions:

Free the upstream lable resource. label resource and delete the control block.

State: RELEASE_AWAITED

Event: Internal Downstream Nak NAK

New State: RELEASE_AWAITED

Actions:

Ignore the event. And continue waiting for the LDP-RELEASE msg. LDP-RELEASE.

State: RELEASE_AWAITED

Event: Upstream Lost

New State: IDLE

Actions:

Free the upstream lable resource. label resource and delete the control block.

State: RELEASE_AWAITED

Event: Internal New NH

New State: RELEASE_AWAITED

Actions:

Ignore the event. And continue waiting for the LDP-RELEASE msg. LDP-RELEASE.

State: RELEASE_AWAITED

Event: Internal Re-Cross-Connect

New State: RELEASE_AWAITED

Actions:

Ignore the event. It is an internal implementation error.

3.2.3.5 State of the Downstream_LSP_Control_Block's State Machine
for Downstream-on-demand Mode

-- IDLE

This is the initial LSP state.

-- RESPONSE_AWAITED

This state means that the LSR has received an LDP-REQUEST from an
upstream LSR, has processed the LDP-REQUEST, and has sent a new LDP-
REQUEST towards a downstream LSR. The LSR is waiting for the LDP-
MAPPING message from the downstream LSR.

-- ESTABLISHED

This state means that the LSR has received the LDP-MAPPING message from the
downstream LSR and the LSP is up and operational.

3.2.3.6 Events of the Downstream_LSP_Control_Block's State Machine
for Downstream-on-demand Mode

-- Internal AddUpstream

This event is sent by an Upstream_LSP_Control_Block's state machine
when it is created.

-- Internal DeleteUpstream

This event is sent by an Upstream_LSP_Control_Block's state machine
when it is deleted.

-- LDP Mapping

The LSR receives an LDP-MAPPING message from a downstream LSR.

-- LDP Withdraw

The LSR receives an LDP-WITHDRAW message from a downstream LSR.

-- LDP Downstream Nak NAK

The LSR receives an LDP-NAK from a downstream LSR.

-- Downstream Lost

The LSR loses the LDP session with its downstream LSR.

3.2.3.7 State Transitions of the Downstream_LSP_Control_Block'S Downstream_LSP_Control_Block's
State Machine for Downstream-on-demand mode

3.2.3.8 Downstream_LSP_Control_Block'S Downstream_LSP_Control_Block's State Machine for
Downstream-on-demand Mode.

3.2.3.8.1 State -- "IDLE"

State: IDLE

Event: Internal AddUpstream

New State: RESPONSE_AWAITED

Actions

Initialize the list of pointers in the Upstream_LSP_Control_Block to
contain the newly added upstream pointer.

Send a new LDP-REQUEST downstream and go to the state
'RESPONSE_AWAITED'.
`RESPONSE_AWAITED'.

State: IDLE

Event: Internal DeleteUpstream

New State: IDLE

Actions

Ignore the event. It is an internal implementation error.

State: IDLE

Event: LDP Mapping

New State: IDLE

Actions

Ignore the event. It is an internal implementation error.

State: IDLE

Event: LDP Withdraw

New State: IDLE

Actions

Ignore the event.It event. It is an internal implementation error.

State: IDLE

Event: LDP Downstream Nak NAK

New State: IDLE

Actions

Ignore the event. It is an internal implementation error.

State: IDLE

Event: Downstream Lost

New State: IDLE

Actions
Ignore the event. It is an internal implementation error.

3.2.3.8.2 State -- "RESPONSE_AWAITED"

State: RESPONSE_AWAITED

Event: Internal AddUpstream

New State: RESPONSE_AWAITED

Actions

Add the pointer to new Upstream_LSP_Control_Block to the
Upstream_LSP_Control_Blocks pointer list.

State: RESPONSE_AWAITED

Event: Internal DeleteUpstream

New State: Depend on the action routine

Actions

Delete the Upstream_LSP_Control_Block pointer from the
Upstream_LSP_Control_Block pointers list.

If the list becomes empty, release the resources, send an LDP-Abort
downstream, and then delete the control block.

State: RESPONSE_AWAITED

Event: LDP Mapping

New State: ESTABLISHED

Actions

For each Upstream_LSP_Control_Block in the Upstream_LSP_Control_Block
pointers list, pass the event 'Internal `Internal Downstream Mapping' to its
state machine.

State: RESPONSE_AWAITED

Event: LDP Withdraw

New State: RESPONSE_AWAITED

Actions
It is a protocol error from the downstream LDP peer and peer; send a LDP-
RELEASE msg downstream

State: RESPONSE_AWAITED

Event: LDP Downstream Nak NAK

New State: IDLE

Actions

For each Upstream_LSP_Control_Block in the Upstream_LSP_Control_Block
pointers list, pass the event 'Internal `Internal Downstream Nak' NAK' to its state
machine.

Release the resources, and delete the control block.

State: RESPONSE_AWAITED

Event: Downstream Lost

New State: IDLE

Actions

For each Upstream_LSP_Control_Block in the Upstream_LSP_Control_Block
pointers list, pass the event 'Internal `Internal Downstream Nak' NAK' to its state
machine.

Release the resources, and delete the control block.

3.2.3.8.3 State -- "ESTABLISHED"

State: ESTABLISHED

Event: Internal AddUpstream

New State: ESTABLISHED

Actions

Add the pointer to new Upstream_LSP_Control_Block to the
Upstream_LSP_Control_Block pointers list.

State: ESTABLISHED

Event: Internal DeleteUpstream
New State: Depends on the action routine

Actions

Delete the pointer of Upstream_LSP_Control_Block from its
Upstream_LSP_Control_Block pointers list.

If the list becomes empty, release the resources, send an LDP-RELEASE
downstream, and then delete the control block.

State: ESTABLISHED

Event: LDP Mapping

New State: ESTABLISHED

Actions

For each Upstream_LSP_Control_Block in the Upstream_LSP_Control_Block
pointers list, pass the event 'Internal `Internal Downstream mapping' to its
state machine.

State: ESTABLISHED

Event: LDP Withdraw

New State: IDLE

Actions

For each Upstream_LSP_Control_Block in the Upstream_LSP_Control_Block
pointers list, pass the event 'Internal `Internal Downstream withdraw' to its
state machine.

Release the resources, and delete the control block and send LDP-
RELEASE downstream.

State: ESTABLISHED

Event: LDP Downstream Nak NAK

New State: ESTABLISHED

Actions

It is a protocol error from the downstream LDP peer.

3.2.3.9 State of the Next_Hop_Trigger_Control_Block's State Machine
for Downstream-on-demand Mode

-- IDLE

This is the initial LSP state.

-- NEW_NH_RETRY

This is the state where an LSR waits for a retry timer to expire and
then tries to establish an LSP through a new next hop.

-- NEW_NH_RESPONSE_AWAITED

This state means that the LSR has sent a new LDP-REQUEST towards a
downstream LSR. The LSR is waiting for the LDP-MAPPING message from the
downstream LSR.

3.2.3.10 Events of the Next_Hop_Trigger_Control_Block's State Machine
for Downstream-on-demand Mode

-- Internal New NH

Trigger to setup an LSP through a better next hop.

-- Internal Downstream Mapping

-- Internal Downstream Nak NAK

This event is sent by one Downstream_LSP_Control_Block's state
machine. This Downstream_LSP_Control_Block is the merged
Downstream_LSP_Control_Block of this Upstream_LSP_Control_Block. The
event is the result of receiving an LDP-NAK message by the
Downstream_LSP_Control_Block's state machine, or it detects an error.

-- Internal Destroy This event is used to stop the procedure of
switching over to the better next hop.

3.2.3.11 State Transitions of the Next_Hop_Trigger_Control_Block's State
Machine for Downstream-on-demand Mode

|
|
|
| Internal New NH
|
v
+---------------------+
| | Internal destroy
| NEW_NH_RETRY |--------------
| | |
+---------------------+ |
| |
| |
| (Internal retry timeout) |
| |
v |
+---------------------+ |
| | Internal |
| NEW_NH_RESPONSE | Destroy |
| _AWAITED |-------------|
| | |
+---------------------+ |
| |
| (Internal Downstream |
| Mapping |
| (Internal Downstream |
| Nak) NAK) |
v v
the control block is deleted

3.2.3.12 State Machine

3.2.3.12.1 State -- "IDLE"

State: IDLE

Event: Internal New NH

New States: State: NEW_NH_RETRY

Actions:

Start the LSP retry timer and go to the 'NEW_NH_RETRY' `NEW_NH_RETRY' state.

State: IDLE

Event: Internal retry timeout

New States: State: IDLE

Actions:

Ignore. It is an internal implementation error.

State: IDLE

Event: Internal Downstream Mapping

New States: State: IDLE

Actions:

Ignore. It is an internal implementation error.

State: IDLE

Event: Internal Downstream Nak NAK

New States: State: IDLE

Actions:

Ignore. It is an internal implementation error.

State: IDLE

Event: Internal destroy

New States: State: IDLE

Actions:

Ignore. It is an internal implementation error.

3.2.3.12.2 State -- "NEW_NH_RETRY"

State: NEW_NH_RETRY

Event: Internal New NH

New States: State: NEW_NH_RETRY
Actions:

Restart the LSP retry timer.

State: NEW_NH_RETRY

Event: Internal retry timeout

New States: State: NEW_NH_RESPONSE_AWAITED

Actions:

If the new next hop is the same one as the old next hop, delete the
control block.

Otherwise, find an downstream LSP control block which go through the
same next hop for the same FEC, if there is no one, create one, and
pass "Internal AddUpstream'event `Internal AddUpstream' event to its state machine.

State: NEW_NH_RETRY

Event: Internal Downstream Mapping

New States: State: NEW_NH_RETRY

Actions:

Ignore. It is an internal implementation error.

State: NEW_NH_RETRY

Event: Internal Downstream NAK

New States: State: NEW_NH_RETRY

Actions:

Ignore. It is an internal implementation error.

State: NEW_NH_RETRY

Event: Internal destroy

New States: State: IDLE

Actions:

Stop the timer and delete the control block.

3.2.3.12.3 State -- "NEW_NH_RESPONSE_AWAITED"

State: NEW_NH_RESPONSE_AWAITED

Event: Internal New NH

New States: State: NEW_NH_RETRY

Actions:

Restart the LSP retry timer, send "Internal destroy" `Internal destroy' to the control
block of the LSP for the new next hop and go to the 'NEW_NH_RETRY' `NEW_NH_RETRY'
state.

State: NEW_NH_RESPONSE_AWAITED

Event: Internal retry timeout

New States: State: NEW_NH_RESPONSE_AWAITED

Actions:

Ignore. It is an internal implementation error.

State: NEW_NH_RESPONSE_AWAITED

Event: Internal Downstream Mapping

New States: State: IDLE

Actions:

Send event "Internal Re-cross-connect" `Internal Re-cross-connect' event to the Upstream upstream LSP
control block of the new next hop.

Send event "DeleteUpstream" `DeleteUpstream' event to the downstream LSP control block
of the the new next hop, since the upstream has spliced into the new
next hop.

Then delete the control block.

State: NEW_NH_RESPONSE_AWAITED

Event: Internal Downstream NAK

New States: State: IDLE
Actions:

Delete the control block.

State: NEW_NH_RESPONSE_AWAITED

Event: Internal destroy

New States: State: IDLE

Actions:

Send event "Internal DeleteUpstream" `Internal DeleteUpstream' the control block for the new
LSP through the new next hop.

3.2.4 LDP Related Message Processing

- If an LSR receives an LDP-REQUEST message: LDP-REQUEST:

b) Otherwise, create a new Upstream_LSP_Control_Block. Then pass the
event `LDP Request' to this Upstream_LSP_Control_Block's state
machine.

- If an LSR receives an LDP-MAPPING message: LDP-MAPPING:

Locate a Downstream_LSP_Control_Block which has the same FEC, the
same Downstream LDP Session Identifier and the same Downstream Label.
If a Downstream_LSP_Control_Block is found, pass the event `LDP
Mapping' to its state table. This could mean that the attributes of
label binding have changed.

Otherwise, use the Downstream LDP request ID(the 'Lable ID (the 'Label Request
Message ID' field in the LDP-MAPPING MSG) LDP-MAPPING) and Downstream LDP Session
Identifier to locate the Downstream_LSP_Control_Block and pass the
event `LDP Mapping' to its state machine. If no
Downstream_LSP_Control_Block is found, ignore the message.

- If an LSR receives an LDP-RELEASE message: LDP-RELEASE:

Locate an Upstream_LSP_Control_Block which has the same FEC, the same
Upstream Label, the same Upstream LDP Session Identifier. If no
Upstream_LSP_Control_Block is found, ignore the message. If an
Upstream_LSP_Control_Block is found, send the event `LDP Release' to
its state machine.

- If an LSR receives an LDP-WITHDRAW message: LDP-WITHDRAW:

Find a Downstream_LSP_Control_Block which has the same FEC, the same
Downstream LDP Session Identifier and the same Downstream Label. Pass
the event `LDP Withdraw' to its state machines.

- If an Upstream LDP peer is lost:

Pass the event `Upstream Lost' to the state machines of all the
Upstream_LSP_Control_Blocks whose upstream LDP peer is that LSR.

- If a Downstream LDP peer is lost:

Pass the event `Downstream Lost' to the state machines of all the
Downstream_LSP_Control_Blocks whose the downstream LDP peer is that
LSR.

- If a next hop of an FEC is changed:

For all the Upstream_LSP_Control_Blocks which are infected by this
change, pass the event 'Internal `Internal New NH' to their state machines.

- If an LSR receives an LDP-ABORT from an Upstream upstream LSR:

Use the Upstream LDP Request ID and Upstream LDP Session Identifier
to locate the Upstream_LSP_Control_Block and pass the event `LDP
Abort' to its state machine.

- If an LSR receives an LDP-NAK from a downstream LSR:

Use the Downstream LDP Request ID and Downstream Session Identifier
to locate a Downstream_LSP_control_block and pass the event `LDP
Downstream Nak' NAK' to its state machine.

4. State Machine for Downstream Unsolicited

The following sections describe the state machines for the ATM-LSR
which uses downstream unsolicited mode.

While both independent LSP control and ordered LSP control modes are
possible, only the ordered mode is taken into account, because the
independant
independent LSP control mode uses the liberal label retention mode
and so is considered burning too many ATM resources.

In downstream unsolicited mode, multiple path is not allowed supported in
this version and will be For Further Study(FFS). Study (FFS). We suspect with
multiple next hops and Downstream mode, it is easy to get into a loop
condition.

4.0 Control Block

There are 2 types of control blocks involved:
Upstream_LSP_Control_Block, Downstream_LSP_Control_Block.

There is a list of Upstream_LSP_Control_Blocks for each FEC in the
routing table, with each one correspondng corresponding to a LDP peer. A
Upstream_LSP_Control_Block is created for each FEC when there is a
label ready to be distributed to that upstream. It is deleted when
the FEC is deleted from the FEC table, or the LDP peer disappears, or
the downstream label is withdrawed.

There is one Downstream_LSP_Control_Blocks for each FEC in the
routing table. It is created when the FEC is inserted into the
forwarding table and deleted when the FEC is removed from the
forwarding table.

An Upstream_LSP_Control_Block may contain the following information:

- Upstream LDP Session Identifier

- State

- Upstream Label(assigned Label (assigned by this LSR)

- FEC

Upstream Label and Upstream LDP Session Identifier, or FEC and
Upstream LDP Session Identifier can be used to locate a unique
Upstream_LSP_Control_Block.

A Downstream_LSP_Control_Block may contain the following information:

- FEC

- State

- Downstream LDP Session Identifier

- Downstream Label(assigned Label (assigned by the downstream LSR)

- Downstream Label Request ID (assigned by the LSR itself)
Downstream Label and Downstream LDP Session Identifier, or FEC and
Downsteam
Downstream LDP Session Identifier can be used to locate a unique
Downstream_LSP_Control_Block.

4.1 States of the Upstream_LSP_Control_Block's State Machine
for Downstream Mode

-- IDLE

This is the initial LSP state.

-- ESTABLISHED

This state means that the LSR has received the LDP-MAPPING message from the
downstream LSR and the LSP is up and operational.

-- RELEASE_AWAITED

This state means that the LSR is waiting for the LDP-RELEASE msg in
respond to the LDP-WITHDRAW sent by this LSR.

-- RESOUCES_AWAITED RESOURCES_AWAITED

This state means that the LSR is waiting for the label resources.

4.2 Events of the Upstream_LSP_Control_Block's State Machine
for Downstream Mode

-- Internal Downstream Mapping

This event is sent by one Downstream_LSP_Control_Block's state
machine. The event is the result of receiving an LDP-MAPPING message by the
Downstream_LSP_Control_Block's state machine. Or when the LDP peer is
discovered and there is a downstream Label available for this FEC.

-- LDP Release

The LSR receives an LDP-RELEASE from an upstream LSR.

-- Internal Withdraw

This event is sent by Downstream_LSP_Control_Block's state machine.
The event is the result of receiving an LDP-WITHDRAW message by the
Downstream_LSP_Control_Block's state machine.

-- Resource Available

This event means the local resource(such resource (such as label) becomes
available.

-- Delete FEC

This event means that either the FEC is removed from the forwarding
table.

-- Upstream Lost

This event means that the upstream LDP peer is lost.

4.3 State Transitions of Upstream_LSP_Control_Block's State
Machine for Downstream Mode

|
|(created when
|a label is to be distributed
| to the LDP peer)
v
+-------------------+
| |
| IDLE |<--------------+
| | |
+-------------------+ |
| |(LDP Release)
| |
| |
| |
|(Internal Downstream |
+-------------------| Mapping) |
| | |
|(no label resource)v |
| +-------------------+ |
| | | |
| +-----| ESTABLISHED |---------------+
| | | | ^
| | +-------------------+ |
| |(delete FEC) ^ |
| |(Internal |(Resource Available) | (LDP Release)
| | Withdraw) | | (Internal
| | | | Downstraem Downstream
| | | | Withdraw)
| | +-------------------+ |
+--------->| | |
| |RESOURCES_AWAITED |---------------+
| | | |
| +-------------------+ |
| |
| (Internal Downstream Withdraw) |(LDP Release)
| +-------------------+ |
| | | |
+---->| RELEASE_AWAITED |---------------+
| |
+-------------------+

4.4 Upstream_LSP_Control_Block's State Machine for
Downstream Mode

4.4.1 : State -- "IDLE"

State: IDLE

Event: Internal Downstream mapping

New State: Depends on the action.

Actions

Choose an upstream label, connect the upstream label with the
downstream label. And go to state 'ESTABLISHED' `ESTABLISHED'

Propagate the LDP-MAPPING upstream.

If there is no resource for the upstream label, go to state
'RESOURCE_AWAITED'.
`RESOURCE_AWAITED'.

State: IDLE

Event: LDP Release

New State: IDLE

Actions

Ignore the event. It is an internal implementation error.

State: IDLE

Event: Internal Downstream Withdraw

New State: IDLE

Actions

Ignore the event. It is an internal implementation error.

State: IDLE

Event: Resource Available

New State: IDLE

Actions

Ignore the event. It is an internal implementation error.

State: IDLE

Event: Delete FEC

New State: IDLE

Actions

Delete the control block.

State: IDLE

Event: Upstream Lost

New State: IDLE

Actions

Delete the control block.

4.4.2 : State -- "ESTABLISHED"

State: ESTABLISHED

Event: Internal Downstream Mapping

New State: ESTABLISHED

Actions

Process the new attributes of the new mapping msg. message.

Propagate the LDP-MAPPING upstream.

State: ESTABLISHED

Event: LDP Release

New State: IDLE

Actions

Disconnect upstream label from downstream label.

Release the upstream label resource

Delete the control block.

State: ESTABLISHED

Event: Internal Downstream Withdraw

New State: RELEASE_AWAITED

Actions

Disconnect upstream label from downstream label.

Propagate the LDP-WITHDRAW upstream.

State: ESTABLISHED

Event: Resource Available

New State: ESTABLISHED

Actions

Ignore the event. It is an internal implementation error.

State: ESTABLISHED

Event: Delete FEC

New State: RELEASE_AWAITED

Actions

Send a LDP-WITHDRAW upstream.

State: ESTABLISHED

Event: Upstream Lost

New State: IDLE

Actions

Release the upstream label and delete the control block.

4.4.2 : State -- "RELEASE_AWAITED"

State: RELEASE_AWAITED

Event: Internal Downstream Mapping
New State: RELEASE_AWAITED

Actions

Ignore the msg. message.

State: RELEASE_AWAITED

Event: LDP Release

New State: IDLE

Actions

Release the upstream label and delete the control block.

State: RELEASE_AWAITED

Event: Internal Downstream Withdraw

New State: RELEASE_AWAITED

Actions

Ignore the event.

State: RELEASE_AWAITED

Event: Resource Available

New State: RELEASE_AWAITED

Actions

Ignore the event. It is an internal implementation error.

State: RELEASE_AWAITED

Event: Delete FEC

New State: RELEASE_AWAITED

Actions

Do nothing.

State: RELEASE_AWAITED
Event: Upstream Lost

New State: IDLE

Actions

Release the upstream label and delete the control block.

4.4.2 : State -- "RESOURCE_AWAITED"

State: RESOURCE_AWAITED

Event: Internal Downstream Mapping

New State: RESOURCE_AWAITED

Actions

Ignore the msg. message.

State: RESOURCE_AWAITED

Event: LDP Release

New State: RESOURCE_AWAITED

Actions

Ignore the msg. message. It is an internal implementation error.

State: RESOURCE_AWAITED

Event: Internal Downstream Withdraw

New State: IDLE

Actions

Delete the control block.

State: RESOURCE_AWAITED

Event: Resource Available

New State: ESTABLISHED

Actions
Allocate an upstream label, connect the upstream label with the
downstream label, and send LDP-MAPPING upstream.

State: RESOURCE_AWAITED

Event: Delete FEC

New State: IDLE

Actions

Delete the control block.

State: RESOURCE_AWAITED

Event: Upstream Lost

New State: IDLE

Actions

Delete the control block.

4.5 State of the Downstream_LSP_Control_Block's State Machine
for Downstream Mode

-- IDLE

This is the initial LSP state.

-- ESTABLISHED

This state means that the LSR has received the LDP-MAPPING msg from the
downstream LSR.

3.2.4.6 Events of the Downstream_LSP_Control_Block's State Machine
for Downstream Mode

-- LDP Mapping

The LSR receives an LDP-MAPPING msg from a downstream LSR.

-- LDP Withdraw

The LSR receives an LDP-WITHDRAW msg from a downstream LSR.

-- Delete FEC

The FEC is deleted from the forwarding table.

-- Next Hop Change

The next hop for this FEC is change to different LSR.

-- Downstream Lost

The downstream peer is gone.

4.7 State Transitions of Downstream_LSP_Control_Block's State
Machine for Downstream Mode

|
|(FEC is being added into the forwarding
table)
v
+-------------------+
| |
| IDLE |<--------------+
| | |
+-------------------+ |
| |
| |(LDP Withdraw)
| |(Internal New NH)
| |(Downstream Lost)
| (LDP Mapping) |
| |
v |
+-------------------+ |
| | |
| ESTABLISHED |---------------+
| |
+-------------------+
|
|(FEC is deleted from the forwarding table)
v

4.8 Downstream_LSP_Control_Block's State Machine
for Downstream Mode

4.8.1 : State -- "IDLE"

State: IDLE

Event: LDP mapping
New State: ESTABLISHED

Actions

For all the LDP peers except the downstream LSR which assigned the
label, create an Upstream_LSP_Control_Block, and pass the event
`Internal Downstream Mapping' to each of the
Upstream_LSP_Control_Block's state machines.

State: IDLE

Event: LDP withdraw

New State: IDLE

Actions
Ignore the event. It is an internal implementation error.

State: IDLE

Event: Delete FEC

New State: IDLE

Actions

Delete the control block.

State: IDLE

Event: Next Hop Change

New State: IDLE

Actions

Ignore the event.

State: IDLE

Event: Downstream Lost

New State: IDLE

Actions

Ignore the event.

4.8.1 : State -- "ESTABLISHED"

State: ESTABLISHED

Event: LDP mapping

New State: ESTABLISHED

Actions

For each Upstream_LSP_control_block of this FEC, pass event `Internal
downstream mapping' to its state machine.

State: ESTABLISHED

Event: LDP withdraw

New State: IDLE

Actions

For each Upstream_LSP_control_block for this FEC, pass event
`Internal downstream Withdraw' to its state machine.

Send a LDP Withdraw downstream.

State: ESTABLISHED

Event: Delete FEC

New State: IDLE

Actions

Send LDP-RELEASE downstream and delete the control block.

State: ESTABLISHED

Event: Next Hop Change

New State: IDLE

Actions

For each Upstream_LSP_control_block for this FEC, pass event
`Internal downstream Withdraw' to its state machine.

Send LDP-REQUEST to the new next hop.

State: ESTABLISHED

Event: Downstream Lost

New State: IDLE

Actions

Send LDP-WITHDRAW to all Upstream_Control_Block's state machine of
this FEC.

4.5 LDP Related Message Processing for downstream mode.

- If an LSR receives an LDP-REQUEST message: LDP-REQUEST:

If there is a next hop for this FEC and there is a
Downstream_Control_Block for this FEC whose state is 'ESTABLISHED', `ESTABLISHED',
create a new Upstream_Control_Block and pass 'internal `internal Mapping' event
to its state machine.

- If an LSR receives an LDP-MAPPING message: LDP-MAPPING:

Otherwise, if there is no matching Downstream_LSP_Control_Block
found, find a Downstream_LSP_Control_Block of this FEC and its next
hop is the this downstream peer, pass the event `LDP Mapping' to its
state machine.

- If an LSR receives an LDP-RELEASE message: LDP-RELEASE:

- If an LSR receives an LDP-WITHDRAW message: LDP-WITHDRAW:

Find a Downstream_LSP_Control_Block which has the same FEC, the same
Downstream LDP Session Identifier and the same Downstream Label. Pass
the event `LDP Withdraw' to its state machines.

- If an Upstream LDP peer is lost:

Pass the event `Upstream Lost' to the state machines of all the
Upstream_LSP_Control_Blocks whose upstream LDP peer is that LSR.

- If a Downstream LDP peer is lost:

Pass the event `Label Withdraw' to the state machines of all the
Downstream_LSP_Control_Blocks whose the downstream LDP peer is that
LSR.

- If a next hop of an FEC is changed:

Find all the Downstream_LSP_Control_Blocks which has the same FEC and
the same next hop and pass the event `Next Hop Change' to their state
machine

- If there is a FEC being added to the forwarding table

Create a new Downstream_LSP_Control_Block with state 'IDLE' `IDLE'

- If the FEC is deleted from the forwarding table

Send the 'Delete `Delete FEC' event to the its control block.

- If an LSR receives an LDP-NAK from an Upstream upstream LSR:

Ignore the msg. message. An LDP-NAK should never appear in the
downstream-mode LSR

- If an LSR receives an LDP-NAK from a downstream LSR:

Ignore the msg. message. It is an protocol error from the downstream LSR.

5. Security Considerations

This document is provided as an informational extension of the LDP
specification [4]. State machines presented here are intended to
clarify procedures defined in the LDP specification, but do not
supplant or override definitions and procedures provided there.

Implementations of a state machine may be vulnerable to spurious
events generated by an external source. In this document, events fall
in two categories: internal events and external events caused by
receipt of an LDP message.

LDP messages may be protected using mechanisms described in the LDP
specification. See "Security Considerations" in the LDP specification
[4].

Security considerations will be relating to generation of spurious internal
events are not addressed in a future revision of this document.

6. Acknowledgements

The authors would like to acknowledge the helpful comments and
suggestions of the following people: Bob Thomas and Myunghee Son.

7. Authors's Authors' Address

Liwen Wu

Alcatel
44983 Knoll Square
Ashburn, VA. 20147
U.S.A
Phone: 703-724-2619
Email:liwen.wu@adn.alcatel.com

Pierrick Cheval

Alcatel
44983 Knoll Square
Ashburn, VA. 20147
U.S.A
Phone: 703-724-2080
Email: pierrick.cheval@adn.alcatel.com

Christophe Boscher

Alcatel CIT
Le Mail
44700 Nantes-Orvault Orvault
France
Phone: (33) 251781828
Email: christophe.boscher@or.cit.alcatel.fr christophe.boscher@alcatel.fr

Pierrick Cheval

Alcatel
5 rue Noel-Pons
92734 Nanterre Cedex
France
Phone: (33) 146524027
Email: pierrick.cheval@alcatel.fr

Eric Gray

Lucent Technologies, Inc.
1600 Osgood Street
North Andover, MA 01845
P.O. Box 710
Durham, NH 03824
Phone: (603) 659-3386
Email: ewgray@lucent.com

Liwen Wu

Cisco Systems, Inc.
250 Apollo Drive
Chelmsford, MA 01824
U.S.A
Phone: 978-224-3087
Email:liwwu@cisco.com

8. References

1."Use of Label Switching With ATM",

1."MPLS Using LDP and ATM Switching", Bruce Davie, Jeremy Lawrence,
Keith McCloghrie, Yakov Rekhter, Eric Rosen, George Swallow, Paul
Doolan, work in progress, Internet Draft, <draft-ietf-mpls-atm-01.txt> <draft-ietf-mpls-atm-02.txt>

2."Multiprotocol Label Switching Architecture", Eric C Rosen, Arun
Viswanathan, Ross Callon, work in progress, Internet Draft, <draft-
ietf-mpls-arch-02.txt>
ietf-mpls-arch-06.txt>

3."Definition of Managed Objects for the Multiprotocol Label Switching,
Label Distribution Protocol (LDP)", Joan Cucchiara, Hans Sjostrand,
James V. Luciani, work in progress, Internet Draft, <draft-ietf-mpls-
ldp-mib-00.txt>

4."Requirements for Traffic Engineering Over MPLS", Daniel O.Awduche,
Joe Malcolm, Johnson Agogbua, Mike O'Dell, Jim McMaus, work in
progress,Internet Draft, <draft-ietf-mpls-traffic-eng-00.txt>

5.
ldp-mib-02.txt>

4. "LDP Specification", Loa Andersson, Paul Doolan,Nancy Doolan, Nancy Feldman,
Andre Fredette, Bob Thomas, work in progress, Internet Draft, <draft-ietf-
mpls-ldp-04.txt>

6. "MPLS Loop Prevention Mechanism", Yoshihiro Ohba, Yasuhiro Katsube,
Eric Rosen, Paul Doolan, work in progress, Internet Draft, <draft-
ohba-mpls-loop-prevention-02.txt>
7.
ietf-mpls-ldp-06.txt>

5. "Constraint-Based LSP Set up Using LDP", Bilel Jamoussi, et.al., et al.,
work in progress, Internet Draft, <draft-ietf-mpls-cr-ldp-01.txt> <draft-ietf-mpls-cr-ldp-03.txt>