Internet Research Task Force (IRTF)                             K. Scott
Request for Comments: 7116                         The MITRE Corporation
Category: Informational                                      M. Blanchet
ISSN: 2070-1721                                                 Viagenie
                                                           February 2014
        
Internet Research Task Force (IRTF)                             K. Scott
Request for Comments: 7116                         The MITRE Corporation
Category: Informational                                      M. Blanchet
ISSN: 2070-1721                                                 Viagenie
                                                           February 2014
        

Licklider Transmission Protocol (LTP), Compressed Bundle Header Encoding (CBHE), and Bundle Protocol IANA Registries

利克利德传输协议(LTP)、压缩包头编码(CBHE)和包协议IANA注册表

Abstract

摘要

The DTNRG Research Group has defined the experimental Licklider Transmission Protocol (LTP) and the Compressed Bundle Header Encoding (CBHE) mechanism for the InterPlanetary Network ('ipn' URI scheme). Moreover, RFC 5050 defines values for the Bundle Protocol administrative record type. All of these fields are subject to a registry. For the purpose of its research work, the group has created ad hoc registries. As the specifications are stable and have multiple interoperable implementations, the group would like to hand off the registries to IANA for official management. This document describes the necessary IANA actions.

DTNRG研究小组已经为星际网络(“ipn”URI方案)定义了实验性的利克利德传输协议(LTP)和压缩束头编码(CBHE)机制。此外,RFC 5050定义捆绑协议管理记录类型的值。所有这些字段都受注册表约束。为了开展研究工作,专家组设立了特设登记处。由于规范是稳定的,并且有多个可互操作的实现,该集团希望将注册中心移交给IANA进行正式管理。本文件描述了必要的IANA措施。

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 Research Task Force (IRTF). The IRTF publishes the results of Internet-related research and development activities. These results might not be suitable for deployment. This RFC represents the consensus of the Delay-Tolerant Networking (DTNRG) Research Group of the Internet Research Task Force (IRTF). Documents approved for publication by the IRSG are not a candidate for any level of Internet Standard; see Section 2 of RFC 5741.

本文件是互联网研究工作组(IRTF)的产品。IRTF发布互联网相关研究和开发活动的结果。这些结果可能不适合部署。本RFC代表了互联网研究任务组(IRTF)的延迟容忍网络(DTNRG)研究小组的共识。IRSG批准发布的文件不适用于任何级别的互联网标准;见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/rfc7116.

有关本文件当前状态、任何勘误表以及如何提供反馈的信息,请访问http://www.rfc-editor.org/info/rfc7116.

Copyright Notice

版权公告

Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved.

版权所有(c)2014 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.

本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件,因为它们描述了您对本文件的权利和限制。

Table of Contents

目录

   1. Introduction ....................................................2
   2. Security Considerations .........................................3
   3. IANA Considerations .............................................3
      3.1. Licklider Transmission Protocol ............................3
           3.1.1. LTP Cancel Segment Reason Codes .....................3
           3.1.2. LTP Engine ID .......................................4
           3.1.3. LTP Client Service ID ...............................5
      3.2. Compressed Bundle Header Encoding ..........................6
           3.2.1. CBHE Node Numbers ...................................6
           3.2.2. CBHE Service Numbers ................................7
      3.3. Bundle Administrative Record Types .........................8
   4. Acknowledgements ................................................8
   5. References ......................................................9
      5.1. Normative References .......................................9
      5.2. Informative References .....................................9
        
   1. Introduction ....................................................2
   2. Security Considerations .........................................3
   3. IANA Considerations .............................................3
      3.1. Licklider Transmission Protocol ............................3
           3.1.1. LTP Cancel Segment Reason Codes .....................3
           3.1.2. LTP Engine ID .......................................4
           3.1.3. LTP Client Service ID ...............................5
      3.2. Compressed Bundle Header Encoding ..........................6
           3.2.1. CBHE Node Numbers ...................................6
           3.2.2. CBHE Service Numbers ................................7
      3.3. Bundle Administrative Record Types .........................8
   4. Acknowledgements ................................................8
   5. References ......................................................9
      5.1. Normative References .......................................9
      5.2. Informative References .....................................9
        
1. Introduction
1. 介绍

The DTNRG Research Group has defined the Licklider Transmission Protocol (LTP) [RFC5326]. LTP contains certain fields that are subject to a registry. For the purpose of its research work, the group has created ad hoc registries. As the specifications are stable and have multiple interoperable implementations, the group would like to hand off the registries to IANA for official management. This document describes the actions that IANA needs to take and uses the well-known IANA policy definitions as described in Section 4.1 of [RFC5226].

