draft-ietf-softwire-map-mib-01.txt   draft-ietf-softwire-map-mib-02.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: June 21, 2014 Huawei Technologies Co., Ltd Expires: December 15, 2014 Huawei Technologies Co., Ltd
J.Dong J.Dong
Y.Chen Y.Chen
Tsinghua University Tsinghua University
December 18, 2013 June 13, 2014
Definitions of Managed Objects for MAP-E Definitions of Managed Objects for MAP-E
draft-ietf-softwire-map-mib-01 draft-ietf-softwire-map-mib-02
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 June 21, 2014. This Internet-Draft will expire on December 15, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 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
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License. warranty as described in the Simplified BSD License.
Abstract Abstract
This memo defines a Management Information Base (MIB) module for use This memo defines a portion of the Management Information Base (MIB)
with network management protocols in the Internet community. In for using with network management protocols in the Internet
particular, it defines managed objects used in a Mapping of Address community. In particular, it defines managed objects for MAP
and Port with Encapsulation (MAP) system. 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.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 ......................................... 11
7. Security Considerations ..................................... 11 7. Security Considerations ..................................... 11
8. Acknowledgments ............................................. 12 8. Acknowledgments ............................................. 12
9. References .................................................. 12 9. References .................................................. 12
9.1. Normative References ................................... 12 9.1. Normative References ................................... 12
9.2. Informative References ................................. 13 9.2. Informative References ................................. 13
10. Change Log [RFC Editor please remove] ...................... 13 Author's Addresses ............................................. 13
Author's Addresses ............................................. 14
1. Introduction 1. Introduction
MAP [I-D. ietf-softwire-map] is a stateless mechanism for running MAP [I-D. draft-ietf-softwire-map] is a stateless mechanism for
IPv4 over IPv6-only infrastructure. In particular, it includes two running IPv4 over IPv6-only infrastructure. In particular, it
modes, translation mode (MAP-T)and encapsulation mode (MAP-E). For includes two mode, translation mode or encapsulation mode. For the
the encapsulation mode, it provides an automatic tunnelling encapsulation mode, it provides an automatic tunnelling mechanism
mechanism for providing IPv4 connectivity service to end users over for providing IPv4 connectivity service to end users over a service
a service provider's IPv6 network. provider's IPv6 network.
This document defines a Management Information Base (MIB) module This document defines a portion of the Management Information Base
which may be used for monitoring the devices in the MAP-E scenario. (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 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
[RFC3410]. [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the MIB. MIB objects are generally accessed through the Simple the MIB. MIB objects are generally accessed through the Simple
Network Management Protocol (SNMP). Network Management Protocol (SNMP).
skipping to change at page 5, line 6 skipping to change at page 5, line 6
FROM IF-MIB FROM IF-MIB
InetAddressType, InetAddress, InetAddressType, InetAddress,
InetPortNumber, InetAddressPrefixLength InetPortNumber, InetAddressPrefixLength
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
OBJECT-GROUP, MODULE-COMPLIANCE OBJECT-GROUP, MODULE-COMPLIANCE
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
mapMIB MODULE-IDENTITY mapMIB MODULE-IDENTITY
LAST-UPDATED "201306260000Z" -- June 26, 2013 LAST-UPDATED "201406130000Z" -- June 13, 2014
ORGANIZATION "IETF Softwire Working Group" ORGANIZATION "IETF Softwire Working Group"
CONTACT-INFO CONTACT-INFO
"Yu Fu "Yu Fu
Huawei Technologies Co., Ltd Huawei Technologies Co., Ltd
Huawei Building, 156 Beiqing Rd., Hai-Dian District Huawei Building, 156 Beiqing Rd., Hai-Dian District
Beijing, P.R. China 100095 Beijing, P.R. China 100095
EMail: eleven.fuyu@huawei.com EMail: eleven.fuyu@huawei.com
Sheng Jiang Sheng Jiang
Huawei Technologies Co., Ltd Huawei Technologies Co., Ltd
skipping to change at page 5, line 44 skipping to change at page 5, line 44
Yuchi Chen Yuchi Chen
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: chenycmx@gmail.com" Email: chenycmx@gmail.com"
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 "201306260000Z" REVISION "201406130000Z"
DESCRIPTION DESCRIPTION
"Initial version. Published as RFC xxxx." "Initial version. Published as RFC xxxx."
--RFC Ed.: RFC-edtitor pls fill in xxxx --RFC Ed.: RFC-edtitor pls fill in xxxx
::= { transmission xxx } ::= { transmission xxx }
--xxx to be replaced withIANA-assigned value --xxx to be replaced withIANA-assigned value
mapMIBObjects OBJECT IDENTIFIER ::= {mapMIB 1} mapMIBObjects OBJECT IDENTIFIER ::= {mapMIB 1}
mapRule OBJECT IDENTIFIER mapRule OBJECT IDENTIFIER
::= { mapMIBObjects 1 } ::= { mapMIBObjects 1 }
skipping to change at page 9, line 41 skipping to change at page 9, line 41
} }
mapSecurityCheckInvalidv4 OBJECT-TYPE mapSecurityCheckInvalidv4 OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The CE SHOULD check that MAP received packets' "The CE SHOULD check that MAP received packets'
transport-layer destination port number is in the range transport-layer destination port number is in the range
configured by MAP for the CE" configured by MAP for the CE. So this object indicate
the number of the invalid IPv4 packets received by the
MAP."
::= { mapSecurityCheckEntry 1 } ::= { mapSecurityCheckEntry 1 }
mapSecurityCheckInvalidv6 OBJECT-TYPE mapSecurityCheckInvalidv6 OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BR MUST perform a validation of the consistency of "The BR MUST perform a validation of the consistency of
the source IPv6 address and source port number for the the source IPv6 address and source port number for the
packet using BMR." packet using BMR. So this object indicate the number of
the invalid IPv6 packets received by the BR."
::= { mapSecurityCheckEntry 2 } ::= { mapSecurityCheckEntry 2 }
-- Conformance Information -- Conformance Information
mapMIBConformance OBJECT IDENTIFIER ::= {mapMIB 2} mapMIBConformance OBJECT IDENTIFIER ::= {mapMIB 2}
mapMIBCompliances OBJECT IDENTIFIER ::= { mapMIBConformance 1 } mapMIBCompliances OBJECT IDENTIFIER ::= { mapMIBConformance 1 }
mapMIBGroups OBJECT IDENTIFIER ::= { mapMIBConformance 2 } mapMIBGroups OBJECT IDENTIFIER ::= { mapMIBConformance 2 }
skipping to change at page 13, line 11 skipping to change at page 13, line 11
Mrugalski, T.,etc., "DHCPv6 Options for Mapping of Address Mrugalski, T.,etc., "DHCPv6 Options for Mapping of Address
and Port", draft-ietf-softwire-map-dhcp-option, working in and Port", draft-ietf-softwire-map-dhcp-option, working in
progress. progress.
9.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.
10. Change Log [RFC Editor please remove]
draft-fu-softwire-map-mib-00, original version, 2012-03-01
draft-fu-softwire-map-mib-03, deleted tunnel object according to the
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
draft-ietf-softwire-map-mib-00, adopted as softwire WG draft, 2013-
06-26
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
 End of changes. 13 change blocks. 
42 lines changed or deleted 33 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/