Network Working Group G. Klyne
Request for Comments: 3342 Clearswift Corporation
Category: Standards Track M. Rose
Dover Beach Consulting, Inc.
M. Schwartz
Code On The Road, LLC
E. Dixon
H. Franklin
J. Kint
D. New
S. Pead
July 2002
Network Working Group G. Klyne
Request for Comments: 3342 Clearswift Corporation
Category: Standards Track M. Rose
Dover Beach Consulting, Inc.
M. Schwartz
Code On The Road, LLC
E. Dixon
H. Franklin
J. Kint
D. New
S. Pead
July 2002
The Application Exchange (APEX) Option Party Pack, Part Deux!
应用程序交换（APEX）选项党包，部分双份！
Status of this Memo
本备忘录的状况
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2002). All Rights Reserved.
版权所有（C）互联网协会（2002年）。版权所有。
Abstract
摘要
Application Exchange (APEX), at its core, provides a best-effort application-layer datagram service. Options are used to alter the semantics of the core service. This memo defines various options to change the default behavior of APEX's "relaying mesh".
应用程序交换（APEX）的核心是提供尽力而为的应用程序层数据报服务。选项用于更改核心服务的语义。此备忘录定义了各种选项，以更改APEX的“中继网格”的默认行为。
Table of Contents
目录
1. The attachOverride Option . . . . . . . . . . . . . . . . . 2
2. The dataTiming Option . . . . . . . . . . . . . . . . . . . 3
2.1 Upper-Bounds on Delivery . . . . . . . . . . . . . . . . . . 4
2.1.1 Final Hop Report . . . . . . . . . . . . . . . . . . . . . . 5
2.1.2 Timing Error Report . . . . . . . . . . . . . . . . . . . . 7
2.2 Reporting on Delayed Delivery . . . . . . . . . . . . . . . 8
2.2.1 Transient Timing Report . . . . . . . . . . . . . . . . . . 9
3. The hold4Endpoint Option . . . . . . . . . . . . . . . . . . 10
4. The dataHopping Option . . . . . . . . . . . . . . . . . . . 13
5. Initial Registrations . . . . . . . . . . . . . . . . . . . 15
5.1 Registration: The attachOverride Option . . . . . . . . . . 15
5.2 Registration: The dataTiming Option . . . . . . . . . . . . 16
5.3 Registration: The hold4Endpoint Option . . . . . . . . . . . 16
5.4 Registration: The dataHopping Option . . . . . . . . . . . . 16
6. The APEX Party Pack DTD . . . . . . . . . . . . . . . . . . 17
7. Security Considerations . . . . . . . . . . . . . . . . . . 18
References . . . . . . . . . . . . . . . . . . . . . . . . . 18
A. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19
B. IANA Considerations . . . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 20
Full Copyright Statement . . . . . . . . . . . . . . . . . . 22
1. The attachOverride Option . . . . . . . . . . . . . . . . . 2
2. The dataTiming Option . . . . . . . . . . . . . . . . . . . 3
2.1 Upper-Bounds on Delivery . . . . . . . . . . . . . . . . . . 4
2.1.1 Final Hop Report . . . . . . . . . . . . . . . . . . . . . . 5
2.1.2 Timing Error Report . . . . . . . . . . . . . . . . . . . . 7
2.2 Reporting on Delayed Delivery . . . . . . . . . . . . . . . 8
2.2.1 Transient Timing Report . . . . . . . . . . . . . . . . . . 9
3. The hold4Endpoint Option . . . . . . . . . . . . . . . . . . 10
4. The dataHopping Option . . . . . . . . . . . . . . . . . . . 13
5. Initial Registrations . . . . . . . . . . . . . . . . . . . 15
5.1 Registration: The attachOverride Option . . . . . . . . . . 15
5.2 Registration: The dataTiming Option . . . . . . . . . . . . 16
5.3 Registration: The hold4Endpoint Option . . . . . . . . . . . 16
5.4 Registration: The dataHopping Option . . . . . . . . . . . . 16
6. The APEX Party Pack DTD . . . . . . . . . . . . . . . . . . 17
7. Security Considerations . . . . . . . . . . . . . . . . . . 18
References . . . . . . . . . . . . . . . . . . . . . . . . . 18
A. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19
B. IANA Considerations . . . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 20
Full Copyright Statement . . . . . . . . . . . . . . . . . . 22
Section 5.1 contains the APEX option registration for the "attachOverride" option.
第5.1节包含“attachOverride”选项的APEX选项注册。
The default behavior of the APEX relaying mesh, in the absence of processing options, is to allow at most one application to attach as a particular endpoint, on a "first come, first served" basis. The "attachOverride" option provides gives preference to the current application trying to attach.
在没有处理选项的情况下，APEX中继网格的默认行为是允许最多一个应用程序作为特定端点“先到先得”地连接。“attachOverride”选项为尝试连接的当前应用程序提供优先权。
If this option is present in the "attach" operation (c.f., Section 4.4.1 of [1]) and if any application is already attached as the specified endpoint, that endpoint has its attachment terminated (c.f., Section 4.4.3 of [1]) concurrently with processing of that "attach" operation. The "code" attribute of the resulting "terminate" operation is set to 556.
如果此选项出现在“附加”操作中（c.f.，第4.4.1节[1]），并且如果任何应用程序已作为指定端点附加，则该端点在处理该“附加”操作的同时终止其附加（c.f.，第4.4.3节[1]）。结果“终止”操作的“代码”属性设置为556。
Note that any data being expected by the previously-attached application may instead be delivered to the last application to successfully attach. Accordingly, applications should take care to properly deal with incoming data having unrecognized transaction-identifiers (c.f., Section 6.1.1 of [1]).
请注意，以前连接的应用程序预期的任何数据可能会被传递到最后一个应用程序以成功连接。因此，应用程序应注意正确处理具有无法识别的事务标识符的传入数据（c.f.[1]第6.1.1节）。
This option provides for a new attachment to automatically terminate any existing attachment for the same endpoint. For example, this might be helpful when a new attachment is required from a different device while a previously-used device is still attached e.g.,
此选项提供一个新附件，用于自动终止同一端点的任何现有附件。例如，当以前使用的设备仍然连接时，需要从不同的设备连接新的附件时，这可能会有所帮助，例如。，
+-------+ +-------+
| | -- attach -----> | |
| appl. | | relay |
| #1 | <--------- ok -- | |
+-------+ +-------+
+-------+ +-------+
| | -- attach -----> | |
| appl. | | relay |
| #1 | <--------- ok -- | |
+-------+ +-------+
C: <attach endpoint='fred@example.com' transID='1' />
S: <ok />
C: <attach endpoint='fred@example.com' transID='1' />
S: <ok />
... some time later appl #2 starts on a different computer ...
... 一段时间后，appl#2在另一台计算机上启动。。。
+-------+ +-------+
| | <----- attach -- | |
+-------+ | | | appl. |
| | <-- terminate -- | relay | -- ok ---------> | #2 |
| appl. | | | +-------+
| #1 | -- ok ---------> | |
+-------+ +-------+
+-------+ +-------+
| | <----- attach -- | |
+-------+ | | | appl. |
| | <-- terminate -- | relay | -- ok ---------> | #2 |
| appl. | | | +-------+
| #1 | -- ok ---------> | |
+-------+ +-------+
C: <attach endpoint='fred@example.com' transID='2'>
<option internal='attachOverride' transID='3' />
</attach>
S: <ok />
C: <attach endpoint='fred@example.com' transID='2'>
<option internal='attachOverride' transID='3' />
</attach>
S: <ok />
C: <terminate transID='1' code='556'>overriden</terminate>
S: <ok />
C: <terminate transID='1' code='556'>overriden</terminate>
S: <ok />
Section 5.2 contains the APEX option registration for the "dataTiming" option. This option contains a "dataTiming" element (c.f., Section 6).
第5.2节包含“数据定时”选项的APEX选项注册。此选项包含“数据定时”元素（c.f.，第6节）。
The default behavior of the APEX relaying mesh is "immediate, best effort", and expects that all relays and endpoints are able to process and transfer data without delay -- in the absence of processing options, if a relay is unavailable, then data is silently dropped. The "dataTiming" option provides for controlled queuing delays in processing, whilst providing reasonable deterministic behavior for the originator.
APEX中继网格的默认行为是“立即、尽最大努力”，并期望所有中继和端点都能够毫不延迟地处理和传输数据——在没有处理选项的情况下，如果中继不可用，则数据会自动丢弃。“数据定时”选项在处理过程中提供受控排队延迟，同时为发起者提供合理的确定性行为。
There are two types of delays addressed by the "dataTiming" option:
“数据定时”选项可解决两种类型的延迟：
o delays in transit through the relaying mesh, possibly due to intermittent or slow connections, or congested relays; and,
o 通过中继网的传输延迟，可能是由于间歇性或慢速连接，或继电器堵塞；和
o delays because the intended endpoint is not available to receive the data, when used in conjunction with the hold4Endpoint option (Section 3).
o 延迟，因为当与hold4Endpoint选项（第3节）一起使用时，目标端点不可用于接收数据。
Accordingly, the "dataTiming" option allows for:
因此，“数据定时”选项允许：
o data to be discarded if not delivered within a finite amount of time as specified using the "noLaterThan" attribute (Section 2.1);
o 如果未在使用“noLaterThan”属性规定的有限时间内交付，则将丢弃数据（第2.1节）；
o a "statusResponse" message (c.f., Section 5.1 of [1]) to be generated if data is not delivered within a known amount of time as specified using the "reportAfter" attribute (Section 2.2); and,
o 如果在使用“reportAfter”属性（第2.2节）规定的已知时间内未交付数据，则生成“statusResponse”消息（c.f.[1]第5.1节）；和
o an upper limit on the amount of time for the "statusResponse" message to be delivered using the "returnTrip" attribute (Section 2.1.1), after which the sender may presume the message to be lost.
o 使用“returnTrip”属性（第2.1.1节）发送“statusResponse”消息的时间上限，在此之后，发送方可能会认为消息丢失。
This option does not provide any functionality with respect to the priority of the data. Nor does this option have any effect on other parts of the relaying process.
此选项不提供与数据优先级相关的任何功能。此选项对中继过程的其他部分也没有任何影响。
Further, note that because this option is processed on a per-hop basis, the originator must set the "targetHop" attribute to the value "all" and the "mustUnderstand" attribute to the value "true".
此外，请注意，由于此选项是按每跳处理的，因此发起者必须将“targettop”属性设置为值“all”，将“mustUnderstand”属性设置为值“true”。
The "noLaterThan" attribute of the "dataTiming" option provides for control over delays that may occur in transit through the relaying mesh or to the recipient endpoint.
“dataTiming”选项的“noLaterThan”属性提供了对通过中继网或到接收方端点的传输过程中可能发生的延迟的控制。
If this option is present in the "data" operation (c.f., Section 4.4.4 of [1]) and the value of the "noLaterThan" attribute is non-zero, then:
如果此选项出现在“数据”操作中（c.f.[1]第4.4.4节），且“noLaterThan”属性的值为非零，则：
o For Step 5.2 of Section 4.4.4.1 of [1]:
o [1]第4.4.4.1节第5.2步：
Immediately prior to sending the data to the next relay, the value of the "noLaterThan" attribute is adjusted to reflect the processing time of the data at the local relay (e.g., the time required to determine the next relay, to successfully issue a "bind" operation, and then be ready to immediately issue a "data" operation).
在将数据发送到下一个中继器之前，调整“noLaterThan”属性的值，以反映本地中继器上数据的处理时间（例如，确定下一个中继器、成功发出“绑定”操作、然后准备立即发出“数据”操作所需的时间）。
If the value of the "noLaterThan" attribute becomes less than or equal to zero, an error in processing has occurred, the data element is not sent to the next relay, and if the "reportErrors" attribute is true, the APEX report service is invoked to send a timing error report.
如果“noLaterThan”属性的值小于或等于零，则处理中发生错误，数据元素不会发送到下一个中继，如果“reportErrors”属性为true，则调用APEX报告服务以发送计时错误报告。
o For Step 5.3 of Section 4.4.4.1 of [1]:
o [1]第4.4.4.1节第5.3步：
If the relay does not receive an "ok" element from the recipient endpoint within the number of milli-seconds indicated by the value of the "noLaterThan" attribute, an error in processing has occurred, and if the "reportErrors" attribute is true, the APEX report service is invoked to send a timing error report.
如果中继在“noLaterThan”属性值指示的毫秒数内未从接收方端点接收到“ok”元素，则处理中发生错误，如果“reportErrors”属性为true，则调用APEX report service以发送计时错误报告。
Otherwise, if the data is successfully transmitted to the recipient, and the "returnTrip" attribute is non-zero, the APEX report service is invoked to send a final hop report.
否则，如果数据成功传输到收件人，并且“returnTrip”属性为非零，则调用APEX report服务以发送最终跃点报告。
Note that in some cases, a relay may be able to predict this outcome without actually connecting to the next relay; if so, a timing error report may be sent without connecting to the next relay.
注意，在某些情况下，继电器可能能够预测此结果，而无需实际连接到下一个继电器；如果是这样，则可能会在不连接下一个继电器的情况下发送定时错误报告。
If the APEX report service (c.f., Section 6.2 of [1]) is invoked to send a final hop report, it issues a data operation with:
如果调用APEX report service（c.f.[1]第6.2节）发送最终跃点报告，它将发出一个数据操作，其中包括：
o its originator identifying the report service associated with the issuing relay
o 其发起人标识与发布中继关联的报表服务
o its recipient identifying the endpoint address of the originator associated with the "dataTiming" option
o 其收件人标识与“数据定时”选项关联的发端人的端点地址
o a new "dataTiming" option having:
o 新的“数据定时”选项具有：
* its "noLaterThan" attribute equal to the "returnTrip" attribute of the original "dataTiming" option
* 其“noLaterThan”属性等于原始“dataTiming”选项的“returnTrip”属性
* and no other attributes present
* 没有其他属性存在
o its content consisting of a "statusResponse" element having:
o 其内容由“statusResponse”元素组成，该元素具有：
* its "transID" attribute equal to the "transID" attribute of the "dataTiming" option
* 其“transID”属性等于“dataTiming”选项的“transID”属性
* and identifying the original recipient with a permanent success indicator
* 以及用一个永久的成功指标来识别原始接收者
For example:
例如：
+-------+ +-------+
| | -- data -------> | |
| relay | | appl. |
| | <--------- ok -- | #2 |
+-------+ +-------+
+-------+ +-------+
| | -- data -------> | |
| relay | | appl. |
| | <--------- ok -- | #2 |
+-------+ +-------+
C: <data content='cid:1@example.com'>
<originator identity='fred@example.com' />
<recipient identity='barney@example.com' />
<option internal='dataTiming' targetHop='all'
mustUnderstand='true' transID='86'>
<dataTiming noLaterThan='10000' returnTrip='20000' />
</option>
</data>
S: <ok />
C: <data content='cid:1@example.com'>
<originator identity='fred@example.com' />
<recipient identity='barney@example.com' />
<option internal='dataTiming' targetHop='all'
mustUnderstand='true' transID='86'>
<dataTiming noLaterThan='10000' returnTrip='20000' />
</option>
</data>
S: <ok />
+-------+ +-------+
| | <------- data -- | |
| appl. | | relay |
| #1 | -- ok ---------> | |
+-------+ +-------+
+-------+ +-------+
| | <------- data -- | |
| appl. | | relay |
| #1 | -- ok ---------> | |
+-------+ +-------+
C: <data content='#Content'>
<originator identity='apex=report@example.com' />
<recipient identity='fred@example.com' />
<option internal='dataTiming' targetHop='all'
mustUnderstand='true' transID='99'>
<dataTiming noLaterThan='20000' />
</option>
<data-content Name='Content'>
<statusResponse transID='86'>
<destination identity='barney@example.com'>
<reply code='250' />
</destination>
</statusResponse>
</data-content>
</data>
S: <ok />
C: <data content='#Content'>
<originator identity='apex=report@example.com' />
<recipient identity='fred@example.com' />
<option internal='dataTiming' targetHop='all'
mustUnderstand='true' transID='99'>
<dataTiming noLaterThan='20000' />
</option>
<data-content Name='Content'>
<statusResponse transID='86'>
<destination identity='barney@example.com'>
<reply code='250' />
</destination>
</statusResponse>
</data-content>
</data>
S: <ok />
If the APEX report service (c.f., Section 6.2 of [1]) is invoked to send a timing error report, it issues a data operation with:
如果调用APEX report service（c.f.[1]第6.2节）发送计时错误报告，它将发出一个数据操作，其中包括：
o its originator identifying the report service associated with the issuing relay
o 其发起人标识与发布中继关联的报表服务
o its recipient identifying the endpoint address of the originator associated with the "dataTiming" option
o 其收件人标识与“数据定时”选项关联的发端人的端点地址
o its content consisting of a "statusResponse" element having:
o 其内容由“statusResponse”元素组成，该元素具有：
* its "transID" attribute equal to the "transID" attribute of the "dataTiming" option
* 其“transID”属性等于“dataTiming”选项的“transID”属性
* and identifying the original recipient with a permanent failure indicator
* 以及使用永久故障指示器识别原始接收者
For example:
例如：
+-------+ +-------+
| | -- data -------> | |
| appl. | | relay |
| | <--------- ok -- | |
+-------+ +-------+
+-------+ +-------+
| | -- data -------> | |
| appl. | | relay |
| | <--------- ok -- | |
+-------+ +-------+
C: <data content='cid:1@example.com'>
<originator identity='fred@example.com' />
<recipient identity='barney@example.com' />
<option internal='dataTiming' targetHop='all'
mustUnderstand='true' transID='86'>
<dataTiming noLaterThan='6000' reportErrors='true' />
</option>
</data>
S: <ok />
C: <data content='cid:1@example.com'>
<originator identity='fred@example.com' />
<recipient identity='barney@example.com' />
<option internal='dataTiming' targetHop='all'
mustUnderstand='true' transID='86'>
<dataTiming noLaterThan='6000' reportErrors='true' />
</option>
</data>
S: <ok />
... some time later ...
... 过了一段时间。。。
+-------+ +-------+
| | <------- data -- | |
| appl. | | relay |
| | -- ok ---------> | |
+-------+ +-------+
+-------+ +-------+
| | <------- data -- | |
| appl. | | relay |
| | -- ok ---------> | |
+-------+ +-------+
C: <data content='#Content'>
<originator identity='apex=report@example.com' />
<recipient identity='fred@example.com' />
<data-content Name='Content'>
<statusResponse transID='86'>
<destination identity='barney@example.com'>
<reply code='550' />
</destination>
</statusResponse>
</data-content>
</data>
S: <ok />
C: <data content='#Content'>
<originator identity='apex=report@example.com' />
<recipient identity='fred@example.com' />
<data-content Name='Content'>
<statusResponse transID='86'>
<destination identity='barney@example.com'>
<reply code='550' />
</destination>
</statusResponse>
</data-content>
</data>
S: <ok />
The "reportAfter" attribute of the "dataTiming" option provides for the originator to be notified if delivery is delayed beyond a specified time. Delivery of the data is not affected. Note that if the value of the "noLaterThan" attribute is non-zero, then it provides the operational upper-bounds for the "reportAfter" attribute.
“dataTiming”选项的“reportAfter”属性提供了在交付延迟超过指定时间时通知发起人的功能。数据的交付不受影响。请注意，如果“noLaterThan”属性的值非零，则它为“reportAfter”属性提供操作上限。
If this option is present in the "data" operation (c.f., Section 4.4.4 of [1]) and the value of the "reportAfter" attribute is non-zero, then:
如果此选项出现在“数据”操作中（c.f.[1]第4.4.4节），且“reportAfter”属性的值为非零，则：
o For Step 5.2 of Section 4.4.4.1 of [1]:
o [1]第4.4.4.1节第5.2步：
Immediately prior to sending the data to the next relay, the value of the "reportAfter" attribute is adjusted to reflect the processing time of the data at the local relay (e.g., the time required to determine the next relay, to successfully issue a "bind" operation, and then be ready to immediately issue a "data" operation).
在将数据发送到下一个中继器之前，调整“reportAfter”属性的值以反映本地中继器的数据处理时间（例如，确定下一个中继器、成功发出“绑定”操作、然后准备立即发出“数据”操作所需的时间）。
If the value of the "reportAfter" attribute becomes less than or equal to zero, then its value is set to zero and the APEX report service is invoked to send a transient timing report; regardless, the data element is sent to the next relay.
如果“reportAfter”属性的值小于或等于零，则将其值设置为零，并调用APEX report service发送临时计时报告；无论如何，数据元素被发送到下一个继电器。
o For Step 5.3 of Section 4.4.4.1 of [1]:
o [1]第4.4.4.1节第5.3步：
If the relay does not receive an "ok" element from the recipient endpoint within the number of milli-seconds indicated by the value of the "reportAfter" attribute, then its value is set to zero and the APEX report service is invoked to send a transient timing report.
如果中继在“reportAfter”属性的值指示的毫秒数内没有从接收方端点接收到“ok”元素，则其值设置为零，并调用APEX report service以发送临时计时报告。
If the APEX report service (c.f., Section 6.2 of [1]) is invoked to send a transient timing report, it issues a data operation with:
如果调用APEX report service（c.f.[1]第6.2节）来发送临时计时报告，它将发出一个数据操作，其中包括：
o its originator identifying the report service associated with the issuing relay
o 其发起人标识与发布中继关联的报表服务
o its recipient identifying the endpoint address of the originator associated with the "dataTiming" option
o 其收件人标识与“数据定时”选项关联的发端人的端点地址
o its content consisting of a "statusResponse" element having:
o 其内容由“statusResponse”元素组成，该元素具有：
* its "transID" attribute equal to the "transID" attribute of the "dataTiming" option
* 其“transID”属性等于“dataTiming”选项的“transID”属性
* and identifying the original recipient with a transient success indicator
* 以及用一个短暂的成功指示器来识别原始接收者
For example:
例如：
+-------+ +-------+
| | -- data -------> | |
| appl. | | relay |
| #1 | <--------- ok -- | |
+-------+ +-------+
+-------+ +-------+
| | -- data -------> | |
| appl. | | relay |
| #1 | <--------- ok -- | |
+-------+ +-------+
C: <data content='cid:1@example.com'>
<originator identity='fred@example.com' />
<recipient identity='barney@example.com' />
<option internal='dataTiming' targetHop='all'
mustUnderstand='true' transID='86'>
<dataTiming reportAfter='60000' />
</option>
</data>
S: <ok />
C: <data content='cid:1@example.com'>
<originator identity='fred@example.com' />
<recipient identity='barney@example.com' />
<option internal='dataTiming' targetHop='all'
mustUnderstand='true' transID='86'>
<dataTiming reportAfter='60000' />
</option>
</data>
S: <ok />
... some time later ...
... 过了一段时间。。。
+-------+ +-------+
| | <------- data -- | |
| relay | | relay |
| #n-1 | -- ok ---------> | #n |
+-------+ +-------+
+-------+ +-------+
| | <------- data -- | |
| relay | | relay |
| #n-1 | -- ok ---------> | #n |
+-------+ +-------+
C: <data content='#Content'>
<originator identity='apex=report@example.com' />
<recipient identity='fred@example.com' />
<data-content Name='Content'>
<statusResponse transID='86'>
<destination identity='barney@example.com'>
<reply code='350' />
</destination>
</statusResponse>
</data-content>
</data>
S: <ok />
C: <data content='#Content'>
<originator identity='apex=report@example.com' />
<recipient identity='fred@example.com' />
<data-content Name='Content'>
<statusResponse transID='86'>
<destination identity='barney@example.com'>
<reply code='350' />
</destination>
</statusResponse>
</data-content>
</data>
S: <ok />
Section 5.3 contains the APEX option registration for the "hold4Endpoint" option.
第5.3节包含“hold4Endpoint”选项的APEX选项注册。
The default behavior of the APEX relaying mesh, in the absence of processing options, is to silently drop data for a recipient if its endpoint isn't attached. The "hold4Endpoint" option provides for data to be queued if the recipient endpoint is not attached.
在没有处理选项的情况下，APEX中继网格的默认行为是，如果收件人的端点未连接，则自动删除收件人的数据。“hold4Endpoint”选项用于在未连接收件人端点的情况下对数据进行排队。
If this option is present in the "data" operation (c.f., Section 4.4.4 of [1]), and the value of the "hold4Endpoint" attribute is true then:
如果此选项出现在“数据”操作中（c.f.[1]第4.4.4节），且“hold4Endpoint”属性的值为真，则：
o For Step 5.3 of Section 4.4.4.1 of [1]:
o [1]第4.4.4.1节第5.3步：
If the recipient's endpoint is not currently attached, the relay will queue the data waiting for an application to attach as that endpoint.
如果收件人的端点当前未连接，则中继将对等待应用程序作为该端点连接的数据进行排队。
Note that in the absence of an upper-bounds on delivery, such as limits provided by the dataTiming option (Section 2), the data will be queued indefinitely for the endpoint.
请注意，在没有交付上限的情况下，例如dataTiming选项（第2节）提供的限制，数据将无限期地排队等待端点。
For example:
例如：
+-------+ +-------+
| | -- data -------> | |
| appl. | | relay |
| #1 | <--------- ok -- | |
+-------+ +-------+
+-------+ +-------+
| | -- data -------> | |
| appl. | | relay |
| #1 | <--------- ok -- | |
+-------+ +-------+
C: <data content='cid:1@example.com'>
<originator identity='fred@example.com' />
<recipient identity='barney@example.com' />
<option internal='hold4Endpoint' />
<option internal='dataTiming' targetHop='all'
mustUnderstand='true' transID='86'>
<dataTiming noLaterThan='60000' />
</option>
</data>
S: <ok />
C: <data content='cid:1@example.com'>
<originator identity='fred@example.com' />
<recipient identity='barney@example.com' />
<option internal='hold4Endpoint' />
<option internal='dataTiming' targetHop='all'
mustUnderstand='true' transID='86'>
<dataTiming noLaterThan='60000' />
</option>
</data>
S: <ok />
... some time later the recipient's endpoint attaches ...
... 一段时间后，收件人的端点连接。。。
+-------+ +-------+
| | <----- attach -- | |
| | | |
| | -- ok ---------> | |
| relay | | appl. |
| | -- data -------> | #2 |
| | | |
| | <--------- ok -- | |
+-------+ +-------+
+-------+ +-------+
| | <----- attach -- | |
| | | |
| | -- ok ---------> | |
| relay | | appl. |
| | -- data -------> | #2 |
| | | |
| | <--------- ok -- | |
+-------+ +-------+
C: <attach endpoint='barney@example.com' transID='2'>
<option internal='attachOverride' transID='3' />
</attach>
S: <ok />
C: <attach endpoint='barney@example.com' transID='2'>
<option internal='attachOverride' transID='3' />
</attach>
S: <ok />
C: <data content='cid:1@example.com'>
<originator identity='fred@example.com' />
<recipient identity='barney@example.com' />
<option internal='hold4Endpoint' />
<option internal='dataTiming' targetHop='all'
mustUnderstand='true' transID='86'>
<dataTiming noLaterThan='18000' />
</option>
</data>
S: <ok />
C: <data content='cid:1@example.com'>
<originator identity='fred@example.com' />
<recipient identity='barney@example.com' />
<option internal='hold4Endpoint' />
<option internal='dataTiming' targetHop='all'
mustUnderstand='true' transID='86'>
<dataTiming noLaterThan='18000' />
</option>
</data>
S: <ok />
To detect misconfigurations that cause forwarding loops in the APEX relaying mesh, the APEX pubsub service re-introduces a mechanism similar to the IP TTL [2] mechanism, in the form of an APEX option. Section 5.4 contains the APEX option registration for the "dataHopping" option.
为了检测导致APEX中继网中的转发循环的错误配置，APEX pubsub服务以APEX选项的形式重新引入了一种类似于IP TTL[2]机制的机制。第5.4节包含“数据跳变”选项的APEX选项注册。
If this option is present in the "data" operation (c.f., Section 4.4.4 of [1]) and the value of the "noMoreThan" attribute is non-zero, then:
如果此选项出现在“数据”操作中（c.f.[1]第4.4.4节），且“noMoreThan”属性的值为非零，则：
o For Step 5.2 of Section 4.4.4.1 of [1]:
o [1]第4.4.4.1节第5.2步：
Immediately prior to sending the data to the next relay, the value of the "noMoreThan" attribute is reduced by 1.
在将数据发送到下一个中继之前，“noMoreThan”属性的值将减少1。
If the value of the "noMoreThan" attribute becomes less than or equal to zero, an error in processing has occurred, the data element is not sent to the next relay, and if the "reportErrors" attribute is true, the APEX report service is invoked to send an error report.
如果“noMoreThan”属性的值小于或等于零，则处理过程中发生错误，数据元素不会发送到下一个中继，如果“reportErrors”属性为true，则调用APEX report service以发送错误报告。
Further, note that because this option is processed on a per-hop basis, the originator must set the "targetHop" attribute to the value "all" and the "mustUnderstand" attribute to the value "true".
此外，请注意，由于此选项是按每跳处理的，因此发起者必须将“targettop”属性设置为值“all”，将“mustUnderstand”属性设置为值“true”。
If the APEX report service (c.f., Section 6.2 of [1]) is invoked to send an error report, it issues a data operation with:
如果调用APEX report service（c.f.[1]第6.2节）来发送错误报告，它将发出一个数据操作，其中包括：
o its originator identifying the report service associated with the issuing relay
o 其发起人标识与发布中继关联的报表服务
o its recipient identifying the endpoint address of the originator associated with the "dataHopping" option
o 其收件人标识与“数据跳转”选项关联的发起人的端点地址
o its content consisting of a "statusResponse" element having:
o 其内容由“statusResponse”元素组成，该元素具有：
* its "transID" attribute equal to the "transID" attribute of the "dataHopping" option
* 其“transID”属性等于“dataHopping”选项的“transID”属性
* and identifying the original recipient with a permanent failure indicator
* 以及使用永久故障指示器识别原始接收者
For example:
例如：
+-------+ +-------+
| | -- data -------> | |
| appl. | | relay |
| | <--------- ok -- | #1 |
+-------+ +-------+
+-------+ +-------+
| | -- data -------> | |
| appl. | | relay |
| | <--------- ok -- | #1 |
+-------+ +-------+
C: <data content='cid:1@example.com'>
<originator identity='appl=pubsub/topic=fred@example.com' />
<recipient identity='barney@example.com' />
<option internal='dataHopping' targetHop='all'
mustUnderstand='true' transID='86'>
<dataHopping noMoreThan='2' reportErrors='true' />
</option>
</data>
S: <ok />
+-------+ +-------+
| | -- data -------> | |
| relay | | relay |
| #1 | <--------- ok -- | #2 |
+-------+ +-------+
C: <data content='cid:1@example.com'>
<originator identity='appl=pubsub/topic=fred@example.com' />
<recipient identity='barney@example.com' />
<option internal='dataHopping' targetHop='all'
mustUnderstand='true' transID='86'>
<dataHopping noMoreThan='2' reportErrors='true' />
</option>
</data>
S: <ok />
+-------+ +-------+
| | -- data -------> | |
| relay | | relay |
| #1 | <--------- ok -- | #2 |
+-------+ +-------+
C: <data content='cid:1@example.com'>
<originator identity='appl=pubsub/topic=fred@example.com' />
<recipient identity='barney@example.com' />
<option internal='dataHopping' targetHop='all'
mustUnderstand='true' transID='86'>
<dataHopping noMoreThan='1' reportErrors='true' />
</option>
</data>
S: <ok />
C: <data content='cid:1@example.com'>
<originator identity='appl=pubsub/topic=fred@example.com' />
<recipient identity='barney@example.com' />
<option internal='dataHopping' targetHop='all'
mustUnderstand='true' transID='86'>
<dataHopping noMoreThan='1' reportErrors='true' />
</option>
</data>
S: <ok />
relay #2 determines that further relaying is necessary:
继电器#2确定需要进一步的继电器：
+-------+ +-------+
| | <------- data -- | |
| relay | | relay |
| #1 | -- ok ---------> | #2 |
+-------+ +-------+
+-------+ +-------+
| | <------- data -- | |
| relay | | relay |
| #1 | -- ok ---------> | #2 |
+-------+ +-------+
C: <data content='#Content'>
<originator identity='apex=report@example.com' />
<recipient identity='appl=pubsub/topic=fred@example.com' />
<data-content Name='Content'>
<statusResponse transID='86'>
<destination identity='barney@example.com'>
<reply code='550' />
</destination>
</statusResponse>
</data-content>
</data>
S: <ok />
C: <data content='#Content'>
<originator identity='apex=report@example.com' />
<recipient identity='appl=pubsub/topic=fred@example.com' />
<data-content Name='Content'>
<statusResponse transID='86'>
<destination identity='barney@example.com'>
<reply code='550' />
</destination>
</statusResponse>
</data-content>
</data>
S: <ok />
The APEX option registration template is defined in Section 7.1 of [1].
[1]第7.1节定义了APEX期权注册模板。
Option Identification: attachOverride
选项标识：attachOverride
Present in: APEX's "attach" element
存在于：APEX的“附加”元素中
Contains: nothing
包含：无
Processing Rules: c.f., Section 1
处理规则：c.f.，第1节
Contact Information: c.f., the "Authors' Addresses" section of this memo
联系方式：c.f.，本备忘录的“作者地址”部分
Option Identification: dataTiming
选项标识：数据定时
Present in: APEX's "data" element
出现在：APEX的“数据”元素中
Contains: dataTiming (c.f., Section 6)
包含：数据定时（c.f.，第6节）
Processing Rules: c.f., Section 2
处理规则：c.f.，第2节
Contact Information: c.f., the "Authors' Addresses" section of this memo
联系方式：c.f.，本备忘录的“作者地址”部分
Option Identification: hold4Endpoint
选项标识：hold4Endpoint
Present in: APEX's "data" element
出现在：APEX的“数据”元素中
Contains: nothing
包含：无
Processing Rules: c.f., Section 3
处理规则：c.f.，第3节
Contact Information: c.f., the "Authors' Addresses" section of this memo
联系方式：c.f.，本备忘录的“作者地址”部分
Option Identification: dataHopping
选项标识：数据跳变
Present in: APEX's "data" element
出现在：APEX的“数据”元素中
Contains: dataHopping (c.f., Section 6)
包含：数据跳转（c.f.，第6节）
Processing Rules: c.f., Section 4
处理规则：c.f.，第4节
Contact Information: c.f., the "Authors' Addresses" section of this memo
联系方式：c.f.，本备忘录的“作者地址”部分
<!-- DTD for the APEX option party pack, as of 2001-05-14
<!-- 自2001年5月14日起，APEX选项派对套餐的DTD
Refer to this DTD as:
将此DTD称为：
<!ENTITY % APEXPARTY PUBLIC "-//IETF//DTD APEX PARTY//EN" "">
%APEXPARTY;
-->
<!ENTITY % APEXPARTY PUBLIC "-//IETF//DTD APEX PARTY//EN" "">
%APEXPARTY;
-->
<!ENTITY % APEXCORE PUBLIC "-//IETF//DTD APEX CORE//EN"
%APEXCORE;
<!ENTITY % APEXCORE PUBLIC "-//IETF//DTD APEX CORE//EN"
%APEXCORE;
<!-- DTD data types:
<!-- DTD数据类型：
entity syntax/reference example
====== ================ =======
hopcount
HOPS 0..255 17
entity syntax/reference example
====== ================ =======
hopcount
HOPS 0..255 17
milli-seconds MILLISECS 0..2147483647 60000 -->
毫秒毫秒0..2147483647 60000-->
<!ENTITY % HOPS "CDATA">
<!ENTITY % MILLISECS
"CDATA">
<!ENTITY % HOPS "CDATA">
<!ENTITY % MILLISECS
"CDATA">
<!ELEMENT dataHopping EMPTY>
<!ATTLIST dataHopping
noMoreThan %HOPS; "0"
reportErrors
(true|false) "false">
<!ELEMENT dataHopping EMPTY>
<!ATTLIST dataHopping
noMoreThan %HOPS; "0"
reportErrors
(true|false) "false">
<!ELEMENT dataTiming EMPTY>
<!ATTLIST dataTiming
noLaterThan %MILLISECS; "0"
returnTrip %MILLISECS; "0"
reportAfter %MILLISECS; "0"
reportErrors
(true|false) "false">
<!ELEMENT dataTiming EMPTY>
<!ATTLIST dataTiming
noLaterThan %MILLISECS; "0"
returnTrip %MILLISECS; "0"
reportAfter %MILLISECS; "0"
reportErrors
(true|false) "false">
Consult [1]'s Section 11 for a discussion of security issues.
有关安全问题的讨论，请参阅[1]的第11节。
In addition:
此外：
o The dataTiming option (Section 2) may be used to expose private network topology. Accordingly, an administrator may wish to choose to disable this option except at the ingress/egress points for its administrative domain.
o 数据定时选项（第2节）可用于公开专用网络拓扑。因此，除了在其管理域的入口/出口点之外，管理员可能希望选择禁用该选项。
o The hold4Endpoint option (Section 3) may be used to facilitate denial-of-service attacks. Accordingly, an administrator may wish to impose administrative limits on this attribute (e.g., always require that the "dataTiming" option also be present with a short-lived "noLaterThan" attribute).
o hold4Endpoint选项（第3节）可用于促进拒绝服务攻击。因此，管理员可能希望对该属性施加管理限制（例如，始终要求“dataTiming”选项也具有短期“noLaterThan”属性）。
References
工具书类
[1] Rose, M., Klyne, G. and D. Crocker, "The Application Exchange Core", RFC 3340, July 2002.
[1] Rose，M.，Klyne，G.和D.Crocker，“应用程序交换核心”，RFC3440，2002年7月。
[2] Postel, J., "Internet Protocol", STD 5, RFC 791, September 1981.
[2] Postel，J.，“互联网协议”，STD 5，RFC 7911981年9月。
[3] Newman, D., "Deliver By SMTP Service Extension", RFC 2852, June 2000.
[3] Newman，D.，“通过SMTP服务扩展交付”，RFC 2852，2000年6月。
The authors gratefully acknowledge the contributions of Chris Newman and Bob Wyman. Further, the dataTiming option is similar in function to "Deliver By" SMTP service extension defined by Dan Newman in [3].
作者衷心感谢Chris Newman和Bob Wyman的贡献。此外，dataTiming选项在功能上类似于Dan Newman在[3]中定义的“Deliver By”SMTP服务扩展。
The IANA completed the registrations specified in Section 5.
IANA完成了第5节规定的注册。
Authors' Addresses
作者地址
Graham Klyne Clearswift Corporation 1310 Waterside Arlington Business Park Theale, Reading RG7 4SA UK
Graham Klyne Clearwift Corporation 1310水边阿灵顿商业园Theale，Reading RG7 4SA UK
Phone: +44 11 8903 8903
EMail: Graham.Klyne@MIMEsweeper.com
Phone: +44 11 8903 8903
EMail: Graham.Klyne@MIMEsweeper.com
Marshall T. Rose Dover Beach Consulting, Inc. POB 255268 Sacramento, CA 95865-5268 US
马歇尔T.罗斯多佛海滩咨询公司POB 255268萨克拉门托，加利福尼亚州95865-5268美国
Phone: +1 916 483 8878
EMail: mrose@dbc.mtview.ca.us
Phone: +1 916 483 8878
EMail: mrose@dbc.mtview.ca.us
Michael F. Schwartz Code On The Road, LLC
Michael F.Schwartz Code On The Road，LLC
EMail: schwartz@CodeOnTheRoad.com
URI: http://www.CodeOnTheRoad.com
EMail: schwartz@CodeOnTheRoad.com
URI: http://www.CodeOnTheRoad.com
Eric Dixon
埃里克·迪克森
EMail: edixon@myrealbox.com
EMail: edixon@myrealbox.com
Huston Franklin
休斯顿富兰克林
EMail: huston@franklin.ro
EMail: huston@franklin.ro
Jay Kint
杰伊·金特
EMail: d20@icosahedron.org
EMail: d20@icosahedron.org
Darren New 5390 Caminito Exquisito San Diego, CA 92130 US
美国加利福尼亚州圣地亚哥Darren New 5390 Caminito Exquisito 92130
Phone: +1 858 350 9733
EMail: dnew@san.rr.com
Phone: +1 858 350 9733
EMail: dnew@san.rr.com
Scott Pead
斯科特·皮德
EMail: spead@fiber.net
EMail: spead@fiber.net
Full Copyright Statement
完整版权声明
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编辑功能的资金目前由互联网协会提供。