DTNRG研究小组定义了利克利德传输协议(LTP)[RFC5326]。LTP包含受注册表约束的某些字段。为了开展研究工作,专家组设立了特设登记处。由于规范是稳定的,并且有多个可互操作的实现,该集团希望将注册中心移交给IANA进行正式管理。本文件描述了IANA需要采取的行动,并使用了[RFC5226]第4.1节中所述的众所周知的IANA政策定义。

The Compressed Bundle Header Encoding (CBHE) [RFC6260] specification defines the concepts of 'Node Number' and 'Service Number' in the 'ipn' URI scheme. In this document, we request formation of IANA registries for these fields.

压缩包头编码(CBHE)[RFC6260]规范定义了“ipn”URI方案中“节点号”和“服务号”的概念。在本文件中,我们要求为这些领域建立IANA登记册。

Because of its association with space communication and the Consultative Committee for Space Data Systems [CCSDS], portions of the "CBHE Node Numbers", "CBHE Service Numbers", and "LTP Engine Numbers" spaces are delegated by this document to the CCSDS Space Assigned Numbers Authority [SANA]. SANA functions similarly to IANA in that it maintains registries of managed values, with a focus on values used by protocols used by CCSDS member agencies.

由于其与空间通信和空间数据系统咨询委员会[CCSDS]的关联,“CBHE节点号”、“CBHE服务号”和“LTP发动机号”空间的一部分由本文件委托给CCSDS空间分配号管理局[SANA]。SANA的功能与IANA类似,它维护托管值的注册,重点关注CCSDS成员机构使用的协议使用的值。

This document represents the consensus of the DTNRG. It has been discussed and reviewed by the research group and interested parties.

本文件代表了DTNRG的共识。研究小组和相关方已经对其进行了讨论和审查。

2. Security Considerations
2. 安全考虑

This document requests the creation of registries managed by IANA. There are no security issues involved. Refer to the Security Considerations section of [RFC5326] for security issues with LTP.

本文件要求创建IANA管理的注册中心。不涉及安全问题。有关LTP的安全问题,请参阅[RFC5326]的安全注意事项部分。

3. IANA Considerations
3. IANA考虑

IANA has created the registries described in this section.

IANA已经创建了本节所述的注册表。

3.1. Licklider Transmission Protocol
3.1. 利克利德传输协议

The Licklider Transmission Protocol has fields requiring registries managed by IANA. This document requests the creation of the three registries in this section and requests that they be associated with the other LTP registries.

Licklider传输协议具有需要IANA管理的注册表的字段。本文件要求在本节中创建三个注册中心,并要求它们与其他LTP注册中心相关联。

3.1.1. LTP Cancel Segment Reason Codes
3.1.1. LTP取消段原因代码

Section 3.2.4 of [RFC5326] defines the reason codes that may be present in Cancel Segments in LTP. IANA has set up a registry to manage the cancel reason codes. This registry, titled "LTP Cancel Segment Reason Codes", has been added to the list of registries associated with the Licklider Transmission Protocol.

[RFC5326]第3.2.4节定义了LTP中可能出现在取消段中的原因码。IANA已经建立了一个注册表来管理取消原因代码。该注册表名为“LTP取消段原因代码”,已添加到与Licklider传输协议相关的注册表列表中。

The registration policy for this registry is Specification Required.

此注册表的注册策略是必需的。

The initial values (as defined by RFC 5326) for the "LTP Cancel Segment Reason Codes" are:

“LTP取消段原因代码”的初始值(由RFC 5326定义)为:

      +-------+---------------------------------+---------------+
      | Value | Description                     | Reference     |
      +-------+---------------------------------+---------------+
      |   0   | Client service canceled session | [RFC5326]     |
      |   1   | Unreachable client service      | [RFC5326]     |
      |   2   | Retransmission limit exceeded   | [RFC5326]     |
      |   3   | Miscolored data received        | [RFC5326]     |
      |   4   | System error caused termination | [RFC5326]     |
      |   5   | Retransmission limit exceeded   | [RFC5326]     |
      | 6-255 | Unassigned                      | This document |
      +-------+---------------------------------+---------------+
        
      +-------+---------------------------------+---------------+
      | Value | Description                     | Reference     |
      +-------+---------------------------------+---------------+
      |   0   | Client service canceled session | [RFC5326]     |
      |   1   | Unreachable client service      | [RFC5326]     |
      |   2   | Retransmission limit exceeded   | [RFC5326]     |
      |   3   | Miscolored data received        | [RFC5326]     |
      |   4   | System error caused termination | [RFC5326]     |
      |   5   | Retransmission limit exceeded   | [RFC5326]     |
      | 6-255 | Unassigned                      | This document |
      +-------+---------------------------------+---------------+
        
