Network Working Group Y. Fu
Internet Draft S. Jiang
Intended status: Standards Track B.Liu
Expires: January 18, 2013 Huawei Technologies Co., Ltd
J.Dong
P. Wu
Tsinghua University
July 16, 2012
Definitions of Managed Objects for MAP-E
draft-fu-softwire-map-mib-01
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute working
documents as Internet-Drafts. The list of current Internet-Drafts is
at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 18, 2013.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
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.
Fu, et al. Expires January 18, 2013 [Page 1]
Internet-Draft draft-fu-softwire-map-mib-01.txt July 2012
Abstract
This memo defines a portion of the Management Information Base
(MIB) for using with network management protocols in the Internet
community.In particular, it defines managed objects for MAP
encapsulation mode.
Table of Contents
1. Introduction ................................................. 3
2. The Internet-Standard Management Framework ................... 3
3. Terminology .................................................. 3
4. Structure of the MIB Module .................................. 3
4.1. The mapTunnel Subtree ................................... 4
4.2. The mapStatisticInfo Subtree ............................ 4
4.3. The mapTrap Subtree ..................................... 4
4.4. The mapConformance Subtree .............................. 4
5. MIB modules required for IMPORTS ............................. 4
6. Definitions .................................................. 4
7. IANA Considerations ......................................... 13
8. Security Considerations ..................................... 13
9. References .................................................. 14
9.1. Normative References ................................... 14
9.2. Informative References ................................. 14
10. Change Log [RFC Editor please remove] ...................... 15
Author's Addresses ............................................. 15
Fu, et al. Expires January 18, 2013 [Page 2]
Internet-Draft draft-fu-softwire-map-mib-01.txt July 2012
1. Introduction
MAP [I-D. draft-ietf-softwire-map] is a stateless mechanism for
running IPv4 over IPv6-only infrastructure. In particular, it
includes two mode, translation mode or encapsulation mode. For the
encapsulation mode, it provides an automatic tunnelling mechanism for
providing IPv4 connectivity service to end users over a service
provider's IPv6 network.
This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet
community. This MIB module may be used for monitoring the devices in
the MAP scenario, especially, for the encapsulation mode.
2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
[RFC3410].
Managed objects are accessed via a virtual information store, termed
the 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
[RFC2578], [RFC2579] and [RFC2580].
3. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
4. Structure of the MIB Module
The MAP-E MIB provides a way to configure and manage the devices in
MAP encapsulation mode through SNMP.
MAP-E MIB is configurable on a per-interface basis. It depends on
several parts of the IF-MIB [RFC2863] and tunnel MIB [RFC4087].
Fu, et al. Expires January 18, 2013 [Page 3]
Internet-Draft draft-fu-softwire-map-mib-01.txt July 2012
4.1. The mapTunnel Subtree
The mapTunnel subtree describes managed objects used for managing
tunnels in the MAP encapsulation mode. Because the tunnel MIB
supports the tunnel management function in MAP encapsulation mode, we
may reuse it in MAP-E MIB. However, a MAP BR is considered to be a
collection of MAP tunnel endpoints which is distinguished by
different mapping rules. It needs to extend the tunnel MIB by some
parameters of mapping rule ID to distinguish the different tunnels.
4.2. The mapStatisticInfo Subtree
The mapStatisticInfo subtree provides state and statistical
information for MAP BRs or MAP tunnel endpoints.
4.3. The mapTrap Subtree
The mapTrap Subtree provides trap information in MAP encapsulation
mode.
4.4. The mapConformance Subtree
The Subtree provides conformance information of MIB objects.
5. MIB modules required for IMPORTS
This MIB module IMPORTs objects from [RFC4087], [RFC2580], [RFC2578],
[RFC2863], [RFC4001], [RFC3411].
6. Definitions
MAP-E-MIB DEFFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2, transmission,
Gauge32, Integer32, Counter64
FROM SNMPv2-SMI
RowStatus, StorageType, DisplayString
FROM SNMPv2-TC
ifIndex, InterfaceIndexOrZero
FROM IF-MIB
InetAddress, InetAddressIPv6
InetPortNumber, InetAddressPrefixLength
FROM INET-ADDRESS-MIB
Fu, et al. Expires January 18, 2013 [Page 4]
Internet-Draft draft-fu-softwire-map-mib-01.txt July 2012
tunnelInetConfigIfIndex
FROM tunnelMIB
mapMIB MODULE-IDENTITY
LAST-UPDATED "201207160000Z" -- July 16, 2012
ORGANIZATION "IETF Softwire Working Group"
CONTACT-INFO
"Yu Fu
Huawei Technologies Co., Ltd
Huawei Building, 156 Beiqing Rd., Hai-Dian District
Beijing, P.R. China 100095
EMail: eleven.fuyu@huawei.com
Sheng Jiang
Huawei Technologies Co., Ltd
Huawei Building, 156 Beiqing Rd., Hai-Dian District
Beijing, P.R. China 100095
EMail: jiangsheng@huawei.com
Bing Liu
Huawei Technologies Co., Ltd
Huawei Building, 156 Beiqing Rd., Hai-Dian District
Beijing, P.R. China 100095
EMail: leo.liubing@huawei.com
Jiang Dong
Tsinghua University
Department of Computer Science, Tsinghua University
Beijing 100084
P.R. China
Email: dongjiang@csnet1.cs.tsinghua.edu.cn
Peng Wu
Tsinghua University
Department of Computer Science, Tsinghua University
Beijing 100084
P.R. China
Email: weapon@csnet1.cs.tsinghua.edu.cn"
DESCRIPTION
"The MIB module is defined for management of object in the
MAP encapsulation mode."
::= { transmission xxx } --xxx to be replaced with correct
value
mapTunnel OBJECT IDENTIFIER
:: = { mapMIB 1 }
Fu, et al. Expires January 18, 2013 [Page 5]
Internet-Draft draft-fu-softwire-map-mib-01.txt July 2012
mapStatisticInfo OBJECT IDENTIFIER
:: = { mapMIB 2 }
mapTraps OBJECT IDENTIFIER
::= { mapMIB 3 }
--Conformance
mapConformance OBJECT IDENTIFIER
:: = { mapMIB 4 }
--mapTunnel
--mapTunnelTable
mapTunnelTable OBJECT-TYPE
SYNTAX SEQUENCE OF mapTunnelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table containing information on configured
tunnels. This table can be used to map CE address to the
associated BR address. It can also be used for row
creation."
:: = { mapTunnel 1 }
mapTunnelEntry OBJECT-TYPE
SYNTAX mapTunnelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry in this table contains the information on a
particular configured tunnel."
INDEX { mapTunnelBRAddress,
mapTunnelMapRuleID}
:: = { mapTunnelTable 1 }
mapTunnelEntry :: =
SEQUENCE {
mapTunnelBRAddress InetAddressIPv6,
mapTunnelMapRuleID Integer32,
mapTunnelMapRuleIPv6Prefix InetAddressIPv6,
mapTunnelMapRuleIPv6PrefixLen InetAddressPrefixLength,
mapTunnelMapRuleIPv4Prefix InetAddress,
mapTunnelMapRuleIPv4PrefixLen InetAddressPrefixLength,
mapTunnelMAPRuleExPorts InetPortNumber,
mapTunnelMAPEALen Integer32,
mapTunnelCEAddress InetAddressIPv6,
mapTunnelID Integer32,
Fu, et al. Expires January 18, 2013 [Page 6]
Internet-Draft draft-fu-softwire-map-mib-01.txt July 2012
mapTunnelIfIndex tunnelInetConfigIfIndex,
mapTunnelStatus RowStatus,
mapTunnelStorageType StorageType
}
mapTunnelBRAddress OBJECT-TYPE
SYNTAX InetAddressIPv6
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The address of the BR. It is one endpoint of the MAP
Tunnel"
::= { mapTunnelEntry 1 }
mapTunnelMapRuleID OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An identifier used to distinguish the multiple mapping
rule which is unique with each CE in the same BR."
::= { mapTunnelEntry 2 }
mapTunnelMapRuleIPv6Prefix OBJECT-TYPE
SYNTAX InetAddressIPv6
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The IPv6 prefix defined in mapping rule which will be
assigned to CE ."
::= { mapTunnelEntry 3 }
mapTunnelMapRuleIPv6PrefixLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The length of the IPv6 prefix defined in the mapping rule.
As a parameter for mapping rule, it will be also assigned
to CE."
::= { mapTunnelEntry 4 }
mapTunnelMapRuleIPv4Prefix OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
Fu, et al. Expires January 18, 2013 [Page 7]
Internet-Draft draft-fu-softwire-map-mib-01.txt July 2012
" The IPv4 prefix defined in mapping rule which will be
assigned to CE."
::= { mapTunnelEntry 5 }
mapTunnelMapRuleIPv4PrefixLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The length of the IPv4 prefix defined in the mapping
rule. As a parameter for mapping rule, it will be also
assigned to CE."
::= { mapTunnelEntry 6 }
mapTunnelMAPRuleExPorts OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The upper bound for range of excluded ports
defined in mapping rule which will be assigned to CE."
::= { mapTunnelEntry 7 }
mapTunnelMAPEALen OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The length of the Embedded-Address (EA) defined in
mapping rule which will be assigned to CE."
::= { mapTunnelEntry 8 }
mapTunnelCEAddress OBJECT-TYPE
SYNTAX InetAddressIPv6
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The address of the CE as the another endpoint of MAP
tunnel. It is derived by the parameters defined in the
mapping rule assigned to the CE."
::= { mapTunnelEntry 9 }
mapTunnelID OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
Fu, et al. Expires January 18, 2013 [Page 8]
Internet-Draft draft-fu-softwire-map-mib-01.txt July 2012
"An identifier used to distinguish between multiple
tunnels in MAP encapsulation mode."
::= { mapTunnelEntry 10 }
mapTunnelIfIndex OBJECT-TYPE
SYNTAX tunnelInetConfigIfIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If the value of mapTunnelStatus for this row
is active, then this object contains the value of
ifIndex corresponding to the tunnel interface. A
value of 0 is not legal in the active state,
and means that the interface index has not
yet been assigned."
::= { mapTunnelEntry 11 }
mapTunnelStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this row, by which new entries may be
created, or old entries deleted from this table.
::= { mapTunnelEntry 12 }
mapTunnelStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type of this row. If the row is
permanent(4), no objects in the row need be
writable."
::= { mapTunnelEntry 13 }
--mapStatisticInfo
mapStatisticTable OBJECT-TYPE
SYNTAX SEQUENCE OF mapStatisticEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table provides some statistical information
of MAP encapsulation mode."
::= { mapStatisticInfo 1 }
Fu, et al. Expires January 18, 2013 [Page 9]
Internet-Draft draft-fu-softwire-map-mib-01.txt July 2012
mapStatisticEntry OBJECT-TYPE
SYNTAX dsliteStatisticEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table provides statistical information
of MAP encapsulation mode."
INDEX { mapStatisticBRAddress }
::= { mapStatisticTable 1 }
mapStatisticEntry ::=
SEQUENCE {
mapStatisticBRAddress InetAddressIPv6,
mapStatisticDiscard Counter64,
mapStatisticReceived Counter64,
mapStatisticTransmitted Counter64,
mapStatisticConnections Integer32,
mapStatisticSpecificIP DisplayString,
mapStatisticStorageType StorageType,
mapStatisticRowStatus RowStatus
}
mapStatisticBRAddress OBJECT-TYPE
SYNTAX InetAddressIPv6
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The address of the BR. It is one endpoint of the
Tunnel in the MAP encapsulation mode "
::= { mapStatisticEntry 1 }
mapStatisticDiscard OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-create
STATUS current
DESCRIPTION
" This object indicate the count number of
the discarded packet."
::= { mapStatisticEntry 2 }
mapStatisticReceived OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicate the count number of
Fu, et al. Expires January 18, 2013 [Page 10]
Internet-Draft draft-fu-softwire-map-mib-01.txt July 2012
received packet count."
::= { mapStatisticEntry 3 }
mapStatisticTransmitted OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicate the count number of
transmitted packet count."
::= { mapStatisticEntry 4 }
mapStatisticConnections OBJECT-TYPE
SYNTAX Integer32 (60..90)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
" This object indicate the threshold of tunnel
connections for this BR."
::= { mapStatisticEntry 5 }
mapStatisticSpecificIP OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
" This object indicate the IP address of CE whose port usage
reach threshold "
::= { mapStatisticEntry 6 }
---map trap
mapTunnelNumAlarm NOTIFICATION-TYPE
STATUS current
DESCRIPTION
"This trap is triggered when tunnels
reach the threshold in the MAP encapsulation mode."
::= { mapTraps 1 }
mapBRPortUsageOfSpecificIpAlarm NOTIFICATION-TYPE
OBJECTS { mapStatisticSpecificIP }
STATUS current
DESCRIPTION
"This trap is triggered when the used ports of
specific CE address reach the threshold."
::= { dsliteTraps 2 }
Fu, et al. Expires January 18, 2013 [Page 11]
Internet-Draft draft-fu-softwire-map-mib-01.txt July 2012
--Module Conformance statement
mapCompliances OBJECT IDENTIFIER ::= { mapConformance 1 }
mapCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Description."
MODULE -- this module
MANDATORY-GROUPS { mapTunnelGroup,
mapStatisticInfoGroup }
::= { mapCompliances 1 }
mapGroups OBJECT IDENTIFIER ::= { mapConformance 2 }
mapTunnelGroup OBJECT-GROUP
OBJECTS { mapTunnelBRAddress, mapTunnelMapRuleID,
mapTunnelMapRuleIPv6Prefix,
mapTunnelMapRuleIPv6PrefixLen,
mapTunnelMapRuleIPv4Prefix,
mapTunnelMapRuleIPv4PrefixLen,
mapTunnelMAPRuleExPorts, mapTunnelMAPEALen,
mapTunnelCEAddress, mapTunnelID,
mapTunnelIfIndex, mapTunnelStatus,
mapTunnelStorageType }
STATUS current
DESCRIPTION
" The collection of this objects are used to give the
information for tunnels in MAP-E."
::= { mapGroups 1 }
mapStatisticGroup OBJECT-GROUP
OBJECTS { mapStatisticBRAddress,
mapStatisticDiscard,
mapStatisticReceived,
mapStatisticTransmitted,
mapStatisticConnections,
mapStatisticSpecificIP,
mapStatisticStorageType,
mapStatisticRowStatus }
STATUS current
DESCRIPTION
" The collection of this objects are used to give the
statistical information of MAP-E."
::= { mapGroups 2 }
Fu, et al. Expires January 18, 2013 [Page 12]
Internet-Draft draft-fu-softwire-map-mib-01.txt July 2012
mapTrapsGroup NOTIFICATION-GROUP
NOTIFICATIONS { mapTunnelNumAlarm,
mapBRPortUsageOfSpecificIpAlarm }
STATUS current
DESCRIPTION
"The collection of this objects are used to give the
trap information for MAP-E."
::= { mapGroups 3 }
END
7. IANA Considerations
The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
MAP-E-MIB { transmission XXX }
8. Security Considerations
The MAP-E MIB module can be used for configuration of certain
objects, and anything that can be configured can be incorrectly
configured, with potentially disastrous results. Because this MIB
module reuses the IP tunnel MIB, the security considerations for
these MIBs are also applicable to the MAP-E MIB.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec),
even then, 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.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
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 principles (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
Fu, et al. Expires January 18, 2013 [Page 13]
Internet-Draft draft-fu-softwire-map-mib-01.txt July 2012
9. References
9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Structure of Management Information Version 2 (SMIv2)",
RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual
Conventions for SMIv2", RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", RFC 2580, April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz. "The Interfaces Group
MIB", RFC 2863, June 2000.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", RFC 3411, December
2002.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005.
[RFC4087] Thaler, D., "IP Tunnel MIB", RFC 4087, June 2005.
[I-D.ietf-softwire-map]
Troan, O.,etc., "Mapping of Address and Port (MAP)", draft-
ietf-softwire-map, working in progress.
[I-D.mdt-softwire-map-dhcp-option]
Mrugalski, T.,etc., "DHCPv6 Options for Mapping of Address
and Port", draft-mdt-softwire-map-dhcp-option, working in
progress.
9.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
Fu, et al. Expires January 18, 2013 [Page 14]
Internet-Draft draft-fu-softwire-map-mib-01.txt July 2012
10. Change Log [RFC Editor please remove]
draft-fu-softwire-map-mib-00, original version, 2012-03-01
draft-fu-softwire-map-mib-01, 01 version, 2012-07-16
Author's Addresses
Yu Fu
Huawei Technologies Co., Ltd
Huawei Building, 156 Beiqing Rd.,
Hai-Dian District, Beijing 100095
P.R. China
Email: eleven.fuyu@huawei.com
Sheng Jiang
Huawei Technologies Co., Ltd
Huawei Building, 156 Beiqing Rd.,
Hai-Dian District, Beijing 100095
P.R. China
Email: jiangsheng@huawei.com
Bing Liu
Huawei Technologies Co., Ltd
Huawei Building, 156 Beiqing Rd.,
Hai-Dian District, Beijing 100095
P.R. China
Email: leo.liubing@huawei.com
Jiang Dong
Tsinghua University
Department of Computer Science, Tsinghua University
Beijing 100084
P.R. China
Email: dongjiang@csnet1.cs.tsinghua.edu.cn
Peng Wu
Tsinghua University
Department of Computer Science, Tsinghua University
Beijing 100084
P.R. China
Email: weapon@csnet1.cs.tsinghua.edu.cn
Fu, et al. Expires January 18, 2013 [Page 15]