Internet Engineering Task Force (IETF) S. Venaas
Request for Comments: 6166 Cisco Systems
Category: Standards Track April 2011
ISSN: 2070-1721
Internet Engineering Task Force (IETF) S. Venaas
Request for Comments: 6166 Cisco Systems
Category: Standards Track April 2011
ISSN: 2070-1721
A Registry for PIM Message Types
PIM消息类型的注册表
Abstract
摘要
This document provides instructions to IANA for the creation of a registry for PIM message types. It specifies the initial content of the registry, based on existing RFCs specifying PIM message types. It also specifies a procedure for registering new types.
本文档为IANA提供了创建PIM消息类型注册表的说明。它根据指定PIM消息类型的现有RFC指定注册表的初始内容。它还指定了注册新类型的过程。
In addition to this, one message type is reserved, and may be used for a future extension of the message type space.
除此之外，还保留了一种消息类型，可用于消息类型空间的未来扩展。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
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). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（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/rfc6166.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6166.
Copyright Notice
版权公告
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2011 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 ....................................................2
2. Security Considerations .........................................2
3. IANA Considerations .............................................2
3.1. Initial Registry ...........................................3
3.2. Assignment of New Message Types ............................3
4. Acknowledgements ................................................3
5. Informative References ..........................................3
1. Introduction ....................................................2
2. Security Considerations .........................................2
3. IANA Considerations .............................................2
3.1. Initial Registry ...........................................3
3.2. Assignment of New Message Types ............................3
4. Acknowledgements ................................................3
5. Informative References ..........................................3
Apart from this document, there is no existing document specifying a registry for PIM message types. PIM version 1 made use of IGMP [RFC1112], and there is an IGMP registry [IGMPREG] listing the message types used by PIM version 1. PIM version 2, however, is not based on IGMP, and a separate PIM message type registry is needed. There are currently several RFCs specifying new PIM version 2 message types that should be in this new registry. They are the RFCs for PIM Dense Mode [RFC3973], PIM Sparse Mode [RFC4601], and Bidirectional PIM [RFC5015].
除本文档外，没有为PIM消息类型指定注册表的现有文档。PIM版本1使用了IGMP[RFC1112]，并且有一个IGMP注册表[IGMPREG]，列出了PIM版本1使用的消息类型。然而，PIM版本2并不基于IGMP，需要一个单独的PIM消息类型注册表。目前有多个RFC指定应在此新注册表中的新PIM版本2消息类型。它们是PIM密集模式[RFC3973]、PIM稀疏模式[RFC4601]和双向PIM[RFC5015]的RFC。
This document specifies the initial content of the new PIM message type registry, based on those existing RFCs. This document also specifies a procedure for registering new PIM message types.
本文档根据现有RFC指定新PIM消息类型注册表的初始内容。本文档还规定了注册新PIM消息类型的过程。
In addition to this, this document reserves one message type. This type may be used for a future extension of the message type space. The current message type space is only 4 bits, so it is not unlikely that this will be needed. How exactly the extension should be done is left to a future document.
除此之外，本文档还保留一种消息类型。此类型可用于消息类型空间的未来扩展。当前消息类型空间只有4位，因此不太可能需要这样的空间。扩展应该如何进行将留待将来的文档决定。
This document only creates an IANA registry. There may be a security benefit in a well-known place for finding information on which PIM message types are valid and how they are used. Apart from that, there are no security considerations.
本文档仅创建IANA注册表。在一个众所周知的地方，查找哪些PIM消息类型是有效的以及如何使用它们的信息可能会带来安全好处。除此之外，没有安全考虑。
IANA has created a PIM message type registry. It has been placed in the "Protocol Independent Multicast (PIM)" branch of the tree. Each entry in the registry consists of a message type, a message name, and references to the documents defining the type. The message type is a 4-bit integer with possible values from 0 to 15.
IANA已创建PIM消息类型注册表。它被放置在树的“协议独立多播（PIM）”分支中。注册表中的每个条目都由消息类型、消息名称和对定义该类型的文档的引用组成。消息类型为4位整数，可能值为0到15。
The initial content of the registry should be as follows.
登记册的初始内容应如下所示。
Type Name Reference
------ ---------------------------------------- -------------------
0 Hello [RFC3973] [RFC4601]
1 Register [RFC4601]
2 Register Stop [RFC4601]
3 Join/Prune [RFC3973] [RFC4601]
4 Bootstrap [RFC4601]
5 Assert [RFC3973] [RFC4601]
6 Graft [RFC3973]
7 Graft-Ack [RFC3973]
8 Candidate RP Advertisement [RFC4601]
9 State Refresh [RFC3973]
10 DF Election [RFC5015]
11-14 Unassigned
15 Reserved (for extension of type space) this document
Type Name Reference
------ ---------------------------------------- -------------------
0 Hello [RFC3973] [RFC4601]
1 Register [RFC4601]
2 Register Stop [RFC4601]
3 Join/Prune [RFC3973] [RFC4601]
4 Bootstrap [RFC4601]
5 Assert [RFC3973] [RFC4601]
6 Graft [RFC3973]
7 Graft-Ack [RFC3973]
8 Candidate RP Advertisement [RFC4601]
9 State Refresh [RFC3973]
10 DF Election [RFC5015]
11-14 Unassigned
15 Reserved (for extension of type space) this document
Assignment of new message types is done according to the "IETF Review" model; see [RFC5226].
根据“IETF审查”模型分配新的消息类型；见[RFC5226]。
Thanks to Toerless Eckert for his suggestion to reserve a type for future extension of the message type space. Also thanks to Mykyta Yevstifeyev for reviewing the document and proposing improvements to the text.
感谢Toerless Eckert建议为消息类型空间的未来扩展保留一个类型。还感谢Mykyta Yevstifeyev审阅了该文件并对文本提出了改进建议。
[IGMPREG] IANA, "Internet Group Management Protocol (IGMP) Type Numbers - per [RFC3228], [BCP57]", <http://www.iana.org/>.
[IGMPREG]IANA，“互联网组管理协议（IGMP）类型编号-根据[RFC3228]，[BCP57]”<http://www.iana.org/>.
[RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5, RFC 1112, August 1989.
[RFC1112]Deering，S.，“IP多播的主机扩展”，STD 5，RFC11121989年8月。
[RFC3973] Adams, A., Nicholas, J., and W. Siadak, "Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised)", RFC 3973, January 2005.
[RFC3973]Adams，A.，Nicholas，J.，和W.Siadak，“协议独立多播-密集模式（PIM-DM）：协议规范（修订版）”，RFC 3973，2005年1月。
[RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)", RFC 4601, August 2006.
[RFC4601]Fenner，B.，Handley，M.，Holbrook，H.，和I.Kouvelas，“协议独立多播-稀疏模式（PIM-SM）：协议规范（修订版）”，RFC 46012006年8月。
[RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, "Bidirectional Protocol Independent Multicast (BIDIR-PIM)", RFC 5015, October 2007.
[RFC5015]Handley，M.，Kouvelas，I.，Speakman，T.，和L.Vicisano，“双向协议独立多播（BIDIR-PIM）”，RFC 50152007年10月。
[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月。
Author's Address
作者地址
Stig Venaas Cisco Systems Tasman Drive San Jose, CA 95134 USA
美国加利福尼亚州圣何塞市塔斯曼大道Stig Venaas思科系统公司，邮编95134
EMail: stig@cisco.com
EMail: stig@cisco.com