3.1.2. LTP Engine ID
3.1.2. LTP引擎ID

The Licklider Transmission Protocol has an LTP Engine ID field (Section 2 of [RFC5326]). IANA has set up a registry to manage the Engine IDs. This registry, titled "LTP Engine Numbers", has been added to the list of registries associated with the Licklider Transmission Protocol.

利克利德传输协议有一个LTP引擎ID字段(RFC5326的第2节)。IANA已经建立了一个注册表来管理引擎ID。此名为“LTP引擎号”的注册表已添加到与Licklider传输协议相关的注册表列表中。

The registration policy for this registry is:

此注册表的注册策略为:

1 -- (2**14)-1 Expert Review required.

1--(2**14)-1需要专家评审。

(2**14) -- (2**21)-1 Allocated to the Space Assigned Numbers Authority ([SANA]) for use by Consultative Committee for Space Data Systems (CCSDS) missions.

(2**14--(2**21)-1分配给空间分配号码管理局([SANA]),供空间数据系统协商委员会(CCSDS)任务使用。

(2**21) -- (2**28)-1 Private or Experimental Use.

(2**21)--(2**28)-1私人或实验用途。

(2**28) -- (2**42)-1 First Come First Served basis for requests for less than or equal to 2**14 values to a single entity or organization. Expert Review is required for requests of more than 2**14 values to a single entity or organization.

(2**28)--(2**42)-1对于向单个实体或组织提出的小于或等于2**14值的请求,采用先到先得的原则。对于向单个实体或组织提出的超过2**14值的请求,需要进行专家审查。

The LTP Engine ID is expressed as a Self-Delimiting Numeric Value (SDNV) in LTP, and no maximum is specified in the protocol definition. SDNVs are described in Section 4.1 of the Bundle Protocol specification [RFC5050] and in [RFC6256]. The initial values for the "LTP Engine Numbers" registry are:

LTP引擎ID在LTP中表示为自定界数值(SDNV),协议定义中未指定最大值。捆绑协议规范[RFC5050]第4.1节和[RFC6256]中描述了SDNV。“LTP引擎号”注册表的初始值为:

    +--------------------+---------------------------+---------------+
    |              Value | Description               | Reference     |
    +--------------------+---------------------------+---------------+
    |                  0 | Reserved                  | This document |
    |       1--(2**14)-1 | Unassigned                | This document |
    | (2**14)--(2**21)-1 | Allocated to CCSDS (SANA) | This document |
    | (2**21)--(2**28)-1 | Private/Experimental Use  | This document |
    | (2**28)--(2**42)-1 | Unassigned                | This document |
    |          >=(2**42) | Reserved                  | This document |
    +--------------------+---------------------------+---------------+
        
    +--------------------+---------------------------+---------------+
    |              Value | Description               | Reference     |
    +--------------------+---------------------------+---------------+
    |                  0 | Reserved                  | This document |
    |       1--(2**14)-1 | Unassigned                | This document |
    | (2**14)--(2**21)-1 | Allocated to CCSDS (SANA) | This document |
    | (2**21)--(2**28)-1 | Private/Experimental Use  | This document |
    | (2**28)--(2**42)-1 | Unassigned                | This document |
    |          >=(2**42) | Reserved                  | This document |
    +--------------------+---------------------------+---------------+
        
3.1.3. LTP Client Service ID
3.1.3. LTP客户端服务ID

The Licklider Transmission Protocol has a client service ID number field (Section 3.2.1 of [RFC5326]). IANA has set up a registry to manage LTP Client Service IDs. This registry, titled "LTP Client Service Identifiers", has been added to the list of registries associated with the Licklider Transmission Protocol.

利克利德传输协议有一个客户服务ID号字段(RFC5326的第3.2.1节)。IANA已经建立了一个注册表来管理LTP客户端服务ID。此名为“LTP客户端服务标识符”的注册表已添加到与Licklider传输协议相关联的注册表列表中。

The registration policy for this registry is:

此注册表的注册策略为:

4 -- (2**14)-1 Allocated to the Space Assigned Numbers Authority ([SANA]) for use by Consultative Committee for Space Data Systems (CCSDS) missions.

4-(2**14)-1分配给空间分配号码管理局([SANA]),供空间数据系统协商委员会(CCSDS)任务使用。

2**14 -- 32,767 Private or Experimental Use.

2**14--32767私人或实验使用。

>= 32,768 Specification Required.

>=32768所需规格。

The LTP Client Service ID is expressed as a Self-Delimiting Numeric Value (SDNV) in LTP, and no maximum value is specified in the protocol definition. The initial values for the "LTP Client Service Identifiers" are:

LTP客户端服务ID在LTP中表示为自定界数值(SDNV),协议定义中未指定最大值。“LTP客户端服务标识符”的初始值为:

    +-----------------+------------------------------+---------------+
    |           Value | Description                  | Reference     |
    +-----------------+------------------------------+---------------+
    |               0 | Reserved                     | [RFC5326]     |
    |               1 | Bundle Protocol              | This document |
    |               2 | LTP Service Data Aggregation | This document |
    |               3 | CCSDS File Delivery Service  | This document |
    |    4--(2**14)-1 | Allocated to CCSDS (SANA)    | This document |
    | (2**14)--32,767 | Private/Experimental Use     | This document |
    |        >=32,768 | Unassigned                   | This document |
    +-----------------+------------------------------+---------------+
        
    +-----------------+------------------------------+---------------+
    |           Value | Description                  | Reference     |
    +-----------------+------------------------------+---------------+
    |               0 | Reserved                     | [RFC5326]     |
    |               1 | Bundle Protocol              | This document |
    |               2 | LTP Service Data Aggregation | This document |
    |               3 | CCSDS File Delivery Service  | This document |
    |    4--(2**14)-1 | Allocated to CCSDS (SANA)    | This document |
    | (2**14)--32,767 | Private/Experimental Use     | This document |
    |        >=32,768 | Unassigned                   | This document |
    +-----------------+------------------------------+---------------+
        
3.2. Compressed Bundle Header Encoding
3.2. 压缩包头编码

The CBHE specification [RFC6260] defines concepts of 'Node Number' and 'Service Number' that require registries managed by IANA.

CBHE规范[RFC6260]定义了需要IANA管理的注册表的“节点号”和“服务号”概念。

3.2.1. CBHE Node Numbers
3.2.1. CBHE节点号

The CBHE specification defines a Node Number (node-nbr) field (Section 2.1 of [RFC6260]). IANA has set up a registry to manage CBHE Node Numbers. This registry, titled "CBHE Node Numbers", has been added to the list of registries associated with the Bundle Protocol.

CBHE规范定义了节点编号(节点编号)字段(RFC6260第2.1节)。IANA已经建立了一个注册表来管理CBHE节点号。此名为“CBHE节点号”的注册表已添加到与捆绑协议相关的注册表列表中。

The registration policy for this registry is:

此注册表的注册策略为:

1 -- (2**14)-1 Expert Review required.

1--(2**14)-1需要专家评审。

(2**14) -- (2**21)-1 Allocated to the Space Assigned Numbers Authority ([SANA]) for use by Consultative Committee for Space Data Systems (CCSDS) missions.

(2**14--(2**21)-1分配给空间分配号码管理局([SANA]),供空间数据系统协商委员会(CCSDS)任务使用。

(2**21) -- (2**28)-1 Private or Experimental Use.

(2**21)--(2**28)-1私人或实验用途。

(2**28) -- (2**42)-1 First Come First Served basis for requests for less than or equal to 2**14 values to a single entity or organization. Expert Review is required for requests of more than 2**14 values to a single entity or organization.

(2**28)--(2**42)-1对于向单个实体或组织提出的小于或等于2**14值的请求,采用先到先得的原则。对于向单个实体或组织提出的超过2**14值的请求,需要进行专家审查。

   >= (2**42)  Reserved.
        
   >= (2**42)  Reserved.
        

The CBHE Node Number is expressed as a Self-Delimiting Numeric Value (SDNV) in the CBHE specification. Allowable values for the Node Number range from 1 -- (2**64)-1. The initial values for the "CBHE Node Number" registry shall be:

CBHE节点编号在CBHE规范中表示为自定界数值(SDNV)。节点编号的允许值范围为1--(2**64)-1。“CBHE节点编号”注册表的初始值应为:

    +--------------------+---------------------------+---------------+
    |              Value | Description               | Reference     |
    +--------------------+---------------------------+---------------+
    |                  0 | Reserved                  | This document |
    |       1--(2**14)-1 | Unassigned                | This document |
    | (2**14)--(2**21)-1 | Allocated to CCSDS (SANA) | This document |
    | (2**21)--(2**28)-1 | Private/Experimental Use  | This document |
    | (2**28)--(2**42)-1 | Unassigned                | This document |
    |          >=(2**42) | Reserved                  | This document |
    +--------------------+---------------------------+---------------+
        
    +--------------------+---------------------------+---------------+
    |              Value | Description               | Reference     |
    +--------------------+---------------------------+---------------+
    |                  0 | Reserved                  | This document |
    |       1--(2**14)-1 | Unassigned                | This document |
    | (2**14)--(2**21)-1 | Allocated to CCSDS (SANA) | This document |
    | (2**21)--(2**28)-1 | Private/Experimental Use  | This document |
    | (2**28)--(2**42)-1 | Unassigned                | This document |
    |          >=(2**42) | Reserved                  | This document |
    +--------------------+---------------------------+---------------+
        
3.2.2. CBHE Service Numbers
3.2.2. CBHE服务编号

The Compressed Bundle Header Encoding specification defines a Service Number (service-nbr) field (Section 2.1 of [RFC6260]). IANA has set up a registry to manage CBHE Service Numbers. This registry, titled "CBHE Service Numbers", has been added to the list of registries associated with the Bundle Protocol.

压缩包头编码规范定义了服务编号(服务编号)字段(RFC6260第2.1节)。IANA已经建立了一个注册表来管理CBHE服务编号。此名为“CBHE服务编号”的注册表已添加到与捆绑协议相关的注册表列表中。

The registration policy for this registry is:

此注册表的注册策略为:

0-63 Specification Required.

需要0-63规格。

64-1023 Allocated to the Space Assigned Numbers Authority ([SANA]) for use by Consultative Committee for Space Data Systems (CCSDS) missions.

64-1023分配给空间分配号码管理局([SANA]),供空间数据系统协商委员会(CCSDS)任务使用。

1024 - 2**16-1 Specification Required.

1024-2**16-1所需规格。

>= 2**16 Private/Experimental Use.

>=2**16私人/实验用途。

The CBHE Service Number is expressed as a Self-Delimiting Numeric Value (SDNV) in the CBHE specification. Allowable values for the Service Number range from 1 -- (2**64)-1. The initial values for the "CBHE Service Number" registry are:

CBHE服务编号在CBHE规范中表示为自定界数值(SDNV)。服务编号的允许值范围为1--(2**64)-1。“CBHE服务编号”注册表的初始值为:

   +----------------+--------------------------------+---------------+
   |          Value | Description                    | Reference     |
   +----------------+--------------------------------+---------------+
   |              0 | Bundle Protocol Administrative | [RFC6260]     |
   |                |   Record                       |               |
   |              1 | CCSDS File Delivery Service    | [CFDP]        |
   |              2 | Reserved                       | This document |
   |           3-63 | Unassigned                     | This document |
   |        64-1023 | Allocated to CCSDS (SANA)      | This document |
   | 1024 - 2**16-1 | Unassigned                     | This document |
   |        >=2**16 | Private/Experimental Use       | This document |
   +----------------+--------------------------------+---------------+
        
   +----------------+--------------------------------+---------------+
   |          Value | Description                    | Reference     |
   +----------------+--------------------------------+---------------+
   |              0 | Bundle Protocol Administrative | [RFC6260]     |
   |                |   Record                       |               |
   |              1 | CCSDS File Delivery Service    | [CFDP]        |
   |              2 | Reserved                       | This document |
   |           3-63 | Unassigned                     | This document |
   |        64-1023 | Allocated to CCSDS (SANA)      | This document |
   | 1024 - 2**16-1 | Unassigned                     | This document |
   |        >=2**16 | Private/Experimental Use       | This document |
   +----------------+--------------------------------+---------------+
        
3.3. Bundle Administrative Record Types
3.3. 捆绑管理记录类型

Section 6.1 of the Bundle Protocol specification [RFC5050] specifies a 4-bit Administrative Record type code. IANA has set up a registry to manage these record types. This registry, titled "Bundle Administrative Record Types", has been added to the list of registries associated with the Bundle Protocol.

捆绑协议规范[RFC5050]第6.1节规定了4位管理记录类型代码。IANA已经建立了一个注册表来管理这些记录类型。此名为“捆绑管理记录类型”的注册表已添加到与捆绑协议关联的注册表列表中。

The registration policy for this registry is Specification Required.

此注册表的注册策略是必需的。

The initial values for the "Bundle Administrative Record Type" registry are:

“捆绑管理记录类型”注册表的初始值为:

           +-------+----------------------+---------------+
           | Value | Description          | Reference     |
           +-------+----------------------+---------------+
           |     0 | Reserved             | This document |
           |     1 | Bundle status report | [RFC5050]     |
           |     2 | Custody signal       | [RFC5050]     |
           |  3-15 | Unassigned           | This document |
           +-------+----------------------+---------------+
        
           +-------+----------------------+---------------+
           | Value | Description          | Reference     |
           +-------+----------------------+---------------+
           |     0 | Reserved             | This document |
           |     1 | Bundle status report | [RFC5050]     |
           |     2 | Custody signal       | [RFC5050]     |
           |  3-15 | Unassigned           | This document |
           +-------+----------------------+---------------+
        
4. Acknowledgements
4. 致谢

The authors would like to thank the following people, in no specific order: Scott Burleigh, Stephen Farrell, and John Buford.

作者要感谢以下人士,没有具体顺序:斯科特·伯利、斯蒂芬·法雷尔和约翰·布福德。

5. References
5. 工具书类
5.1. Normative References
5.1. 规范性引用文件

[CFDP] Consultative Committee for Space Data Systems, "CCSDS File Delivery Protocol Version 4 (CCSDS 727.0-B-4)", January 2007, <http://www.ccsds.org>.

[CFDP]空间数据系统咨询委员会,“CCSDS文件交付协议第4版(CCSDS 727.0-B-4)”,2007年1月<http://www.ccsds.org>.

[RFC5050] Scott, K. and S. Burleigh, "Bundle Protocol Specification", RFC 5050, November 2007.

[RFC5050]Scott,K.和S.Burleigh,“捆绑协议规范”,RFC 50502007年11月。

[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.

[RFC5226]Narten,T.和H.Alvestrand,“在RFCs中编写IANA注意事项部分的指南”,BCP 26,RFC 5226,2008年5月。

[RFC5326] Ramadas, M., Burleigh, S., and S. Farrell, "Licklider Transmission Protocol - Specification", RFC 5326, September 2008.

[RFC5326]Ramadas,M.,Burleigh,S.和S.Farrell,“利克利德传输协议-规范”,RFC 5326,2008年9月。

[RFC6256] Eddy, W. and E. Davies, "Using Self-Delimiting Numeric Values in Protocols", RFC 6256, May 2011.

[RFC6256]Eddy,W.和E.Davies,“在协议中使用自定界数值”,RFC 6256,2011年5月。

[RFC6260] Burleigh, S., "Compressed Bundle Header Encoding (CBHE)", RFC 6260, May 2011.

[RFC6260]Burleigh,S.,“压缩包头编码(CBHE)”,RFC6260,2011年5月。

5.2. Informative References
5.2. 资料性引用

[CCSDS] CCSDS, "The Consultative Committee for Space Data Systems", <http://www.ccsds.org>.

[CCSDS]CCSDS,“空间数据系统协商委员会”<http://www.ccsds.org>.

[SANA] SANA, "The CCSDS SANA Registry page", <http://sanaregistry.org>.

[SANA]SANA,“CCSDS SANA注册页面”<http://sanaregistry.org>.

Authors' Addresses

作者地址

Keith Scott The MITRE Corporation 7515 Colshire Drive McLean, VA 22102 USA

基思·斯科特米特尔公司美国弗吉尼亚州麦克莱恩科尔郡大道7515号,邮编:22102

   Phone: +1-703-983-6547
   Fax:   +1-703-983-7142
   EMail: kscott@mitre.org
        
   Phone: +1-703-983-6547
   Fax:   +1-703-983-7142
   EMail: kscott@mitre.org
        

Marc Blanchet Viagenie 246 Aberdeen Quebec G1R 2E1 Canada

Marc Blanchet Viagenie 246加拿大魁北克阿伯丁G1R 2E1

   Phone: +1-418-656-9254
   EMail: marc.blanchet@viagenie.ca
        
   Phone: +1-418-656-9254
   EMail: marc.blanchet@viagenie.ca