Network Working Group E. Stephan
Request for Comments: 3919 France Telecom R&D
Category: Informational J. Palet
Consulintel
October 2004
Network Working Group E. Stephan
Request for Comments: 3919 France Telecom R&D
Category: Informational J. Palet
Consulintel
October 2004
Remote Network Monitoring (RMON) Protocol Identifiers for IPv6 and Multi Protocol Label Switching (MPLS)
IPv6和多协议标签交换（MPLS）的远程网络监控（RMON）协议标识符
Status of this Memo
本备忘录的状况
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2004).
版权所有（C）互联网协会（2004年）。
Abstract
摘要
This memo defines additional (to those in RFC 2896) protocol identifier examples for IP version 6 and MPLS protocols. These can be used to produce valid protocolDirTable INDEX encodings, as defined by the Remote Network Monitoring MIB (Management Information Base) Version 2 [RFC2021] and the RMON Protocol Identifier Reference [RFC2895].
本备忘录定义了IP版本6和MPLS协议的附加（RFC 2896中的除外）协议标识符示例。这些可用于生成有效的protocolDirTable索引编码，如远程网络监控MIB（管理信息库）版本2[RFC2021]和RMON协议标识符参考[RFC2895]所定义。
This document contains additional (to those in RFC 2896) protocol identifier macros for well-known protocols. A conformant implementation of the RMON-2 MIB [RFC2021] can be accomplished without the use of these protocol identifiers, and accordingly, this document does not specify any IETF standard. It is published to encourage better interoperability between RMON-2 agent implementations, by providing RMON related IPv6 and MPLS protocol information.
本文档包含已知协议的附加（RFC 2896中的除外）协议标识符宏。RMON-2 MIB[RFC2021]的一致性实现可以在不使用这些协议标识符的情况下完成，因此，本文件未规定任何IETF标准。它的发布旨在通过提供与RMON相关的IPv6和MPLS协议信息，鼓励RMON-2代理实现之间更好的互操作性。
Table of Contents
目录
1. The Internet-Standard Management Framework . . . . . . . . . . 2
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Relationship to the Remote Network Monitoring MIB. . . . . . . 2
4. MPLS layer protocol identifiers . . . . . . . . . . . . . . . 2
5. IPv6 Protocols . . . . . . . . . . . . . . . . . . . . . . . . 3
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1. The Internet-Standard Management Framework . . . . . . . . . . 2
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Relationship to the Remote Network Monitoring MIB. . . . . . . 2
4. MPLS layer protocol identifiers . . . . . . . . . . . . . . . 2
5. IPv6 Protocols . . . . . . . . . . . . . . . . . . . . . . . . 3
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 7
Full Copyright Statement. . . . . . . . . . . .. . . . . . . . 8
8.1. Normative References . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 7
Full Copyright Statement. . . . . . . . . . . .. . . . . . . . 8
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
有关描述当前互联网标准管理框架的文件的详细概述，请参阅RFC 3410[RFC3410]第7节。托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。本备忘录规定了符合SMIv2的MIB模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
This memo defines basic protocol identifiers for IP version 6 and MPLS protocols.
本备忘录定义了IP版本6和MPLS协议的基本协议标识符。
The "Remote Network Monitoring MIB Protocol Identifier Macros" [RFC2896], defines various protocol identifiers. The syntax of the protocol identifier descriptor is defined in the RMON Protocol Identifier Reference [RFC2895]. The reader should be familiar with these documents.
“远程网络监控MIB协议标识符宏”[RFC2896]定义了各种协议标识符。协议标识符描述符的语法在RMON协议标识符参考[RFC2895]中定义。读者应熟悉这些文件。
The intent of this document is not to adapt each protocol identifier defined in the RFC 2895 and in the RFC 2896 to IP version 6, but to define protocol identifiers for IP version 6 protocols and for MPLS protocol.
本文件的目的不是使RFC 2895和RFC 2896中定义的每个协议标识符适应IP版本6，而是为IP版本6协议和MPLS协议定义协议标识符。
RMON MIB implementations use protocol identifiers to describe unambiguous capabilities in protocolDirTable entries.
RMON MIB实现使用协议标识符来描述protocolDirTable条目中明确的功能。
This section defines protocol identifiers for MPLS with unambiguous names to distinguish MPLS Unicast from MPLS Multicast.
本节使用明确的名称定义MPLS的协议标识符，以区分MPLS单播和MPLS多播。
-- MPLS unicast
--MPLS单播
mplsu PROTOCOL-IDENTIFIER
PARAMETERS { }
ATTRIBUTES { }
DESCRIPTION
"MPLS Label Stack Encoding."
mplsu PROTOCOL-IDENTIFIER
PARAMETERS { }
ATTRIBUTES { }
DESCRIPTION
"MPLS Label Stack Encoding."
CHILDREN
"Children of MPLS are not systematically identifiable. "
REFERENCE
"RFC 3032, MPLS Label Stack Encoding [RFC3032]."
::= {
ether2 0x8847, -- RFC 3032 section 5
snap 0x8847,
802-1Q 0x8847,
ppp 0x0281, -- RFC 3032 section 4.3
}
CHILDREN
"Children of MPLS are not systematically identifiable. "
REFERENCE
"RFC 3032, MPLS Label Stack Encoding [RFC3032]."
::= {
ether2 0x8847, -- RFC 3032 section 5
snap 0x8847,
802-1Q 0x8847,
ppp 0x0281, -- RFC 3032 section 4.3
}
-- MPLS multicast
--多播
mplsm PROTOCOL-IDENTIFIER
PARAMETERS { }
ATTRIBUTES { }
DESCRIPTION
"MPLS Label Stack Encoding."
CHILDREN
"Children of MPLS are not systematically identifiable."
REFERENCE
"RFC 3032, MPLS Label Stack Encoding [RFC3032]."
::= {
ether2 0x8848, -- RFC 3032 section 5
snap 0x8848,
802-1Q 0x8848,
ppp 0x0283, -- RFC 3032 section 4.3
}
mplsm PROTOCOL-IDENTIFIER
PARAMETERS { }
ATTRIBUTES { }
DESCRIPTION
"MPLS Label Stack Encoding."
CHILDREN
"Children of MPLS are not systematically identifiable."
REFERENCE
"RFC 3032, MPLS Label Stack Encoding [RFC3032]."
::= {
ether2 0x8848, -- RFC 3032 section 5
snap 0x8848,
802-1Q 0x8848,
ppp 0x0283, -- RFC 3032 section 4.3
}
ip6 PROTOCOL-IDENTIFIER
PARAMETERS {}
ATTRIBUTES {}
DESCRIPTION
"The protocol identifiers for the Internet Protocol, Version 6
[RFC2460]."
ip6 PROTOCOL-IDENTIFIER
PARAMETERS {}
ATTRIBUTES {}
DESCRIPTION
"The protocol identifiers for the Internet Protocol, Version 6
[RFC2460]."
CHILDREN "Children of 'ip6' are selected by the value in the Protocol field (one octet), as defined in the PROTOCOL NUMBERS table within the Assigned Numbers Document.
“ip6”的“子项”由协议字段（一个八位字节）中的值选择，如分配号码文档中的协议号码表中所定义。
The value of the Protocol field is encoded in an octet string as [ 0.0.0.a ], where 'a' is the protocol field. Children of 'ip6' are encoded as [ 0.0.0.a ], and named as 'ip6 a' where 'a' is the protocol field value. For example, a protocolDirID-fragment value of: 0.0.0.1.0.0.0.41.0.0.0.58
协议字段的值在八位字节字符串中编码为[0.0.0.a]，其中“a”是协议字段。“ip6”的子级编码为[0.0.0.a]，并命名为“ip6 a”，其中“a”是协议字段值。例如，protocolDirID片段值为：0.0.0.1.0.0.0.41.0.0.0.58
defines an encapsulation of IPv6-ICMP (ether2.ip6.icmp6)" ADDRESS-FORMAT "16 octets of the IPv6 address, in network byte order. Each ip packet contains two addresses, the source address and the destination address." DECODING "Note: ether2.ip.ipip6.udp is a different protocolDirID than ether2.ip6.udp, as identified in the protocolDirTable. As such, two different local protocol index values will be assigned by the agent. E.g., (full INDEX values shown): ether2.ip.ipip6.udp = 16.0.0.0.1.0.0.8.0.0.0.0.41.0.0.0.17.4.0.0.0.0 ether2.ip6.udp = 12.0.0.0.1.0.0.0.41.0.0.0.17.3.0.0.0 " REFERENCE
定义IPv6 ICMP（ether2.ip6.icmp6）“地址格式”的封装，以网络字节顺序封装IPv6地址的16个八位字节。每个ip数据包包含两个地址，即源地址和目标地址。“解码”注意：ether2.ip.ipip6.udp是与ether2.ip6.udp不同的protocolDirID，如protocolDirTable中所标识。因此，代理将分配两个不同的本地协议索引值。例如，（显示完整索引值）：ether2.ip.ipip6.udp=16.0.0.0.1.0.0.0.8.0.0.0.0.0.41.0.0.0.0.17.4.0.0.0.0.0 ether2.ip6.udp=12.0.0.0.0.0.0.41.0.0.0.17.3.0.0“参考
"RFC 2460 [RFC2460] defines the Internet Protocol version 6; The following URL defines the authoritative repository for the PROTOCOL NUMBERS Table:
“RFC 2460[RFC2460]定义了Internet协议版本6；以下URL定义了协议编号表的权威存储库：
http://www.iana.org/assignments/protocol-numbers"
::= {
ether2 0x86DD,
802-1Q 0x86DD,
mplsu 41,
mplsm 41
}
http://www.iana.org/assignments/protocol-numbers"
::= {
ether2 0x86DD,
802-1Q 0x86DD,
mplsu 41,
mplsm 41
}
ipip6 PROTOCOL-IDENTIFIER
PARAMETERS { }
ATTRIBUTES {
ipip6 PROTOCOL-IDENTIFIER
PARAMETERS { }
ATTRIBUTES {
} DESCRIPTION "IPv6 in IPv4 Tunneling"
}说明“IPv4隧道中的IPv6”
CHILDREN
"Children of 'ipip6' are selected and encoded in the same manner
as children of ip6."
ADDRESS-FORMAT
"The 'ipip6' address format is the same as the IPv6 address
format."
DECODING
"Note: ether2.ip.ipip6.udp is a different protocolDirID than
ether2.ip6.udp, as identified in the protocolDirTable. As such,
two different local protocol index values will be assigned by
the agent. E.g., (full INDEX values shown):
ether2.ip.ipip6.udp =
16.0.0.0.1.0.0.8.0.0.0.0.41.0.0.0.17.4.0.0.0.0
ether2.ip6.udp =
12.0.0.0.1.0.0.0.41.0.0.0.17.3.0.0.0 "
REFERENCE
"RFC 2473 [RFC2473] defines Generic Packet Tunneling in IPv6
Specification."
::= {
ip 41
}
CHILDREN
"Children of 'ipip6' are selected and encoded in the same manner
as children of ip6."
ADDRESS-FORMAT
"The 'ipip6' address format is the same as the IPv6 address
format."
DECODING
"Note: ether2.ip.ipip6.udp is a different protocolDirID than
ether2.ip6.udp, as identified in the protocolDirTable. As such,
two different local protocol index values will be assigned by
the agent. E.g., (full INDEX values shown):
ether2.ip.ipip6.udp =
16.0.0.0.1.0.0.8.0.0.0.0.41.0.0.0.17.4.0.0.0.0
ether2.ip6.udp =
12.0.0.0.1.0.0.0.41.0.0.0.17.3.0.0.0 "
REFERENCE
"RFC 2473 [RFC2473] defines Generic Packet Tunneling in IPv6
Specification."
::= {
ip 41
}
icmp6 PROTOCOL-IDENTIFIER
PARAMETERS { }
ATTRIBUTES { }
DESCRIPTION
"Internet Message Control Protocol for IP Version 6"
REFERENCE
"RFC 2463 [RFC2463] Internet Control Message Protocol (ICMPv6)
for the Internet Protocol Version 6 (IPv6) Specification "
::= {
ip6 58,
ipip6 58
}
icmp6 PROTOCOL-IDENTIFIER
PARAMETERS { }
ATTRIBUTES { }
DESCRIPTION
"Internet Message Control Protocol for IP Version 6"
REFERENCE
"RFC 2463 [RFC2463] Internet Control Message Protocol (ICMPv6)
for the Internet Protocol Version 6 (IPv6) Specification "
::= {
ip6 58,
ipip6 58
}
This document contains textual descriptions of well-known networking protocols, not the definition of any networking behavior. As such, no security considerations are raised by its publication.
本文档包含已知网络协议的文本描述，而不是任何网络行为的定义。因此，其发布没有提出任何安全考虑。
The authors would like to acknowledge the European Commission support in the co-funding of the 6QM project, where this work is being developed.
作者希望感谢欧盟委员会对6QM项目的共同资助，该项目正在开发中。
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC 2460, December 1998.
[RFC2460]Deering，S.和R.Hinden，“互联网协议，第6版（IPv6）规范”，RFC 2460，1998年12月。
[RFC2463] Conta, A. and S. Deering, "Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification", RFC 2463, December 1998.
[RFC2463]Conta，A.和S.Deering，“互联网协议版本6（IPv6）规范的互联网控制消息协议（ICMPv6）”，RFC2463，1998年12月。
[RFC2473] Conta, A. and S. Deering, "Generic Packet Tunneling in IPv6 Specification", RFC 2473, December 1998.
[RFC2473]Conta，A.和S.Deering，“IPv6规范中的通用数据包隧道”，RFC 2473，1998年12月。
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC2895] Bierman, A., Bucci, C., and R. Iddon, "Remote Network Monitoring MIB Protocol Identifier Reference", RFC 2895, August 2000.
[RFC2895]Bierman，A.，Bucci，C.，和R.Iddon，“远程网络监控MIB协议标识符参考”，RFC 28952000年8月。
[RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack Encoding", RFC 3032, January 2001.
[RFC3032]Rosen，E.，Tappan，D.，Fedorkow，G.，Rekhter，Y.，Farinaci，D.，Li，T.，和A.Conta，“MPLS标签堆栈编码”，RFC 3032，2001年1月。
[RFC2021] Waldbusser, S., "Remote Network Monitoring Management Information Base Version 2 using SMIv2", RFC 2021, January 1997.
[RFC2021]Waldbusser，S.，“使用SMIv2的远程网络监控管理信息库版本2”，RFC 20211997年1月。
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996.
[RFC2026]Bradner，S.，“互联网标准过程——第3版”，BCP 9，RFC 2026，1996年10月。
[RFC2896] Bierman, A., Bucci, C., and R. Iddon, "Remote Network Monitoring MIB Protocol Identifier Macros", RFC 2896, August 2000.
[RFC2896]Bierman，A.，Bucci，C.，和R.Iddon，“远程网络监控MIB协议标识符宏”，RFC 28962000年8月。
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
[RFC3410]Case，J.，Mundy，R.，Partain，D.，和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 34102002年12月。
Authors' Addresses
作者地址
Stephan Emile France Telecom R & D 2 avenue Pierre Marzin Lannion, F-22307
Stephan Emile法国电信研发2大道Pierre Marzin Lannion，F-22307
Fax: +33 2 96 05 18 52
EMail: emile.stephan@francetelecom.com
Fax: +33 2 96 05 18 52
EMail: emile.stephan@francetelecom.com
Jordi Palet Consulintel, IPv6 R&D San Jose Artesano, 1 Alcobendas, Madrid, Spain E-28108
Jordi Palet Consultintel，IPv6研发圣何塞Artesano，1 Alcobendas，马德里，西班牙E-28108
Fax: +34 91 151 81 98
EMail: jordi.palet@consulintel.es
Fax: +34 91 151 81 98
EMail: jordi.palet@consulintel.es
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2004).
版权所有（C）互联网协会（2004年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the IETF's procedures with respect to rights in IETF Documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关IETF文件中权利的IETF程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。