draft-fu-softwire-map-mib-04.txt   draft-fu-softwire-map-mib-05.txt 
Network Working Group Y. Fu Network Working Group Y. Fu
Internet Draft S. Jiang Internet Draft S. Jiang
Intended status: Standards Track B.Liu Intended status: Standards Track B.Liu
Expires: October 29, 2013 Huawei Technologies Co., Ltd Expires: November 15, 2013 Huawei Technologies Co., Ltd
J.Dong J.Dong
P. Wu P. Wu
Tsinghua University Tsinghua University
April 27, 2013 May 14, 2013
Definitions of Managed Objects for MAP-E Definitions of Managed Objects for MAP-E
draft-fu-softwire-map-mib-04 draft-fu-softwire-map-mib-05
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as reference at any time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 29, 2013. This Internet-Draft will expire on November 15, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 20 skipping to change at page 2, line 20
encapsulation mode. encapsulation mode.
Table of Contents Table of Contents
1. Introduction ................................................. 3 1. Introduction ................................................. 3
2. The Internet-Standard Management Framework ................... 3 2. The Internet-Standard Management Framework ................... 3
3. Terminology .................................................. 3 3. Terminology .................................................. 3
4. Structure of the MIB Module .................................. 3 4. Structure of the MIB Module .................................. 3
4.1. The mapMIBObjects ....................................... 4 4.1. The mapMIBObjects ....................................... 4
4.1.1. The mapRule Subtree ................................ 4 4.1.1. The mapRule Subtree ................................ 4
4.1.2. The mapSecurityCheck Subtree ....................... 4
4.2. The mapMIBConformance Subtree ........................... 4 4.2. The mapMIBConformance Subtree ........................... 4
5. Definitions .................................................. 4 5. Definitions .................................................. 4
6. IANA Considerations ......................................... 11 6. IANA Considerations ......................................... 12
7. Security Considerations ..................................... 11 7. Security Considerations ..................................... 12
8. References .................................................. 11 8. Acknowledgments ............................................. 12
8.1. Normative References ................................... 11 9. References .................................................. 12
8.2. Informative References ................................. 12 9.1. Normative References ................................... 12
9. Change Log [RFC Editor please remove] ....................... 12 9.2. Informative References ................................. 13
Author's Addresses ............................................. 13 10. Change Log [RFC Editor please remove] ...................... 13
Author's Addresses ............................................. 14
1. Introduction 1. Introduction
MAP [I-D. draft-ietf-softwire-map] is a stateless mechanism for MAP [I-D. draft-ietf-softwire-map] is a stateless mechanism for
running IPv4 over IPv6-only infrastructure. In particular, it running IPv4 over IPv6-only infrastructure. In particular, it
includes two mode, translation mode or encapsulation mode. For the includes two mode, translation mode or encapsulation mode. For the
encapsulation mode, it provides an automatic tunnelling mechanism encapsulation mode, it provides an automatic tunnelling mechanism
for providing IPv4 connectivity service to end users over a service for providing IPv4 connectivity service to end users over a service
provider's IPv6 network. provider's IPv6 network.
skipping to change at page 4, line 12 skipping to change at page 4, line 12
MAP-E MIB is configurable on a per-interface basis. It depends on MAP-E MIB is configurable on a per-interface basis. It depends on
several parts of the IF-MIB [RFC2863]. several parts of the IF-MIB [RFC2863].
4.1. The mapMIBObjects 4.1. The mapMIBObjects
4.1.1. The mapRule Subtree 4.1.1. The mapRule Subtree
The mapRule subtree describes managed objects used for managing the The mapRule subtree describes managed objects used for managing the
multiple mapping rules in the MAP encapsulation mode. multiple mapping rules in the MAP encapsulation mode.
According to the MAP specification, the mapping rules are divided
into two categories, which are BMR (Basic Mapping Rule), and FMR
(Forwarding Mapping Rule).
4.1.2. The mapSecurityCheck Subtree
The mapSecurityCheck subtree is to statistic the number of invalid
packets that been identified. There are two kind of invalid packets
which are defined in the MAP specification as the following.
- The BR MUST perform a validation of the consistency of the source
IPv6 address and source port number for the packet using BMR.
- The CE SHOULD check that MAP received packets' transport-layer
destination port number is in the range configured by MAP for the CE.
4.2. The mapMIBConformance Subtree 4.2. The mapMIBConformance Subtree
The mapMIBConformance subtree provides conformance information of The mapMIBConformance subtree provides conformance information of
MIB objects. MIB objects.
5. Definitions 5. Definitions
MAP-E-MIB DEFINITIONS ::= BEGIN MAP-E-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2, transmission, MODULE-IDENTITY, OBJECT-TYPE, mib-2, transmission,
Gauge32, Integer32, Counter64 Gauge32, Integer32, Counter64
FROM SNMPv2-SMI --[RFC2578] FROM SNMPv2-SMI --[RFC2578]
RowStatus, StorageType, DisplayString RowStatus, StorageType, DisplayString
FROM SNMPv2-TC --[RFC2579] FROM SNMPv2-TC --[RFC2579]
ifIndex, InterfaceIndexOrZero ifIndex, InterfaceIndexOrZero
FROM IF-MIB --[RFC2863] FROM IF-MIB --[RFC2863]
InetAddress, InetAddressIPv6, InetAddressType, InetAddress,
InetPortNumber, InetAddressPrefixLength InetPortNumber, InetAddressPrefixLength
FROM INET-ADDRESS-MIB --[RFC4001] FROM INET-ADDRESS-MIB --[RFC4001]
OBJECT-GROUP, MODULE-COMPLIANCE, OBJECT-GROUP, MODULE-COMPLIANCE,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF; --[RFC2580] FROM SNMPv2-CONF; --[RFC2580]
mapMIB MODULE-IDENTITY mapMIB MODULE-IDENTITY
LAST-UPDATED "201302070000Z" -- February 6, 2013 LAST-UPDATED "201302070000Z" -- February 6, 2013
ORGANIZATION "IETF Softwire Working Group" ORGANIZATION "IETF Softwire Working Group"
skipping to change at page 5, line 32 skipping to change at page 5, line 49
Tsinghua University Tsinghua University
Department of Computer Science, Tsinghua University Department of Computer Science, Tsinghua University
Beijing 100084 Beijing 100084
P.R. China P.R. China
Email: weapon@csnet1.cs.tsinghua.edu.cn" Email: weapon@csnet1.cs.tsinghua.edu.cn"
DESCRIPTION DESCRIPTION
"The MIB module is defined for management of objects in the "The MIB module is defined for management of objects in the
MAP-E BRs or CEs." MAP-E BRs or CEs."
REVISION "201304270000Z" REVISION "201305140000Z"
::= { transmission xxx } --xxx to be replaced with
::= { transmission xxx } --xxx to be replaced with correct IANA-assigned value
value
mapMIBObjects OBJECT IDENTIFIER ::= {mapMIB 1} mapMIBObjects OBJECT IDENTIFIER ::= {mapMIB 1}
mapRule OBJECT IDENTIFIER mapRule OBJECT IDENTIFIER
::= { mapMIBObjects 1 } ::= { mapMIBObjects 1 }
mapSecurityCheck OBJECT IDENTIFIER mapSecurityCheck OBJECT IDENTIFIER
::= { mapMIBObjects 2 } ::= { mapMIBObjects 2 }
mapRuleTable OBJECT-TYPE mapRuleTable OBJECT-TYPE
skipping to change at page 6, line 22 skipping to change at page 6, line 38
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry in this table contains the information on a "Each entry in this table contains the information on a
particular mapping rule." particular mapping rule."
INDEX { mapRuleID } INDEX { mapRuleID }
::= { mapRuleTable 1 } ::= { mapRuleTable 1 }
mapRuleEntry ::= mapRuleEntry ::=
SEQUENCE { SEQUENCE {
mapRuleID Integer32, mapRuleID Integer32,
mapRuleIPv6Prefix InetAddressIPv6, mapRuleIPv6PrefixType InetAddressType,
mapRuleIPv6Prefix InetAddress,
mapRuleIPv6PrefixLen InetAddressPrefixLength, mapRuleIPv6PrefixLen InetAddressPrefixLength,
mapRuleIPv4PrefixType InetAddressType,
mapRuleIPv4Prefix InetAddress, mapRuleIPv4Prefix InetAddress,
mapRuleIPv4PrefixLen InetAddressPrefixLength, mapRuleIPv4PrefixLen InetAddressPrefixLength,
mapRuleStartPort InetPortNumber, mapRuleStartPort InetPortNumber,
mapRuleEndPort InetPortNumber, mapRuleEndPort InetPortNumber,
mapRuleEALen Integer32, mapRuleEALen Integer32,
mapRuleStatus RowStatus, mapRuleStatus RowStatus,
mapRuleStorageType StorageType mapRuleStorageType StorageType,
mapRuleType Integer32
} }
mapRuleID OBJECT-TYPE mapRuleID OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An identifier used to distinguish the multiple mapping "An identifier used to distinguish the multiple mapping
rule which is unique with each CE in the same BR." rule which is unique with each CE in the same BR."
::= { mapRuleEntry 1 } ::= { mapRuleEntry 1 }
mapRuleIPv6PrefixType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"In this object, it MUST be set to the value of 2 to
present IPv6 type. It complies the textule convention
of IPv6 address defined in [RFC4001]."
::= { mapRuleEntry 2 }
mapRuleIPv6Prefix OBJECT-TYPE mapRuleIPv6Prefix OBJECT-TYPE
SYNTAX InetAddressIPv6 SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IPv6 prefix defined in mapping rule which will be "The IPv6 prefix defined in mapping rule which will be
assigned to CE ." assigned to CE ."
::= { mapRuleEntry 2 } ::= { mapRuleEntry 3 }
mapRuleIPv6PrefixLen OBJECT-TYPE mapRuleIPv6PrefixLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length of the IPv6 prefix defined in the mapping rule. "The length of the IPv6 prefix defined in the mapping rule.
As a parameter for mapping rule, it will be also assigned As a parameter for mapping rule, it will be also assigned
to CE." to CE."
::= { mapRuleEntry 3 } ::= { mapRuleEntry 4 }
mapRuleIPv4PrefixType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"In this object, it MUST be set to the value of 1 to
present IPv4 type. It complies the textual convention
of IPv6 address defined in [RFC4001]."
::= { mapRuleEntry 5 }
mapRuleIPv4Prefix OBJECT-TYPE mapRuleIPv4Prefix OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The IPv4 prefix defined in mapping rule which will be " The IPv4 prefix defined in mapping rule which will be
assigned to CE." assigned to CE."
::= { mapRuleEntry 4 } ::= { mapRuleEntry 6 }
mapRuleIPv4PrefixLen OBJECT-TYPE mapRuleIPv4PrefixLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length of the IPv4 prefix defined in the mapping "The length of the IPv4 prefix defined in the mapping
rule. As a parameter for mapping rule, it will be also rule. As a parameter for mapping rule, it will be also
assigned to CE." assigned to CE."
::= { mapRuleEntry 5 } ::= { mapRuleEntry 7 }
mapRuleStartPort OBJECT-TYPE mapRuleStartPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The start port number of the port range derived "The start port number of the port range derived
from the mapping rule which will be assigned to CE." from the mapping rule which will be assigned to CE."
::= { mapRuleEntry 6 } ::= { mapRuleEntry 8 }
mapRuleEndPort OBJECT-TYPE mapRuleEndPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The end port number of the port range derived " The end port number of the port range derived
from the mapping rule which will be assigned to CE." from the mapping rule which will be assigned to CE."
::= { mapRuleEntry 7 } ::= { mapRuleEntry 9 }
mapRuleEALen OBJECT-TYPE mapRuleEALen OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length of the Embedded-Address (EA) defined in "The length of the Embedded-Address (EA) defined in
mapping rule which will be assigned to CE." mapping rule which will be assigned to CE."
::= { mapRuleEntry 8 } ::= { mapRuleEntry 10 }
mapRuleStatus OBJECT-TYPE mapRuleStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this row, by which new entries may be "The status of this row, by which new entries may be
created, or old entries deleted from this table. created, or old entries deleted from this table.
::= { mapRuleEntry 9 } ::= { mapRuleEntry 11 }
mapRuleStorageType OBJECT-TYPE mapRuleStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type of this row. If the row is "The storage type of this row. If the row is
permanent(4), no objects in the row need be permanent(4), no objects in the row need be
writable." writable."
::= { mapRuleEntry 10 } ::= { mapRuleEntry 12 }
mapRuleType OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of the mapping rule. A value of 0 means it
is a BMR; a non-zero value means it is a FMR."
::= { mapRuleEntry 12 }
mapSecurityCheckTable OBJECT-TYPE mapSecurityCheckTable OBJECT-TYPE
SYNTAX SEQUENCE OF MapSecurityCheckEntry SYNTAX SEQUENCE OF MapSecurityCheckEntry
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table containing information on "The (conceptual) table containing information on
MAP security checks. This table can be used to statistic MAP security checks. This table can be used to statistic
the number of invalid packets that been identified" the number of invalid packets that been identified"
::= { mapSecurityCheck 1 } ::= { mapSecurityCheck 1 }
skipping to change at page 11, line 41 skipping to change at page 12, line 41
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principles (users) that have legitimate the objects only to those principles (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
8. References 8. Acknowledgments
8.1. Normative References The authors would like to thank for valuable comments from David
Harrington, Mark Townsley, and Shishio Tsuchiya.
9. References
9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Structure of Management Information Version 2 (SMIv2)", "Structure of Management Information Version 2 (SMIv2)",
RFC 2578, April 1999. RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Textual Conventions for SMIv2", RFC 2579, April 1999. "Textual Conventions for SMIv2", RFC 2579, April 1999.
skipping to change at page 12, line 34 skipping to change at page 13, line 38
[I-D.ietf-softwire-map] [I-D.ietf-softwire-map]
Troan, O.,etc., "Mapping of Address and Port (MAP)", Troan, O.,etc., "Mapping of Address and Port (MAP)",
draft-ietf-softwire-map, working in progress. draft-ietf-softwire-map, working in progress.
[I-D.mdt-softwire-map-dhcp-option] [I-D.mdt-softwire-map-dhcp-option]
Mrugalski, T.,etc., "DHCPv6 Options for Mapping of Address Mrugalski, T.,etc., "DHCPv6 Options for Mapping of Address
and Port", draft-mdt-softwire-map-dhcp-option, working in and Port", draft-mdt-softwire-map-dhcp-option, working in
progress. progress.
8.2. Informative References 9.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
9. Change Log [RFC Editor please remove] 10. Change Log [RFC Editor please remove]
draft-fu-softwire-map-mib-00, original version, 2012-03-01 draft-fu-softwire-map-mib-00, original version, 2012-03-01
draft-fu-softwire-map-mib-01, 01 version, 2012-07-16 draft-fu-softwire-map-mib-01, 01 version, 2012-07-16
draft-fu-softwire-map-mib-03, deleted tunnel object according to the draft-fu-softwire-map-mib-03, deleted tunnel object according to the
discussion in IETF85, 2013-02-04 discussion in IETF85, 2013-02-04
draft-fu-softwire-map-mib-04, added security check object according
to discussion in IETF86
draft-fu-softwire-map-mib-05, distinguishing FMR and BMR in mapRule
object definition; added some description in section 4; modifying a
little bit to the mapRuleEntry definiction
Author's Addresses Author's Addresses
Yu Fu Yu Fu
Huawei Technologies Co., Ltd Huawei Technologies Co., Ltd
Huawei Building, 156 Beiqing Rd. Huawei Building, 156 Beiqing Rd.
Hai-Dian District, Beijing 100095 Hai-Dian District, Beijing 100095
P.R. China P.R. China
Email: eleven.fuyu@huawei.com Email: eleven.fuyu@huawei.com
Sheng Jiang Sheng Jiang
Huawei Technologies Co., Ltd Huawei Technologies Co., Ltd
Huawei Building, 156 Beiqing Rd. Huawei Building, 156 Beiqing Rd.
Hai-Dian District, Beijing 100095 Hai-Dian District, Beijing 100095
P.R. China P.R. China
Email: jiangsheng@huawei.com Email: jiangsheng@huawei.com
Bing Liu Bing Liu
Huawei Technologies Co., Ltd Huawei Technologies Co., Ltd
Huawei Building, 156 Beiqing Rd. Huawei Building, 156 Beiqing Rd.,
Hai-Dian District, Beijing 100095 Hai-Dian District, Beijing 100095
P.R. China P.R. China
Email: leo.liubing@huawei.com Email: leo.liubing@huawei.com
Jiang Dong Jiang Dong
Tsinghua University Tsinghua University
Department of Computer Science, Tsinghua University Department of Computer Science, Tsinghua University
Beijing 100084 Beijing 100084
P.R. China P.R. China
Email: dongjiang@csnet1.cs.tsinghua.edu.cn Email: dongjiang@csnet1.cs.tsinghua.edu.cn
 End of changes. 29 change blocks. 
33 lines changed or deleted 91 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/