Network Working Group C. Boscher
Request for Comments: 3215 P. Cheval
Category: Informational Alcatel
L. Wu
Cisco
E. Gray
Sandburst
January 2002
Network Working Group C. Boscher
Request for Comments: 3215 P. Cheval
Category: Informational Alcatel
L. Wu
Cisco
E. Gray
Sandburst
January 2002
LDP State Machine
LDP状态机
Status of this Memo
本备忘录的状况
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2002). All Rights Reserved.
版权所有（C）互联网协会（2002年）。版权所有。
Abstract
摘要
This document provides state machine tables for ATM (Asynchronous Transfer Mode) switch LSRs. In the current LDP specification, there is no state machine specified for processing LDP messages. We think that defining a common state machine is very important for interoperability between different LDP and CR-LDP implementations.
本文档提供了ATM（异步传输模式）交换机LSR的状态机表。在当前的LDP规范中，没有指定用于处理LDP消息的状态机。我们认为，定义公共状态机对于不同LDP和CR-LDP实现之间的互操作性非常重要。
We begin in section 1 by defining a list of terminologies. Then in section 2, we propose two sets of state machine tables for ATM switch LSRs that use downstream-on-demand mode, one method can be used for non-vc merge capable ATM LSRs, while the other one can be used for the vc-merge capable ATM LSRs. In section 3, we provides a state machine for downstream unsolicited mode ATM LSRs.
我们从第1节开始定义术语列表。然后在第2节中，我们为使用下游按需模式的ATM交换机LSR提出了两组状态机表，一种方法可用于不支持vc合并的ATM LSR，而另一种方法可用于支持vc合并的ATM LSR。在第3节中，我们为下游非请求模式ATM LSR提供了一个状态机。
We focus on the LDP state machines and the associated control blocks used for establishing and maintaining LSPs. We do not describe state machines for the "LDP controller" that is in charge of LDP session initialization, address mapping messages management, routing interface, etc. that is defined in the LDP specification.
我们关注LDP状态机以及用于建立和维护LSP的相关控制块。我们不描述LDP规范中定义的负责LDP会话初始化、地址映射消息管理、路由接口等的“LDP控制器”的状态机。
Even though the state machines in this document are specific for ATM-LSR, they can be easily adapted for other types of LSRs.
尽管本文档中的状态机专门用于ATM-LSR，但它们可以很容易地适用于其他类型的LSR。
Table Of Contents
目录
1. Terminology ................................................... 4
2. State Machine for Downstream-on-Demand Mode ................... 4
2.1 An LSR's Behavior in the Case of a Next Hop Change ........... 4
2.2. ATM Switch LSR with No VC-merge Capability .................. 5
2.2.1 LSP Control Block .......................................... 5
2.2.2 States ..................................................... 7
2.2.3 Events ..................................................... 8
2.2.4 State Transitions .......................................... 9
2.2.5 State Machine .............................................. 10
2.2.5.1 State -- "IDLE" .......................................... 10
2.2.5.2 State -- "RESPONSE_AWAITED" .............................. 13
2.2.5.3 State -- "ESTABLISHED" ................................... 16
2.2.5.4 State -- "RELEASE_AWAITED" ............................... 21
2.2.6 Handling the Next Hop Change ............................... 23
2.2.6.1 Next Hop Trigger Control Block ........................... 24
2.2.6.2 States ................................................... 24
2.2.6.3 Events ................................................... 24
2.2.6.4 State Transition for next hop change ..................... 25
2.2.6.5 State Machine ............................................ 25
2.2.6.5.1 State -- "IDLE" ........................................ 25
2.2.6.5.2 State -- "NEW_NH_RETRY" ................................ 27
2.2.6.5.3 State -- "NEW_NH_RESPONSE_AWAITED" ..................... 28
2.2.7 LDP Related Message Handling ............................... 29
2.3. ATM Switch LSR with VC-merge ................................ 31
2.3.1 VC-merge ................................................... 31
2.3.2 Control Block .............................................. 31
2.3.3 State Machines for Downstream-on-demand Mode ............. 34
2.3.3.1 State of the Upstream LSP Control Block's State Machine
for Downstream-on-demand Mode ............................ 34
2.3.3.2 Events of the Upstream LSP Control Block's State Machine
for Downstream-on-demand Mode ............................ 35
2.3.3.3 State Transitions of the Upstream LSP Control Block's State
Machine for Downstream-on-demand Mode .................... 36
2.3.3.4 Upstream LSP Control Block's State Machine
for Downstream-on-demand Mode ............................ 37
2.3.3.4.1 State -- "IDLE" ........................................ 37
2.3.3.4.2 State -- "RESPONSE_AWAITED" ............................ 39
2.3.3.4.3 State -- "ESTABLISHED" ................................. 42
2.3.3.4.4 State -- "RELEASE_AWAITED" ............................. 45
2.3.3.5 State of the Downstream LSP Control Block's State Machine
for Downstream-on-demand Mode ............................ 47
2.3.3.6 Events of the Downstream LSP Control Block's State Machine
for Downstream-on-demand Mode ............................ 47
2.3.3.7 State Transitions of the Downstream LSP Control Block's
State Machine for Downstream-on-demand mode .............. 48
1. Terminology ................................................... 4
2. State Machine for Downstream-on-Demand Mode ................... 4
2.1 An LSR's Behavior in the Case of a Next Hop Change ........... 4
2.2. ATM Switch LSR with No VC-merge Capability .................. 5
2.2.1 LSP Control Block .......................................... 5
2.2.2 States ..................................................... 7
2.2.3 Events ..................................................... 8
2.2.4 State Transitions .......................................... 9
2.2.5 State Machine .............................................. 10
2.2.5.1 State -- "IDLE" .......................................... 10
2.2.5.2 State -- "RESPONSE_AWAITED" .............................. 13
2.2.5.3 State -- "ESTABLISHED" ................................... 16
2.2.5.4 State -- "RELEASE_AWAITED" ............................... 21
2.2.6 Handling the Next Hop Change ............................... 23
2.2.6.1 Next Hop Trigger Control Block ........................... 24
2.2.6.2 States ................................................... 24
2.2.6.3 Events ................................................... 24
2.2.6.4 State Transition for next hop change ..................... 25
2.2.6.5 State Machine ............................................ 25
2.2.6.5.1 State -- "IDLE" ........................................ 25
2.2.6.5.2 State -- "NEW_NH_RETRY" ................................ 27
2.2.6.5.3 State -- "NEW_NH_RESPONSE_AWAITED" ..................... 28
2.2.7 LDP Related Message Handling ............................... 29
2.3. ATM Switch LSR with VC-merge ................................ 31
2.3.1 VC-merge ................................................... 31
2.3.2 Control Block .............................................. 31
2.3.3 State Machines for Downstream-on-demand Mode ............. 34
2.3.3.1 State of the Upstream LSP Control Block's State Machine
for Downstream-on-demand Mode ............................ 34
2.3.3.2 Events of the Upstream LSP Control Block's State Machine
for Downstream-on-demand Mode ............................ 35
2.3.3.3 State Transitions of the Upstream LSP Control Block's State
Machine for Downstream-on-demand Mode .................... 36
2.3.3.4 Upstream LSP Control Block's State Machine
for Downstream-on-demand Mode ............................ 37
2.3.3.4.1 State -- "IDLE" ........................................ 37
2.3.3.4.2 State -- "RESPONSE_AWAITED" ............................ 39
2.3.3.4.3 State -- "ESTABLISHED" ................................. 42
2.3.3.4.4 State -- "RELEASE_AWAITED" ............................. 45
2.3.3.5 State of the Downstream LSP Control Block's State Machine
for Downstream-on-demand Mode ............................ 47
2.3.3.6 Events of the Downstream LSP Control Block's State Machine
for Downstream-on-demand Mode ............................ 47
2.3.3.7 State Transitions of the Downstream LSP Control Block's
State Machine for Downstream-on-demand mode .............. 48
2.3.3.8 Downstream LSP Control Block's State Machine for
Downstream-on-demand Mode ................................ 49
2.3.3.8.1 State -- "IDLE" ........................................ 48
2.3.3.8.2 State -- "RESPONSE_AWAITED" ............................ 50
2.3.3.8.3 State -- "ESTABLISHED" ................................. 52
2.3.3.9 State of the Next_Hop_Trigger_Control_Block's State
Machine for Downstream-on-demand Mode .................... 53
2.3.3.10 Events of the Next_Hop_Trigger_Control_Block's State
Machine for Downstream-on-demand Mode ................... 53
2.3.3.11 State Transitions of the Next_Hop_Trigger_Control_Block's
State Machine for Downstream-on-demand Mode ............. 55
2.3.3.12 State Machine ........................................... 55
2.3.3.12.1 State -- "IDLE" ....................................... 55
2.3.3.12.2 State -- "NEW_NH_RETRY" ............................... 57
2.3.3.12.3 State -- "NEW_NH_RESPONSE_AWAITED" .................... 58
2.3.4 LDP Related Message Processing ............................. 59
3. State Machine for Downstream Unsolicited ...................... 61
3.1 Control Block ................................................ 61
3.2 States of the Upstream LSP Control Block's State Machine
for Downstream Mode .......................................... 62
3.3 Events of the Upstream LSP Control Block's State Machine
for Downstream Mode .......................................... 62
3.4 State Transitions of Upstream LSP Control Block's State
Machine for Downstream Mode .................................. 64
3.5 Upstream LSP Control Block's State Machine for
Downstream Mode .............................................. 65
3.5.1 : State -- "IDLE" .......................................... 65
3.5.2 : State -- "ESTABLISHED" ................................... 66
3.5.3 : State -- "RELEASE_AWAITED" ............................... 67
3.5.4 : State -- "RESOURCE_AWAITED" .............................. 69
3.6 State of the Downstream LSP Control Block's State Machine
for Downstream Mode .......................................... 70
3.7 Events of the Downstream LSP Control Block's State Machine
for Downstream Mode .......................................... 70
3.8 State Transitions of Downstream LSP Control Block's State
Machine for Downstream Mode .................................. 71
3.9 Downstream LSP Control Block's State Machine
for Downstream Mode .......................................... 71
3.9.1 : State -- "IDLE" .......................................... 71
3.9.2 : State -- "ESTABLISHED" ................................... 73
3.10 LDP Related Message Processing for downstream mode .......... 74
4. Security Considerations ....................................... 75
5. Acknowledgements .............................................. 76
6. References .................................................... 76
7. Authors' Address .............................................. 77
8. Full Copyright Statement ...................................... 78
2.3.3.8 Downstream LSP Control Block's State Machine for
Downstream-on-demand Mode ................................ 49
2.3.3.8.1 State -- "IDLE" ........................................ 48
2.3.3.8.2 State -- "RESPONSE_AWAITED" ............................ 50
2.3.3.8.3 State -- "ESTABLISHED" ................................. 52
2.3.3.9 State of the Next_Hop_Trigger_Control_Block's State
Machine for Downstream-on-demand Mode .................... 53
2.3.3.10 Events of the Next_Hop_Trigger_Control_Block's State
Machine for Downstream-on-demand Mode ................... 53
2.3.3.11 State Transitions of the Next_Hop_Trigger_Control_Block's
State Machine for Downstream-on-demand Mode ............. 55
2.3.3.12 State Machine ........................................... 55
2.3.3.12.1 State -- "IDLE" ....................................... 55
2.3.3.12.2 State -- "NEW_NH_RETRY" ............................... 57
2.3.3.12.3 State -- "NEW_NH_RESPONSE_AWAITED" .................... 58
2.3.4 LDP Related Message Processing ............................. 59
3. State Machine for Downstream Unsolicited ...................... 61
3.1 Control Block ................................................ 61
3.2 States of the Upstream LSP Control Block's State Machine
for Downstream Mode .......................................... 62
3.3 Events of the Upstream LSP Control Block's State Machine
for Downstream Mode .......................................... 62
3.4 State Transitions of Upstream LSP Control Block's State
Machine for Downstream Mode .................................. 64
3.5 Upstream LSP Control Block's State Machine for
Downstream Mode .............................................. 65
3.5.1 : State -- "IDLE" .......................................... 65
3.5.2 : State -- "ESTABLISHED" ................................... 66
3.5.3 : State -- "RELEASE_AWAITED" ............................... 67
3.5.4 : State -- "RESOURCE_AWAITED" .............................. 69
3.6 State of the Downstream LSP Control Block's State Machine
for Downstream Mode .......................................... 70
3.7 Events of the Downstream LSP Control Block's State Machine
for Downstream Mode .......................................... 70
3.8 State Transitions of Downstream LSP Control Block's State
Machine for Downstream Mode .................................. 71
3.9 Downstream LSP Control Block's State Machine
for Downstream Mode .......................................... 71
3.9.1 : State -- "IDLE" .......................................... 71
3.9.2 : State -- "ESTABLISHED" ................................... 73
3.10 LDP Related Message Processing for downstream mode .......... 74
4. Security Considerations ....................................... 75
5. Acknowledgements .............................................. 76
6. References .................................................... 76
7. Authors' Address .............................................. 77
8. Full Copyright Statement ...................................... 78
- LDP-REQUEST: LDP Label Request message
- LDP-REQUEST：LDP标签请求报文
- LDP-MAPPING: LDP Label Mapping message
- LDP映射：LDP标签映射消息
- LDP-WITHDRAW: LDP Label Withdraw message
- LDP-DRUCH：LDP标签撤销报文
- LDP-RELEASE: LDP Label Release message
- LDP-RELEASE：LDP标签释放消息
- LDP-ABORT: LDP Abort message used to abort a LSP setup.
- LDP-ABORT：用于中止LSP设置的LDP ABORT消息。
- LDP-NAK: LDP Notification message used to reject an LDP message.
- LDP-NAK：用于拒绝LDP消息的LDP通知消息。
In this document, we provide two sets of state machines: one for the ATM LSR that does not have VC-merge capability, and the other for the ATM LSR that does have VC-merge capability.
在本文中，我们提供了两组状态机：一组用于不具有VC合并功能的ATM LSR，另一组用于具有VC合并功能的ATM LSR。
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.
状态机描述以控制块、状态、事件、响应动作和状态转换的形式给出。控制块包含支持事件处理所需的信息。控制块还可以包含任何特定实现或支持其他所需功能所需的任何附加信息。在每种情况下，支持LDP规范[4]中定义的过程或LDP MIB[3]中定义的管理对象所需的附加信息将存储在特定LDP实现中-作为控制块结构的一部分或以某种其他方式。
The state machines cover both independent LSP control and ordered LSP control.
状态机包括独立LSP控制和有序LSP控制。
Loop detection and loop prevention messages will be processed as specified in [4]. The impact of loop detection and loop prevention messages on state transitions is left for further study.
循环检测和循环预防消息将按照[4]中的规定进行处理。循环检测和循环预防消息对状态转换的影响留待进一步研究。
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:
当拓扑发生变化且LSR检测到LSP的新的更好的下一跳时，它可能以两种不同的方式运行：
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.
1) 它试图进行“局部修复”。这意味着它通过新的下一跳扩展LSP，向前释放来自此LSR的旧路径，然后拼接到新扩展的LSP中。
2) If the LSP is created with the "pinned" 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 containing attributes for this New Next Hop (NH) that have changed.
2) 如果使用“pinted”选项（CR-LDP[5]）创建LSP，则LSR忽略新的下一跳更改，并且LSP保持不变。LSR可以决定发送LDP映射，该LDP映射包含已更改的新下一跳（NH）的属性。
In an MPLS domain where some ATM LSRs do not have VC-merge capability, downstream-on-demand mode is required for these ATM LSRs [1]. Also, "conservative label retention mode" is required in this case [1].
在一些ATM LSR不具备VC合并功能的MPLS域中，这些ATM LSR需要下游按需模式[1]。此外，在这种情况下需要“保守标签保留模式”[1]。
For each LSP, there are 2 kinds of state machines involved:
对于每个LSP，涉及两种状态机：
1) the LSP Control Block and its state machine that 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.
1) 可用于处理正常LSP设置的LSP控制块及其状态机。它是在LSR接收到新的LDP请求时创建的，在该请求的LSP被删除时删除。
2) the Next Hop Trigger Control Block and its state machine that 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 after a routing transient has had time to stabilize.
2) 下一跳触发控制块及其状态机，用于处理通过不同的下一跳切换到更好的LSP。它是在LSR决定切换到更好的下一跳时创建的，在LSR完成切换到更好的下一跳时删除。该状态机使用计时器（并具有相应的状态）确保在路由瞬态有时间稳定后及时发生切换。
For each LSP, an LSP Control Block is defined that may contain the following information:
对于每个LSP，定义的LSP控制块可能包含以下信息：
- Upstream Label Request ID (assigned by the upstream LSR), that is the 'Message Id' in the Label Request Message received from the upstream LSR.
- 上游标签请求ID（由上游LSR分配），即从上游LSR接收的标签请求消息中的“消息ID”。
- Downstream Label Request ID (assigned by this LSR itself), that is 'Message Id' in the Label Request Message sent to the downstream LSR.
- 下游标签请求ID（由该LSR本身分配），即发送到下游LSR的标签请求消息中的“消息ID”。
- Upstream LDP Identifier
- 上行LDP标识符
- Downstream LDP Identifier
- 下游LDP标识符
- State
- 状态
- FEC
- FEC
- Upstream Label (assigned by this LSR)
- 上游标签（由该LSR分配）
- Downstream Label (assigned by the downstream LSR)
- 下游标签（由下游LSR指定）
- Trigger Control Block Pointer, (Only used at the ingress LSR of a LSP) that points to the control block that triggers setting up this LSP or tearing down this LSP.
- 触发控制块指针（仅用于LSP的入口LSR），指向触发设置此LSP或拆除此LSP的控制块。
- Next Hop Control Block Pointer, that points to the control block that is used for switching over to a better LSP.
- 下一跳控制块指针，指向用于切换到更好LSP的控制块。
The following index combinations can be used to locate a unique LSP Control Block:
以下索引组合可用于定位唯一的LSP控制块：
- Downstream Label and Downstream LDP Identifier, or
- 下游标签和下游LDP标识符，或
- Upstream Label and Upstream LDP Identifier, or
- 上游标签和上游LDP标识符，或
- Downstream Label Request ID and Downstream LDP Identifier
- 下游标签请求ID和下游LDP标识符
- Upstream Label Request ID and Upstream LDP Identifier
- 上游标签请求ID和上游LDP标识符
Here is the relationship between different control blocks, the detail definition of Next Hop Trigger Control Block is described in section 2.2.6.
这是不同控制块之间的关系，下一跳触发控制块的详细定义见第2.2.6节。
For example, an LSP that transits through (LSR-A, LSR-B, LSR-C, LSR-D):
例如，通过（LSR-A、LSR-B、LSR-C、LSR-D）传输的LSP：
LSR-A ----> LSR-B ---> LSR-C ---> LSR-D
LSR-A ----> LSR-B ---> LSR-C ---> LSR-D
The control blocks in LSR-A are:
LSR-A中的控制块为：
+-----------------------+
| Trigger Control Block |
| (e.g, by config) |
+-----------------------+
^
|(Trigger Control block pointer)
|
|
+-----------------------+
| LSP Control Block |
+-----------------------+
+-----------------------+
| 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:
当LSR-B通过LSR-E检测到更好的LSR-D下一跳，并决定切换到它时，LSR-B中的控制块为：
+-----------------------+
| LSP Control Block |
| (original LSP) |
+-----------------------+
(LSP ^ |
Control | | (Next Hop Trigger Control Block Pointer)
Block | |
Pointer) | v
+--------------------------------+
| Next Hop Trigger Control Block |
+--------------------------------+
^ |
(Trigger | | (New Next Hop LSP
Control | | Control Block Pointer)
Block | |
Pointer)| |
| v
+------------------------+
| LSP Control Block |
| (for LSP: LSR-B, LSR-E,|
| LSR-D) |
+------------------------+
+-----------------------+
| LSP Control Block |
| (original LSP) |
+-----------------------+
(LSP ^ |
Control | | (Next Hop Trigger Control Block Pointer)
Block | |
Pointer) | v
+--------------------------------+
| Next Hop Trigger Control Block |
+--------------------------------+
^ |
(Trigger | | (New Next Hop LSP
Control | | Control Block Pointer)
Block | |
Pointer)| |
| v
+------------------------+
| LSP Control Block |
| (for LSP: LSR-B, LSR-E,|
| LSR-D) |
+------------------------+
This section describes the various states that are used in the state machine for the ATM non VC-merge LSR.
本节描述ATM非VC合并LSR的状态机中使用的各种状态。
-- IDLE
--闲散
This is the initial LSP state, when the LSP Control Block is created.
这是创建LSP控制块时的初始LSP状态。
-- 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 from the downstream LSR.
该状态意味着LSR已经接收并处理来自上游LSR的LDP请求，或者它已经接收到内部设置请求。它向下游LSR发送了一个新的LDP-REQUEST。LSR正在等待来自下游LSR的LDP映射。
-- ESTABLISHED
--确立
This state means that the LSR has received the LDP-MAPPING from the downstream LSR and the LSP is up and operational.
该状态意味着LSR已从下游LSR接收到LDP-MAPPING，并且LSP已启动并可操作。
-- RELEASE_AWAITED
--等待发布
This state means that the LSR has sent a LDP-WITHDRAW upstream and is waiting for the LDP-RELEASE before freeing up the label resource.
此状态意味着LSR已向上游发送LDP-RECURD，并在释放标签资源之前等待LDP-RELEASE。
-- LDP Request
--自民党请求
The LSR receives an LDP-REQUEST from an upstream LSR.
LSR接收来自上游LSR的LDP请求。
-- LDP Mapping
--LDP映射
The LSR receives an LDP-MAPPING from a downstream LSR.
LSR从下游LSR接收LDP映射。
-- LDP Release
--自民党释放
The LSR receives an LDP-RELEASE from an upstream LSR.
LSR从上游LSR接收LDP-RELEASE。
-- LDP Withdraw
--自民党退出
The LSR receives an LDP-WITHDRAW from a downstream LSR.
LSR从下游LSR接收LDP-draw。
-- LDP Upstream Abort
--上游中止
The LSR receives an LDP-ABORT from an upstream LSR.
LSR从上游LSR接收LDP-ABORT。
-- LDP Downstream NAK The LSR receives an LDP-NAK (notification) from an downstream LSR.
--LDP下游NAK LSR从下游LSR接收LDP-NAK（通知）。
-- Upstream Lost
--上游损失
The LSR loses its LDP session with an upstream LDP peer.
LSR失去与上游LDP对等方的LDP会话。
-- Downstream Lost
--下游损失
The LSR loses its LDP session with a downstream LDP peer.
LSR失去与下游LDP对等方的LDP会话。
-- 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.
出于某些原因，例如，流量工程隧道的配置请求或识别新FEC可能会触发内部设置事件，以从此节点设置新LSP。
-- Internal Destroy
--内部破坏
The LSR send an Internal Destroy event to tear down an LSP.
LSR发送内部销毁事件以拆除LSP。
-- Internal Cross-Connect
--内部交叉连接
The LSR send an Internal Cross-Connect to splice two LSPs into one LSP. This happens when a LSR switches over to a better next hop.
LSR发送内部交叉连接，将两个LSP拼接成一个LSP。当LSR切换到更好的下一跳时，就会发生这种情况。
-- Internal New NH
--新罕布什尔州内部
The LSR decides to switch over the better next hop.
LSR决定切换到更好的下一跳。
The following diagram describes briefly the state transitions.
下图简要描述了状态转换。
+-------------------+
| |<-------------------+
+-------->| IDLE | |
| | |----------+ |
| +-------------------+ | |
|(LDP Release) | | |
|(LDP Upstream |(LDP Request 1) | | (LDP Release)
| Abort |(Internal SetUp) | | (Upstream Lost)
|(Internal Destroy) | | |
|(Upstream Lost) v | |
| +-------------------+ | |
+---------| | | |
| RESPONSE_AWAITED | | |
+---------| | | |
| +-------------------+ | |
| | | |
|(Downstream Lost) |(LDP Mapping) | |
|(LDP Downstream | | |
| NAK) | +---------------+ |
| | | (LDP Request 2) |
| | | |
| v v |
| +-------------------+ (LDP Withdraw 1) |
| | | (Internal Destroy) |
| | ESTABLISHED |------------>-------+
| | | |
| +-------------------+ |
| | |
| | |
| |(LDP Withdraw 2) | (LDP Upstream
| |(Downstream Lost) | Abort)
| | |
| v |
| +-------------------+ |
| | | |
+-------->| RELEASE_AWAITED |------------>-------+
| |
+-------------------+
+-------------------+
| |<-------------------+
+-------->| IDLE | |
| | |----------+ |
| +-------------------+ | |
|(LDP Release) | | |
|(LDP Upstream |(LDP Request 1) | | (LDP Release)
| Abort |(Internal SetUp) | | (Upstream Lost)
|(Internal Destroy) | | |
|(Upstream Lost) v | |
| +-------------------+ | |
+---------| | | |
| RESPONSE_AWAITED | | |
+---------| | | |
| +-------------------+ | |
| | | |
|(Downstream Lost) |(LDP Mapping) | |
|(LDP Downstream | | |
| NAK) | +---------------+ |
| | | (LDP Request 2) |
| | | |
| v v |
| +-------------------+ (LDP Withdraw 1) |
| | | (Internal Destroy) |
| | ESTABLISHED |------------>-------+
| | | |
| +-------------------+ |
| | |
| | |
| |(LDP Withdraw 2) | (LDP Upstream
| |(Downstream Lost) | Abort)
| | |
| v |
| +-------------------+ |
| | | |
+-------->| RELEASE_AWAITED |------------>-------+
| |
+-------------------+
State: IDLE
状态：空闲
Event: LDP Request
事件：LDP请求
New State: Depends upon the action routine.
新状态：取决于操作例程。
Actions:
行动：
If this LSR is the LSP Egress or Proxy Egress [2]
如果此LSR是LSP出口或代理出口[2]
Then: Choose an upstream label, connect this upstream label to the local IP forwarding module, allocate the resources, send the LDP-MAPPING upstream with the upstream label, and go to the new state `ESTABLISHED'.
然后：选择一个上游标签，将该上游标签连接到本地IP转发模块，分配资源，将LDP-MAPPING与上游标签一起发送到上游，并转到新状态“已建立”。
else Obtain a next hop (or interface) with the FEC specified in the LDP-REQUEST, propagate the LDP-REQUEST, with newly assigned Message ID by this LSR, towards the obtained next hop, and go to the new state `RESPONSE_AWAITED'.
否则，使用LDP-REQUEST中指定的FEC获得下一跳（或接口），使用该LSR新分配的消息ID向获得的下一跳传播LDP-REQUEST，并转到新状态“RESPONSE_waitied”。
If the LSR uses the independent control mode [2], choose an upstream label, connect this upstream label to the local IP forwarding module, go to the ESTABLISHED state and send an LDP-MAPPING upstream with the upstream label.
如果LSR使用独立控制模式[2]，选择一个上游标签，将该上游标签连接到本地IP转发模块，转到已建立状态，并向上游发送带有上游标签的LDP映射。
If unable to process the request for any reason, issue an LDP-NAK to the sender with the appropriate error code, go to IDLE and delete the LSP Control Block.
如果由于任何原因无法处理该请求，则向发送方发出带有适当错误代码的LDP-NAK，转到IDLE并删除LSP控制块。
State: IDLE
状态：空闲
Event: LDP Mapping
事件：LDP映射
New State: IDLE
新状态：空闲
Actions:
行动：
Ignore the event. It is an internal implementation error.
忽略事件。这是一个内部实现错误。
State: IDLE
状态：空闲
Event: LDP Release
事件：LDP发布
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
事件：LDP上游中止
New State: IDLE
新状态：空闲
Actions:
行动：
Ignore the event. It is an internal implementation error.
忽略事件。这是一个内部实现错误。
State: IDLE
状态：空闲
Event: LDP Downstream NAK
事件：LDP下游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'.
使用内部设置消息中指定的FEC获得下一跳（或接口），向获得的下一跳发送LDP请求，并转到新状态“RESPONSE_waitied”。
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 implementation error.
忽视这是一个内部实现错误。
State: RESPONSE_AWAITED
国家：等待答复
Event: LDP Request
事件：LDP请求
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.
忽略事件。这是一个内部实现错误。非VC合并ATM LSR必须为新LDP请求创建新的LSP控制块。
State: RESPONSE_AWAITED
国家：等待答复
Event: LDP Mapping
事件：LDP映射
New State: ESTABLISHED
新国家：成立
Actions:
行动：
1) If the LSP is triggered by the local router (Trigger Control Block Pointer is not zero), send event `Internal LSP UP' to the Trigger control block.
1) 如果本地路由器触发LSP（触发器控制块指针不为零），则向触发器控制块发送事件“Internal LSP UP”。
2) Else If the LSR uses the ordered control mode, choose an upstream label.
2) 否则，如果LSR使用有序控制模式，请选择上游标签。
3) Connect the upstream label to the downstream label. Allocate the resources. Propagate the LDP-MAPPING upstream with the upstream label.
3) 将上游标签连接到下游标签。分配资源。使用上游标签向上游传播LDP映射。
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 downstream and an LDP-NAK upstream with status (No Label Resources [4]), go to IDLE and delete the LSP Control Block.
如果无法处理消息，请断开上游标签与下游标签的连接，释放上游标签，释放资源，向下游发送LDP-release和向上游发送状态为（无标签资源[4]）的LDP-NAK，转到IDLE并删除LSP控制块。
State: RESPONSE_AWAITED
国家：等待答复
Event: LDP Release
事件：LDP发布
New State: IDLE
新状态：空闲
Actions:
行动：
If the LSR uses the independent control mode, free the upstream label.
如果LSR使用独立控制模式，则释放上游标签。
Send an LDP-ABORT downstream, go to IDLE and delete the LSP Control Block.
向下游发送LDP-ABORT，转到IDLE并删除LSP控制块。
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.
注意：只有当LSR使用独立控制模式时，才会出现这种情况。在有序控制模式下，在等待来自下游的标签映射时，不会发送与此LSP对应的上游标签映射。
State: RESPONSE_AWAITED
国家：等待答复
Event: LDP Withdraw
事件：自民党退出
New State: RESPONSE_AWAITED
新国家：等待答复
Actions:
行动：
Ignore the event. It's a protocol error from the downstream LSR.
忽略事件。这是来自下游LSR的协议错误。
State: RESPONSE_AWAITED
国家：等待答复
Event: LDP Upstream Abort
事件：LDP上游中止
New State: IDLE
新状态：空闲
Actions:
行动：
If the LSR uses the independent control mode, free the upstream label.
如果LSR使用独立控制模式，则释放上游标签。
Send an LDP-ABORT downstream.
向下游发送LDP-ABORT。
Delete the LSP Control Block.
删除LSP控制块。
State: RESPONSE_AWAITED
国家：等待答复
Event: LDP Downstream NAK
事件：LDP下游NAK
New State: Depends on the action routine.
新状态：取决于操作例程。
Actions:
行动：
1. If the LSP is triggered by the local router (Trigger Control Block Pointer is not zero), send event `Internal LSP DOWN' to the Trigger control block, go to IDLE and delete the LSP Control Block.
1. 如果本地路由器触发了LSP（触发控制块指针不为零），则向触发控制块发送事件“Internal LSP DOWN”，转到IDLE并删除LSP控制块。
2. Else If the LSR uses the independent control mode, send an LDP-WITHDRAW upstream and go to state `RELEASE_AWAITED'.
2. 否则，如果LSR使用独立控制模式，则向上游发送LDP-RECUR并进入状态“RELEASE_WAITED”。
If the LSR uses the ordered control mode, send an LDP-NAK upstream, go to IDLE and delete the LSP Control Block.
如果LSR使用有序控制模式，则向上游发送LDP-NAK，转到IDLE并删除LSP控制块。
State: RESPONSE_AWAITED
国家：等待答复
Event: Upstream Lost
事件：上游损失
New State: IDLE
新状态：空闲
Actions:
行动：
If the LSR uses the independent control mode, free the upstream label.
如果LSR使用独立控制模式，则释放上游标签。
Send an LDP-ABORT downstream, go to IDLE and delete the LSP Control Block.
向下游发送LDP-ABORT，转到IDLE并删除LSP控制块。
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 Control Block Pointer is not zero), send event `Internal LSP DOWN' to the trigger control block, go to IDLE and delete the LSP Control Block.
1. 如果本地路由器触发了LSP（触发控制块指针不为零），则向触发控制块发送事件“Internal LSP DOWN”，转到IDLE并删除LSP控制块。
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'.
2. 否则，如果LSR使用独立控制模式，则释放上游标签并向上游发送LDP-RECUR并进入状态“RELEASE_WAITED”。
If the LSR uses the ordered control mode, send an LDP-NAK upstream (with a status `No Route' [4]), go to IDLE and delete the LSP Control Block.
如果LSR使用有序控制模式，则向上游发送LDP-NAK（状态为“无路由”[4]），转到IDLE并删除LSP控制块。
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, go to IDLE and delete the LSP Control Block.
向下游发送LDP-ABORT，转到IDLE并删除LSP控制块。
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.
向旧下游发送LDP-ABORT，向新的下一跳发送LDP-REQUEST。
State: ESTABLISHED
国家：已建立
Event: LDP Request
事件：LDP请求
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.
忽略事件。这是一个内部实现错误。对于非VC合并ATM LSR，始终为每个LDP请求创建一个新的LSP控制块。
State: ESTABLISHED
国家：已建立
Event: LDP Mapping
事件：LDP映射
New State: ESTABLISHED
新国家：成立
Actions:
行动：
Process the LDP-MAPPING, that may contain the new attributes of the label mapping and then propagate the LDP-MAPPING upstream.
处理LDP映射，该映射可能包含标签映射的新属性，然后向上游传播LDP映射。
State: ESTABLISHED
国家：已建立
Event: LDP Release
事件：LDP发布
New State: IDLE
新状态：空闲
Actions:
行动：
Disconnect the upstream label from the downstream label.
断开上游标签与下游标签的连接。
Free the upstream label.
释放上游标签。
Free the resources.
释放资源。
Send event `Internal Destroy' to the Next Hop Trigger Control Block if it was in the middle of switching over to the better next hop.
如果事件在切换到更好的下一跳中，则将事件“内部破坏”发送到下一跳触发控制块。
Propagate the LDP-RELEASE downstream if the LSR is not the egress for the LSP, go to IDLE and delete the LSP Control Block.
如果LSR不是LSP的出口，则向下游传播LDP释放，转到IDLE并删除LSP控制块。
State: ESTABLISHED
国家：已建立
Event: LDP Withdraw
事件：自民党退出
New State: Depends on the action routine.
新状态：取决于操作例程。
Actions:
行动：
1) Free the resources and send LDP-RELEASE downstream.
1) 释放资源并向下游发送LDP-RELEASE。
2) If it is independent control mode, set the state to `IDLE', create a internal LDP Request with the information in the LSP Control Block, and pass event `LDP Request' to its own state machine.
2) 如果是独立控制模式，则将状态设置为“空闲”，使用LSP控制块中的信息创建一个内部LDP请求，并将事件“LDP请求”传递给它自己的状态机。
3) Else for the ordered control mode
3) 顺序控制模式的Else
3.1) If the LSP is triggered to be setup by itself (e.g it is the ingress LSR of this LSP), send event `Internal LSP Down' to the trigger control block, go to IDLE and delete the LSP Control Block.
3.1）如果触发LSP自行设置（例如，它是该LSP的入口LSR），则向触发控制块发送事件“内部LSP Down”，转到IDLE并删除LSP控制块。
3.2) Else, if it is triggered by the incoming LDP Request, Disconnect the upstream label from the downstream label. Propagate the LDP-WITHDRAW upstream and go to state `RELEASE_AWAITED'.
3.2）否则，如果由传入LDP请求触发，则断开上游标签与下游标签的连接。向上游宣传LDP-RECUR，并进入“等待发布”状态。
3.3) If the LSP is in the middle of switching over to a better LSP, send event `Internal Destroy' to the state machine of its New Next Hop LSP Control Block, go to IDLE and delete the LSP Control Block.
3.3）如果LSP处于切换到更好的LSP的中间，将事件“内部破坏”发送到其新的下一跳LSP控制块的状态机，转到空闲并删除LSP控制块。
State: ESTABLISHED
国家：已建立
Event: LDP Upstream Abort
事件：LDP上游中止
New State: ESTABLISHED
新国家：成立
Actions:
行动：
Ignore the event.
忽略事件。
Note: This scenario can occur if the upstream LSR sends a LDP-ABORT at about the same time as the local LSR sends a LDP-MAPPING. In this situation, it should be up to exactly one of the two LSRs as to whether or not the label that was sent remains valid. The LDP specification [4] procedures leave the choice to the upstream LSR that must send an LDP-RELEASE if it will not use the label provided.
注意：如果上游LSR发送LDP-ABORT的时间与本地LSR发送LDP-MAPPING的时间大致相同，则可能出现这种情况。在这种情况下，发送的标签是否仍然有效，取决于两个LSR中的一个。LDP规范[4]程序将选择权留给上游LSR，如果上游LSR不使用提供的标签，则必须发送LDP-RELEASE。
State: ESTABLISHED
国家：已建立
Event: LDP Downstream NAK
事件：LDP下游NAK
New State: ESTABLISHED
新国家：成立
Actions:
行动：
Ignore the event. It is a protocol error from the downstream LSR. The downstream LSR should always LSP-WITHDRAW to tear down the LSP when the LSP is established.
忽略事件。这是来自下游LSR的协议错误。当LSP建立时，下游LSR应始终使用LSP-DRUCH拆除LSP。
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' 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 downstream, go to IDLE and delete the LSP Control Block.
向下游传播LDP释放，转到空闲并删除LSP控制块。
State: ESTABLISHED
国家：已建立
Event: Downstream Lost
事件：下游损失
New State: Depends on the action routine.
新状态：取决于操作例程。
Actions:
行动：
1) If the LSP is triggered by the local router (Trigger Control Block Pointer is not zero), send event `Internal LSP NAK' to the Trigger control block, go to IDLE and delete the LSP Control Block.
1) 如果本地路由器触发LSP（触发控制块指针不为零），则向触发控制块发送事件“Internal LSP NAK”，转到IDLE并删除LSP控制块。
2) Else, disconnect the upstream label from the downstream label. Propagate an LDP-WITHDRAW upstream and go to `RELEASE_AWAITED' state.
2) 否则，断开上游标签与下游标签的连接。向上游传播LDP-RECURE并进入“释放等待”状态。
3) Send event `Internal Destroy' to the Next Hop Trigger Control Block if it was in the middle of switching over to the better next hop.
3) 如果事件在切换到更好的下一跳中，则将事件“内部破坏”发送到下一跳触发控制块。
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.
如果上游标签不是LSP入口，则断开上游标签与下游标签的连接。
Free the resources.
释放资源。
Send an LDP-RELEASE downstream, go to IDLE and delete the LSP Control Block.
向下游发送LDP释放，转到IDLE并删除LSP控制块。
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.
可能需要向上游发送一个新的LDP映射，其中包含来自新下一跳的属性。
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 Trigger Control Block Pointer is not zero), it send `Internal New NH' to that control block.
1) 如果LSR处于切换到更好的下一跳（下一跳触发器控制块指针不是零）的中间，则它将“内部新NH”发送到该控制块。
2) Else, create a new Next Hop Trigger Control Block, set Next Hop Trigger Control Block pointer to point to this control block, and pass 'Internal New NH' to this control block.
2) 否则，创建一个新的下一跳触发器控制块，将下一跳触发器控制块指针设置为指向该控制块，并将“内部新NH”传递给该控制块。
State: RELEASE_AWAITED
状态：等待发布
Event: LDP Request
事件：LDP请求
New State: RELEASE_AWAITED
新状态：等待发布
Actions:
行动：
Ignore the event. It is an internal implementation error.
忽略事件。这是一个内部实现错误。
State: RELEASE_AWAITED
状态：等待发布
Event: LDP Mapping
事件：LDP映射
New State: RELEASE_AWAITED
新状态：等待发布
Actions:
行动：
It is a protocol error from the downstream LDP peer, but anyway send a LDP-RELEASE downstream.
这是来自下游LDP对等方的协议错误，但无论如何都会向下游发送LDP-RELEASE。
State: RELEASE_AWAITED
状态：等待发布
Event: LDP Release
事件：LDP发布
New State: IDLE
新状态：空闲
Actions:
行动：
1) Free the upstream label
1) 释放上游标签
2) Delete the control block.
2) 删除控制块。
State: RELEASE_AWAITED
状态：等待发布
Event: LDP Withdraw
事件：自民党退出
New State: RELEASE_AWAITED
新状态：等待发布
Actions:
行动：
It is a protocol error from the downstream LDP peer, but send a LDP- RELEASE anyway.
这是来自下游LDP对等方的协议错误，但无论如何发送LDP释放。
State: RELEASE_AWAITED
状态：等待发布
Event: LDP Upstream Abort
事件：LDP上游中止
New State: IDLE
新状态：空闲
Actions:
行动：
1) Free the upstream label
1) 释放上游标签
2) Delete the control block.
2) 删除控制块。
State: RELEASE_AWAITED
状态：等待发布
Event: LDP Downstream NAK
事件：LDP下游NAK
New State: RELEASE_AWAITED
新状态：等待发布
Actions:
行动：
Ignore the event. Continue waiting for the LDP-RELEASE from upstream.
忽略事件。继续等待上游的LDP释放。
State: RELEASE_AWAITED
状态：等待发布
Event: Upstream Lost
事件：上游损失
New State: IDLE
新状态：空闲
Actions:
行动：
1) Free the upstream label
1) 释放上游标签
2) Delete the control block.
2) 删除控制块。
State: RELEASE_AWAITED
状态：等待发布
Event: Downstream Lost
事件：下游损失
New State: RELEASE_AWAITED
新状态：等待发布
Actions:
行动：
Ignore the event. Continue waiting for the LDP-RELEASE from upstream.
忽略事件。继续等待上游的LDP释放。
State: RELEASE_AWAITED
状态：等待发布
Event: Internal SetUp
事件：内部设置
New State: RELEASE_AWAITED
新状态：等待发布
Actions:
行动：
Ignore the event. It is an internal implementation error.
忽略事件。这是一个内部实现错误。
State: RELEASE_AWAITED
状态：等待发布
Event: Internal Destroy
事件：内部销毁
New State: RELEASE_AWAITED
新状态：等待发布
Actions:
行动：
Ignore the event. It is an internal implementation error.
忽略事件。这是一个内部实现错误。
State: RELEASE_AWAITED
状态：等待发布
Event: Internal Cross-Connect
事件：内部交叉连接
New State: RELEASE_AWAITED
新状态：等待发布
Actions:
行动：
Ignore the event. It is an internal implementation error.
忽略事件。这是一个内部实现错误。
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.
当LSR检测到更好的下一跳时，它可能决定通过该下一跳建立新的LSP。例如，LSR配置为“本地修复”，或LSR配置为“全局修复”，并且它是LSP的入口端。然后，它可以创建下一跳触发控制块，并使用下一跳触发控制块的状态机通过更好的下一跳建立新的LSP。
-- State
--陈述
-- LSP Control Block Pointer, that points to the original LSP control block.
--LSP控制块指针，指向原始LSP控制块。
-- New Next Hop LSP Control Block Pointer, that points to the LSP Control Block that is setting up an LSP through the new next hop.
--新下一跳LSP控制块指针，指向通过新下一跳设置LSP的LSP控制块。
-- IDLE
--闲散
This is the initial LSP state, when the Trigger_Control_Block is created.
这是创建触发器控制块时的初始LSP状态。
-- NEW_NH_RETRY
--新建\u nhu\u重试
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.
这是LSR等待重试计时器过期，然后尝试通过新的下一跳建立LSP的状态。
-- 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.
这是LSR正在通过新的下一跳建立新的LSP的过程中的状态。它已触发LSP控制块向新的下一跳发送LDP请求，并正在等待LDP映射。
-- Internal New NH
--新罕布什尔州内部
The LSR detects there is a new next hop for a FEC.
LSR检测到FEC存在新的下一跳。
-- Internal Retry Timeout
--内部重试超时
The LSP retry timer expires.
LSP重试计时器过期。
-- Internal LSP UP
--内部LSP启动
The LSP to the new Next Hop is UP
新下一跳的LSP已启动
-- Internal LSP NAK
--内部LSP NAK
The LSP through the new next hop could not get set up
无法设置通过新下一跳的LSP
-- Internal Destroy
--内部破坏
This event is triggered when the LSR lost the LDP session with its upstream neighbor.
当LSR失去与其上游邻居的LDP会话时，会触发此事件。
+---------------------+
| |
| IDLE |<------------+
| | |
+---------------------+ |
| |
| |
| (Internal New NH) |
| |
v |
+---------------------+ |
| | |
| NEW_NH_RETRY |----------->-+
| | (Internal |
+---------------------+ Destroy) |
| |
| |
| (Internal retry timeout) |
| |
v |
+---------------------+ |
| | (Internal |
| NEW_NH_RESPONSE | Destroy) |
| _AWAITED |----------->-+
| | |
+---------------------+ |
| |
| (Internal LSP UP) |
| (Internal LSP NAK) |
+------------------------>-+
+---------------------+
| |
| IDLE |<------------+
| | |
+---------------------+ |
| |
| |
| (Internal New NH) |
| |
v |
+---------------------+ |
| | |
| NEW_NH_RETRY |----------->-+
| | (Internal |
+---------------------+ Destroy) |
| |
| |
| (Internal retry timeout) |
| |
v |
+---------------------+ |
| | (Internal |
| NEW_NH_RESPONSE | Destroy) |
| _AWAITED |----------->-+
| | |
+---------------------+ |
| |
| (Internal LSP UP) |
| (Internal LSP NAK) |
+------------------------>-+
State: IDLE
状态：空闲
Event: Internal New NH
事件：新罕布什尔州内部
New State: NEW_NH_RETRY
新状态：新重试
Actions:
行动：
Start the LSP retry timer and go to the `NEW_NH_RETRY' state.
启动LSP重试计时器并转到“新建重试”状态。
State: IDLE
状态：空闲
Event: Internal retry timeout
事件：内部重试超时
New State: IDLE
新状态：空闲
Actions:
行动：
Ignore. It is an internal implementation error.
忽视这是一个内部实现错误。
State: IDLE
状态：空闲
Event: Internal LSP UP
事件：内部LSP启动
New State: IDLE
新状态：空闲
Actions:
行动：
Ignore. It is an internal implementation error.
忽视这是一个内部实现错误。
State: IDLE
状态：空闲
Event: Internal LSP NAK
事件：内部LSP NAK
New State: IDLE
新状态：空闲
Actions:
行动：
Ignore. It is an internal implementation error.
忽视这是一个内部实现错误。
State: IDLE
状态：空闲
Event: Internal destroy
事件：内部销毁
New State: IDLE
新状态：空闲
Actions:
行动：
Ignore. It is an internal implementation error.
忽视这是一个内部实现错误。
State: NEW_NH_RETRY
状态：新建\u nhu\u重试
Event: Internal New NH
事件：新罕布什尔州内部
New State: NEW_NH_RETRY
新状态：新重试
Actions:
行动：
Restart the LSP retry timer.
重新启动LSP重试计时器。
State: NEW_NH_RETRY
状态：新建\u nhu\u重试
Event: Internal retry timeout
事件：内部重试超时
New State: Depends on action routine.
新状态：取决于操作例程。
Actions:
行动：
If the new next hop is the same one as the old next hop, go to IDLE and delete the control block.
如果新的下一个跃点与旧的下一个跃点相同，请转到IDLE并删除控制块。
Otherwise, create an LSP control block that will try to establish a new LSP through the new next hop, send event `Internal Setup' to its state machine and go to NEW_NH_RESPONSE_AWAITED.
否则，创建一个LSP控制块，该控制块将尝试通过新的下一跳建立一个新的LSP，将事件“内部设置”发送到其状态机，并转到等待的新响应。
State: NEW_NH_RETRY
状态：新建\u nhu\u重试
Event: Internal LSP UP
事件：内部LSP启动
New State: NEW_NH_RETRY
新状态：新重试
Actions:
行动：
Ignore. It is an internal implementation error.
忽视这是一个内部实现错误。
State: NEW_NH_RETRY
状态：新建\u nhu\u重试
Event: Internal LSP NAK
事件：内部LSP NAK
New State: NEW_NH_RETRY
新状态：新重试
Actions:
行动：
Ignore. It is an internal implementation error.
忽视这是一个内部实现错误。
State: NEW_NH_RETRY
状态：新建\u nhu\u重试
Event: Internal destroy
事件：内部销毁
New State: IDLE
新状态：空闲
Actions:
行动：
Stop the timer, go to IDLE and delete the control block.
停止定时器，转到IDLE并删除控制块。
State: NEW_NH_RESPONSE_AWAITED
州：等待新的答复
Event: Internal New NH
事件：新罕布什尔州内部
New State: NEW_NH_RETRY
新状态：新重试
Actions:
行动：
Restart the LSP retry timer, send `Internal destroy' to the control block of the LSP for the new next hop and go to the `NEW_NH_RETRY' state.
重新启动LSP重试计时器，将“内部销毁”发送到LSP的控制块以用于新的下一跳，并转到“新重试”状态。
State: NEW_NH_RESPONSE_AWAITED
州：等待新的答复
Event: Internal retry timeout
事件：内部重试超时
New State: NEW_NH_RESPONSE_AWAITED
新州：等待新的答复
Actions:
行动：
Ignore. It is an internal implementation error.
忽视这是一个内部实现错误。
State: NEW_NH_RESPONSE_AWAITED
州：等待新的答复
Event: Internal LSP UP
事件：内部LSP启动
New State: IDLE
新状态：空闲
Actions:
行动：
Send event `Internal cross-connect' event to the LSP control block of the new next hop.
将事件“内部交叉连接”事件发送到新下一跳的LSP控制块。
Send event `Internal destroy' event to the original LSP control block.
将事件“内部销毁”事件发送到原始LSP控制块。
Then go to IDLE and delete the control block.
然后转到IDLE并删除控制块。
State: NEW_NH_RESPONSE_AWAITED
州：等待新的答复
Event: Internal LSP NAK
事件：内部LSP NAK
New State: IDLE
新状态：空闲
Actions:
行动：
Delete the control block.
删除控制块。
State: NEW_NH_RESPONSE_AWAITED
州：等待新的答复
Event: Internal destroy
事件：内部销毁
New State: IDLE
新状态：空闲
Actions:
行动：
Send event `Internal destroy' the control block for the new LSP through the new next hop.
通过新的下一跳向新LSP的控制块发送事件“内部销毁”。
- If an LSR receives an LDP-REQUEST from an upstream LSR:
- 如果LSR从上游LSR接收到LDP请求：
a) If this is a duplicate request, discard the message. A duplicate request means that there is a LSP Control Block that has the same FEC, Upstream Label Request ID and Upstream Label Request ID and same Upstream LDP Session Identifier.
a) 如果这是重复的请求，则丢弃该消息。重复请求意味着存在具有相同FEC、上游标签请求ID和上游标签请求ID以及相同上游LDP会话标识符的LSP控制块。
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.
b) 否则，创建一个新的LSP控制块，将消息中的相关信息存储到控制块中，然后将事件“LDP Request”传递给其状态机。
- If an LSR receives an LDP-MAPPING from a downstream LSR:
- 如果LSR从下游LSR接收到LDP映射：
a) Extract the 'Label Request Message ID' field and from the LDP-MAPPING.
a) 从LDP映射中提取“标签请求消息ID”字段和。
b) Find an LSP Control Block that has the same Downstream Label Request ID and the same Downstream LDP Session Identifier.
b) 查找具有相同下游标签请求ID和相同下游LDP会话标识符的LSP控制块。
c) If an LSP Control Block is found, pass the event `LDP Mapping' to its state machine.
c) 如果找到LSP控制块，则将事件“LDP映射”传递到其状态机。
d) If there is no matching LSP Control Block found, then try to find an LSP Control Block that has the same Downstream Label and the same Downstream LDP Session Identifier.
d) 如果没有找到匹配的LSP控制块，则尝试查找具有相同下游标签和相同下游LDP会话标识符的LSP控制块。
e) If an LSP Control Block is found, pass the event `LDP Mapping' to its state machine.
e) 如果找到LSP控制块，则将事件“LDP映射”传递到其状态机。
f) Otherwise, ignore the LDP-MAPPING and send a LDP-RELEASE downstream.
f) 否则，忽略LDP映射并向下游发送LDP释放。
- If an LSR receives an LDP-RELEASE from an upstream LSR:
- 如果LSR从上游LSR接收到LDP释放：
a) Find an LSP Control Block that has the same Upstream Label and the same Upstream LDP Session Identifier.
a) 查找具有相同上游标签和相同上游LDP会话标识符的LSP控制块。
b) If an LSP Control Block is found, pass the event `LDP Release' to its state machine.
b) 如果找到LSP控制块，则将事件“LDP释放”传递给其状态机。
c) Otherwise, ignore the message.
c) 否则，忽略该消息。
- If an LSR receives an LDP-WITHDRAW from a downstream LSR:
- 如果LSR从下游LSR接收到LDP-DROW：
a) Find an LSP Control Block that has the same Downstream Label and the same Downstream LDP Session Identifier.
a) 查找具有相同下游标签和相同下游LDP会话标识符的LSP控制块。
b) If an LSP Control Block is found, pass the event `LDP Withdraw' to its state machine.
b) 如果找到LSP控制块，则将事件“LDP RECURN”传递给其状态机。
c) Otherwise, ignore the LDP-WITHDRAW and send a LDP-RELEASE downstream.
c) 否则，忽略LDP-REQUE并向下游发送LDP-REQUE。
- If an upstream LDP peer is lost:
- 如果上游LDP对等点丢失：
a) Find all the LSP Control Blocks whose upstream LDP peer is that LSR.
a) 查找其上游LDP对等方为该LSR的所有LSP控制块。
b) Then pass the event `Upstream Lost' to their state machines.
b) 然后将事件“上游丢失”传递给它们的状态机。
- If a downstream LDP peer is lost:
- 如果下游LDP对等点丢失：
a) Find all the LSP Control Blocks whose downstream LDP peer is that LSR.
a) 查找其下游LDP对等方为该LSR的所有LSP控制块。
b) Then pass the event `Downstream Lost' to their state machines.
b) 然后将事件“下游丢失”传递给它们的状态机。
- If the LSR detects a new next hop for an FEC:
- 如果LSR检测到FEC的新下一跳：
For each LSP that 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.
对于每个需要“本地修复”或需要“全局修复”且是LSP入口的LSP，将事件“Internal New NH”传递到其状态机。
- If an LSR receives an LDP-Abort from an upstream LSR:
- 如果LSR从上游LSR接收到LDP中止：
a) Extract the LDP Request ID value from the LDP-Abort message.
a) 从LDP中止消息中提取LDP请求ID值。
b) Find an LSP Control Block that has the same Upstream Label Request ID and the same Upstream LDP Session Identifier.
b) 查找具有相同上游标签请求ID和相同上游LDP会话标识符的LSP控制块。
c) If an LSP Control Block is found, pass the event `LDP Upstream Abort' to its state machine.
c) 如果找到LSP控制块，则将事件“LDP上游中止”传递给其状态机。
d) Otherwise, ignore the message.
d) 否则，忽略该消息。
- If the LSR receives an LDP-NAK from a downstream LSR:
- 如果LSR从下游LSR接收到LDP-NAK：
a) Extract the LDP Request ID value from the LDP-NAK.
a) 从LDP-NAK中提取LDP请求ID值。
b) Find an LSP Control Block that has the same Downstream Label Request ID and the same Downstream LDP Session Identifier.
b) 查找具有相同下游标签请求ID和相同下游LDP会话标识符的LSP控制块。
c) If an LSP Control Block is found, pass the event `LDP Downstream NAK' to its state machine.
c) 如果找到LSP控制块，则将事件“LDP下游NAK”传递给其状态机。
d) Otherwise, ignore the message.
d) 否则，忽略该消息。
A VC-merge capable LSR can map multiple incoming 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 [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.
支持VC合并的LSR可以将多个传入标签（VPI/VCI）映射到一个传出标签。此LSR可能只能将有限数量的传入标签合并到单个传出标签中。如[2]所述，例如，假设由于某些硬件限制，一个节点能够将四个传入标签合并为一个传出标签。但是，假设这个特定节点有六个到达它的特定FEC的传入标签。在这种情况下，此节点可以将这些标签合并为两个传出标签。
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.
当上游LSR具有有限的合并能力时，下游LSR很难知道应该为每个FEC分配多少标签。在这种情况下，建议按需下游。
There are 3 types of control blocks involved: Upstream LSP Control Block, Downstream LSP Control Block, and Next Hop Trigger Control Block.
涉及到3种类型的控制块：上游LSP控制块、下游LSP控制块和下一跳触发控制块。
There is one Upstream LSP Control Block for each LDP-REQUEST received.
对于接收到的每个LDP请求，都有一个上游LSP控制块。
There is one Downstream LSP Control Block for each unique 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 for an FEC. This LSR must assign a unique upstream label and it can not merge this upstream label into an existing downstream label for this FEC.
对于发送到下游LSR的每个唯一LDP请求，存在一个下游LSP控制块。在LSR中，每个FEC可以有多个下游LSP控制块。这可能是上游LSR请求FEC标签的结果。此LSR必须分配唯一的上游标签，并且不能将此上游标签合并到此FEC的现有下游标签。
There is one Next Hop Trigger Control Block for each FEC for which a better next hop has been detected and the LSR has decided to switch 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.
对于已检测到更好的下一跳且LSR已决定切换到此更好的下一跳的每个FEC，存在一个下一跳触发控制块。如果LSR是LSP的入口LSR，则可能是“本地修复”或“全局修复”的结果。
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.
下游LSP控制块包含指向上游LSP控制块或下一跳触发控制块的指针列表。这意味着该LSR已决定将上游LSP控制块和下一跳触发控制块中列出的多个标签映射到下游LSP控制块中列出的单个标签。
An Upstream LSP Control Block may contain the following information:
上游LSP控制块可包含以下信息：
- Upstream LDP Session Identifier
- 上行LDP会话标识符
- State
- 状态
- Upstream Label (assigned by this LSR)
- 上游标签（由该LSR分配）
- Downstream LSP Control Block pointer
- 下游LSP控制块指针
- Upstream LDP Request ID (assigned by the upstream LSR in downstream-on-demand mode)
- 上游LDP请求ID（由上游LSR在下游按需模式下分配）
- Next_Hop_Trigger_Block pointer
- 下一跳触发块指针
Upstream Label and Upstream LDP Session Identifier can be used to locate a unique Upstream LSP Control Block.
上游标签和上游LDP会话标识符可用于定位唯一的上游LSP控制块。
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.
如果LSR使用下游按需模式，则它可以使用上游LDP请求ID和上游LDP会话标识符来定位唯一的上游LSP控制块。
An Next_Hop_Trigger LSP Control Block may contain the following information:
下一跳触发LSP控制块可包含以下信息：
- Upstream LSP Control Block pointer, that points to the one that is needed to switch over to the better next hop
- 上游LSP控制块指针，指向切换到更好的下一跳所需的指针
- State
- 状态
- Downstream LSP Control Block pointer
- 下游LSP控制块指针
A Downstream LSP Control Block may contain the following information:
下游LSP控制块可包含以下信息：
- FEC
- FEC
- State
- 状态
- Downstream LDP Session Identifier
- 下行LDP会话标识符
- list of pointers to the Upstream LSP Control Blocks or the Trigger_Control_Blocks that are merged at this LSR for this FEC
- 指向上游LSP控制块或触发器控制块的指针列表，这些控制块在该FEC的该LSR处合并
- Downstream Label (assigned by the downstream LSR)
- 下游标签（由下游LSR指定）
- Downstream Label Request ID (assigned by the LSR itself if it is using downstream-on-demand mode)
- 下游标签请求ID（如果使用下游按需模式，则由LSR本身分配）
Downstream Label, Downstream LDP Session Identifier can be used to locate a unique Downstream LSP Control Block.
下游标签，下游LDP会话标识符可用于定位唯一的下游LSP控制块。
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.
如果LSR使用下游按需模式，则它还可以使用下游标签请求ID和下游LDP会话标识符来定位唯一的下游LSP控制块。
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 into one LDP-REQUEST and sent it to a downstream LSR4.
例如，LSR已决定将来自上游LSR1、LSR2、LSR3的FEC的3个LDP请求合并为一个LDP请求，并将其发送到下游LSR4。
+---------------------+
| |
| Upstream_LSP_Control|
| _Block for Upstream|------+
| LSR1 | |
+---------------------+ |
|
+---------------------+ |
| | |
| Upstream_LSP_Control| | (merged into)
| _Block for Upstream |------+
| LSR2 | |
+---------------------+ | +------------------------------+
| | |
+---------------------+ +--->| Downstream LSP Control Block |
| Next_Hop_Trigger_ | | | for Downstream LSR4 |
| LSP Control Block |------+ | |
| | +------------------------------+
+---------------------+
+---------------------+
| |
| Upstream_LSP_Control|
| _Block for Upstream|------+
| LSR1 | |
+---------------------+ |
|
+---------------------+ |
| | |
| Upstream_LSP_Control| | (merged into)
| _Block for Upstream |------+
| LSR2 | |
+---------------------+ | +------------------------------+
| | |
+---------------------+ +--->| Downstream LSP Control Block |
| Next_Hop_Trigger_ | | | for Downstream LSR4 |
| LSP Control Block |------+ | |
| | +------------------------------+
+---------------------+
The following sections describe the state machines used in downstream-on-demand mode.
以下各节描述了下游按需模式中使用的状态机。
2.3.3.1 State of the Upstream LSP Control Block's State Machine for Downstream-on-demand Mode
2.3.3.1 下游按需模式的上游LSP控制块状态机的状态
-- IDLE
--闲散
This is the initial LSP state.
这是初始LSP状态。
-- 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 from the downstream LSR.
该状态意味着LSR已经接收并处理来自上游LSR的LDP-REQUEST，并且已经向下游LSR发送新的LDP-REQUEST。LSR正在等待来自下游LSR的LDP映射。
-- ESTABLISHED
--确立
This state means that the LSR has received the LDP-MAPPING from the downstream LSR and the LSP is up and operational.
该状态意味着LSR已从下游LSR接收到LDP-MAPPING，并且LSP已启动并可操作。
-- RELEASE_AWAITED
--等待发布
This state means that the LSR has sent a LDP-WITHDRAW upstream and is waiting for the LDP-RELEASE before freeing up the label resource.
此状态意味着LSR已向上游发送LDP-RECURD，并在释放标签资源之前等待LDP-RELEASE。
2.3.3.2 Events of the Upstream LSP Control Block's State Machine for Downstream-on-demand Mode
2.3.3.2 下游按需模式的上游LSP控制块状态机事件
-- LDP Request
--自民党请求
The LSR receives an LDP-REQUEST from an upstream LSR.
LSR接收来自上游LSR的LDP请求。
-- 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 by the Downstream LSP Control Block's state machine.
此事件由一个下游LSP控制块的状态机发送。该下游LSP控制块是该上游LSP控制块的合并下游LSP控制块。该事件是下游LSP控制块的状态机接收LDP映射的结果。
-- LDP Release
--自民党释放
The LSR receives an LDP-RELEASE from an upstream LSR.
LSR从上游LSR接收LDP-RELEASE。
-- 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 by the Downstream LSP Control Block's state machine.
此事件由一个下游LSP控制块的状态机发送。该下游LSP控制块是该上游LSP控制块的合并下游LSP控制块。该事件是下游LSP控制块的状态机接收LDP-RECUND的结果。
-- LDP Upstream Abort
--上游中止
The LSR receives an LDP-ABORT from an upstream LSR.
LSR从上游LSR接收LDP-ABORT。
-- 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 by the Downstream LSP Control Block's state machine, or it detects an error.
此事件由一个下游LSP控制块的状态机发送。该下游LSP控制块是该上游LSP控制块的合并下游LSP控制块。事件是下游LSP控制块的状态机接收LDP-NAK的结果，或者它检测到错误。
-- Upstream Lost
--上游损失
The LSR loses the LDP session with its upstream LDP peer.
LSR失去与其上游LDP对等方的LDP会话。
-- Internal New NH
--新罕布什尔州内部
The LSR detects there is better next hop and decides to establish the lsp through this better next hop.
LSR检测到存在更好的下一跳，并决定通过该更好的下一跳建立lsp。
-- 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.
此事件用于触发拼接到不同的下游LSP。当它通过新的下一跳切换到更好的LSP时，就会发生这种情况。
2.3.3.3 State Transitions of the Upstream LSP Control Block's State Machine for Downstream-on-demand Mode
2.3.3.3 下游按需模式的上游LSP控制块状态机的状态转换
+-------------------+
| |
+-------->| IDLE |<-------------------+
| | | |
| +-------------------+ |
|(LDP Abort) | |
|(Internal |(LDP Request) |
| Downstream NAK) | |
|(Upstream Lost) | (Upstream Lost) |
| v (LDP Release) |
| +-------------------+ |
| | | |
+---------| RESPONSE_AWAITED | |
| | |
+-------------------+ |
| |
|(Internal Downstream |
| mapping) |
| |
v |
+-------------------+ |
| | |
| ESTABLISHED |------->------------+
| | |
+-------------------+ |
| |
| |
|(Internal Downstream Withdraw) |
|(Internal Downstream NAK) |
v |
+-------------------+ (LDP Upstream |
| | Abort) |
|RELEASE_AWAITED |------->------------+
| |
+-------------------+
+-------------------+
| |
+-------->| IDLE |<-------------------+
| | | |
| +-------------------+ |
|(LDP Abort) | |
|(Internal |(LDP Request) |
| Downstream NAK) | |
|(Upstream Lost) | (Upstream Lost) |
| v (LDP Release) |
| +-------------------+ |
| | | |
+---------| RESPONSE_AWAITED | |
| | |
+-------------------+ |
| |
|(Internal Downstream |
| mapping) |
| |
v |
+-------------------+ |
| | |
| ESTABLISHED |------->------------+
| | |
+-------------------+ |
| |
| |
|(Internal Downstream Withdraw) |
|(Internal Downstream NAK) |
v |
+-------------------+ (LDP Upstream |
| | Abort) |
|RELEASE_AWAITED |------->------------+
| |
+-------------------+
2.3.3.4 Upstream LSP Control Block's State Machine for Downstream-on-demand Mode
2.3.3.4 下游按需模式的上游LSP控制块状态机
State: IDLE
状态：空闲
Event: LDP Request
事件：LDP请求
New State: Depends upon the action routine.
新状态：取决于操作例程。
Actions:
行动：
If this LSR is the LSP Egress or Proxy Egress [2],
如果此LSR是LSP出口或代理出口[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'.
然后：选择一个上游标签，分配资源，将该上游标签连接到本地IP转发模块，向上游发送一个带有上游标签的LDP映射，并转到“已建立”状态。
else Obtain a next hop (or interface). Find a Downstream LSP Control Block that 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'.
否则获得下一跳（或接口）。查找具有相同FEC和相同下一跳并且能够合并更多输入标签的下游LSP控制块。如果未找到，则创建一个状态为“IDLE”的新下游LSP控制块。
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 upstream with the upstream label, and go to the state `ESTABLISHED'.
如果下游LSP控制块的状态为“已建立”，则选择上游标签，将上游标签与下游标签连接，并向上游发送LDP映射与上游标签，然后转到状态“已建立”。
If the state of Downstream LSP Control Block is not `ESTABLISHED', set the state of the Upstream LSP Control Block to `RESPONSE_AWAITED'. If the LSR use the independent control mode [2], choose an upstream label, and send an LDP-MAPPING upstream.
如果下游LSP控制块的状态未“建立”，则将上游LSP控制块的状态设置为“等待响应”。如果LSR使用独立控制模式[2]，则选择上游标签，并向上游发送LDP映射。
Pass the event `Internal AddUpstream' to the Downstream LSP Control Block's state machine.
将事件“Internal AddUpstream”传递给下游LSP控制块的状态机。
If unable to process the request for any reason, issue an LDP-NAK to the sender with the appropriate error code, go to IDLE and delete the control block.
如果由于任何原因无法处理该请求，则向发送方发出带有适当错误代码的LDP-NAK，转到IDLE并删除控制块。
State: IDLE
状态：空闲
Event: Internal Downstream Mapping
事件：内部下游映射
New State: IDLE
新状态：空闲
Actions:
行动：
Ignore the event. It is an internal implementation error.
忽略事件。这是一个内部实现错误。
State: IDLE
状态：空闲
Event: LDP Release
事件：LDP发布
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
事件：LDP上游中止
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.
忽略事件。这是一个内部实现错误。
State: RESPONSE_AWAITED
国家：等待答复
Event: LDP Request
事件：LDP请求
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 upstream with the upstream label and go to `ESTABLISHED'.
如果LSR使用有序控制模式，则分配一个上游标签，将上游标签连接到下游标签并分配资源，向上游发送一个LDP-MAPPING（LDP-MAPPING）和上游标签，然后转到“已建立”。
If unable to process the message for any reason, issue an LDP-NAK upstream and an LDP-RELEASE downstream, go to IDLE and delete the control block.
如果由于任何原因无法处理消息，则在上游发出LDP-NAK，在下游发出LDP-RELEASE，转到IDLE并删除控制块。
State: RESPONSE_AWAITED
国家：等待答复
Event: LDP Release
事件：LDP发布
New State: RESPONSE_AWAITED
新国家：等待答复
Actions
行动
Ignore the event. It is a 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
事件：LDP上游中止
New State: IDLE
新状态：空闲
Actions
行动
If the LSR uses the independent control mode, free the upstream label and the resources.
如果LSR使用独立控制模式，则释放上游标签和资源。
Send the event `Internal DeleteUpstream' to its Downstream LSP Control Block's state machine.
将事件“Internal DeleteUpstream”发送到其下游LSP控制块的状态机。
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 upstream.
如果LSR使用独立控制模式，则释放上游标签和资源。然后，向上游发送LDP-REQUE。
If the LSR uses the ordered control mode, propagate the LDP-NAK upstream.
如果LSR使用有序控制模式，则向上游传播LDP-NAK。
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.
如果LSR使用独立控制模式，则释放上游标签和资源。
Send the event `Internal DeleteUpstream' to its Downstream LSP Control Block's state machine.
将事件“Internal DeleteUpstream”发送到其下游LSP控制块的状态机。
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' to its old downstream control block.
将事件“Internal DeleteUpstream”发送到其旧的下游控制块。
Find a Downstream LSP Control Block that 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'.
查找具有相同FEC和相同下一跳并且能够合并更多输入标签的下游LSP控制块。如果未找到，则创建一个状态为“IDLE”的新下游LSP控制块。
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 upstream with the upstream label, and go to the state `ESTABLISHED'.
如果下游LSP控制块的状态为“已建立”，则选择上游标签，将上游标签与下游标签连接，并向上游发送LDP映射与上游标签，然后转到状态“已建立”。
If the state of Downstream LSP Control Block is not `ESTABLISHED', set the state of the Upstream LSP Control Block to `RESPONSE_AWAITED'.
如果下游LSP控制块的状态未“建立”，则将上游LSP控制块的状态设置为“等待响应”。
Pass the event `Internal AddUpstream' to the new Downstream LSP Control Block's state machine.
将事件“Internal AddUpstream”传递给新的下游LSP控制块的状态机。
State: ESTABLISHED
国家：已建立
Event: LDP Request
事件：LDP请求
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 upstream.
处理映射的新属性，然后向上游传播LDP映射。
State: ESTABLISHED
国家：已建立
Event: LDP Release
事件：LDP发布
New State: IDLE
新状态：空闲
Actions
行动
Disconnect the upstream label from the downstream label, free the upstream label and resources.
断开上游标签与下游标签的连接，释放上游标签和资源。
Send the event `Internal DeleteUpstream' to its Downstream LSP Control Block's state machine.
将事件“Internal DeleteUpstream”发送到其下游LSP控制块的状态机。
Send the event `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.
如果LSR处于切换到更好的下一跳的状态，则将事件“内部破坏”发送到NEXTHOPPHORGETGRYGLE块的状态机。
Delete the control block.
删除控制块。
State: ESTABLISHED
国家：已建立
Event: Internal Downstream Withdraw
事件：内部下游撤回
New State: Depends on the action routine.
新状态：取决于操作例程。
Actions
行动
If it uses independent mode, set its state to `IDLE' and create a internal `LDP Request' and send to its own state machine.
如果它使用独立模式，则将其状态设置为“空闲”，并创建一个内部“LDP请求”，然后发送到自己的状态机。
Else Disconnect the upstream label from the downstream label.
否则，断开上游标签与下游标签的连接。
Propagate the LDP-WITHDRAW upstream and go to state `RELEASE_AWAITED'.
向上游宣传LDP-RECUR，并进入“等待发布”状态。
Send the event `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.
如果LSR处于切换到更好的下一跳的状态，则将事件“内部破坏”发送到NEXTHOPPHORGETGRYGLE块的状态机。
State: ESTABLISHED
国家：已建立
Event: LDP Upstream Abort
事件：LDP上游中止
New State: ESTABLISHED
新国家：成立
Actions
行动
Ignore the event.
忽略事件。
Note: This scenario can occur if the upstream LSR sends a LDP-ABORT at about the same time as the local LSR sends a LDP-MAPPING. In this situation, it should be up to exactly one of the two LSRs as to whether or not the label that was sent remains valid. The LDP specification [4] procedures leave the choice to the upstream LSR that must send an LDP-RELEASE if it will not use the label provided.
注意：如果上游LSR发送LDP-ABORT的时间与本地LSR发送LDP-MAPPING的时间大致相同，则可能出现这种情况。在这种情况下，发送的标签是否仍然有效，取决于两个LSR中的一个。LDP规范[4]程序将选择权留给上游LSR，如果上游LSR不使用提供的标签，则必须发送LDP-RELEASE。
State: ESTABLISHED
国家：已建立
Event: Internal Downstream NAK
事件：内部下游NAK
New State: Depends on the action routine.
新状态：取决于操作例程。
Actions:
行动：
If it uses independent mode, set its state to `IDLE' and create a internal `LDP Request' and send to its own state machine.
如果它使用独立模式，则将其状态设置为“空闲”，并创建一个内部“LDP请求”，然后发送到自己的状态机。
Else Disconnect the upstream label from the downstream label
否则，断开上游标签与下游标签的连接
Send an LDP-WITHDRAW upstream and go to state `RELEASE_AWAITED'.
向上游发送LDP-RECUR，并进入“等待释放”状态。
Send the event `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.
如果LSR处于切换到更好的下一跳的状态，则将事件“内部破坏”发送到NEXTHOPPHORGETGRYGLE块的状态机。
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 DeleteUpstream' to its Downstream LSP Control Block's state machine.
将事件“Internal DeleteUpstream”发送到其下游LSP控制块的状态机。
Send the event `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.
如果LSR处于切换到更好的下一跳的状态，则将事件“内部破坏”发送到NEXTHOPPHORGETGRYGLE块的状态机。
Delete the control block.
删除控制块。
State: ESTABLISH
国家：建立
Event: Internal Re-Cross-Connect
事件：内部重新交叉连接
New State: ESTABLISH
新国家：建立
Actions:
行动：
Reconnect the upstream label to the new downstream label.
将上游标签重新连接到新的下游标签。
Send the event `Internal DeleteUpstream' to its old Downstream LSP Control Block's state machine.
将事件“Internal DeleteUpstream”发送到其旧的下游LSP控制块的状态机。
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.
创建一个新的下一跳触发控制块，并将事件“Internal new NH”传递给其状态机。
State: RELEASE_AWAITED
状态：等待发布
Event: LDP Request
事件：LDP请求
New State: RELEASE_AWAITED
新状态：等待发布
Actions:
行动：
Ignore the event. It is a protocol error from the upstream LSR.
忽略事件。这是来自上游LSR的协议错误。
State: RELEASE_AWAITED
状态：等待发布
Event: Internal Downstream Mapping
事件：内部下游映射
New State: RELEASE_AWAITED
新状态：等待发布
Actions:
行动：
Ignore the event. It is an internal implementation error.
忽略事件。这是一个内部实现错误。
State: RELEASE_AWAITED
状态：等待发布
Event: LDP Release
事件：LDP发布
New State: IDLE
新状态：空闲
Actions:
行动：
Free the upstream 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.
忽略事件。这是来自下游LSR的协议错误。
State: RELEASE_AWAITED
状态：等待发布
Event: LDP Upstream Abort
事件：LDP上游中止
New State: IDLE
新状态：空闲
Actions:
行动：
Free the upstream 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.
忽略事件。继续等待自民党的释放。
State: RELEASE_AWAITED
状态：等待发布
Event: Upstream Lost
事件：上游损失
New State: IDLE
新状态：空闲
Actions:
行动：
Free the upstream 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.
忽略事件。继续等待自民党的释放。
State: RELEASE_AWAITED
状态：等待发布
Event: Internal Re-Cross-Connect
事件：内部重新交叉连接
New State: RELEASE_AWAITED
新状态：等待发布
Actions:
行动：
Ignore the event. It is an internal implementation error.
忽略事件。这是一个内部实现错误。
2.3.3.5 State of the Downstream LSP Control Block's State Machine for Downstream-on-demand Mode
2.3.3.5 下游按需模式下下游LSP控制块状态机的状态
-- IDLE
--闲散
This is the initial LSP state.
这是初始LSP状态。
-- 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 from the downstream LSR.
该状态意味着LSR已经从上游LSR接收到LDP-REQUEST，已经处理了LDP-REQUEST，并且已经向下游LSR发送了新的LDP-REQUEST。LSR正在等待来自下游LSR的LDP映射。
-- ESTABLISHED
--确立
This state means that the LSR has received the LDP-MAPPING from the downstream LSR and the LSP is up and operational.
该状态意味着LSR已从下游LSR接收到LDP-MAPPING，并且LSP已启动并可操作。
2.3.3.6 Events of the Downstream LSP Control Block's State Machine for Downstream-on-demand Mode
2.3.3.6 下游按需模式下下游LSP控制块状态机的事件
-- Internal AddUpstream
--内部添加上游
This event is sent by an Upstream LSP Control Block's state machine when it is created.
此事件在创建时由上游LSP控制块的状态机发送。
-- Internal DeleteUpstream
--上游内部删除
This event is sent by an Upstream LSP Control Block's state machine when it is deleted.
此事件在被删除时由上游LSP控制块的状态机发送。
-- LDP Mapping
--LDP映射
The LSR receives an LDP-MAPPING from a downstream LSR.
LSR从下游LSR接收LDP映射。
-- LDP Withdraw
--自民党退出
The LSR receives an LDP-WITHDRAW from a downstream LSR.
LSR从下游LSR接收LDP-draw。
-- LDP Downstream NAK
--LDP下游NAK
The LSR receives an LDP-NAK from a downstream LSR.
LSR从下游LSR接收LDP-NAK。
-- Downstream Lost
--下游损失
The LSR loses the LDP session with its downstream LSR.
LSR与其下游LSR失去LDP会话。
2.3.3.7 State Transitions of the Downstream LSP Control Block's State Machine for Downstream-on-demand mode
2.3.3.7 下游按需模式下下游LSP控制块状态机的状态转换
+-------------------+
| |
| IDLE |<--------------+
| | |(last Internal
+-------------------+ | DeleteUpstream)
| |(LDP Withdraw)
|(1st Internal AddUpstream)|
| |(LDP Downstream
v | NAK)
+-------------------+ |(Downstream
| | | Lost)
| RESPONSE_AWAITED |---------->----+
| | |
+-------------------+ |
| |
|(LDP Mapping) |
| |
v |
+-------------------+ |
| | |
| ESTABLISHED |-------->------+
| |
+-------------------+
+-------------------+
| |
| IDLE |<--------------+
| | |(last Internal
+-------------------+ | DeleteUpstream)
| |(LDP Withdraw)
|(1st Internal AddUpstream)|
| |(LDP Downstream
v | NAK)
+-------------------+ |(Downstream
| | | Lost)
| RESPONSE_AWAITED |---------->----+
| | |
+-------------------+ |
| |
|(LDP Mapping) |
| |
v |
+-------------------+ |
| | |
| ESTABLISHED |-------->------+
| |
+-------------------+
2.3.3.8 Downstream LSP Control Block's State Machine for Downstream-on-demand Mode.
2.3.3.8 下游LSP控制块的下游按需模式状态机。
State: IDLE
状态：空闲
Event: Internal AddUpstream
事件：内部AddUpstream
New State: RESPONSE_AWAITED
新国家：等待答复
Actions
行动
Initialize the list of pointers in the Upstream LSP Control Block to contain the newly added upstream pointer.
初始化上游LSP控制块中的指针列表，以包含新添加的上游指针。
Send a new LDP-REQUEST downstream and go to the state `RESPONSE_AWAITED'.
向下游发送一个新的LDP-REQUEST并转到状态“RESPONSE_waitied”。
State: IDLE
状态：空闲
Event: Internal DeleteUpstream
事件：内部删除上游
New State: IDLE
新状态：空闲
Actions
行动
Ignore the event. It is an internal implementation error.
忽略事件。这是一个内部实现错误。
State: IDLE
状态：空闲
Event: LDP Mapping
事件：LDP映射
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 Downstream NAK
事件：LDP下游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.
忽略事件。这是一个内部实现错误。
State: RESPONSE_AWAITED
国家：等待答复
Event: Internal AddUpstream
事件：内部AddUpstream
New State: RESPONSE_AWAITED
新国家：等待答复
Actions
行动
Add the pointer to new Upstream LSP Control Block to the Upstream LSP Control Blocks pointer list.
将指向新上游LSP控制块的指针添加到上游LSP控制块指针列表中。
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.
从上游LSP控制块指针列表中删除上游LSP控制块指针。
If the list becomes empty, release the resources, send an LDP-Abort downstream, go to IDLE and then delete the control block.
如果列表变为空，释放资源，向下游发送LDP中止，转到IDLE，然后删除控制块。
State: RESPONSE_AWAITED
国家：等待答复
Event: LDP Mapping
事件：LDP映射
New State: ESTABLISHED
新国家：成立
Actions
行动
For each Upstream LSP Control Block in the Upstream LSP Control Block pointers list, pass the event `Internal Downstream Mapping' to its state machine.
对于上游LSP控制块指针列表中的每个上游LSP控制块，将事件“内部下游映射”传递给其状态机。
State: RESPONSE_AWAITED
国家：等待答复
Event: LDP Withdraw
事件：自民党退出
New State: RESPONSE_AWAITED
新国家：等待答复
Actions
行动
It is a protocol error from the downstream LDP peer; send a LDP-RELEASE downstream
这是来自下游LDP对等方的协议错误；向下游发送LDP-RELEASE
State: RESPONSE_AWAITED
国家：等待答复
Event: LDP Downstream NAK
事件：LDP下游NAK
New State: IDLE
新状态：空闲
Actions
行动
For each Upstream LSP Control Block in the Upstream LSP Control Block pointers list, pass the event `Internal Downstream NAK' to its state machine.
对于上游LSP控制块指针列表中的每个上游LSP控制块，将事件“内部下游NAK”传递给其状态机。
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 Downstream NAK' to its state machine.
对于上游LSP控制块指针列表中的每个上游LSP控制块，将事件“内部下游NAK”传递给其状态机。
Release the resources, and delete the control block.
释放资源，并删除控制块。
State: ESTABLISHED
国家：已建立
Event: Internal AddUpstream
事件：内部AddUpstream
New State: ESTABLISHED
新国家：成立
Actions
行动
Add the pointer to new Upstream LSP Control Block to the Upstream LSP Control Block pointers list.
将指向新上游LSP控制块的指针添加到上游LSP控制块指针列表中。
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.
从上游LSP控制块指针列表中删除上游LSP控制块指针。
If the list becomes empty, release the resources, send an LDP-RELEASE downstream, go to IDLE and then delete the control block.
如果列表变为空，释放资源，向下游发送LDP-release，转到IDLE，然后删除控制块。
Otherwise, remain in the ESTABLISHED state.
否则，请保持已建立的状态。
State: ESTABLISHED
国家：已建立
Event: LDP Mapping
事件：LDP映射
New State: ESTABLISHED
新国家：成立
Actions
行动
For each Upstream LSP Control Block in the Upstream LSP Control Block pointers list, pass the event `Internal Downstream mapping' to its state machine.
对于上游LSP控制块指针列表中的每个上游LSP控制块，将事件“内部下游映射”传递给其状态机。
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 Downstream withdraw' to its state machine.
对于上游LSP控制块指针列表中的每个上游LSP控制块，将事件“内部下游撤回”传递给其状态机。
Release the resources, and delete the control block and send LDP-RELEASE downstream.
释放资源，删除控制块并向下游发送LDP-Release。
State: ESTABLISHED
国家：已建立
Event: LDP Downstream NAK
事件：LDP下游NAK
New State: ESTABLISHED
新国家：成立
Actions
行动
It is a protocol error from the downstream LDP peer.
这是来自下游LDP对等方的协议错误。
2.3.3.9 State of the Next_Hop_Trigger_Control_Block's State Machine for Downstream-on-demand Mode
2.3.3.9 下游按需模式下一跳触发控制块状态机的状态
-- IDLE
--闲散
This is the initial LSP state.
这是初始LSP状态。
-- NEW_NH_RETRY
--新建\u nhu\u重试
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.
这是LSR等待重试计时器过期，然后尝试通过新的下一跳建立LSP的状态。
-- 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 from the downstream LSR.
该状态意味着LSR已经向下游LSR发送了新的LDP-REQUEST。LSR正在等待来自下游LSR的LDP映射。
2.3.3.10 Events of the Next_Hop_Trigger_Control_Block's State Machine for Downstream-on-demand Mode
2.3.3.10 下游按需模式下下一跳触发控制块状态机的事件
-- Internal New NH
--新罕布什尔州内部
Trigger to setup an LSP through a better next hop.
触发通过更好的下一跳设置LSP。
-- 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 by the Downstream LSP Control Block's state machine.
此事件由一个下游LSP控制块的状态机发送。该下游LSP控制块是该上游LSP控制块的合并下游LSP控制块。该事件是下游LSP控制块的状态机接收LDP映射的结果。
-- 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 by the Downstream LSP Control Block's state machine, or it detects an error.
此事件由一个下游LSP控制块的状态机发送。该下游LSP控制块是该上游LSP控制块的合并下游LSP控制块。事件是下游LSP控制块的状态机接收LDP-NAK的结果，或者它检测到错误。
-- Internal Destroy This event is used to stop the procedure of switching over to the better next hop.
--内部销毁此事件用于停止切换到更好的下一跳的过程。
2.3.3.11 State Transitions of the Next_Hop_Trigger_Control_Block's State Machine for Downstream-on-demand Mode
2.3.3.11 下游按需模式下下一跳触发控制块状态机的状态转换
+---------------------+
| |
| IDLE |<------------+
| | |
+---------------------+ |
| |
| |
| (Internal New NH) |
| |
v |
+---------------------+ |
| | |
| NEW_NH_RETRY |----------->-+
| | (Internal |
+---------------------+ Destroy) |
| |
| |
| (Internal retry timeout) |
| |
v |
+---------------------+ |
| | (Internal |
| NEW_NH_RESPONSE | Destroy) |
| _AWAITED |----------->-+
| | |
+---------------------+ |
| |
| (Internal Downstream |
| Mapping |
| (Internal Downstream |
| NAK) |
+------------------------>-+
+---------------------+
| |
| IDLE |<------------+
| | |
+---------------------+ |
| |
| |
| (Internal New NH) |
| |
v |
+---------------------+ |
| | |
| NEW_NH_RETRY |----------->-+
| | (Internal |
+---------------------+ Destroy) |
| |
| |
| (Internal retry timeout) |
| |
v |
+---------------------+ |
| | (Internal |
| NEW_NH_RESPONSE | Destroy) |
| _AWAITED |----------->-+
| | |
+---------------------+ |
| |
| (Internal Downstream |
| Mapping |
| (Internal Downstream |
| NAK) |
+------------------------>-+
State: IDLE
状态：空闲
Event: Internal New NH
事件：新罕布什尔州内部
New State: NEW_NH_RETRY
新状态：新重试
Actions:
行动：
Start the LSP retry timer and go to the `NEW_NH_RETRY' state.
启动LSP重试计时器并转到“新建重试”状态。
State: IDLE
状态：空闲
Event: Internal retry timeout
事件：内部重试超时
New State: IDLE
新状态：空闲
Actions:
行动：
Ignore. It is an internal implementation error.
忽视这是一个内部实现错误。
State: IDLE
状态：空闲
Event: Internal Downstream Mapping
事件：内部下游映射
New State: IDLE
新状态：空闲
Actions:
行动：
Ignore. It is an internal implementation error.
忽视这是一个内部实现错误。
State: IDLE
状态：空闲
Event: Internal Downstream NAK
事件：内部下游NAK
New State: IDLE
新状态：空闲
Actions:
行动：
Ignore. It is an internal implementation error.
忽视这是一个内部实现错误。
State: IDLE
状态：空闲
Event: Internal destroy
事件：内部销毁
New State: IDLE
新状态：空闲
Actions:
行动：
Ignore. It is an internal implementation error.
忽视这是一个内部实现错误。
State: NEW_NH_RETRY
状态：新建\u nhu\u重试
Event: Internal New NH
事件：新罕布什尔州内部
New State: NEW_NH_RETRY
新状态：新重试
Actions:
行动：
Restart the LSP retry timer.
重新启动LSP重试计时器。
State: NEW_NH_RETRY
状态：新建\u nhu\u重试
Event: Internal retry timeout
事件：内部重试超时
New State: Depends on the action routine.
新状态：取决于操作例程。
Actions:
行动：
If the new next hop is the same one as the old next hop, go to IDLE and delete the control block.
如果新的下一个跃点与旧的下一个跃点相同，请转到IDLE并删除控制块。
Otherwise, go to NEW_NH_RESPONSE_AWAITED, find a downstream LSP control block that goes through the same next hop for the same FEC, if there are none, create one, and pass 'Internal AddUpstream' event to its state machine.
否则，转到NEW_NH_RESPONSE_Waitied（等待的新响应），找到一个下游LSP控制块，该控制块经过同一FEC的同一下一跳，如果没有，则创建一个，并将“Internal AddUpstream”事件传递给其状态机。
State: NEW_NH_RETRY
状态：新建\u nhu\u重试
Event: Internal Downstream Mapping
事件：内部下游映射
New State: NEW_NH_RETRY
新状态：新重试
Actions:
行动：
Ignore. It is an internal implementation error.
忽视这是一个内部实现错误。
State: NEW_NH_RETRY
状态：新建\u nhu\u重试
Event: Internal Downstream NAK
事件：内部下游NAK
New State: NEW_NH_RETRY
新状态：新重试
Actions:
行动：
Ignore. It is an internal implementation error.
忽视这是一个内部实现错误。
State: NEW_NH_RETRY
状态：新建\u nhu\u重试
Event: Internal destroy
事件：内部销毁
New State: IDLE
新状态：空闲
Actions:
行动：
Stop the timer and delete the control block.
停止计时器并删除控制块。
State: NEW_NH_RESPONSE_AWAITED
州：等待新的答复
Event: Internal New NH
事件：新罕布什尔州内部
New State: NEW_NH_RETRY
新状态：新重试
Actions:
行动：
Restart the LSP retry timer and send event `Internal destroy' to the control block of the LSP for the new next hop.
重新启动LSP重试计时器，并将事件“Internal destroy”发送到LSP的控制块以用于新的下一跳。
State: NEW_NH_RESPONSE_AWAITED
州：等待新的答复
Event: Internal retry timeout
事件：内部重试超时
New State: NEW_NH_RESPONSE_AWAITED
新州：等待新的答复
Actions:
行动：
Ignore. It is an internal implementation error.
忽视这是一个内部实现错误。
State: NEW_NH_RESPONSE_AWAITED
州：等待新的答复
Event: Internal Downstream Mapping
事件：内部下游映射
New State: IDLE
新状态：空闲
Actions:
行动：
Send event `Internal Re-cross-connect' event to the upstream LSP control block of the new next hop.
将事件“内部重新交叉连接”事件发送到新下一跳的上游LSP控制块。
Send event `DeleteUpstream' event to the downstream LSP control block of the the new next hop, since the upstream has spliced into the new next hop.
将事件“DeleteUpstream”事件发送到新下一跳的下游LSP控制块，因为上游已拼接到新的下一跳。
Delete the control block.
删除控制块。
State: NEW_NH_RESPONSE_AWAITED
州：等待新的答复
Event: Internal Downstream NAK
事件：内部下游NAK
New State: IDLE
新状态：空闲
Actions:
行动：
Delete the control block.
删除控制块。
State: NEW_NH_RESPONSE_AWAITED
州：等待新的答复
Event: Internal destroy
事件：内部销毁
New State: IDLE
新状态：空闲
Actions:
行动：
Send event `Internal DeleteUpstream' the control block for the new LSP through the new next hop.
通过新的下一跳向新LSP的控制块发送事件“Internal DeleteUpstream”。
- If an LSR receives an LDP-REQUEST:
- 如果LSR收到LDP-1请求：
a) If this is a duplicate request, discard the message. A duplicate request means that there is a LSP Control Block that has the same FEC, Upstream Label Request ID and Upstream LDP Session Identifier.
a) 如果这是重复的请求，则丢弃该消息。重复请求意味着存在具有相同FEC、上游标签请求ID和上游LDP会话标识符的LSP控制块。
b) Otherwise, create a new Upstream LSP Control Block. Then pass the event `LDP Request' to this Upstream LSP Control Block's state machine.
b) 否则，创建一个新的上游LSP控制块。然后将事件“LDP请求”传递给该上游LSP控制块的状态机。
- If an LSR receives an LDP-MAPPING:
- 如果LSR接收到LDP映射：
Locate a Downstream LSP Control Block that 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.
定位具有相同FEC、相同下游LDP会话标识符和相同下游标签的下游LSP控制块。如果找到下游LSP控制块，则将事件“LDP映射”传递到其状态表。这可能意味着标签绑定的属性已更改。
Otherwise, use the Downstream LDP request ID (the 'Label Request Message ID' field in the LDP-MAPPING) and Downstream LDP Session Identifier to locate the Downstream LSP Control Block and pass the
否则，使用下游LDP请求ID（LDP映射中的“标签请求消息ID”字段）和下游LDP会话标识符来定位下游LSP控制块并传递消息
event `LDP Mapping' to its state machine. If no Downstream LSP Control Block is found, ignore the message.
事件“LDP映射”到其状态机。如果未找到下游LSP控制块，则忽略该消息。
- If an LSR receives an LDP-RELEASE:
- 如果LSR收到LDP-RELEASE：
Locate an Upstream LSP Control Block that 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.
定位具有相同FEC、相同上游标签、相同上游LDP会话标识符的上游LSP控制块。如果未找到上游LSP控制块，则忽略该消息。如果发现上游LSP控制块，则将事件“LDP释放”发送到其状态机。
- If an LSR receives an LDP-WITHDRAW:
- 如果LSR收到LDP-DROW：
Find a Downstream LSP Control Block that has the same FEC, the same Downstream LDP Session Identifier and the same Downstream Label. Pass the event `LDP Withdraw' to its state machines.
查找具有相同FEC、相同下游LDP会话标识符和相同下游标签的下游LSP控制块。将事件“LDP撤回”传递给其状态机。
- If an Upstream LDP peer is lost:
- 如果上游LDP对等点丢失：
Pass the event `Upstream Lost' to the state machines of all the Upstream LSP Control Blocks whose upstream LDP peer is that LSR.
将事件“上游丢失”传递给上游LDP对等方为该LSR的所有上游LSP控制块的状态机。
- If a Downstream LDP peer is lost:
- 如果下游LDP对等点丢失：
Pass the event `Downstream Lost' to the state machines of all the Downstream LSP Control Blocks whose downstream LDP peer is that LSR.
将事件“下游丢失”传递给其下游LDP对等方为该LSR的所有下游LSP控制块的状态机。
- If a next hop of an FEC is changed:
- 如果FEC的下一跳发生更改：
For all the Upstream LSP Control Blocks that are affected by this change, pass the event `Internal New NH' to their state machines.
对于受此更改影响的所有上游LSP控制块，将事件“Internal New NH”传递给它们的状态机。
- If an LSR receives an LDP-ABORT from an upstream LSR:
- 如果LSR从上游LSR接收到LDP-ABORT：
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.
使用上游LDP请求ID和上游LDP会话标识符定位上游LSP控制块，并将事件“LDP Abort”传递给其状态机。
- If an LSR receives an LDP-NAK from a downstream LSR:
- 如果LSR从下游LSR接收到LDP-NAK：
Use the Downstream LDP Request ID and Downstream Session Identifier to locate a Downstream_LSP_control_block and pass the event `LDP Downstream NAK' to its state machine.
使用下游LDP请求ID和下游会话标识符来定位下游LSP控制块，并将事件“LDP下游NAK”传递给其状态机。
The following sections describe the state machines for the ATM-LSR that uses downstream unsolicited mode.
以下各节描述了使用下游非请求模式的ATM-LSR的状态机。
While both independent LSP control and ordered LSP control modes are possible, only the ordered mode is taken into account, because the independent LSP control mode uses the liberal label retention mode and so is considered burning too many ATM resources.
虽然独立LSP控制模式和有序LSP控制模式都是可能的，但只考虑有序模式，因为独立LSP控制模式使用自由标签保留模式，因此被认为消耗了太多ATM资源。
In downstream unsolicited mode, multiple path is not supported in this version and will be For Further Study (FFS). We suspect with multiple next hops and Downstream mode, it is easy to get into a loop condition.
在下游未经请求的模式下，此版本不支持多路径，将进行进一步研究（FFS）。我们怀疑，由于有多个下一跳和下行模式，很容易进入循环状态。
There are 2 types of control blocks involved: Upstream LSP Control Block, Downstream LSP Control Block.
涉及到两种类型的控制块：上游LSP控制块、下游LSP控制块。
There is a list of Upstream LSP Control Blocks for each FEC in the routing table, with each one 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 withdrawn.
对于路由表中的每个FEC，存在上游LSP控制块的列表，每个控制块对应于LDP对等方。当存在准备分发到该上游的标签时，为每个FEC创建上游LSP控制块。当FEC从FEC表中删除，或LDP对等点消失，或下游标签被撤回时，它被删除。
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.
路由表中的每个FEC都有一个下游LSP控制块。它在FEC插入转发表时创建，在FEC从转发表中删除时删除。
An Upstream LSP Control Block may contain the following information:
上游LSP控制块可包含以下信息：
- Upstream LDP Session Identifier
- 上行LDP会话标识符
- State
- 状态
- Upstream Label (assigned by this LSR)
- 上游标签（由该LSR分配）
- FEC
- 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.
上游标签和上游LDP会话标识符，或FEC和上游LDP会话标识符可用于定位唯一的上游LSP控制块。
A Downstream LSP Control Block may contain the following information:
下游LSP控制块可包含以下信息：
- FEC
- FEC
- State
- 状态
- Downstream LDP Session Identifier
- 下行LDP会话标识符
- Downstream Label (assigned by the downstream LSR)
- 下游标签（由下游LSR指定）
- Downstream Label Request ID (assigned by the LSR itself)
- 下游标签请求ID（由LSR本身分配）
Downstream Label and Downstream LDP Session Identifier, or FEC and Downstream LDP Session Identifier can be used to locate a unique Downstream LSP Control Block.
下游标签和下游LDP会话标识符，或FEC和下游LDP会话标识符可用于定位唯一的下游LSP控制块。
3.2 States of the Upstream LSP Control Block's State Machine for Downstream Mode
3.2 下游模式的上游LSP控制块状态机的状态
-- IDLE
--闲散
This is the initial LSP state.
这是初始LSP状态。
-- ESTABLISHED
--确立
This state means that the LSR has received the LDP-MAPPING from the downstream LSR and the LSP is up and operational.
该状态意味着LSR已从下游LSR接收到LDP-MAPPING，并且LSP已启动并可操作。
-- RELEASE_AWAITED
--等待发布
This state means that the LSR is waiting for the LDP-RELEASE in respond to the LDP-WITHDRAW sent by this LSR.
该状态意味着LSR正在等待LDP-RELEASE，以响应该LSR发送的LDP-REQUE。
-- RESOURCES_AWAITED
--等待的资源
This state means that the LSR is waiting for the label resources.
此状态表示LSR正在等待标签资源。
3.3 Events of the Upstream LSP Control Block's State Machine for Downstream Mode
3.3 下游模式的上游LSP控制块状态机事件
-- 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 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.
此事件由一个下游LSP控制块的状态机发送。该事件是下游LSP控制块的状态机接收LDP映射的结果。或者当发现LDP对等点并且存在可用于该FEC的下游标签时。
-- LDP Release
--自民党释放
The LSR receives an LDP-RELEASE from an upstream LSR.
LSR从上游LSR接收LDP-RELEASE。
-- Internal Withdraw
--内部提取
This event is sent by Downstream LSP Control Block's state machine. The event is the result of receiving an LDP-WITHDRAW by the Downstream LSP Control Block's state machine.
此事件由下游LSP控制块的状态机发送。该事件是下游LSP控制块的状态机接收LDP-RECUND的结果。
-- Resource Available
--可用资源
This event means the local resource (such as label) becomes available.
此事件表示本地资源（如标签）变为可用。
-- Delete FEC
--删除FEC
This event means that the FEC is removed from the forwarding table.
此事件表示FEC已从转发表中删除。
-- Upstream Lost
--上游损失
This event means that the upstream LDP peer is lost.
此事件表示上游LDP对等点丢失。
3.4 State Transitions of Upstream LSP Control Block's State Machine for Downstream Mode
3.4 下游模式上游LSP控制块状态机的状态转换
|
|(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
| | | | Downstream
| | | | Withdraw)
| | +-------------------+ |
+--------->| | |
| |RESOURCES_AWAITED |---------------+
| | | |
| +-------------------+ |
| |
| (Internal Downstream Withdraw) |(LDP Release)
| +-------------------+ |
| | | |
+---->| RELEASE_AWAITED |---------------+
| |
+-------------------+
|
|(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
| | | | Downstream
| | | | Withdraw)
| | +-------------------+ |
+--------->| | |
| |RESOURCES_AWAITED |---------------+
| | | |
| +-------------------+ |
| |
| (Internal Downstream Withdraw) |(LDP Release)
| +-------------------+ |
| | | |
+---->| RELEASE_AWAITED |---------------+
| |
+-------------------+
State: IDLE
状态：空闲
Event: Internal Downstream mapping
事件：内部下游映射
New State: Depends on the action routine.
新状态：取决于操作例程。
Actions
行动
Choose an upstream label, connect the upstream label with the downstream label, propagate the LDP-MAPPING upstream and go to state `ESTABLISHED'
选择一个上游标签，将上游标签与下游标签连接，向上游传播LDP映射，并转到“已建立”状态
If there is no resource for the upstream label, go to state `RESOURCE_AWAITED'.
如果上游标签没有资源，请转到状态“resource_waitied”。
State: IDLE
状态：空闲
Event: LDP Release
事件：LDP发布
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
事件：删除FEC
New State: IDLE
新状态：空闲
Actions
行动
Delete the control block.
删除控制块。
State: IDLE
状态：空闲
Event: Upstream Lost
事件：上游损失
New State: IDLE
新状态：空闲
Actions
行动
Delete the control block.
删除控制块。
State: ESTABLISHED
国家：已建立
Event: Internal Downstream Mapping
事件：内部下游映射
New State: ESTABLISHED
新国家：成立
Actions
行动
Process the new attributes of the new mapping message.
处理新映射消息的新属性。
Propagate the LDP-MAPPING upstream.
向上游传播LDP映射。
State: ESTABLISHED
国家：已建立
Event: LDP Release
事件：LDP发布
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.
向上游传播LDP-REACH。
State: ESTABLISHED
国家：已建立
Event: Resource Available
事件：可用资源
New State: ESTABLISHED
新国家：成立
Actions
行动
Ignore the event. It is an internal implementation error.
忽略事件。这是一个内部实现错误。
State: ESTABLISHED
国家：已建立
Event: Delete FEC
事件：删除FEC
New State: RELEASE_AWAITED
新状态：等待发布
Actions
行动
Send a LDP-WITHDRAW upstream.
向上游发送LDP-REQUE。
State: ESTABLISHED
国家：已建立
Event: Upstream Lost
事件：上游损失
New State: IDLE
新状态：空闲
Actions
行动
Release the upstream label and delete the control block.
释放上游标签并删除控制块。
State: RELEASE_AWAITED
状态：等待发布
Event: Internal Downstream Mapping
事件：内部下游映射
New State: RELEASE_AWAITED
新状态：等待发布
Actions
行动
Ignore the message.
忽略此消息。
State: RELEASE_AWAITED
状态：等待发布
Event: LDP Release
事件：LDP发布
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
事件：删除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.
释放上游标签并删除控制块。
State: RESOURCE_AWAITED
状态：等待资源
Event: Internal Downstream Mapping
事件：内部下游映射
New State: RESOURCE_AWAITED
新状态：等待资源
Actions
行动
Ignore the message.
忽略此消息。
State: RESOURCE_AWAITED
状态：等待资源
Event: LDP Release
事件：LDP发布
New State: RESOURCE_AWAITED
新状态：等待资源
Actions
行动
Ignore the 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.
分配上游标签，将上游标签与下游标签连接，向上游发送LDP-MAPPING。
State: RESOURCE_AWAITED
状态：等待资源
Event: Delete FEC
事件：删除FEC
New State: IDLE
新状态：空闲
Actions
行动
Delete the control block.
删除控制块。
State: RESOURCE_AWAITED
状态：等待资源
Event: Upstream Lost
事件：上游损失
New State: IDLE
新状态：空闲
Actions
行动
Delete the control block.
删除控制块。
3.6 State of the Downstream LSP Control Block's State Machine for Downstream Mode
3.6 下游LSP控制块的下游模式状态机的状态
-- IDLE
--闲散
This is the initial LSP state.
这是初始LSP状态。
-- ESTABLISHED
--确立
This state means that the LSR has received the LDP-MAPPING from the downstream LSR.
该状态意味着LSR已经从下游LSR接收到LDP-MAPPING。
3.7 Events of the Downstream LSP Control Block's State Machine for Downstream Mode
3.7 下游LSP控制块的下游模式状态机的事件
-- LDP Mapping
--LDP映射
The LSR receives an LDP-MAPPING from a downstream LSR.
LSR从下游LSR接收LDP映射。
-- LDP Withdraw
--自民党退出
The LSR receives an LDP-WITHDRAW from a downstream LSR.
LSR从下游LSR接收LDP-draw。
-- Delete FEC
--删除FEC
The FEC is deleted from the forwarding table.
FEC将从转发表中删除。
-- Next Hop Change
--下一跳改变
The next hop for this FEC is change to different LSR.
此FEC的下一个跃点是更改为不同的LSR。
-- Downstream Lost
--下游损失
The downstream peer is gone.
下游的对等点消失了。
3.8 State Transitions of Downstream LSP Control Block's State Machine for Downstream Mode
3.8 下游模式下下游LSP控制块状态机的状态转换
|
|(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
|
|(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
State: IDLE
状态：空闲
Event: LDP mapping
事件：LDP映射
New State: ESTABLISHED
新国家：成立
Actions
行动
For all the LDP peers except the downstream LSR that 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.
对于除分配标签的下游LSR之外的所有LDP对等点，创建上游LSP控制块，并将事件“内部下游映射”传递给每个上游LSP控制块的状态机。
State: IDLE
状态：空闲
Event: LDP withdraw
事件：自民党退出
New State: IDLE
新状态：空闲
Actions
行动
Ignore the event. It is an internal implementation error.
忽略事件。这是一个内部实现错误。
State: IDLE
状态：空闲
Event: Delete FEC
事件：删除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.
忽略事件。
State: ESTABLISHED
国家：已建立
Event: LDP mapping
事件：LDP映射
New State: ESTABLISHED
新国家：成立
Actions
行动
For each Upstream_LSP_control_block of this FEC, pass event `Internal downstream mapping' to its state machine.
对于此FEC的每个上游\u LSP\u控制\u块，将事件“内部下游映射”传递到其状态机。
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.
对于此FEC的每个上游\u LSP\u控制\u块，将事件“内部下游撤回”传递给其状态机。
Send a LDP Withdraw downstream.
向下游发送自民党退出命令。
State: ESTABLISHED
国家：已建立
Event: Delete FEC
事件：删除FEC
New State: IDLE
新状态：空闲
Actions
行动
Send LDP-RELEASE downstream and delete the control block.
向下游发送LDP-RELEASE并删除控制块。
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.
对于此FEC的每个上游\u LSP\u控制\u块，将事件“内部下游撤回”传递给其状态机。
Send LDP-REQUEST to the new next hop.
向新的下一跳发送LDP-REQUEST。
State: ESTABLISHED
国家：已建立
Event: Downstream Lost
事件：下游损失
New State: IDLE
新状态：空闲
Actions
行动
Send LDP-WITHDRAW to all Upstream_Control_Block's state machine of this FEC.
向该FEC的所有上游控制块的状态机发送LDP-RECUN。
3.10 LDP Related Message Processing for downstream mode.
3.10 下游模式的LDP相关消息处理。
- If an LSR receives an LDP-REQUEST:
- 如果LSR收到LDP-1请求：
If there is a next hop for this FEC and there is a Downstream_Control_Block for this FEC whose state is `ESTABLISHED', create a new Upstream_Control_Block and pass `internal Mapping' event to its state machine.
如果此FEC有下一个跃点，并且此FEC有一个状态为“已建立”的下游控制块，则创建一个新的上游控制块，并将“内部映射”事件传递给其状态机。
- If an LSR receives an LDP-MAPPING:
- 如果LSR接收到LDP映射：
Locate a Downstream LSP Control Block that 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.
定位具有相同FEC、相同下游LDP会话标识符和相同下游标签的下游LSP控制块。如果找到下游LSP控制块，则将事件“LDP映射”传递到其状态表。这可能意味着标签绑定的属性已更改。
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.
否则，如果没有找到匹配的下游LSP控制块，则找到该FEC的下游LSP控制块，其下一跳是该下游对等方，将事件“LDP映射”传递给其状态机。
- If an LSR receives an LDP-RELEASE:
- 如果LSR收到LDP-RELEASE：
Locate an Upstream LSP Control Block that 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.
定位具有相同FEC、相同上游标签、相同上游LDP会话标识符的上游LSP控制块。如果未找到上游LSP控制块，则忽略该消息。如果发现上游LSP控制块，则将事件“LDP释放”发送到其状态机。
- If an LSR receives an LDP-WITHDRAW:
- 如果LSR收到LDP-DROW：
Find a Downstream LSP Control Block that has the same FEC, the same Downstream LDP Session Identifier and the same Downstream Label. Pass the event `LDP Withdraw' to its state machines.
查找具有相同FEC、相同下游LDP会话标识符和相同下游标签的下游LSP控制块。将事件“LDP撤回”传递给其状态机。
- If an Upstream LDP peer is lost:
- 如果上游LDP对等点丢失：
Pass the event `Upstream Lost' to the state machines of all the Upstream LSP Control Blocks whose upstream LDP peer is that LSR.
将事件“上游丢失”传递给上游LDP对等方为该LSR的所有上游LSP控制块的状态机。
- If a Downstream LDP peer is lost:
- 如果下游LDP对等点丢失：
Pass the event `Label Withdraw' to the state machines of all the Downstream LSP Control Blocks whose the downstream LDP peer is that LSR.
将事件“Label Retrach”传递给下游LDP对等方为该LSR的所有下游LSP控制块的状态机。
- If a next hop of an FEC is changed:
- 如果FEC的下一跳发生更改：
Find all the Downstream LSP Control Blocks that has the same FEC and the same next hop and pass the event `Next Hop Change' to their state machine
查找具有相同FEC和相同下一跳的所有下游LSP控制块，并将事件“下一跳更改”传递给它们的状态机
- If there is a FEC being added to the forwarding table
- 如果正在将FEC添加到转发表中
Create a new Downstream LSP Control Block with state `IDLE'
创建状态为“空闲”的新下游LSP控制块
- If the FEC is deleted from the forwarding table
- 如果从转发表中删除FEC
Send the `Delete FEC' event to the its control block.
将“删除FEC”事件发送到its控制块。
- If an LSR receives an LDP-NAK from an upstream LSR:
- 如果LSR从上游LSR接收到LDP-NAK：
Ignore the message. An LDP-NAK should never appear in the downstream-mode LSR
忽略此消息。LDP-NAK不应出现在下游模式LSR中
- If an LSR receives an LDP-NAK from a downstream LSR:
- 如果LSR从下游LSR接收到LDP-NAK：
Ignore the message. It is a protocol error from the downstream LSR.
忽略此消息。这是来自下游LSR的协议错误。
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.
本文件作为LDP规范[4]的信息扩展提供。本文介绍的状态机旨在澄清LDP规范中定义的程序，但不取代或覆盖其中提供的定义和程序。
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消息引起的外部事件。
LDP messages may be protected using mechanisms described in the LDP specification. See "Security Considerations" in the LDP specification [4].
可以使用LDP规范中描述的机制来保护LDP消息。参见LDP规范[4]中的“安全注意事项”。
Security considerations relating to generation of spurious internal events are not addressed in this document.
本文件未涉及与生成虚假内部事件相关的安全注意事项。
The authors would like to acknowledge the helpful comments and suggestions of the following people: Bob Thomas, Myunghee Son and Adrian Farrel.
作者希望感谢以下人士的有益评论和建议：鲍勃·托马斯、明希森和阿德里安·法雷尔。
[1] Davie, B., Lawrence, J., McCloghrie, K., Rosen, E., Swallow, G., Rekhter, Y. and P. Doolan, "MPLS Using LDP and ATM Switching", RFC 3035, January 2001.
[1] Davie，B.，Lawrence，J.，McCloghrie，K.，Rosen，E.，Swallow，G.，Rekhter，Y.和P.Doolan，“使用LDP和ATM交换的MPLS”，RFC 3035，2001年1月。
[2] Rosen, E., Viswanathan, A. and R. Callon, "Multiprotocol Label Switching Architecture", RFC 3031, January 2001.
[2] Rosen，E.，Viswanathan，A.和R.Callon，“多协议标签交换体系结构”，RFC 30312001年1月。
[3] Cucchiara, J., Sjostrand, H. and J. Lucianai, "Definition of Managed Objects for the Multiprotocol Label Switching, Label Distribution Protocol (LDP)", Work in Progress.
[3] Cucchiara，J.，Sjostrand，H.和J.Lucianai，“多协议标签交换管理对象的定义，标签分发协议（LDP）”，正在进行的工作。
[4] Andersson, L., Doolan, P., Feldman, F., Fredette, A. and B. Thomas, "LDP Specification", RFC 3036, January 2001.
[4] Andersson，L.，Doolan，P.，Feldman，F.，Fredette，A.和B.Thomas，“LDP规范”，RFC 3036，2001年1月。
[5] Jamoussi, B., Ed., O., Andersson, L., Callon, R., Dantu, R., Wu, L., Doolan, P., Worster, T., Feldman, N., Fredette, A., Girish, M., Gray, E., Heinanen, J., Kilty, T. and A. Malis, "Constraint-Based LSP Set up Using LDP", RFC 3212, January 2002.
[5] Jamoussi，B.，Ed.，O.，Andersson，L.，Callon，R.，Dantu，R.，Wu，L.，Doolan，P.，Worster，T.，Feldman，N.，Fredette，A.，Girish，M.，Gray，E.，Heinanen，J.，Kilty，T.和A.Malis，“使用LDP建立基于约束的LSP”，RFC 3212，2002年1月。
Christophe Boscher Alcatel Le Mail 44700 Orvault France
克里斯托夫·博舍·阿尔卡特法国邮政44700
Phone: (33) 251781828 EMail: christophe.boscher@alcatel.fr
电话：（33）251781828电子邮件：christophe。boscher@alcatel.fr
Pierrick Cheval Alcatel 5 rue Noel-Pons 92734 Nanterre Cedex France
法国南特雷塞德克斯诺埃尔庞街5号皮尔里克·切瓦尔·阿尔卡特92734
Phone: (33) 146524027 EMail: pierrick.cheval@space.alcatel.fr
电话：（33）146524027电子邮件：pierrick。cheval@space.alcatel.fr
Liwen Wu Cisco Systems, Inc. 3550 Cisco Way San Jose, CA 95134 U.S.A
吴立文思科系统有限公司，地址：美国加利福尼亚州圣何塞思科路3550号，邮编：95134
Phone: 408-853-4065 EMail: liwwu@cisco.com
电话：408-853-4065电子邮件：liwwu@cisco.com
Eric Gray Sandburst Corporation 600 Federal Drive Andover, MA 01810
Eric Gray Sandburst Corporation马萨诸塞州安多弗联邦大道600号01810
Phone: (978) 689-1610 EMail: eric.gray@sandburst.com
电话：（978）689-1610电子邮件：埃里克。gray@sandburst.com
Copyright (C) The Internet Society (2002). All Rights Reserved.
版权所有（C）互联网协会（2002年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。