Internet Engineering Task Force (IETF) E. Haleplidis
Request for Comments: 6053 University of Patras
Category: Informational K. Ogawa
ISSN: 2070-1721 NTT Corporation
W. Wang
Zhejiang Gongshang University
J. Hadi Salim
Mojatatu Networks
November 2010
Internet Engineering Task Force (IETF) E. Haleplidis
Request for Comments: 6053 University of Patras
Category: Informational K. Ogawa
ISSN: 2070-1721 NTT Corporation
W. Wang
Zhejiang Gongshang University
J. Hadi Salim
Mojatatu Networks
November 2010
Implementation Report for Forwarding and Control Element Separation (ForCES)
转发和控制单元分离（部队）实施报告
Abstract
摘要
Forwarding and Control Element Separation (ForCES) defines an architectural framework and associated protocols to standardize information exchange between the control plane and the forwarding plane in a ForCES network element (ForCES NE). RFC 3654 has defined the ForCES requirements, and RFC 3746 has defined the ForCES framework.
转发和控制元素分离（ForCES）定义了一个体系结构框架和相关协议，以标准化ForCES网元（ForCES NE）中控制平面和转发平面之间的信息交换。RFC 3654定义了部队需求，RFC 3746定义了部队框架。
This document is an implementation report for the ForCES Protocol, Model, and the Stream Control Transmission Protocol-based Transport Mapping Layer (SCTP TML) documents, and includes a report on interoperability testing and the current state of ForCES implementations.
本文档是ForCES协议、模型和基于流控制传输协议的传输映射层（SCTP TML）文档的实施报告，包括关于互操作性测试和ForCES实施现状的报告。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6053.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6053.
Copyright Notice
版权公告
Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2010 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. ForCES Protocol . . . . . . . . . . . . . . . . . . . . . 4
1.2. ForCES Model . . . . . . . . . . . . . . . . . . . . . . . 4
1.3. Transport Mapping Layer . . . . . . . . . . . . . . . . . 4
2. Terminology and Conventions . . . . . . . . . . . . . . . . . 4
2.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
2.2. Definitions . . . . . . . . . . . . . . . . . . . . . . . 5
3. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Methodology . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6. Detail Section . . . . . . . . . . . . . . . . . . . . . . . . 7
6.1. Implementation Experience . . . . . . . . . . . . . . . . 7
6.1.1. ForCES Protocol Features . . . . . . . . . . . . . . . 9
6.1.1.1. Protocol Messages . . . . . . . . . . . . . . . . 9
6.1.1.2. MainHeader Handling . . . . . . . . . . . . . . . 10
6.1.1.3. TLV Handling . . . . . . . . . . . . . . . . . . . 11
6.1.1.4. Operation Types Supported . . . . . . . . . . . . 12
6.1.1.5. ForCES Protocol Advanced Features . . . . . . . . 13
6.1.2. ForCES Model Features . . . . . . . . . . . . . . . . 14
6.1.2.1. Basic Atomic Types Supported . . . . . . . . . . . 14
6.1.2.2. Compound Types Supported . . . . . . . . . . . . . 15
6.1.2.3. LFBs Supported . . . . . . . . . . . . . . . . . . 15
6.1.3. ForCES SCTP TML Features . . . . . . . . . . . . . . . 19
6.1.3.1. TML Priority Ports . . . . . . . . . . . . . . . . 19
6.1.3.2. Message Handling at Specific Priorities . . . . . 19
6.1.3.3. TML Security Feature . . . . . . . . . . . . . . . 20
6.2. Interoperability Report . . . . . . . . . . . . . . . . . 20
6.2.1. Scenarios . . . . . . . . . . . . . . . . . . . . . . 21
6.2.1.1. Scenario 1 - Pre-Association Setup . . . . . . . . 21
6.2.1.2. Scenario 2 - TML Priority Channels Connection . . 22
6.2.1.3. Scenario 3 - Association Setup - Association
Complete . . . . . . . . . . . . . . . . . . . . . 22
6.2.1.4. Scenario 4 - CE Query . . . . . . . . . . . . . . 23
6.2.1.5. Scenario 5 - Heartbeat Monitoring . . . . . . . . 23
6.2.1.6. Scenario 6 - Simple Config Command . . . . . . . . 23
6.2.1.7. Scenario 7 - Association Teardown . . . . . . . . 24
6.2.2. Tested Features . . . . . . . . . . . . . . . . . . . 25
6.2.2.1. ForCES Protocol Features . . . . . . . . . . . . . 25
6.2.2.2. ForCES Model Features . . . . . . . . . . . . . . 28
6.2.2.3. ForCES SCTP TML Features . . . . . . . . . . . . . 30
6.2.3. Interoperability Results . . . . . . . . . . . . . . . 31
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 32
8. Security Considerations . . . . . . . . . . . . . . . . . . . 33
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 33
9.1. Normative References . . . . . . . . . . . . . . . . . . . 33
9.2. Informative References . . . . . . . . . . . . . . . . . . 33
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. ForCES Protocol . . . . . . . . . . . . . . . . . . . . . 4
1.2. ForCES Model . . . . . . . . . . . . . . . . . . . . . . . 4
1.3. Transport Mapping Layer . . . . . . . . . . . . . . . . . 4
2. Terminology and Conventions . . . . . . . . . . . . . . . . . 4
2.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
2.2. Definitions . . . . . . . . . . . . . . . . . . . . . . . 5
3. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Methodology . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6. Detail Section . . . . . . . . . . . . . . . . . . . . . . . . 7
6.1. Implementation Experience . . . . . . . . . . . . . . . . 7
6.1.1. ForCES Protocol Features . . . . . . . . . . . . . . . 9
6.1.1.1. Protocol Messages . . . . . . . . . . . . . . . . 9
6.1.1.2. MainHeader Handling . . . . . . . . . . . . . . . 10
6.1.1.3. TLV Handling . . . . . . . . . . . . . . . . . . . 11
6.1.1.4. Operation Types Supported . . . . . . . . . . . . 12
6.1.1.5. ForCES Protocol Advanced Features . . . . . . . . 13
6.1.2. ForCES Model Features . . . . . . . . . . . . . . . . 14
6.1.2.1. Basic Atomic Types Supported . . . . . . . . . . . 14
6.1.2.2. Compound Types Supported . . . . . . . . . . . . . 15
6.1.2.3. LFBs Supported . . . . . . . . . . . . . . . . . . 15
6.1.3. ForCES SCTP TML Features . . . . . . . . . . . . . . . 19
6.1.3.1. TML Priority Ports . . . . . . . . . . . . . . . . 19
6.1.3.2. Message Handling at Specific Priorities . . . . . 19
6.1.3.3. TML Security Feature . . . . . . . . . . . . . . . 20
6.2. Interoperability Report . . . . . . . . . . . . . . . . . 20
6.2.1. Scenarios . . . . . . . . . . . . . . . . . . . . . . 21
6.2.1.1. Scenario 1 - Pre-Association Setup . . . . . . . . 21
6.2.1.2. Scenario 2 - TML Priority Channels Connection . . 22
6.2.1.3. Scenario 3 - Association Setup - Association
Complete . . . . . . . . . . . . . . . . . . . . . 22
6.2.1.4. Scenario 4 - CE Query . . . . . . . . . . . . . . 23
6.2.1.5. Scenario 5 - Heartbeat Monitoring . . . . . . . . 23
6.2.1.6. Scenario 6 - Simple Config Command . . . . . . . . 23
6.2.1.7. Scenario 7 - Association Teardown . . . . . . . . 24
6.2.2. Tested Features . . . . . . . . . . . . . . . . . . . 25
6.2.2.1. ForCES Protocol Features . . . . . . . . . . . . . 25
6.2.2.2. ForCES Model Features . . . . . . . . . . . . . . 28
6.2.2.3. ForCES SCTP TML Features . . . . . . . . . . . . . 30
6.2.3. Interoperability Results . . . . . . . . . . . . . . . 31
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 32
8. Security Considerations . . . . . . . . . . . . . . . . . . . 33
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 33
9.1. Normative References . . . . . . . . . . . . . . . . . . . 33
9.2. Informative References . . . . . . . . . . . . . . . . . . 33
This document is an implementation report for the ForCES protocol, model, and the SCTP TML documents, and includes an interoperability report.
本文件是部队协议、模型和SCTP TML文件的实施报告，包括互操作性报告。
It follows the outline suggested by [RFC5657].
它遵循[RFC5657]建议的大纲。
ForCES defines an architectural framework and associated protocols to standardize information exchange between the control plane and the forwarding plane in a ForCES network element (ForCES NE). [RFC3654] has defined the ForCES requirements, and [RFC3746] has defined the ForCES framework.
ForCES定义了一个体系结构框架和相关协议，以标准化ForCES网元（ForCES NE）中控制平面和转发平面之间的信息交换。[RFC3654]定义了部队需求，[RFC3746]定义了部队框架。
The ForCES protocol works in a master-slave mode in which forwarding elements (FEs) are slaves and control elements (CEs) are masters. The protocol includes commands for transport of Logical Functional Block (LFB) configuration information, association setup, status, event notifications, etc. The reader is encouraged to read the ForCES Protocol Specification [RFC5810] for further information.
ForCES协议在主从模式下工作，其中转发元素（FEs）是从元素，控制元素（ce）是主元素。该协议包括用于传输逻辑功能块（LFB）配置信息、关联设置、状态、事件通知等的命令。鼓励读者阅读ForCES协议规范[RFC5810]以获取更多信息。
The ForCES Model [RFC5812] presents a formal way to define FE Logical Functional Blocks (LFBs) using XML. LFB configuration components, capabilities, and associated events are defined when the LFB is formally created. The LFBs within the FE are accordingly controlled in a standardized way by the ForCES protocol.
ForCES模型[RFC5812]提供了一种使用XML定义FE逻辑功能块（LFB）的形式化方法。LFB配置组件、功能和相关事件在正式创建LFB时定义。FE内的LFB由ForCES协议以标准化方式进行相应控制。
The TML transports the protocol layer (PL) messages [RFC5810]. The TML is where the issues of how to achieve transport-level reliability, congestion control, multicast, ordering, etc. are handled. All ForCES protocol layer implementations MUST be portable across all TMLs. Although more than one TML may be standardized for the ForCES protocol, all implementations MUST implement SCTP TML [RFC5811].
TML传输协议层（PL）消息[RFC5810]。TML是处理如何实现传输级可靠性、拥塞控制、多播、排序等问题的地方。所有部队协议层实现必须可移植到所有TML。尽管ForCES协议可以标准化多个TML，但所有实现都必须实现SCTP TML[RFC5811]。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
This document follows the terminology defined by the ForCES requirements in [RFC3654] and by the ForCES framework in [RFC3746]. The definitions are repeated below for clarity.
本文件遵循[RFC3654]中部队要求和[RFC3746]中部队框架定义的术语。为了清楚起见，下面重复这些定义。
Control Element (CE) - A logical entity that implements the ForCES protocol and uses it to instruct one or more FEs on how to process packets. CEs handle functionality such as the execution of control and signaling protocols.
控制元素（CE）-实现强制协议的逻辑实体，并使用它指示一个或多个FEs如何处理数据包。CEs处理控制和信令协议的执行等功能。
Forwarding Element (FE) - A logical entity that implements the ForCES protocol. FEs use the underlying hardware to provide per-packet processing and handling as directed/controlled by one or more CEs via the ForCES protocol.
转发元素（FE）-实现ForCES协议的逻辑实体。FEs使用底层硬件，按照一个或多个CE通过ForCES协议的指示/控制，提供每包处理和处理。
LFB (Logical Functional Block) - The basic building block that is operated on by the ForCES protocol. The LFB is a well defined, logically separable functional block that resides in an FE and is controlled by the CE via the ForCES protocol. The LFB may reside at the FE's datapath and process packets or may be purely an FE control or configuration entity that is operated on by the CE. Note that the LFB is a functionally accurate abstraction of the FE's processing capabilities, but not a hardware-accurate representation of the FE implementation.
LFB（逻辑功能块）-由ForCES协议操作的基本构建块。LFB是一个定义良好、逻辑上可分离的功能块，位于FE中，由CE通过ForCES协议控制。LFB可以驻留在FE的数据路径上并处理分组，或者可以是由CE操作的纯粹FE控制或配置实体。请注意，LFB是FE处理能力的功能精确抽象，但不是FE实现的硬件精确表示。
LFB Class and LFB Instance - LFBs are categorized by LFB Classes. An LFB Instance represents an LFB Class (or Type) existence. There may be multiple instances of the same LFB Class (or Type) in an FE. An LFB Class is represented by an LFB Class ID, and an LFB Instance is represented by an LFB Instance ID. As a result, an LFB Class ID associated with an LFB Instance ID uniquely specifies an LFB existence.
LFB类和LFB实例-LFB按LFB类分类。LFB实例表示LFB类（或类型）的存在。FE中可能存在同一LFB类（或类型）的多个实例。LFB类由LFB类ID表示，LFB实例由LFB实例ID表示。因此，与LFB实例ID关联的LFB类ID唯一地指定LFB的存在。
LFB Metadata - Metadata is used to communicate per-packet state from one LFB to another, but is not sent across the network. The FE model defines how such metadata is identified, produced, and consumed by the LFBs. It defines the functionality but not how metadata is encoded within an implementation.
LFB元数据-元数据用于将每个数据包状态从一个LFB传送到另一个LFB，但不会通过网络发送。FE模型定义了LFB如何识别、生成和使用这些元数据。它定义了功能，但没有定义元数据在实现中的编码方式。
LFB Components - Operational parameters of the LFBs that must be visible to the CEs are conceptualized in the FE model as the LFB components. The LFB components include, for example, flags, single-parameter arguments, complex arguments, and tables that the CE can read and/or write via the ForCES protocol (see below).
LFB组件-必须对CEs可见的LFB操作参数在FE模型中被概念化为LFB组件。LFB组件包括，例如，标志、单参数参数参数、复杂参数以及CE可以通过ForCES协议读取和/或写入的表（见下文）。
ForCES Protocol - While there may be multiple protocols used within the overall ForCES architecture, the term "ForCES protocol" and "protocol" refer to the "Fp" reference points in the ForCES framework in [RFC3746]. This protocol does not apply to CE-to-CE communication, FE-to-FE communication, or to communication between FE and CE managers. Basically, the ForCES protocol works in a master-slave mode in which FEs are slaves and CEs are masters.
部队协议-虽然在整个部队体系结构中可能使用多个协议，但术语“部队协议”和“协议”指的是[RFC3746]中部队框架中的“Fp”参考点。本协议不适用于CE-to-CE通信、FE-to-FE通信或FE与CE经理之间的通信。基本上，ForCES协议在主-从模式下工作，其中FEs是从机，ce是主机。
ForCES Protocol Transport Mapping Layer (ForCES TML) - A layer in ForCES protocol architecture that uses the capabilities of existing transport protocols to specifically address protocol message transportation issues, such as how the protocol messages are mapped to different transport media (like TCP, IP, ATM, Ethernet, etc.), and how to achieve and implement reliability, multicast, ordering, etc. The ForCES TML specifications are detailed in separate ForCES documents, one for each TML.
ForCES协议传输映射层（ForCES TML）-ForCES协议体系结构中的一个层，它使用现有传输协议的功能专门解决协议消息传输问题，例如协议消息如何映射到不同的传输介质（如TCP、IP、ATM、以太网等），以及如何实现和实现可靠性、多播、订购等。ForCES TML规范在单独的ForCES文档中详细说明，每个TML一个。
Three independent implementations, NTT Japan, the University of Patras, and Zhejiang Gongshang University, were surveyed and found to already implement all the major features. All implementors mentioned they will be implementing all missing features in the future.
三个独立的实施方案，NTT日本，佩特雷大学和浙江工商大学，进行了调查，发现已经实现了所有的主要特点。所有实现者都提到，他们将在将来实现所有缺失的功能。
An interop test was conducted in July 2009 for all three implementations. Two other organizations, Mojatatu Networks and Hangzhou Baud Information and Networks Technology Corporation, which independently extended two different well known public domain protocol analyzers, Ethereal/Wireshark and tcpdump, also participated in the interop for a total of five independent organizations implementing. The two protocol analyzers were used to verify the validity of ForCES protocol messages (and in some cases semantics).
2009年7月对所有三种实现进行了互操作测试。另外两个组织，Mojatatu Networks和杭州波特信息网络技术公司，独立扩展了两个不同的知名公共域协议分析器Ethereal/Wireshark和tcpdump，也参与了互操作，共有五个独立组织实施了互操作。这两个协议分析器用于验证ForCES协议消息的有效性（在某些情况下还包括语义）。
There were no notable difficulties in the interoperability test, and almost all issues were code bugs that were dealt with mostly on site; tests repeated successfully, as stated in Section 6.2.3.
在互操作性测试中没有明显的困难，几乎所有的问题都是代码错误，主要在现场处理；如第6.2.3节所述，试验成功重复。
This report describes an implementation experience survey as well as the results of the interoperability test.
本报告描述了实施经验调查以及互操作性测试的结果。
The survey information was gathered after implementors answered a brief questionnaire regarding all ForCES Protocol, Model, and SCTP TML features. The results can be seen in Section 6.1.
调查信息是在实施者回答了关于所有部队协议、模型和SCTP TML功能的简短问卷后收集的。结果见第6.1节。
The interoperability results were part of the interoperability test. Extended Ethereal and extended tcpdump were used to verify the results. The results can be seen in Section 6.2.
互操作性结果是互操作性测试的一部分。使用扩展Ethereal和扩展tcpdump验证结果。结果见第6.2节。
The core features of the ForCES Protocol, Model, and SCTP TML were implemented and assessed in an interop test in July 2009. The intention of the interop testing was to validate that all the main features of the three core documents were interoperable amongst different implementations. The tested features can be seen in Section 6.2.2.
部队协议、模型和SCTP TML的核心功能已在2009年7月的互操作测试中实施和评估。互操作测试的目的是验证这三个核心文档的所有主要特性在不同的实现中都是可互操作的。测试特性见第6.2.2节。
Different organizations surveyed have implemented certain features but not others. This approach is driven by the presence of different LFBs that the different organizations currently implement. All organizations surveyed have indicated their intention to implement all outstanding features in due time. The implemented features can be seen in Section 6.1.
接受调查的不同组织实施了某些功能，但没有实施其他功能。这种方法是由不同组织目前实施的不同LFB所驱动的。所有接受调查的组织都表示打算在适当时候实施所有突出的功能。实现的功能见第6.1节。
The mandated TML security requirement, IP security (IPsec), was not validated during the interop and is not discussed in this document. Since IPsec is well known and widely deployed, not testing in the presence of IPsec does not invalidate the tests done. Note that Section 6.1.3.3 indicates that none of the implementations reporting included support for IPsec, but all indicated their intention to implement it.
强制的TML安全要求IP安全性（IPsec）在互操作期间未得到验证，本文档中未讨论。由于IPsec是众所周知且广泛部署的，因此不在IPsec存在的情况下进行测试不会使所做的测试无效。请注意，第6.1.3.3节指出，报告的实现中没有一个包含对IPsec的支持，但所有实现都表示打算实现IPsec。
Although the SCTP priority ports have changed since the interoperability test with the version of the SCTP TML draft available prior to the publication of RFC 5811, the change has no impact on the validity of the interoperability test.
尽管自互操作性测试以来，SCTP优先级端口发生了变化，在RFC 5811发布之前，SCTP TML草案的版本可用，但该变化对互操作性测试的有效性没有影响。
Three different organizations have implemented the ForCES Protocol, Model, and SCTP TML and answered a questionnaire. These are:
三个不同的组织实施了部队协议、模型和SCTP TML，并回答了问卷调查。这些是：
o NTT Japan
o 日本新台币
o University of Patras
o 佩特雷大学
o Zhejiang Gongshang University
o 浙江工商大学
Extensions to protocol analyzers capable of understanding ForCES protocol messages are considered part of an implementation, since these analyzers can now understand and validate ForCES protocol message that have been exchanged. Two such extensions have been created:
能够理解ForCES协议消息的协议分析器的扩展被视为实现的一部分，因为这些分析器现在可以理解和验证已交换的ForCES协议消息。已经创建了两个这样的扩展：
o Extension to Ethereal/Wireshark [ethereal].
o 扩展到Ethereal/Wireshark[Ethereal]。
o Extension to tcpdump [tcpdump].
o tcpdump[tcpdump]的扩展。
All implementors were asked about the ForCES features they have implemented. For every item listed, the respondents indicated whether they had implemented, will implement, or won't implement at all.
所有实现者都被问及他们已经实现的ForCES特性。对于列出的每一项，受访者表示他们是否已经实施、将实施或根本不实施。
+------------------+-------------+---------------+------------------+
| Protocol Message | NTT Japan | University of | Zhejiang |
| | | Patras | Gongshang |
| | | | University |
+------------------+-------------+---------------+------------------+
| Association | Implemented | Implemented | Implemented |
| Setup | | | |
| | | | |
| Association | Implemented | Implemented | Implemented |
| Setup Response | | | |
| | | | |
| Association | Implemented | Implemented | Implemented |
| Teardown | | | |
| | | | |
| Config | Implemented | Implemented | Implemented |
| | | | |
| Config Response | Implemented | Implemented | Implemented |
| | | | |
| Query | Implemented | Implemented | Implemented |
| | | | |
| Query Response | Implemented | Implemented | Implemented |
| | | | |
| Event | Implemented | Will | Implemented |
| Notification | | Implement | |
| | | | |
| Packet Redirect | Implemented | Will | Implemented |
| | | Implement | |
| | | | |
| Heartbeat | Implemented | Implemented | Implemented |
+------------------+-------------+---------------+------------------+
+------------------+-------------+---------------+------------------+
| Protocol Message | NTT Japan | University of | Zhejiang |
| | | Patras | Gongshang |
| | | | University |
+------------------+-------------+---------------+------------------+
| Association | Implemented | Implemented | Implemented |
| Setup | | | |
| | | | |
| Association | Implemented | Implemented | Implemented |
| Setup Response | | | |
| | | | |
| Association | Implemented | Implemented | Implemented |
| Teardown | | | |
| | | | |
| Config | Implemented | Implemented | Implemented |
| | | | |
| Config Response | Implemented | Implemented | Implemented |
| | | | |
| Query | Implemented | Implemented | Implemented |
| | | | |
| Query Response | Implemented | Implemented | Implemented |
| | | | |
| Event | Implemented | Will | Implemented |
| Notification | | Implement | |
| | | | |
| Packet Redirect | Implemented | Will | Implemented |
| | | Implement | |
| | | | |
| Heartbeat | Implemented | Implemented | Implemented |
+------------------+-------------+---------------+------------------+
ForCES Protocol Messages
强制协议消息
+-----------------+-------------+----------------+------------------+
| Header Field | NTT Japan | University of | Zhejiang |
| | | Patras | Gongshang |
| | | | University |
+-----------------+-------------+----------------+------------------+
| Correlator | Implemented | Implemented | Implemented |
| | | | |
| ACK Indicator | Implemented | Implemented | Implemented |
| Flag | | | |
| | | | |
| Priority Flag | Will | Implemented | Implemented |
| | Implement | | |
| | | | |
| Execution Mode | Will | Will Implement | Implemented |
| Flag | Implement | | |
| | | | |
| Atomic | Will | Will Implement | Implemented |
| Transaction | Implement | | |
| Flag | | | |
| | | | |
| Transaction | Will | Will Implement | Implemented |
| Phase Flag | Implement | | |
+-----------------+-------------+----------------+------------------+
+-----------------+-------------+----------------+------------------+
| Header Field | NTT Japan | University of | Zhejiang |
| | | Patras | Gongshang |
| | | | University |
+-----------------+-------------+----------------+------------------+
| Correlator | Implemented | Implemented | Implemented |
| | | | |
| ACK Indicator | Implemented | Implemented | Implemented |
| Flag | | | |
| | | | |
| Priority Flag | Will | Implemented | Implemented |
| | Implement | | |
| | | | |
| Execution Mode | Will | Will Implement | Implemented |
| Flag | Implement | | |
| | | | |
| Atomic | Will | Will Implement | Implemented |
| Transaction | Implement | | |
| Flag | | | |
| | | | |
| Transaction | Will | Will Implement | Implemented |
| Phase Flag | Implement | | |
+-----------------+-------------+----------------+------------------+
MainHeader Handling
主收割台处理
+------------------+-------------+---------------+------------------+
| TLV | NTT Japan | University of | Zhejiang |
| | | Patras | Gongshang |
| | | | University |
+------------------+-------------+---------------+------------------+
| REDIRECT-TLV | Implemented | Will | Implemented |
| | | Implement | |
| | | | |
| ASResult-TLV | Implemented | Implemented | Implemented |
| | | | |
| ASTReason-TLV | Implemented | Implemented | Implemented |
| | | | |
| LFBSelect-TLV | Implemented | Implemented | Implemented |
| | | | |
| OPER-TLV | Implemented | Implemented | Implemented |
| | | | |
| PATH-DATA-TLV | Implemented | Implemented | Implemented |
| | | | |
| KEYINFO-TLV | Will | Will | Implemented |
| | Implement | Implement | |
| | | | |
| FULLDATA-TLV | Implemented | Implemented | Implemented |
| | | | |
| SPARSEDATA-TLV | Will | Will | Implemented |
| | Implement | Implement | |
| | | | |
| ILV | Will | Will | Implemented |
| | Implement | Implement | |
| | | | |
| METADATA-TLV | Will | Will | Implemented |
| | Implement | Implement | |
| | | | |
| RESULT-TLV | Implemented | Implemented | Implemented |
| | | | |
| REDIRECTDATA-TLV | Implemented | Will | Implemented |
| | | Implement | |
+------------------+-------------+---------------+------------------+
+------------------+-------------+---------------+------------------+
| TLV | NTT Japan | University of | Zhejiang |
| | | Patras | Gongshang |
| | | | University |
+------------------+-------------+---------------+------------------+
| REDIRECT-TLV | Implemented | Will | Implemented |
| | | Implement | |
| | | | |
| ASResult-TLV | Implemented | Implemented | Implemented |
| | | | |
| ASTReason-TLV | Implemented | Implemented | Implemented |
| | | | |
| LFBSelect-TLV | Implemented | Implemented | Implemented |
| | | | |
| OPER-TLV | Implemented | Implemented | Implemented |
| | | | |
| PATH-DATA-TLV | Implemented | Implemented | Implemented |
| | | | |
| KEYINFO-TLV | Will | Will | Implemented |
| | Implement | Implement | |
| | | | |
| FULLDATA-TLV | Implemented | Implemented | Implemented |
| | | | |
| SPARSEDATA-TLV | Will | Will | Implemented |
| | Implement | Implement | |
| | | | |
| ILV | Will | Will | Implemented |
| | Implement | Implement | |
| | | | |
| METADATA-TLV | Will | Will | Implemented |
| | Implement | Implement | |
| | | | |
| RESULT-TLV | Implemented | Implemented | Implemented |
| | | | |
| REDIRECTDATA-TLV | Implemented | Will | Implemented |
| | | Implement | |
+------------------+-------------+---------------+------------------+
TLVs Supported
受支持的TLV
+-------------------+-------------+---------------+-----------------+
| Operation | NTT Japan | University of | Zhejiang |
| | | Patras | Gongshang |
| | | | University |
+-------------------+-------------+---------------+-----------------+
| SET | Implemented | Implemented | Implemented |
| | | | |
| SET-PROP | Will | Will | Implemented |
| | Implement | Implement | |
| | | | |
| SET-RESPONSE | Implemented | Implemented | Implemented |
| | | | |
| SET-PROP-RESPONSE | Will | Will | Implemented |
| | Implement | Implement | |
| | | | |
| DEL | Implemented | Will | Implemented |
| | | Implement | |
| | | | |
| DEL-RESPONSE | Implemented | Will | Implemented |
| | | Implement | |
| | | | |
| GET | Implemented | Implemented | Implemented |
| | | | |
| GET-PROP | Will | Will | Implemented |
| | Implement | Implement | |
| | | | |
| GET-RESPONSE | Implemented | Implemented | Implemented |
| | | | |
| GET-PROP-RESPONSE | Will | Will | Implemented |
| | Implement | Implement | |
| | | | |
| REPORT | Implemented | Implemented | Implemented |
| | | | |
| COMMIT | Will | Will | Implemented |
| | Implement | Implement | |
| | | | |
| COMMIT-RESPONSE | Will | Will | Implemented |
| | Implement | Implement | |
| | | | |
| TRCOMP | Will | Will | Implemented |
| | Implement | Implement | |
+-------------------+-------------+---------------+-----------------+
+-------------------+-------------+---------------+-----------------+
| Operation | NTT Japan | University of | Zhejiang |
| | | Patras | Gongshang |
| | | | University |
+-------------------+-------------+---------------+-----------------+
| SET | Implemented | Implemented | Implemented |
| | | | |
| SET-PROP | Will | Will | Implemented |
| | Implement | Implement | |
| | | | |
| SET-RESPONSE | Implemented | Implemented | Implemented |
| | | | |
| SET-PROP-RESPONSE | Will | Will | Implemented |
| | Implement | Implement | |
| | | | |
| DEL | Implemented | Will | Implemented |
| | | Implement | |
| | | | |
| DEL-RESPONSE | Implemented | Will | Implemented |
| | | Implement | |
| | | | |
| GET | Implemented | Implemented | Implemented |
| | | | |
| GET-PROP | Will | Will | Implemented |
| | Implement | Implement | |
| | | | |
| GET-RESPONSE | Implemented | Implemented | Implemented |
| | | | |
| GET-PROP-RESPONSE | Will | Will | Implemented |
| | Implement | Implement | |
| | | | |
| REPORT | Implemented | Implemented | Implemented |
| | | | |
| COMMIT | Will | Will | Implemented |
| | Implement | Implement | |
| | | | |
| COMMIT-RESPONSE | Will | Will | Implemented |
| | Implement | Implement | |
| | | | |
| TRCOMP | Will | Will | Implemented |
| | Implement | Implement | |
+-------------------+-------------+---------------+-----------------+
Operation Types Supported
支持的操作类型
+---------------+-------------+----------------+--------------------+
| Feature | NTT Japan | University of | Zhejiang Gongshang |
| | | Patras | University |
+---------------+-------------+----------------+--------------------+
| Execute Mode | Will | Will Implement | Implemented |
| | Implement | | |
| | | | |
| Transaction | Will | Will Implement | Implemented |
| | Implement | | |
| | | | |
| Batching | Will | Implemented | Implemented |
| | Implement | | |
| | | | |
| Command | Will | Will Implement | Will Implement |
| Pipelining | Implement | | |
| | | | |
| Heartbeats | Implemented | Implemented | Implemented |
+---------------+-------------+----------------+--------------------+
+---------------+-------------+----------------+--------------------+
| Feature | NTT Japan | University of | Zhejiang Gongshang |
| | | Patras | University |
+---------------+-------------+----------------+--------------------+
| Execute Mode | Will | Will Implement | Implemented |
| | Implement | | |
| | | | |
| Transaction | Will | Will Implement | Implemented |
| | Implement | | |
| | | | |
| Batching | Will | Implemented | Implemented |
| | Implement | | |
| | | | |
| Command | Will | Will Implement | Will Implement |
| Pipelining | Implement | | |
| | | | |
| Heartbeats | Implemented | Implemented | Implemented |
+---------------+-------------+----------------+--------------------+
ForCES Protocol Advanced Features
ForCES协议高级功能
+----------------+-------------+---------------+--------------------+
| Atomic Type | NTT Japan | University of | Zhejiang Gongshang |
| | | Patras | University |
+----------------+-------------+---------------+--------------------+
| char | Implemented | Implemented | Will Implement |
| | | | |
| uchar | Implemented | Implemented | Implemented |
| | | | |
| int16 | Implemented | Implemented | Will Implement |
| | | | |
| uint16 | Implemented | Implemented | Will Implement |
| | | | |
| int32 | Implemented | Implemented | Implemented |
| | | | |
| uint32 | Implemented | Implemented | Implemented |
| | | | |
| int64 | Implemented | Implemented | Will Implement |
| | | | |
| uint64 | Implemented | Implemented | Will Implement |
| | | | |
| boolean | Implemented | Implemented | Implemented |
| | | | |
| string[N] | Implemented | Implemented | Implemented |
| | | | |
| string | Implemented | Implemented | Implemented |
| | | | |
| byte[N] | Implemented | Implemented | Implemented |
| | | | |
| octetstring[N] | Implemented | Implemented | Will Implement |
| | | | |
| float32 | Implemented | Implemented | Will Implement |
| | | | |
| float64 | Implemented | Implemented | Will Implement |
+----------------+-------------+---------------+--------------------+
+----------------+-------------+---------------+--------------------+
| Atomic Type | NTT Japan | University of | Zhejiang Gongshang |
| | | Patras | University |
+----------------+-------------+---------------+--------------------+
| char | Implemented | Implemented | Will Implement |
| | | | |
| uchar | Implemented | Implemented | Implemented |
| | | | |
| int16 | Implemented | Implemented | Will Implement |
| | | | |
| uint16 | Implemented | Implemented | Will Implement |
| | | | |
| int32 | Implemented | Implemented | Implemented |
| | | | |
| uint32 | Implemented | Implemented | Implemented |
| | | | |
| int64 | Implemented | Implemented | Will Implement |
| | | | |
| uint64 | Implemented | Implemented | Will Implement |
| | | | |
| boolean | Implemented | Implemented | Implemented |
| | | | |
| string[N] | Implemented | Implemented | Implemented |
| | | | |
| string | Implemented | Implemented | Implemented |
| | | | |
| byte[N] | Implemented | Implemented | Implemented |
| | | | |
| octetstring[N] | Implemented | Implemented | Will Implement |
| | | | |
| float32 | Implemented | Implemented | Will Implement |
| | | | |
| float64 | Implemented | Implemented | Will Implement |
+----------------+-------------+---------------+--------------------+
Basic Atomic Types Supported
支持的基本原子类型
+------------+-------------+-----------------+----------------------+
| Compound | NTT Japan | University of | Zhejiang Gongshang |
| Type | | Patras | University |
+------------+-------------+-----------------+----------------------+
| structs | Implemented | Implemented | Implemented |
| | | | |
| arrays | Implemented | Implemented | Implemented |
+------------+-------------+-----------------+----------------------+
+------------+-------------+-----------------+----------------------+
| Compound | NTT Japan | University of | Zhejiang Gongshang |
| Type | | Patras | University |
+------------+-------------+-----------------+----------------------+
| structs | Implemented | Implemented | Implemented |
| | | | |
| arrays | Implemented | Implemented | Implemented |
+------------+-------------+-----------------+----------------------+
Compound Types Supported
支持的复合类型
+------------------+-------------+----------------+-----------------+
| Protocol | NTT Japan | University of | Zhejiang |
| Datatypes | | Patras | Gongshang |
| | | | University |
+------------------+-------------+----------------+-----------------+
| CEHBPolicy | Implemented | Implemented | Implemented |
| | | | |
| FEHBPolicy | Implemented | Implemented | Implemented |
| | | | |
| FERestartPolicy | Implemented | Implemented | Implemented |
| | | | |
| CEFailoverPolicy | Implemented | Implemented | Implemented |
| | | | |
| FEHACapab | Implemented | Implemented | Will Implement |
+------------------+-------------+----------------+-----------------+
+------------------+-------------+----------------+-----------------+
| Protocol | NTT Japan | University of | Zhejiang |
| Datatypes | | Patras | Gongshang |
| | | | University |
+------------------+-------------+----------------+-----------------+
| CEHBPolicy | Implemented | Implemented | Implemented |
| | | | |
| FEHBPolicy | Implemented | Implemented | Implemented |
| | | | |
| FERestartPolicy | Implemented | Implemented | Implemented |
| | | | |
| CEFailoverPolicy | Implemented | Implemented | Implemented |
| | | | |
| FEHACapab | Implemented | Implemented | Will Implement |
+------------------+-------------+----------------+-----------------+
FE Protocol LFB Datatypes
FE协议LFB数据类型
+-----------------------+-------------+-------------+---------------+
| Protocol Components | NTT Japan | University | Zhejiang |
| | | of Patras | Gongshang |
| | | | University |
+-----------------------+-------------+-------------+---------------+
| CurrentRunningVersion | Implemented | Implemented | Implemented |
| | | | |
| FEID | Implemented | Implemented | Implemented |
| | | | |
| MulticastFEIDs | Implemented | Implemented | Implemented |
| | | | |
| CEHBPolicy | Implemented | Implemented | Implemented |
| | | | |
| CEHDI | Implemented | Implemented | Implemented |
| | | | |
| FEHBPolicy | Implemented | Implemented | Implemented |
| | | | |
| FEHI | Implemented | Implemented | Implemented |
| | | | |
| CEID | Implemented | Implemented | Implemented |
| | | | |
| BackupCEs | Implemented | Will | Will |
| | | Implement | Implement |
| | | | |
| CEFailoverPolicy | Implemented | Implemented | Implemented |
| | | | |
| CEFTI | Implemented | Implemented | Implemented |
| | | | |
| FERestartPolicy | Implemented | Implemented | Will |
| | | | Implement |
| | | | |
| LastCEID | Implemented | Implemented | Will |
| | | | Implement |
+-----------------------+-------------+-------------+---------------+
+-----------------------+-------------+-------------+---------------+
| Protocol Components | NTT Japan | University | Zhejiang |
| | | of Patras | Gongshang |
| | | | University |
+-----------------------+-------------+-------------+---------------+
| CurrentRunningVersion | Implemented | Implemented | Implemented |
| | | | |
| FEID | Implemented | Implemented | Implemented |
| | | | |
| MulticastFEIDs | Implemented | Implemented | Implemented |
| | | | |
| CEHBPolicy | Implemented | Implemented | Implemented |
| | | | |
| CEHDI | Implemented | Implemented | Implemented |
| | | | |
| FEHBPolicy | Implemented | Implemented | Implemented |
| | | | |
| FEHI | Implemented | Implemented | Implemented |
| | | | |
| CEID | Implemented | Implemented | Implemented |
| | | | |
| BackupCEs | Implemented | Will | Will |
| | | Implement | Implement |
| | | | |
| CEFailoverPolicy | Implemented | Implemented | Implemented |
| | | | |
| CEFTI | Implemented | Implemented | Implemented |
| | | | |
| FERestartPolicy | Implemented | Implemented | Will |
| | | | Implement |
| | | | |
| LastCEID | Implemented | Implemented | Will |
| | | | Implement |
+-----------------------+-------------+-------------+---------------+
FE Protocol LFB Components
FE协议LFB组件
+---------------------+-------------+-------------+-----------------+
| Capabilities | NTT Japan | University | Zhejiang |
| | | of Patras | Gongshang |
| | | | University |
+---------------------+-------------+-------------+-----------------+
| SupportableVersions | Implemented | Implemented | Implemented |
| | | | |
| HACapabilities | Implemented | Implemented | Will Implement |
+---------------------+-------------+-------------+-----------------+
+---------------------+-------------+-------------+-----------------+
| Capabilities | NTT Japan | University | Zhejiang |
| | | of Patras | Gongshang |
| | | | University |
+---------------------+-------------+-------------+-----------------+
| SupportableVersions | Implemented | Implemented | Implemented |
| | | | |
| HACapabilities | Implemented | Implemented | Will Implement |
+---------------------+-------------+-------------+-----------------+
Capabilities Supported
支持的功能
+---------------+------------+----------------+---------------------+
| Events | NTT Japan | University of | Zhejiang Gongshang |
| | | Patras | University |
+---------------+------------+----------------+---------------------+
| PrimaryCEDown | Will | Will Implement | Will Implement |
| | Implement | | |
+---------------+------------+----------------+---------------------+
+---------------+------------+----------------+---------------------+
| Events | NTT Japan | University of | Zhejiang Gongshang |
| | | Patras | University |
+---------------+------------+----------------+---------------------+
| PrimaryCEDown | Will | Will Implement | Will Implement |
| | Implement | | |
+---------------+------------+----------------+---------------------+
Events Supported
支持的事件
+--------------------------+-------------+-------------+-------------+
| Object Datatypes | NTT Japan | University | Zhejiang |
| | | of Patras | Gongshang |
| | | | University |
+--------------------------+-------------+-------------+-------------+
| LFBAdjacencyLimitType | Implemented | Implemented | Implemented |
| | | | |
| PortGroupLimitType | Implemented | Implemented | Implemented |
| | | | |
| SupportedLFBType | Implemented | Implemented | Implemented |
| | | | |
| FEStateValues | Implemented | Implemented | Implemented |
| | | | |
| FEConfiguredNeighborType | Implemented | Implemented | Implemented |
| | | | |
| LFBSelectorType | Implemented | Implemented | Implemented |
| | | | |
| LFBLinkType | Implemented | Implemented | Implemented |
+--------------------------+-------------+-------------+-------------+
+--------------------------+-------------+-------------+-------------+
| Object Datatypes | NTT Japan | University | Zhejiang |
| | | of Patras | Gongshang |
| | | | University |
+--------------------------+-------------+-------------+-------------+
| LFBAdjacencyLimitType | Implemented | Implemented | Implemented |
| | | | |
| PortGroupLimitType | Implemented | Implemented | Implemented |
| | | | |
| SupportedLFBType | Implemented | Implemented | Implemented |
| | | | |
| FEStateValues | Implemented | Implemented | Implemented |
| | | | |
| FEConfiguredNeighborType | Implemented | Implemented | Implemented |
| | | | |
| LFBSelectorType | Implemented | Implemented | Implemented |
| | | | |
| LFBLinkType | Implemented | Implemented | Implemented |
+--------------------------+-------------+-------------+-------------+
FE Object LFB Datatypes
FE对象LFB数据类型
+--------------+-------------+----------------+---------------------+
| Object | NTT Japan | University of | Zhejiang Gongshang |
| Components | | Patras | University |
+--------------+-------------+----------------+---------------------+
| LFBTopology | Implemented | Implemented | Implemented |
| | | | |
| LFBSelectors | Implemented | Implemented | Implemented |
| | | | |
| FEName | Implemented | Implemented | Implemented |
| | | | |
| FEID | Implemented | Implemented | Implemented |
| | | | |
| FEVendor | Implemented | Implemented | Implemented |
| | | | |
| FEModel | Implemented | Implemented | Implemented |
| | | | |
| FEState | Implemented | Implemented | Implemented |
| | | | |
| FENeighbors | Implemented | Implemented | Implemented |
+--------------+-------------+----------------+---------------------+
+--------------+-------------+----------------+---------------------+
| Object | NTT Japan | University of | Zhejiang Gongshang |
| Components | | Patras | University |
+--------------+-------------+----------------+---------------------+
| LFBTopology | Implemented | Implemented | Implemented |
| | | | |
| LFBSelectors | Implemented | Implemented | Implemented |
| | | | |
| FEName | Implemented | Implemented | Implemented |
| | | | |
| FEID | Implemented | Implemented | Implemented |
| | | | |
| FEVendor | Implemented | Implemented | Implemented |
| | | | |
| FEModel | Implemented | Implemented | Implemented |
| | | | |
| FEState | Implemented | Implemented | Implemented |
| | | | |
| FENeighbors | Implemented | Implemented | Implemented |
+--------------+-------------+----------------+---------------------+
FE Object LFB Components
FE对象LFB组件
+-----------------------+-------------+-------------+---------------+
| Capabilities | NTT Japan | University | Zhejiang |
| | | of Patras | Gongshang |
| | | | University |
+-----------------------+-------------+-------------+---------------+
| ModifiableLFBTopology | Implemented | Implemented | Implemented |
| | | | |
| SupportedLFBs | Implemented | Implemented | Implemented |
+-----------------------+-------------+-------------+---------------+
+-----------------------+-------------+-------------+---------------+
| Capabilities | NTT Japan | University | Zhejiang |
| | | of Patras | Gongshang |
| | | | University |
+-----------------------+-------------+-------------+---------------+
| ModifiableLFBTopology | Implemented | Implemented | Implemented |
| | | | |
| SupportedLFBs | Implemented | Implemented | Implemented |
+-----------------------+-------------+-------------+---------------+
Capabilities Supported
支持的功能
+----------------+-------------+---------------+--------------------+
| Port | NTT Japan | University of | Zhejiang Gongshang |
| | | Patras | University |
+----------------+-------------+---------------+--------------------+
| High priority | Implemented | Implemented | Implemented |
| (6700) | | | |
| | | | |
| Medium | Implemented | Implemented | Implemented |
| priority | | | |
| (6701) | | | |
| | | | |
| Low priority | Implemented | Implemented | Implemented |
| (6702) | | | |
+----------------+-------------+---------------+--------------------+
+----------------+-------------+---------------+--------------------+
| Port | NTT Japan | University of | Zhejiang Gongshang |
| | | Patras | University |
+----------------+-------------+---------------+--------------------+
| High priority | Implemented | Implemented | Implemented |
| (6700) | | | |
| | | | |
| Medium | Implemented | Implemented | Implemented |
| priority | | | |
| (6701) | | | |
| | | | |
| Low priority | Implemented | Implemented | Implemented |
| (6702) | | | |
+----------------+-------------+---------------+--------------------+
Priority Ports
优先端口
+------------------+-------------+---------------+------------------+
| ForCES Message | NTT Japan | University of | Zhejiang |
| | | Patras | Gongshang |
| | | | University |
+------------------+-------------+---------------+------------------+
| Association | Implemented | Implemented | Implemented |
| Setup | | | |
| | | | |
| Association | Implemented | Implemented | Implemented |
| Setup Response | | | |
| | | | |
| Association | Implemented | Implemented | Implemented |
| Teardown | | | |
| | | | |
| Config | Implemented | Implemented | Implemented |
| | | | |
| Config Response | Implemented | Implemented | Implemented |
| | | | |
| Query | Implemented | Implemented | Implemented |
| | | | |
| Query Response | Implemented | Implemented | Implemented |
+------------------+-------------+---------------+------------------+
+------------------+-------------+---------------+------------------+
| ForCES Message | NTT Japan | University of | Zhejiang |
| | | Patras | Gongshang |
| | | | University |
+------------------+-------------+---------------+------------------+
| Association | Implemented | Implemented | Implemented |
| Setup | | | |
| | | | |
| Association | Implemented | Implemented | Implemented |
| Setup Response | | | |
| | | | |
| Association | Implemented | Implemented | Implemented |
| Teardown | | | |
| | | | |
| Config | Implemented | Implemented | Implemented |
| | | | |
| Config Response | Implemented | Implemented | Implemented |
| | | | |
| Query | Implemented | Implemented | Implemented |
| | | | |
| Query Response | Implemented | Implemented | Implemented |
+------------------+-------------+---------------+------------------+
Message Handling at High-Priority (6700) Port
高优先级（6700）端口的消息处理
+---------------+-------------+----------------+--------------------+
| ForCES | NTT Japan | University of | Zhejiang Gongshang |
| Message | | Patras | University |
+---------------+-------------+----------------+--------------------+
| Event | Implemented | Implemented | Implemented |
| Notification | | | |
+---------------+-------------+----------------+--------------------+
+---------------+-------------+----------------+--------------------+
| ForCES | NTT Japan | University of | Zhejiang Gongshang |
| Message | | Patras | University |
+---------------+-------------+----------------+--------------------+
| Event | Implemented | Implemented | Implemented |
| Notification | | | |
+---------------+-------------+----------------+--------------------+
Message Handling at Medium-Priority (6701) Port
中等优先级（6701）端口的消息处理
+-------------+-------------+-----------------+---------------------+
| ForCES | NTT Japan | University of | Zhejiang Gongshang |
| Message | | Patras | University |
+-------------+-------------+-----------------+---------------------+
| Packet | Implemented | Implemented | Implemented |
| Redirect | | | |
| | | | |
| Heartbeat | Implemented | Implemented | Implemented |
+-------------+-------------+-----------------+---------------------+
+-------------+-------------+-----------------+---------------------+
| ForCES | NTT Japan | University of | Zhejiang Gongshang |
| Message | | Patras | University |
+-------------+-------------+-----------------+---------------------+
| Packet | Implemented | Implemented | Implemented |
| Redirect | | | |
| | | | |
| Heartbeat | Implemented | Implemented | Implemented |
+-------------+-------------+-----------------+---------------------+
Message Handling at Low-Priority (6702) Port
低优先级（6702）端口的消息处理
+--------------+------------+-----------------+---------------------+
| Security | NTT Japan | University of | Zhejiang Gongshang |
| Feature | | Patras | University |
+--------------+------------+-----------------+---------------------+
| IPsec | Will | Will Implement | Will Implement |
| | Implement | | |
+--------------+------------+-----------------+---------------------+
+--------------+------------+-----------------+---------------------+
| Security | NTT Japan | University of | Zhejiang Gongshang |
| Feature | | Patras | University |
+--------------+------------+-----------------+---------------------+
| IPsec | Will | Will Implement | Will Implement |
| | Implement | | |
+--------------+------------+-----------------+---------------------+
Security Feature Support
安全功能支持
The interoperability test took place at the University of Patras, in the Department of Electrical and Computer Engineering.
互操作性测试在佩特雷大学电气和计算机工程系进行。
There were two options for participation in the interoperability test.
参与互操作性测试有两种选择。
1. Locally, on the University of Patras premises.
1. 当地，在佩特雷大学校舍。
2. Remotely, via Internet.
2. 远程，通过互联网。
Implementations from NTT and the University of Patras were present locally on the University of Patras premises in Greece, while the implementation from Zhejiang Gongshang University, which was behind a NAT, connected remotely from China.
NTT和佩特雷大学的实施是在希腊的佩特雷大学校舍本地进行的，而来自NATT的浙江工商大学的实施则与中国远程连接。
The interoperability test validated the basic functionality of the ForCES protocol, mainly message exchanging and handling.
互操作性测试验证了ForCES协议的基本功能，主要是消息交换和处理。
The following scenarios were tested.
测试了以下场景。
The main goal of the interoperability test was to validate the basic protocol functionality; the test parameters were limited.
互操作性测试的主要目标是验证基本协议功能；试验参数有限。
1. In the Association Setup message, all report messages were ignored.
1. 在关联设置消息中，忽略了所有报告消息。
2. In the Association Setup stage, the FEO OperEnable Event (FE to CE), Config FEO Adminup (CE to FE), and FEO Config-Resp (FE to CE) messages were ignored. The CEs assumed that the FEs were enabled once the LFB selectors had been queried.
2. 在关联设置阶段，忽略了FEO OperEnable事件（FE到CE）、配置FEO Adminup（CE到FE）和FEO配置Resp（FE到CE）消息。CEs假设一旦查询LFB选择器，FEs即被启用。
3. Only FULLDATA-TLVs were used and not SPARSEDATA-TLVs.
3. 仅使用FULLDATA TLV，未使用SPARA TLV。
4. There were no transaction operations.
4. 没有任何事务操作。
5. Each message had only one LFBSelect-TLV, one OPER-TLV, and one PATH-DATA-TLV per message when these were used.
5. 使用时，每条消息只有一个LFBSelect TLV、一个OPER-TLV和一个PATH-DATA-TLV。
While the pre-association setup is not in the ForCES current scope, it is an essential step before CEs and FEs communicate. As the first part in a successful CE-FE connection, the participating CEs and FEs had to be configurable.
虽然预关联设置不在ForCES当前范围内，但在CEs和FEs通信之前，这是一个必不可少的步骤。作为成功CE-FE连接的第一部分，参与的CE和FEs必须是可配置的。
In the pre-association phase, the following configuration items were set up regarding the CEs:
在预关联阶段，针对CEs设置了以下配置项：
o The CE ID.
o 行政长官身份证。
o The FE IDs that were connected to this CE.
o 连接到此CE的FE ID。
o The IP addresses of the FEs that connected to the CE.
o 连接到CE的FEs的IP地址。
o The TML priority ports.
o TML优先级端口。
In the pre-association phase, the following configuration items were set up regarding the FEs:
在预关联阶段，针对FEs设置了以下配置项：
o The FE ID.
o FE ID。
o The CE ID to which this FE was connecting.
o 此FE连接到的CE ID。
o The IP address of the CE to which this FE was connecting.
o 此FE连接到的CE的IP地址。
o The TML priority ports.
o TML优先级端口。
For the interoperability test, the SCTP was used as TML. The TML connection with the associating element was needed for Scenario 2 to be successful.
对于互操作性测试，SCTP被用作TML。场景2的成功需要TML与关联元素的连接。
SCTP TML [RFC5811] defines three priority channels, with specific ports:
SCTP TML[RFC5811]定义了三个具有特定端口的优先级通道：
o High priority - Port number: 6704
o 高优先级-端口号：6704
o Medium priority - Port number: 6705
o 中等优先级-端口号：6705
o Lower priority - Port number: 6706
o 低优先级-端口号：6706
However, at the time of the interoperability test, the SCTP ports of the three priority channels were the following:
然而，在互操作性测试时，三个优先通道的SCTP端口如下所示：
o High priority - Port number: 6700
o 高优先级-端口号：6700
o Medium priority - Port number: 6701
o 中等优先级-端口号：6701
o Lower priority - Port number: 6702
o 低优先级-端口号：6702
As specified in Section 5, "Exceptions", this does not invalidate the results of the interoperability test.
如第5节“例外情况”所述，这不会使互操作性测试的结果无效。
Once the pre-association phase in the previous two scenarios had completed, CEs and FEs would be ready to communicate using the ForCES protocol and enter the Association Setup stage. In this stage, the FEs would attempt to join the NE. The following ForCES protocol messages would be exchanged for each CE-FE pair in the specified order:
一旦前两个场景中的预关联阶段完成，CEs和FEs将准备好使用ForCES协议进行通信，并进入关联设置阶段。在此阶段，FEs将尝试加入NE。以下强制协议消息将按指定顺序为每个CE-FE对交换：
o Association Setup message (from FE to CE)
o 关联设置消息（从FE到CE）
o Association Setup Response message (from CE to FE)
o 关联设置响应消息（从CE到FE）
o Query message: FEO LFB selectors (from CE to FE)
o 查询消息：FEO LFB选择器（从CE到FE）
o Query Response: FEO LFB selectors response (from FE to CE)
o 查询响应：FEO LFB选择器响应（从FE到CE）
Once the Association Setup stage had completed, the FEs and CEs would enter the Established stage. In this stage, the FE will be continuously updated or queried. The CE should query the FE for a specific value from the FE Object LFB and from the FE Protocol LFB. An example from the FE Protocol LFB is the FE Heartbeat Interval (FEHI), and an example from the FE Object LFB is the state of the LFB (FEState).
一旦关联建立阶段完成，FEs和CEs将进入建立阶段。在此阶段，FE将不断更新或查询。CE应向FE查询FE对象LFB和FE协议LFB中的特定值。FE协议LFB的一个示例是FE心跳间隔（FEHI），FE对象LFB的一个示例是LFB的状态（FEState）。
The following ForCES protocol messages were exchanged:
交换了以下部队协议消息：
o Query message
o 查询消息
o Query Response message
o 查询响应消息
The Heartbeat (HB) message is used for one ForCES element (FE or CE) to asynchronously notify one or more other ForCES elements in the same ForCES NE of its liveness. The default configuration of the Heartbeat Policy of the FE is set to 0, which means that the FE should not generate any Heartbeat messages. The CE is responsible for checking FE liveness by setting the PL header ACK flag of the message it sends to AlwaysACK. In this scenario, the CE will send a Heartbeat message with the ACK flag set to AlwaysACK, and the FE should respond.
Heartbeat（HB）消息用于一个ForCES元素（FE或CE）异步通知同一ForCES NE中的一个或多个其他ForCES元素其活动性。FE检测信号策略的默认配置设置为0，这意味着FE不应生成任何检测信号消息。CE负责通过设置发送给AlwaysACK的消息的PL报头ACK标志来检查FE活动性。在这种情况下，CE将发送一条心跳消息，ACK标志设置为AlwaysACK，FE应作出响应。
The following type of ForCES protocol message was exchanged:
交换了以下类型的ForCES协议消息：
o Heartbeat message
o 心跳信息
A Config message is sent by the CE to the FE to configure LFB components in the FE. A simple Config command, easily visible and metered, would be to change the Heartbeat configuration. This was done in two steps:
CE向FE发送配置消息，以配置FE中的LFB组件。一个简单的配置命令，很容易看到和计量，将是改变心跳配置。这是通过两个步骤完成的：
1. Change the FE Heartbeat Policy (FEHBPolicy) to value 1, to force the FE to send heartbeats.
1. 将FE心跳策略（FEHBPolicy）更改为值1，以强制FE发送心跳。
2. After some heartbeats from the FE, the FE Heartbeat Interval (FEHI) was changed.
2. 在FE发出一些心跳后，FE心跳间隔（FEHI）发生变化。
The following ForCES protocol messages were exchanged:
交换了以下部队协议消息：
o Config message
o 配置消息
o Config Response message
o 配置响应消息
In the end, the association must be terminated. There were three scenarios by which the association was terminated:
最后，必须终止这种联系。有三种情况终止了关联：
1. Normal teardown, by exchanging an Association Teardown message.
1. 正常拆卸，通过交换关联拆卸消息。
2. Irregular teardown, by stopping heartbeats from an FE or a CE.
2. 通过停止FE或CE的心跳来进行不规则的撕裂。
3. Irregular teardown, by externally shutting down/rebooting an FE or a CE.
3. 通过外部关闭/重新启动FE或CE进行不规则拆卸。
All scenarios were investigated in the interoperability test.
在互操作性测试中调查了所有场景。
The following type of ForCES protocol message was exchanged:
交换了以下类型的ForCES协议消息：
o Association Teardown message
o 关联拆卸消息
The features that were tested are:
测试的功能包括：
+----------------------------+
| Protocol Message |
+----------------------------+
| Association Setup |
| |
| Association Setup Response |
| |
| Association Teardown |
| |
| Config |
| |
| Config Response |
| |
| Query |
| |
| Query Response |
| |
| Heartbeat |
+----------------------------+
+----------------------------+
| Protocol Message |
+----------------------------+
| Association Setup |
| |
| Association Setup Response |
| |
| Association Teardown |
| |
| Config |
| |
| Config Response |
| |
| Query |
| |
| Query Response |
| |
| Heartbeat |
+----------------------------+
ForCES Protocol Messages
强制协议消息
o PASS: All implementations handled the protocol messages, and all protocol analyzers captured them.
o 通过：所有实现都处理协议消息，所有协议分析器都捕获了它们。
+--------------------+
| Header Field |
+--------------------+
| Correlator |
| |
| ACK Indicator Flag |
| |
| Priority Flag |
+--------------------+
+--------------------+
| Header Field |
+--------------------+
| Correlator |
| |
| ACK Indicator Flag |
| |
| Priority Flag |
+--------------------+
MainHeader Handling
主收割台处理
o PASS: All implementations handled these main header flags, and all protocol analyzers captured them.
o 通过：所有实现都处理这些主要头标志，所有协议分析器都捕获了它们。
+---------------+
| TLV |
+---------------+
| ASResult-TLV |
| |
| ASTReason-TLV |
| |
| LFBSelect-TLV |
| |
| OPER-TLV |
| |
| PATH-DATA-TLV |
| |
| FULLDATA-TLV |
| |
| RESULT-TLV |
+---------------+
+---------------+
| TLV |
+---------------+
| ASResult-TLV |
| |
| ASTReason-TLV |
| |
| LFBSelect-TLV |
| |
| OPER-TLV |
| |
| PATH-DATA-TLV |
| |
| FULLDATA-TLV |
| |
| RESULT-TLV |
+---------------+
TLVs Supported
受支持的TLV
o PASS: All implementations handled these TLVs, and all protocol analyzers captured them.
o 通过：所有实现都处理这些TLV，所有协议分析器都捕获了它们。
+--------------+
| Operation |
+--------------+
| SET |
| |
| SET-RESPONSE |
| |
| GET |
| |
| GET-RESPONSE |
| |
| REPORT |
+--------------+
+--------------+
| Operation |
+--------------+
| SET |
| |
| SET-RESPONSE |
| |
| GET |
| |
| GET-RESPONSE |
| |
| REPORT |
+--------------+
Operation Types Supported
支持的操作类型
o PASS: All implementations handled these operations, and all protocol analyzers captured them.
o 通过：所有实现都处理了这些操作，所有协议分析器都捕获了它们。
+------------+
| Feature |
+------------+
| Batching |
| |
| Heartbeats |
+------------+
+------------+
| Feature |
+------------+
| Batching |
| |
| Heartbeats |
+------------+
ForCES Protocol Advanced Features
ForCES协议高级功能
Although batching was not initially intended to be tested, it was assessed during the interoperability test.
虽然最初并不打算测试批处理，但在互操作性测试期间对其进行了评估。
o PASS: Two implementations handled batching, and all handled heartbeats. The protocol analyzers captured both.
o 通过：两个实现处理了批处理，所有实现都处理了心跳。协议分析器捕捉到了这两种情况。
+-------------+
| Atomic Type |
+-------------+
| uchar |
| |
| uint32 |
+-------------+
+-------------+
| Atomic Type |
+-------------+
| uchar |
| |
| uint32 |
+-------------+
Basic Atomic Types Supported
支持的基本原子类型
o PASS: All implementations handled these basic atomic types.
o 通过：所有实现都处理这些基本原子类型。
+---------------+
| Compound Type |
+---------------+
| structs |
| |
| arrays |
+---------------+
+---------------+
| Compound Type |
+---------------+
| structs |
| |
| arrays |
+---------------+
Compound Types Supported
支持的复合类型
o PASS: All implementations handled these compound types.
o PASS：所有实现都处理这些复合类型。
+--------------------+
| Protocol Datatypes |
+--------------------+
| CEHBPolicy |
| |
| FEHBPolicy |
+--------------------+
+--------------------+
| Protocol Datatypes |
+--------------------+
| CEHBPolicy |
| |
| FEHBPolicy |
+--------------------+
FE Protocol LFB Datatypes
FE协议LFB数据类型
o PASS: All implementations handled these FE Protocol LFB datatypes.
o 通过：所有实现都处理这些FE协议LFB数据类型。
+---------------------+
| Protocol Components |
+---------------------+
| FEID |
| |
| CEHBPolicy |
| |
| CEHDI |
| |
| FEHBPolicy |
| |
| FEHI |
| |
| CEID |
+---------------------+
+---------------------+
| Protocol Components |
+---------------------+
| FEID |
| |
| CEHBPolicy |
| |
| CEHDI |
| |
| FEHBPolicy |
| |
| FEHI |
| |
| CEID |
+---------------------+
FE Protocol LFB Components
FE协议LFB组件
o PASS: All implementations handled these FE Protocol LFB components.
o 通过：所有实现都处理这些FE协议LFB组件。
+------------------+
| Object Datatypes |
+------------------+
| FEStateValues |
| |
| LFBSelectorType |
+------------------+
+------------------+
| Object Datatypes |
+------------------+
| FEStateValues |
| |
| LFBSelectorType |
+------------------+
FE Object LFB Datatypes
FE对象LFB数据类型
o PASS: All implementations handled these FE Object LFB datatypes.
o PASS：所有实现都处理这些FE对象LFB数据类型。
+-------------------+
| Object Components |
+-------------------+
| LFBSelectors |
| |
| FEState |
+-------------------+
+-------------------+
| Object Components |
+-------------------+
| LFBSelectors |
| |
| FEState |
+-------------------+
FE Object LFB Components
FE对象LFB组件
o PASS: All implementations handled these FE Object LFB components.
o 通过：所有实现都处理这些FE对象LFB组件。
+------------------------+
| Port |
+------------------------+
| High priority (6700) |
| |
| Medium priority (6701) |
| |
| Low priority (6702) |
+------------------------+
+------------------------+
| Port |
+------------------------+
| High priority (6700) |
| |
| Medium priority (6701) |
| |
| Low priority (6702) |
+------------------------+
Priority Ports
优先端口
o PASS: All implementations opened and connected to all the SCTP priority ports. The protocol analyzers captured all ports and their corresponding priority.
o 通过：所有实现均已打开并连接到所有SCTP优先级端口。协议分析器捕获所有端口及其相应的优先级。
+----------------------------+
| ForCES Message |
+----------------------------+
| Association Setup |
| |
| Association Setup Response |
| |
| Association Teardown |
| |
| Config |
| |
| Config Response |
| |
| Query |
| |
| Query Response |
+----------------------------+
+----------------------------+
| ForCES Message |
+----------------------------+
| Association Setup |
| |
| Association Setup Response |
| |
| Association Teardown |
| |
| Config |
| |
| Config Response |
| |
| Query |
| |
| Query Response |
+----------------------------+
Message Handling at High-Priority (6700) Port
高优先级（6700）端口的消息处理
o PASS: All implementations handled these messages at this SCTP priority port. The protocol analyzers captured these messages at this priority port.
o 通过：所有实现都在此SCTP优先级端口处理这些消息。协议分析器在此优先级端口捕获这些消息。
+----------------+
| ForCES Message |
+----------------+
| Heartbeats |
+----------------+
+----------------+
| ForCES Message |
+----------------+
| Heartbeats |
+----------------+
Message Handling at Low-Priority (6702) Port
低优先级（6702）端口的消息处理
o PASS: All implementations handled these messages at this SCTP priority port. The protocol analyzers captured these messages at this priority port.
o 通过：所有实现都在此SCTP优先级端口处理这些消息。协议分析器在此优先级端口捕获这些消息。
All implementations were found to be interoperable with each other.
所有的实现都可以相互操作。
All scenarios were tested successfully.
所有场景均已成功测试。
The following issues were found and dealt with.
发现并处理了以下问题。
1. Some messages were sent on the wrong priority channels. There were some ambiguities in the SCTP TML document regarding how to deal with such a situation. The possibilities were an FE response on the same (wrong) channel as a CE query; an FE response on the correctly documented channel for the message; or simply dropping the packet. This has been corrected by mandating the message-to-channel mapping to be a MUST in the SCTP TML document [RFC5811] before it was published as an RFC.
1. 某些消息在错误的优先级通道上发送。SCTP TML文件中关于如何处理这种情况存在一些模糊之处。可能是FE响应与CE查询在同一（错误）通道上；正确记录的信息通道上的FE响应；或者干脆丢弃数据包。在消息作为RFC发布之前，SCTP TML文档[RFC5811]中必须规定消息到通道的映射，从而纠正了这一问题。
2. At some point, a CE sent a Teardown message to the FE. The CE expected the FE to shut down the connection, and the FE waited for the CE to shut down the connection; both were then caught in a deadlock. This was a code bug and was fixed.
2. 在某个时刻，CE向FE发送了一条拆卸消息。CE期望FE关闭连接，FE等待CE关闭连接；两人随后陷入了僵局。这是一个代码错误，已修复。
3. Sometimes, only when the CE and FE were remote to each other (one being in China and another in Greece), the Association Setup message was not received by the CE side, and therefore an association never completed. This was not an implementation issue but rather a network issue. This issue was solved with the retransmission of the non-delivered messages.
3. 有时，只有当CE和FE彼此距离较远（一个在中国，另一个在希腊）时，CE方才收到关联设置消息，因此关联从未完成。这不是一个实施问题，而是一个网络问题。通过重新传输未传递的消息解决了此问题。
4. An implementation did not take into account that the padding in TLVs MUST NOT be included in the length of the TLV. This was a code bug and was fixed.
4. 一个实现没有考虑到TLV中的填充不能包含在TLV的长度中。这是一个代码错误，已修复。
5. The Execution Mode flag was set to Reserved by a CE and was not ignored by the FE. This was a code bug and was fixed.
5. 执行模式标志被CE设置为保留，FE不会忽略。这是一个代码错误，已修复。
6. After the FEHBPolicy was set to 1, the FE didn't send any heartbeats. This was a code bug and was fixed.
6. FEHBPolicy设置为1后，FE没有发送任何心跳。这是一个代码错误，已修复。
7. Some FEs sent heartbeats with the ACK flag set to a value other than NoACK. The CE responded. This was a code bug and was fixed.
7. 某些FEs发送的心跳将ACK标志设置为NoACK以外的值。行政长官回应。这是一个代码错误，已修复。
8. When a cable was disconnected, none of the TML implementations detected it. The association was eventually dropped due to heartbeat detection; this test was a success, but this is an implementation issue that implementors should keep in mind. This is an SCTP options issue. Nothing needed to be done.
8. 当电缆断开连接时，没有一个TML实现检测到它。由于心跳检测，该关联最终被删除；这个测试是成功的，但这是实现人员应该记住的一个实现问题。这是一个SCTP选项问题。没有什么需要做的。
9. A CE crashed due to unknown LFB selector values. This was a code bug and was fixed.
9. 由于LFB选择器值未知，CE崩溃。这是一个代码错误，已修复。
10. With the remote connection from China (which was behind a NAT) to Greece, there were a lot of ForCES packet retransmissions. The problem was that packets like heartbeats were retransmitted. This was an implementation issue regarding SCTP usage that implementors should keep in mind. The SCTP-PR option needed to be used. Nothing needed to be done.
10. 由于从中国（NAT背后的）到希腊的远程连接，有大量的数据包重传。问题是像心跳这样的数据包被重新传输。这是一个关于SCTP使用的实现问题，实现人员应该记住。需要使用SCTP-PR选项。没有什么需要做的。
The interoperability test went so well that an additional extended test was added to check for batching messages. This test was also done successfully.
互操作性测试进行得非常顺利，因此添加了一个额外的扩展测试来检查批处理消息。这项试验也成功地完成了。
The authors would like to give thanks to Professors Odysseas Koufopavlou and Spyros Denazis, and the Department of Electrical and Computer Engineering at the University of Patras, who hosted the ForCES interoperability test.
作者想感谢Odysseas Koufopavlou教授和Spyros Denazis教授以及佩特雷大学的电力与计算机工程系，他们主持了力互操作性测试。
The authors would also like to give thanks to Chuanhuang Li, Ming Gao, and other participants from Zhejiang Gongshang University, which connected remotely. This allowed the discovery of a series of issues that would have been uncaught otherwise.
作者还要感谢来自浙江工商大学的李传煌、高明和其他参与者远程连接。这使得一系列问题得以发现，否则这些问题本来是不可能解决的。
The authors would also like to thank Hideaki Iwata and Yoshinobu Morimoto of NTT Japan for participating locally at the interoperability test; as well as Hiroki Date and Hidefumi Otsuka, also of NTT Japan, for contributing to the interoperability test.
作者还要感谢日本NTT的岩田秀明（Hideaki Iwata）和森本吉彦（Yoshinobu Morimoto），感谢他们在本地参与互操作性测试；以及Hiroki Date和Hidefumi Otsuka，同样来自日本NTT，为互操作性测试做出了贡献。
Additionally, thanks are given to Xinping Wang for her help in writing the interoperability document and to Fenggen Jia for extending the Ethereal protocol analyzer.
此外，感谢王新平在编写互操作性文档方面的帮助，并感谢贾丰根对Ethereal协议分析器的扩展。
No security elements of the protocol or the SCTP TML [RFC5811] specification were tested.
未测试协议或SCTP TML[RFC5811]规范的安全元素。
The survey indicated that no security elements were implemented, but all participants indicated their intention to implement them.
调查表明，没有实施任何安全要素，但所有参与者都表示打算实施这些要素。
For security considerations regarding the ForCES protocol and SCTP TML, please see [RFC5810] and [RFC5811].
有关ForCES协议和SCTP TML的安全注意事项，请参阅[RFC5810]和[RFC5811]。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC5810] Doria, A., Hadi Salim, J., Haas, R., Khosravi, H., Wang, W., Dong, L., Gopal, R., and J. Halpern, "Forwarding and Control Element Separation (ForCES) Protocol Specification", RFC 5810, March 2010.
[RFC5810]Doria，A.，Hadi Salim，J.，Haas，R.，Khosravi，H.，Wang，W.，Dong，L.，Gopal，R.，和J.Halpern，“转发和控制元件分离（部队）协议规范”，RFC 58102010年3月。
[RFC5811] Hadi Salim, J. and K. Ogawa, "SCTP-Based Transport Mapping Layer (TML) for the Forwarding and Control Element Separation (ForCES) Protocol", RFC 5811, March 2010.
[RFC5811]Hadi Salim，J.和K.Ogawa，“转发和控制元素分离（ForCES）协议的基于SCTP的传输映射层（TML）”，RFC 58112010年3月。
[RFC5812] Halpern, J. and J. Hadi Salim, "Forwarding and Control Element Separation (ForCES) Forwarding Element Model", RFC 5812, March 2010.
[RFC5812]Halpern，J.和J.Hadi Salim，“转发和控制单元分离（部队）转发单元模型”，RFC 5812，2010年3月。
[RFC3654] Khosravi, H. and T. Anderson, "Requirements for Separation of IP Control and Forwarding", RFC 3654, November 2003.
[RFC3654]Khosravi，H.和T.Anderson，“IP控制和转发分离的要求”，RFC 3654，2003年11月。
[RFC3746] Yang, L., Dantu, R., Anderson, T., and R. Gopal, "Forwarding and Control Element Separation (ForCES) Framework", RFC 3746, April 2004.
[RFC3746]Yang，L.，Dantu，R.，Anderson，T.，和R.Gopal，“转发和控制单元分离（部队）框架”，RFC 37462004年4月。
[RFC5657] Dusseault, L. and R. Sparks, "Guidance on Interoperation and Implementation Reports for Advancement to Draft Standard", BCP 9, RFC 5657, September 2009.
[RFC5657]Dusseault，L.和R.Sparks，“推进标准草案的互操作和实施报告指南”，BCP 9，RFC 5657，2009年9月。
[ethereal] "Ethereal is a protocol analyzer. The specific Ethereal that was used is an updated Ethereal, by Fenggen Jia, that can analyze and decode the ForCES protocol messages", <http://www.ietf.org/mail-archive/web/forces/ current/msg03687.html>.
[ethereal]“ethereal是一个协议分析器。使用的特定ethereal是一个更新的ethereal，由Fenggen Jia提供，可以分析和解码ForCES协议消息”<http://www.ietf.org/mail-archive/web/forces/ 当前/msg03687.html>。
[tcpdump] "tcpdump is a Linux protocol analyzer. The specific tcpdump that was used is a modified tcpdump, by Jamal Hadi Salim, that can analyze and decode the ForCES protocol messages", <http://www.ietf.org/mail-archive/ web/forces/current/msg03811.html>.
[tcpdump]“tcpdump是一个Linux协议分析器。所使用的特定tcpdump是由Jamal Hadi Salim修改的tcpdump，它可以分析和解码ForCES协议消息”<http://www.ietf.org/mail-archive/ web/forces/current/msg03811.html>。
Authors' Addresses
作者地址
Evangelos Haleplidis University of Patras Patras Greece
帕特雷佩特雷大学
EMail: ehalep@ece.upatras.gr
EMail: ehalep@ece.upatras.gr
Kentaro Ogawa NTT Corporation Tokyo Japan
日本东京小川健太郎NTT公司
EMail: ogawa.kentaro@lab.ntt.co.jp
EMail: ogawa.kentaro@lab.ntt.co.jp
Weiming Wang Zhejiang Gongshang University 18, Xuezheng Str., Xiasha University Town Hangzhou, 310018 P.R. China
王卫明浙江工商大学中国杭州下沙大学城学政街18号，邮编310018
Phone: +86-571-28877721
EMail: wmwang@mail.zjgsu.edu.cn
Phone: +86-571-28877721
EMail: wmwang@mail.zjgsu.edu.cn
Jamal Hadi Salim Mojatatu Networks Ottawa, Ontario Canada
加拿大安大略省渥太华Jamal Hadi Salim Mojatatu Networks
Phone: EMail: hadi@mojatatu.com
电话：电邮：hadi@mojatatu.com