Internet Engineering Task Force (IETF) Y. Cui
Request for Comments: 7856 J. Dong
Category: Standards Track P. Wu
ISSN: 2070-1721 M. Xu
Tsinghua University
A. Yla-Jaaski
Aalto University
May 2016
Internet Engineering Task Force (IETF) Y. Cui
Request for Comments: 7856 J. Dong
Category: Standards Track P. Wu
ISSN: 2070-1721 M. Xu
Tsinghua University
A. Yla-Jaaski
Aalto University
May 2016
Softwire Mesh Management Information Base (MIB)
软线网管理信息库（MIB）
Abstract
摘要
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing a softwire mesh.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它定义了用于管理软线网格的对象。
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/rfc7856.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7856.
Copyright Notice
版权公告
Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2016 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. The Internet-Standard Management Framework . . . . . . . . . 2
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Structure of the MIB Module . . . . . . . . . . . . . . . . . 3
4.1. The swmSupportedTunnelTable Subtree . . . . . . . . . . . 3
4.2. The swmEncapsTable Subtree . . . . . . . . . . . . . . . 3
4.3. The swmBGPNeighborTable Subtree . . . . . . . . . . . . . 4
4.4. The swmConformance Subtree . . . . . . . . . . . . . . . 4
5. Relationship to Other MIB Modules . . . . . . . . . . . . . . 4
5.1. Relationship to the IF-MIB . . . . . . . . . . . . . . . 4
5.2. Relationship to the IP Tunnel MIB . . . . . . . . . . . . 5
5.3. MIB Modules Required for IMPORTS . . . . . . . . . . . . 5
6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 6
7. Security Considerations . . . . . . . . . . . . . . . . . . . 13
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References . . . . . . . . . . . . . . . . . . 15
9.2. Informative References . . . . . . . . . . . . . . . . . 16
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . 2
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Structure of the MIB Module . . . . . . . . . . . . . . . . . 3
4.1. The swmSupportedTunnelTable Subtree . . . . . . . . . . . 3
4.2. The swmEncapsTable Subtree . . . . . . . . . . . . . . . 3
4.3. The swmBGPNeighborTable Subtree . . . . . . . . . . . . . 4
4.4. The swmConformance Subtree . . . . . . . . . . . . . . . 4
5. Relationship to Other MIB Modules . . . . . . . . . . . . . . 4
5.1. Relationship to the IF-MIB . . . . . . . . . . . . . . . 4
5.2. Relationship to the IP Tunnel MIB . . . . . . . . . . . . 5
5.3. MIB Modules Required for IMPORTS . . . . . . . . . . . . 5
6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 6
7. Security Considerations . . . . . . . . . . . . . . . . . . . 13
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References . . . . . . . . . . . . . . . . . . 15
9.2. Informative References . . . . . . . . . . . . . . . . . 16
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
The softwire mesh framework [RFC5565] is a tunneling mechanism that enables connectivity between islands of IPv4 networks across a single IPv6 backbone and vice versa. In a softwire mesh, extended Multiprotocol BGP (MP-BGP) is used to set up tunnels and advertise prefixes among Address Family Border Routers (AFBRs).
softwire mesh framework[RFC5565]是一种隧道机制，支持IPv4网络孤岛之间跨单个IPv6主干的连接，反之亦然。在软线网中，扩展多协议BGP（MP-BGP）用于在地址族边界路由器（AFBR）之间建立隧道和播发前缀。
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing a softwire mesh [RFC5565].
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它定义了用于管理软线网格的对象[RFC5565]。
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
有关描述当前互联网标准管理框架的文件的详细概述，请参阅RFC 3410[RFC3410]第7节。
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
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。此备忘录指定了一个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].
符合SMIv2的模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
This document uses terminology from the softwire problem statement [RFC4925], the BGP encapsulation Subsequent Address Family Identifier (SAFI), the BGP tunnel encapsulation attribute [RFC5512], the softwire mesh framework [RFC5565], and the BGP IPsec tunnel encapsulation attribute [RFC5566].
本文档使用来自软线问题声明[RFC4925]、BGP封装后续地址系列标识符（SAFI）、BGP隧道封装属性[RFC5512]、软线网格框架[RFC5565]和BGP IPsec隧道封装属性[RFC5566]的术语。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“建议”、“不建议”、“可”和“可选”应按照RFC 2119[RFC2119]中的说明进行解释。
The Softwire Mesh MIB provides a method to monitor the softwire mesh objects through SNMP.
Softwire Mesh MIB提供了一种通过SNMP监视Softwire Mesh对象的方法。
The swmSupportedTunnelTable subtree provides the information about what types of tunnels can be used for softwire mesh scenarios in the AFBR. The softwire mesh framework [RFC5565] does not mandate the use of any particular tunneling technology. Based on the BGP tunnel encapsulation attribute tunnel types introduced by RFC 5512 [RFC5512] and RFC 5566 [RFC5566], the softwire mesh tunnel types include at least L2TPv3 (Layer 2 Tunneling Protocol version 3) over IP, GRE (Generic Routing Encapsulation), Transmit tunnel endpoint, IPsec in Tunnel-mode, IP in IP tunnel with IPsec Transport Mode, MPLS-in-IP tunnel with IPsec Transport Mode, and IP in IP. The detailed encapsulation information of different tunnel types (e.g., L2TPv3 Session ID, GRE Key, etc.) is not managed in the Softwire Mesh MIB.
SWMsupportedTuneltable子树提供了有关AFBR中可用于软线网方案的隧道类型的信息。softwire mesh framework[RFC5565]不强制使用任何特定的隧道技术。基于RFC 5512[RFC5512]和RFC 5566[RFC5566]引入的BGP隧道封装属性隧道类型，软线网状隧道类型至少包括IP上的L2TPv3（第2层隧道协议版本3）、GRE（通用路由封装）、传输隧道端点、隧道模式下的IPsec、具有IPsec传输模式的IP隧道中的IP、，采用IPsec传输模式的IP隧道中的MPLS和IP中的IP。不同隧道类型（例如L2TPv3会话ID、GRE密钥等）的详细封装信息不在Softwire Mesh MIB中管理。
The swmEncapsTable subtree provides softwire mesh NLRI-NH information (Network Layer Reachability Information - Next Hop) about the AFBR. It keeps the mapping between the External-IP (E-IP) prefix and the Internal-IP (I-IP) address of the next hop. The mappings determine which I-IP destination address will be used to encapsulate the received packet according to its E-IP destination address. The definitions of E-IP and I-IP are explained in Section 4.1 of RFC 5565 [RFC5565]. The number of entries in swmEncapsTable shows how many softwire mesh tunnels are maintained in this AFBR.
swmEncapsTable子树提供关于AFBR的软线网状NLRI-NH信息（网络层可达性信息-下一跳）。它保持外部IP（E-IP）前缀和下一跳的内部IP（I-IP）地址之间的映射。映射确定将使用哪个I-IP目的地地址根据其E-IP目的地地址来封装所接收的分组。RFC 5565[RFC5565]第4.1节解释了E-IP和I-IP的定义。swmEncapsTable中的条目数显示了此AFBR中维护的软线网隧道数量。
This subtree provides the softwire mesh BGP neighbor information of an AFBR. It includes the address of the softwire mesh BGP peer and the kind of tunnel that the AFBR would use to communicate with this BGP peer.
此子树提供AFBR的softwire mesh BGP邻居信息。它包括软线网状BGP对等方的地址以及AFBR用于与该BGP对等方通信的隧道类型。
This subtree provides the conformance information of MIB objects.
此子树提供MIB对象的一致性信息。
The Interfaces MIB [RFC2863] defines generic managed objects for managing interfaces. Each logical interface (physical or virtual) has an ifEntry. Tunnels are handled by creating logical interfaces (ifEntry). Being a tunnel, the softwire mesh interface has an entry in the Interface MIB, as well as an entry in the IP Tunnel MIB. Those corresponding entries are indexed by ifIndex.
接口MIB[RFC2863]定义了用于管理接口的通用托管对象。每个逻辑接口（物理或虚拟）都有一个ifEntry。隧道是通过创建逻辑接口（ifEntry）来处理的。作为隧道，softwire mesh接口在接口MIB和IP隧道MIB中都有一个条目。这些对应的条目由ifIndex索引。
The ifOperStatus in the ifTable represents whether the mesh function of the AFBR has been triggered. If the softwire mesh capability is negotiated during the BGP OPEN phase, the mesh function is considered to be started, and the ifOperStatus is "up". Otherwise, the ifOperStatus is "down".
ifTable中的ifOperStatus表示是否已触发AFBR的网格功能。如果在BGP开放阶段协商了软线网格功能，则认为网格功能已启动，且iOperationStatus为“up”。否则，iOperationStatus为“down”。
In the case of an IPv4-over-IPv6 softwire mesh tunnel, ifInUcastPkts counts the number of IPv6 packets that are sent to the virtual interface for decapsulation into IPv4. The ifOutUcastPkts counts the number of IPv6 packets that are generated by encapsulating IPv4 packets sent to the virtual interface. In particular, if these IPv4 packets need fragmentation, ifOutUcastPkts counts the number of packets after fragmentation.
在IPv4-over-IPv6软线网状隧道的情况下，ifInUcastPkts统计发送到虚拟接口以解封装为IPv4的IPv6数据包的数量。ifOutUcastPkts统计通过封装发送到虚拟接口的IPv4数据包而生成的IPv6数据包数。特别是，如果这些IPv4数据包需要分段，ifOutUcastPkts会统计分段后的数据包数。
In the case of an IPv6-over-IPv4 softwire mesh tunnel, ifInUcastPkts counts the number of IPv4 packets that are delivered to the virtual interface for decapsulation into IPv6. The ifOutUcastPkts counts the number of IPv4 packets that are generated by encapsulating IPv6 packets sent down to the virtual interface. In particular, if these IPv6 packets need to be fragmented, ifOutUcastPkts counts the number of packets after fragmentation. Similar definitions apply to other counter objects in the ifTable.
在IPv6-over-IPv4软线网状隧道的情况下，ifInUcastPkts统计传递到虚拟接口以解封装到IPv6的IPv4数据包数。ifOutUcastPkts统计通过封装发送到虚拟接口的IPv6数据包而生成的IPv4数据包数。特别是，如果这些IPv6数据包需要分段，ifOutUcastPkts会统计分段后的数据包数量。类似的定义适用于ifTable中的其他计数器对象。
The IP Tunnel MIB [RFC4087] contains objects applicable to all IP tunnels, including softwire mesh tunnels. Meanwhile, the Softwire Mesh MIB extends the IP Tunnel MIB to further describe encapsulation-specific information.
IP隧道MIB[RFC4087]包含适用于所有IP隧道的对象，包括软线网状隧道。同时，软线网状MIB扩展了IP隧道MIB以进一步描述封装特定信息。
When running a point-to-multipoint tunnel, it is necessary for a softwire mesh AFBR to maintain an encapsulation table in order to perform correct "forwarding" among AFBRs. This forwarding function on an AFBR is performed by using the E-IP destination address to look up the I-IP encapsulation destination address in the encapsulation table. An AFBR also needs to know the BGP peer information of the other AFBRs, so that it can negotiate the NLRI-NH information and the tunnel parameters with them.
运行点对多点隧道时，软线网状AFBR需要维护封装表，以便在AFBR之间执行正确的“转发”。AFBR上的此转发功能通过使用E-IP目标地址在封装表中查找I-IP封装目标地址来执行。AFBR还需要知道其他AFBR的BGP对等信息，以便能够与它们协商NLRI-NH信息和隧道参数。
The Softwire Mesh MIB requires the implementation of the IP Tunnel MIB. The tunnelIfEncapsMethod in the tunnelIfEntry MUST be set to softwireMesh(16), and a corresponding entry in the Softwire Mesh MIB module will be presented for the tunnelIfEntry. The tunnelIfRemoteInetAddress MUST be set to "0.0.0.0" for IPv4 or "::" for IPv6 because it is a point-to-multipoint tunnel.
Softwire Mesh MIB需要实现IP隧道MIB。TunnelEntry中的TunnelLifenCapsMethod必须设置为softwireMesh（16），并且将在Softwire Mesh MIB模块中为TunnelEntry显示相应的条目。对于IPv4，tunnelIfRemoteInetAddress必须设置为“0.0.0.0”，对于IPv6，必须设置为“：”，因为它是一个点对多点隧道。
The tunnelIfAddressType in the tunnelIfTable represents the type of address in the corresponding tunnelIfLocalInetAddress and tunnelIfRemoteInetAddress objects. The tunnelIfAddressType is identical to swmEncapsIIPDstType in softwire mesh, which can support either IPv4-over-IPv6 or IPv6-over-IPv4. When the swmEncapsEIPDstType is IPv6 and the swmEncapsIIPDstType is IPv4, the tunnel type is IPv6-over-IPv4; when the swmEncapsEIPDstType is IPv4 and the swmEncapsIIPDstType is IPv6, the encapsulation mode is IPv4- over-IPv6.
tunnelIfTable中的tunnelIfAddressType表示对应tunnelIfLocalInetAddress和tunnelIfRemoteInetAddress对象中的地址类型。tunnelIfAddressType与softwire mesh中的swmEncapsIIPDstType相同，后者可以支持IPv4-over-IPv6或IPv6-over-IPv4。当swmEncapsEIPDstType为IPv6，swmEncapsIIPDstType为IPv4时，隧道类型为IPv6-over-IPv4；当swmEncapsEIPDstType为IPv4且swmEncapsIIPDstType为IPv6时，封装模式为IPv4-over-IPv6。
The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863], and INET-ADDRESS-MIB [RFC4001].
以下MIB模块从SNMPv2 SMI[RFC2578]、SNMPv2 CONF[RFC2580]、IF-MIB[RFC2863]和INET-ADDRESS-MIB[RFC4001]导入对象。
SOFTWIRE-MESH-MIB DEFINITIONS ::= BEGIN
SOFTWIRE-MESH-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, mib-2 FROM SNMPv2-SMI
从SNMPv2 SMI导入模块标识、对象类型、mib-2
OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF
SNMPv2 CONF中的对象组、模块符合性
InetAddress, InetAddressType, InetAddressPrefixLength
InetAddress，InetAddressType，InetAddressPrefixLength
FROM INET-ADDRESS-MIB
来自INET-ADDRESS-MIB
ifIndex FROM IF-MIB
来自IF-MIB的ifIndex
IANAtunnelType FROM IANAifType-MIB;
IANAifType MIB中的IANAtunnelType；
swmMIB MODULE-IDENTITY LAST-UPDATED "201605110000Z" -- May 11, 2016 ORGANIZATION "Softwire Working Group" CONTACT-INFO "Yong Cui Email: yong@csnet1.cs.tsinghua.edu.cn
swmMIB模块标识最后一次更新“2016051110000Z”-2016年5月11日组织“软线工作组”联系方式“Yong Cui电子邮件：yong@csnet1.cs.tsinghua.edu.cn
Jiang Dong Email: knight.dongjiang@gmail.com
江东电邮：奈特。dongjiang@gmail.com
Peng Wu Email: weapon9@gmail.com
吴鹏电邮：weapon9@gmail.com
Mingwei Xu Email: xmw@cernet.edu.cn
徐明伟电子邮件：xmw@cernet.edu.cn
Antti Yla-Jaaski Email: antti.yla-jaaski@aalto.fi
Antti Yla Jaaski电子邮件：Antti.Yla-jaaski@aalto.fi
Email comments directly to the Softwire WG Mailing List at softwires@ietf.org " DESCRIPTION "This MIB module contains managed object definitions for the softwire mesh framework.
将评论直接通过电子邮件发送至Softwire WG邮件列表softwires@ietf.org“说明”此MIB模块包含softwire网格框架的托管对象定义。
Copyright (c) 2016 IETF Trust and the persons identified as authors of the code. All rights reserved.
版权所有（c）2016 IETF信托基金和被确定为代码作者的人员。版权所有。
Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and
允许以源代码和二进制形式重新分发和使用，无论是否修改，以及
subject to the license terms contained in, the Simplified
BSD License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info)."
REVISION "201605110000Z"
DESCRIPTION "Initial version, published as RFC 7856"
::= { mib-2 239 }
subject to the license terms contained in, the Simplified
BSD License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info)."
REVISION "201605110000Z"
DESCRIPTION "Initial version, published as RFC 7856"
::= { mib-2 239 }
swmObjects OBJECT IDENTIFIER ::= { swmMIB 1 }
swmObjects OBJECT IDENTIFIER ::= { swmMIB 1 }
-- swmSupportedTunnelTable
swmSupportedTunnelTable OBJECT-TYPE
SYNTAX SEQUENCE OF SwmSupportedTunnelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that show what kinds of tunnels
can be supported by the AFBR."
::= { swmObjects 1 }
-- swmSupportedTunnelTable
swmSupportedTunnelTable OBJECT-TYPE
SYNTAX SEQUENCE OF SwmSupportedTunnelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that show what kinds of tunnels
can be supported by the AFBR."
::= { swmObjects 1 }
swmSupportedTunnelEntry OBJECT-TYPE
SYNTAX SwmSupportedTunnelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that show what kinds of tunnels
can be supported in the AFBR. If the AFBR supports
multiple tunnel types, the swmSupportedTunnelTable
would have several entries."
INDEX { swmSupportedTunnelType }
::= { swmSupportedTunnelTable 1 }
swmSupportedTunnelEntry OBJECT-TYPE
SYNTAX SwmSupportedTunnelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that show what kinds of tunnels
can be supported in the AFBR. If the AFBR supports
multiple tunnel types, the swmSupportedTunnelTable
would have several entries."
INDEX { swmSupportedTunnelType }
::= { swmSupportedTunnelTable 1 }
SwmSupportedTunnelEntry ::= SEQUENCE {
swmSupportedTunnelType IANAtunnelType
}
SwmSupportedTunnelEntry ::= SEQUENCE {
swmSupportedTunnelType IANAtunnelType
}
swmSupportedTunnelType OBJECT-TYPE SYNTAX IANAtunnelType MAX-ACCESS read-only STATUS current DESCRIPTION "Represents the tunnel type that can be used for softwire mesh scenarios, such as L2TPv3 over IP, GRE, Transmit tunnel endpoint, IPsec in Tunnel-mode, IP in IP tunnel with IPsec Transport Mode, MPLS-in-IP tunnel with IPsec Transport Mode, and IP in IP. There is no restriction on the tunnel type the softwire mesh can use." REFERENCE
SWMS支持的TunnelType对象类型语法IANAtunnelType MAX-ACCESS只读状态当前说明“表示可用于软线网格方案的隧道类型，例如L2TPv3 over IP、GRE、传输隧道端点、隧道模式中的IPsec、具有IPsec传输模式的IP隧道中的IP、具有IPsec传输模式的IP隧道中的MPLS以及IP中的IP。软线网可以使用的隧道类型没有限制。”参考
"L2TPv3 over IP, GRE, and IP in IP in RFC 5512.
Transmit tunnel endpoint, IPsec in Tunnel-mode, IP in IP
tunnel with IPsec Transport Mode, MPLS-in-IP tunnel with
IPsec Transport Mode in RFC 5566."
::= { swmSupportedTunnelEntry 1 }
"L2TPv3 over IP, GRE, and IP in IP in RFC 5512.
Transmit tunnel endpoint, IPsec in Tunnel-mode, IP in IP
tunnel with IPsec Transport Mode, MPLS-in-IP tunnel with
IPsec Transport Mode in RFC 5566."
::= { swmSupportedTunnelEntry 1 }
-- end of swmSupportedTunnelTable
--SWM支持的末端不可熔化
--swmEncapsTable
swmEncapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SwmEncapsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display the
softwire mesh encapsulation information."
::= { swmObjects 2 }
--swmEncapsTable
swmEncapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SwmEncapsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display the
softwire mesh encapsulation information."
::= { swmObjects 2 }
swmEncapsEntry OBJECT-TYPE
SYNTAX SwmEncapsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that manage the softwire mesh I-IP
encapsulation destination based on the E-IP destination
prefix."
INDEX { ifIndex,
swmEncapsEIPDstType,
swmEncapsEIPDst,
swmEncapsEIPPrefixLength
}
::= { swmEncapsTable 1 }
swmEncapsEntry OBJECT-TYPE
SYNTAX SwmEncapsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that manage the softwire mesh I-IP
encapsulation destination based on the E-IP destination
prefix."
INDEX { ifIndex,
swmEncapsEIPDstType,
swmEncapsEIPDst,
swmEncapsEIPPrefixLength
}
::= { swmEncapsTable 1 }
SwmEncapsEntry ::= SEQUENCE {
swmEncapsEIPDstType InetAddressType,
swmEncapsEIPDst InetAddress,
swmEncapsEIPPrefixLength InetAddressPrefixLength,
swmEncapsIIPDstType InetAddressType,
swmEncapsIIPDst InetAddress
}
SwmEncapsEntry ::= SEQUENCE {
swmEncapsEIPDstType InetAddressType,
swmEncapsEIPDst InetAddress,
swmEncapsEIPPrefixLength InetAddressPrefixLength,
swmEncapsIIPDstType InetAddressType,
swmEncapsIIPDst InetAddress
}
swmEncapsEIPDstType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object specifies the address type used for swmEncapsEIPDst. It is different from the
SWMENCAPSEIPDSTYPE对象类型语法InetAddressType MAX-ACCESS不可访问状态当前描述“此对象指定用于swmEncapsEIPDst的地址类型。它与
tunnelIfAddressType in the tunnelIfTable. The
swmEncapsEIPDstType is IPv6 (2) if it is IPv6-over-IPv4
tunneling. The swmEncapsEIPDstType is
IPv4 (1) if it is IPv4-over-IPv6 tunneling."
REFERENCE
"IPv4 and IPv6 in RFC 4001."
::= { swmEncapsEntry 1 }
tunnelIfAddressType in the tunnelIfTable. The
swmEncapsEIPDstType is IPv6 (2) if it is IPv6-over-IPv4
tunneling. The swmEncapsEIPDstType is
IPv4 (1) if it is IPv4-over-IPv6 tunneling."
REFERENCE
"IPv4 and IPv6 in RFC 4001."
::= { swmEncapsEntry 1 }
swmEncapsEIPDst OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The E-IP destination prefix, which is
used for I-IP encapsulation destination looking up.
The type of this address is determined by the
value of swmEncapsEIPDstType"
REFERENCE
"E-IP and I-IP in RFC 5565."
::= { swmEncapsEntry 2 }
swmEncapsEIPDst OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The E-IP destination prefix, which is
used for I-IP encapsulation destination looking up.
The type of this address is determined by the
value of swmEncapsEIPDstType"
REFERENCE
"E-IP and I-IP in RFC 5565."
::= { swmEncapsEntry 2 }
swmEncapsEIPPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The prefix length of the E-IP destination prefix."
::= { swmEncapsEntry 3 }
swmEncapsEIPPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The prefix length of the E-IP destination prefix."
::= { swmEncapsEntry 3 }
swmEncapsIIPDstType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the address type used for
swmEncapsIIPDst. It is the same as the tunnelIfAddressType
in the tunnelIfTable."
REFERENCE
"IPv4 and IPv6 in RFC 4001."
::= { swmEncapsEntry 4 }
swmEncapsIIPDstType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the address type used for
swmEncapsIIPDst. It is the same as the tunnelIfAddressType
in the tunnelIfTable."
REFERENCE
"IPv4 and IPv6 in RFC 4001."
::= { swmEncapsEntry 4 }
swmEncapsIIPDst OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The I-IP destination address, which is used as the encapsulation destination for the corresponding E-IP
swmEncapsIIPDst对象类型语法InetAddress MAX-ACCESS只读状态当前描述“I-IP目标地址，用作相应E-IP的封装目标
prefix. Since the tunnelIfRemoteInetAddress in the
tunnelIfTable should be 0.0.0.0 or ::, swmEncapIIPDst
should be the destination address used in the outer
IP header."
REFERENCE
"E-IP and I-IP in RFC 5565."
::= { swmEncapsEntry 5 }
-- End of swmEncapsTable
prefix. Since the tunnelIfRemoteInetAddress in the
tunnelIfTable should be 0.0.0.0 or ::, swmEncapIIPDst
should be the destination address used in the outer
IP header."
REFERENCE
"E-IP and I-IP in RFC 5565."
::= { swmEncapsEntry 5 }
-- End of swmEncapsTable
-- swmBGPNeighborTable
swmBGPNeighborTable OBJECT-TYPE
SYNTAX SEQUENCE OF SwmBGPNeighborEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display the softwire mesh
BGP neighbor information."
::= { swmObjects 3 }
-- swmBGPNeighborTable
swmBGPNeighborTable OBJECT-TYPE
SYNTAX SEQUENCE OF SwmBGPNeighborEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display the softwire mesh
BGP neighbor information."
::= { swmObjects 3 }
swmBGPNeighborEntry OBJECT-TYPE
SYNTAX SwmBGPNeighborEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that display the softwire mesh
BGP neighbor information."
INDEX {
ifIndex,
swmBGPNeighborInetAddressType,
swmBGPNeighborInetAddress
}
::= { swmBGPNeighborTable 1 }
swmBGPNeighborEntry OBJECT-TYPE
SYNTAX SwmBGPNeighborEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that display the softwire mesh
BGP neighbor information."
INDEX {
ifIndex,
swmBGPNeighborInetAddressType,
swmBGPNeighborInetAddress
}
::= { swmBGPNeighborTable 1 }
SwmBGPNeighborEntry ::= SEQUENCE {
swmBGPNeighborInetAddressType InetAddressType,
swmBGPNeighborInetAddress InetAddress,
swmBGPNeighborTunnelType IANAtunnelType
}
SwmBGPNeighborEntry ::= SEQUENCE {
swmBGPNeighborInetAddressType InetAddressType,
swmBGPNeighborInetAddress InetAddress,
swmBGPNeighborTunnelType IANAtunnelType
}
swmBGPNeighborInetAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object specifies the address type used for
swmBGPNeighborInetAddress."
::= { swmBGPNeighborEntry 1 }
swmBGPNeighborInetAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object specifies the address type used for
swmBGPNeighborInetAddress."
::= { swmBGPNeighborEntry 1 }
swmBGPNeighborInetAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The address of the AFBR's BGP neighbor. The
address type is the same as the tunnelIfAddressType
in the tunnelIfTable."
::= { swmBGPNeighborEntry 2 }
swmBGPNeighborInetAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The address of the AFBR's BGP neighbor. The
address type is the same as the tunnelIfAddressType
in the tunnelIfTable."
::= { swmBGPNeighborEntry 2 }
swmBGPNeighborTunnelType OBJECT-TYPE
SYNTAX IANAtunnelType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the type of tunnel that the AFBR
chooses to transmit traffic with another AFBR/BGP
neighbor."
::= { swmBGPNeighborEntry 3 }
-- End of swmBGPNeighborTable
swmBGPNeighborTunnelType OBJECT-TYPE
SYNTAX IANAtunnelType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the type of tunnel that the AFBR
chooses to transmit traffic with another AFBR/BGP
neighbor."
::= { swmBGPNeighborEntry 3 }
-- End of swmBGPNeighborTable
-- conformance information
swmConformance
OBJECT IDENTIFIER ::= { swmMIB 2 }
swmCompliances
OBJECT IDENTIFIER ::= { swmConformance 1 }
swmGroups
OBJECT IDENTIFIER ::= { swmConformance 2 }
-- conformance information
swmConformance
OBJECT IDENTIFIER ::= { swmMIB 2 }
swmCompliances
OBJECT IDENTIFIER ::= { swmConformance 1 }
swmGroups
OBJECT IDENTIFIER ::= { swmConformance 2 }
-- compliance statements swmCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Describes the requirements for conformance to the Softwire Mesh MIB.
--合规性声明SWMC合规性模块-合规性状态当前描述”描述了符合软线网状MIB的要求。
The following index objects cannot be added as OBJECT
clauses but nevertheless have compliance requirements:
"
-- OBJECT swmEncapsEIPDstType
-- SYNTAX InetAddressType { ipv4(1), ipv6(2) }
-- DESCRIPTION
-- "An implementation is required to support
-- global IPv4 and/or IPv6 addresses, depending
-- on its support for IPv4 and IPv6."
The following index objects cannot be added as OBJECT
clauses but nevertheless have compliance requirements:
"
-- OBJECT swmEncapsEIPDstType
-- SYNTAX InetAddressType { ipv4(1), ipv6(2) }
-- DESCRIPTION
-- "An implementation is required to support
-- global IPv4 and/or IPv6 addresses, depending
-- on its support for IPv4 and IPv6."
-- OBJECT swmEncapsEIPDst
--对象swmEncapsEIPDst
-- SYNTAX InetAddress (SIZE(4|16))
-- DESCRIPTION
-- "An implementation is required to support
-- global IPv4 and/or IPv6 addresses, depending
-- on its support for IPv4 and IPv6."
-- SYNTAX InetAddress (SIZE(4|16))
-- DESCRIPTION
-- "An implementation is required to support
-- global IPv4 and/or IPv6 addresses, depending
-- on its support for IPv4 and IPv6."
-- OBJECT swmEncapsEIPPrefixLength
-- SYNTAX InetAddressPrefixLength (Unsigned32 (0..128))
-- DESCRIPTION
-- "An implementation is required to support
-- global IPv4 and/or IPv6 addresses, depending
-- on its support for IPv4 and IPv6."
-- OBJECT swmEncapsEIPPrefixLength
-- SYNTAX InetAddressPrefixLength (Unsigned32 (0..128))
-- DESCRIPTION
-- "An implementation is required to support
-- global IPv4 and/or IPv6 addresses, depending
-- on its support for IPv4 and IPv6."
-- OBJECT swmBGPNeighborInetAddressType
-- SYNTAX InetAddressType { ipv4(1), ipv6(2) }
-- DESCRIPTION
-- "An implementation is required to support
-- global IPv4 and/or IPv6 addresses, depending
-- on its support for IPv4 and IPv6."
-- OBJECT swmBGPNeighborInetAddressType
-- SYNTAX InetAddressType { ipv4(1), ipv6(2) }
-- DESCRIPTION
-- "An implementation is required to support
-- global IPv4 and/or IPv6 addresses, depending
-- on its support for IPv4 and IPv6."
-- OBJECT swmBGPNeighborInetAddress
-- SYNTAX InetAddress (SIZE(4|16))
-- DESCRIPTION
-- "An implementation is required to support
-- global IPv4 and/or IPv6 addresses, depending
-- on its support for IPv4 and IPv6."
-- OBJECT swmBGPNeighborInetAddress
-- SYNTAX InetAddress (SIZE(4|16))
-- DESCRIPTION
-- "An implementation is required to support
-- global IPv4 and/or IPv6 addresses, depending
-- on its support for IPv4 and IPv6."
MODULE -- this module
MANDATORY-GROUPS {
swmSupportedTunnelGroup,
swmEncapsGroup,
swmBGPNeighborGroup
}
::= { swmCompliances 1 }
MODULE -- this module
MANDATORY-GROUPS {
swmSupportedTunnelGroup,
swmEncapsGroup,
swmBGPNeighborGroup
}
::= { swmCompliances 1 }
swmSupportedTunnelGroup OBJECT-GROUP
OBJECTS {
swmSupportedTunnelType
}
STATUS current
DESCRIPTION
"The collection of objects that are used to show
what kind of tunnel the AFBR supports."
::= { swmGroups 1 }
swmSupportedTunnelGroup OBJECT-GROUP
OBJECTS {
swmSupportedTunnelType
}
STATUS current
DESCRIPTION
"The collection of objects that are used to show
what kind of tunnel the AFBR supports."
::= { swmGroups 1 }
swmEncapsGroup OBJECT-GROUP OBJECTS { swmEncapsIIPDst,
swmEncapsGroup对象组对象{swmEncapsIIPDst，
swmEncapsIIPDstType
}
STATUS current
DESCRIPTION
"The collection of objects that are used to display
softwire mesh encapsulation information."
::= { swmGroups 2 }
swmEncapsIIPDstType
}
STATUS current
DESCRIPTION
"The collection of objects that are used to display
softwire mesh encapsulation information."
::= { swmGroups 2 }
swmBGPNeighborGroup OBJECT-GROUP
OBJECTS {
swmBGPNeighborTunnelType
}
STATUS current
DESCRIPTION
"The collection of objects that are used to display
softwire mesh BGP neighbor information."
::= { swmGroups 3 }
swmBGPNeighborGroup OBJECT-GROUP
OBJECTS {
swmBGPNeighborTunnelType
}
STATUS current
DESCRIPTION
"The collection of objects that are used to display
softwire mesh BGP neighbor information."
::= { swmGroups 3 }
END
终止
Because this MIB module reuses the IP Tunnel MIB, the security considerations of the IP Tunnel MIB are also applicable to the Softwire Mesh MIB.
由于此MIB模块重用IP隧道MIB，因此IP隧道MIB的安全考虑也适用于软线网状MIB。
There are no management objects defined in this MIB module that have a MAX-ACCESS clause of read-write and/or read-create. So, if this MIB module is implemented correctly, then there is no risk that an intruder can alter or create any management objects of this MIB module via direct SNMP SET operations.
此MIB模块中未定义具有读写和/或读创建MAX-ACCESS子句的管理对象。因此，如果此MIB模块实现正确，则入侵者不会通过直接的SNMP集操作更改或创建此MIB模块的任何管理对象。
Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the objects and their sensitivity/ vulnerability:
在某些网络环境中，此MIB模块中的某些可读对象（即具有MAX-ACCESS而非not ACCESS的对象）可能被视为敏感或易受攻击。因此，在通过SNMP通过网络发送这些对象时，控制甚至获取和/或通知对这些对象的访问，甚至可能加密这些对象的值，这一点非常重要。这些是对象及其敏感度/脆弱性：
swmSupportedTunnelType, swmEncapsIIPDstType, swmEncapsIIPDst, and swmBGPNeighborTunnelType can expose the types of tunnels used within the internal network and potentially reveal the topology of the internal network.
SWMS支持的隧道类型、SWMENCAPSIIPDSTYPE、swmEncapsIIPDst和SWMBGPNEXTERTUNNELTYPE可以显示内部网络中使用的隧道类型，并可能显示内部网络的拓扑结构。
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module.
SNMPv3之前的SNMP版本未包含足够的安全性。即使网络本身是安全的（例如通过使用IPsec），也无法控制安全网络上的谁可以访问和获取/设置（读取/更改/创建/删除）此MIB模块中的对象。
Implementations SHOULD provide the security features described by the
SNMPv3 framework (see [RFC3410]), and implementations claiming
compliance to the SNMPv3 standard MUST include full support for
authentication and privacy via the User-based Security Model (USM)
[RFC3414] with the AES cipher algorithm [RFC3826]. Implementations
MAY also provide support for the Transport Security Model (TSM)
[RFC5591] in combination with a secure transport such as SSH
[RFC5592] or TLS/DTLS [RFC6353].
Implementations SHOULD provide the security features described by the
SNMPv3 framework (see [RFC3410]), and implementations claiming
compliance to the SNMPv3 standard MUST include full support for
authentication and privacy via the User-based Security Model (USM)
[RFC3414] with the AES cipher algorithm [RFC3826]. Implementations
MAY also provide support for the Transport Security Model (TSM)
[RFC5591] in combination with a secure transport such as SSH
[RFC5592] or TLS/DTLS [RFC6353].
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.
此外，不建议部署SNMPv3之前的SNMP版本。相反，建议部署SNMPv3并启用加密安全性。然后，客户/运营商应负责确保授予访问此MIB模块实例权限的SNMP实体已正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）访问对象。
IANA has allocated the following OBJECT IDENTIFIER value and recorded it in the SMI Numbers registry in the subregistry called "SMI Network Management MGMT Codes Internet-standard MIB" under the mib-2 branch (1.3.6.1.2.1):
IANA已分配以下对象标识符值，并将其记录在MIB-2分支（1.3.6.1.2.1）下名为“SMI网络管理代码互联网标准MIB”的子区域的SMI编号注册表中：
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
swmMIB { mib-2 239 }
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
swmMIB { mib-2 239 }
IANA has recorded the following IANAtunnelType Textual Convention within the IANAifType-MIB:
IANA在IANAifType MIB中记录了以下IANAtunnelType文本约定：
IANAtunnelType ::= TEXTUAL-CONVENTION
SYNTAX INTEGER {
softwireMesh(16) -- softwire mesh tunnel
}
IANAtunnelType ::= TEXTUAL-CONVENTION
SYNTAX INTEGER {
softwireMesh(16) -- softwire mesh tunnel
}
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，DOI 10.17487/RFC2119，1997年3月<http://www.rfc-editor.org/info/rfc2119>.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/RFC2578, April 1999, <http://www.rfc-editor.org/info/rfc2578>.
[RFC2578]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，DOI 10.17487/RFC2578，1999年4月<http://www.rfc-editor.org/info/rfc2578>.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, <http://www.rfc-editor.org/info/rfc2579>.
[RFC2579]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“SMIv2的文本约定”，STD 58，RFC 2579，DOI 10.17487/RFC2579，1999年4月<http://www.rfc-editor.org/info/rfc2579>.
[RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Conformance Statements for SMIv2", STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, <http://www.rfc-editor.org/info/rfc2580>.
[RFC2580]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“SMIv2的一致性声明”，STD 58，RFC 2580，DOI 10.17487/RFC2580，1999年4月<http://www.rfc-editor.org/info/rfc2580>.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/RFC3414, December 2002, <http://www.rfc-editor.org/info/rfc3414>.
[RFC3414]Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）版本3的基于用户的安全模型（USM）”，STD 62，RFC 3414，DOI 10.17487/RFC3414，2002年12月<http://www.rfc-editor.org/info/rfc3414>.
[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model", RFC 3826, DOI 10.17487/RFC3826, June 2004, <http://www.rfc-editor.org/info/rfc3826>.
[RFC3826]Blumenthal，U.，Maino，F.，和K.McCloghrie，“基于SNMP用户的安全模型中的高级加密标准（AES）密码算法”，RFC 3826，DOI 10.17487/RFC3826，2004年6月<http://www.rfc-editor.org/info/rfc3826>.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 4001, DOI 10.17487/RFC4001, February 2005, <http://www.rfc-editor.org/info/rfc4001>.
[RFC4001]Daniele，M.，Haberman，B.，Routhier，S.，和J.Schoenwaeld，“互联网网络地址的文本约定”，RFC 4001，DOI 10.17487/RFC4001，2005年2月<http://www.rfc-editor.org/info/rfc4001>.
[RFC5512] Mohapatra, P. and E. Rosen, "The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute", RFC 5512, DOI 10.17487/RFC5512, April 2009, <http://www.rfc-editor.org/info/rfc5512>.
[RFC5512]Mohapatra，P.和E.Rosen，“BGP封装后续地址族标识符（SAFI）和BGP隧道封装属性”，RFC 5512，DOI 10.17487/RFC5512，2009年4月<http://www.rfc-editor.org/info/rfc5512>.
[RFC5565] Wu, J., Cui, Y., Metz, C., and E. Rosen, "Softwire Mesh Framework", RFC 5565, DOI 10.17487/RFC5565, June 2009, <http://www.rfc-editor.org/info/rfc5565>.
[RFC5565]Wu，J.，Cui，Y.，Metz，C.和E.Rosen，“软线网格框架”，RFC 5565，DOI 10.17487/RFC5565，2009年6月<http://www.rfc-editor.org/info/rfc5565>.
[RFC5566] Berger, L., White, R., and E. Rosen, "BGP IPsec Tunnel Encapsulation Attribute", RFC 5566, DOI 10.17487/RFC5566, June 2009, <http://www.rfc-editor.org/info/rfc5566>.
[RFC5566]Berger，L.，White，R.，和E.Rosen，“BGP IPsec隧道封装属性”，RFC 5566，DOI 10.17487/RFC5566，2009年6月<http://www.rfc-editor.org/info/rfc5566>.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model for the Simple Network Management Protocol (SNMP)", STD 78, RFC 5591, DOI 10.17487/RFC5591, June 2009, <http://www.rfc-editor.org/info/rfc5591>.
[RFC5591]Harrington，D.和W.Hardaker，“简单网络管理协议（SNMP）的传输安全模型”，STD 78，RFC 5591，DOI 10.17487/RFC55912009年6月<http://www.rfc-editor.org/info/rfc5591>.
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure Shell Transport Model for the Simple Network Management Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June 2009, <http://www.rfc-editor.org/info/rfc5592>.
[RFC5592]Harrington，D.，Salowey，J.，和W.Hardaker，“简单网络管理协议（SNMP）的安全外壳传输模型”，RFC 5592，DOI 10.17487/RFC5592，2009年6月<http://www.rfc-editor.org/info/rfc5592>.
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)", STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, <http://www.rfc-editor.org/info/rfc6353>.
[RFC6353]Hardaker，W.“简单网络管理协议（SNMP）的传输层安全（TLS）传输模型”，STD 78，RFC 6353，DOI 10.17487/RFC6353，2011年7月<http://www.rfc-editor.org/info/rfc6353>.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, <http://www.rfc-editor.org/info/rfc2863>.
[RFC2863]McCloghrie，K.和F.Kastenholz，“接口组MIB”，RFC 2863，DOI 10.17487/RFC2863，2000年6月<http://www.rfc-editor.org/info/rfc2863>.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, DOI 10.17487/RFC3410, December 2002, <http://www.rfc-editor.org/info/rfc3410>.
[RFC3410]Case，J.，Mundy，R.，Partain，D.，和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 3410，DOI 10.17487/RFC3410，2002年12月<http://www.rfc-editor.org/info/rfc3410>.
[RFC4087] Thaler, D., "IP Tunnel MIB", RFC 4087, DOI 10.17487/RFC4087, June 2005, <http://www.rfc-editor.org/info/rfc4087>.
[RFC4087]Thaler，D.，“IP隧道MIB”，RFC 4087，DOI 10.17487/RFC4087，2005年6月<http://www.rfc-editor.org/info/rfc4087>.
[RFC4925] Li, X., Ed., Dawkins, S., Ed., Ward, D., Ed., and A. Durand, Ed., "Softwire Problem Statement", RFC 4925, DOI 10.17487/RFC4925, July 2007, <http://www.rfc-editor.org/info/rfc4925>.
[RFC4925]Li，X.，Ed.，Dawkins，S.，Ed.，Ward，D.，Ed.，和A.Durand，Ed.，“软线问题声明”，RFC 4925，DOI 10.17487/RFC4925，2007年7月<http://www.rfc-editor.org/info/rfc4925>.
Acknowledgements
致谢
The authors would like to thank Dave Thaler, Jean-Philippe Dionne, Qi Sun, Sheng Jiang, and Yu Fu for their valuable comments.
作者要感谢Dave Thaler、Jean-Philippe Dionne、齐孙、盛江和余福的宝贵评论。
Authors' Addresses
作者地址
Yong Cui Tsinghua University Department of Computer Science, Tsinghua University Beijing 100084 China
清华大学计算机科学系北京100084
Phone: +86-10-6260-3059
Email: yong@csnet1.cs.tsinghua.edu.cn
Phone: +86-10-6260-3059
Email: yong@csnet1.cs.tsinghua.edu.cn
Jiang Dong Tsinghua University Department of Computer Science, Tsinghua University Beijing 100084 China
江东清华大学计算机科学系，清华大学北京100084
Phone: +86-10-6278-5822
Email: knight.dongjiang@gmail.com
Phone: +86-10-6278-5822
Email: knight.dongjiang@gmail.com
Peng Wu Tsinghua University Department of Computer Science, Tsinghua University Beijing 100084 China
吴鹏清华大学计算机科学系，清华大学北京100084
Phone: +86-10-6278-5822
Email: weapon9@gmail.com
Phone: +86-10-6278-5822
Email: weapon9@gmail.com
Mingwei Xu Tsinghua University Department of Computer Science, Tsinghua University Beijing 100084 China
徐明伟清华大学计算机科学系，清华大学北京100084
Phone: +86-10-6278-5822
Email: xmw@cernet.edu.cn
Phone: +86-10-6278-5822
Email: xmw@cernet.edu.cn
Antti Yla-Jaaski Aalto University Konemiehentie 2 Espoo 02150 Finland
芬兰科内米汉蒂大学2埃斯波02150
Phone: +358-40-5954222
Email: antti.yla-jaaski@aalto.fi
Phone: +358-40-5954222
Email: antti.yla-jaaski@aalto.fi