draft-ietf-softwire-map-mib-11.txt   draft-ietf-softwire-map-mib-12.txt 
Internet Engineering Task Force Y. Fu Internet Engineering Task Force Y. Fu
Internet-Draft CNNIC Internet-Draft CNNIC
Intended status: Standards Track S. Jiang Intended status: Standards Track S. Jiang
Expires: May 3, 2018 B. Liu Expires: May 19, 2018 B. Liu
Huawei Technologies Co., Ltd Huawei Technologies Co., Ltd
J. Dong J. Dong
Y. Chen Y. Chen
Tsinghua University Tsinghua University
October 30, 2017 November 15, 2017
Definitions of Managed Objects for MAP-E Definitions of Managed Objects for MAP-E
draft-ietf-softwire-map-mib-11 draft-ietf-softwire-map-mib-12
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for Mapping Address and Port with encapsulation (MAP-E) for use with for Mapping Address and Port with encapsulation (MAP-E) for use with
network management protocols. network management protocols.
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
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference 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 May 3, 2018. This Internet-Draft will expire on May 19, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 30 skipping to change at page 2, line 30
7. Security Considerations . . . . . . . . . . . . . . . . . . . 11 7. Security Considerations . . . . . . . . . . . . . . . . . . . 11
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
9.1. Normative References . . . . . . . . . . . . . . . . . . 13 9.1. Normative References . . . . . . . . . . . . . . . . . . 13
9.2. Informative References . . . . . . . . . . . . . . . . . 14 9.2. Informative References . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
Mapping of Address and Port with Encapsulation (MAP-E) [RFC7597] is a Mapping of Address and Port with Encapsulation (MAP-E) [RFC7597] is a
stateless, automatic tunnelling mechanism for providiing an IPv4 stateless, automatic tunnelling mechanism for providing an IPv4
connectivity service to end-users over a service provider's IPv6 connectivity service to end-users over a service provider's IPv6
network. network.
This document defines a portion of the Management Information Base This document defines a portion of the Management Information Base
(MIB) for use with monitoring MAP-E devices. (MIB) for use with monitoring MAP-E devices.
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
skipping to change at page 3, line 21 skipping to change at page 3, line 21
4. Structure of the MIB Module 4. Structure of the MIB Module
The Interfaces MIB [RFC2863] defines generic managed objects for The Interfaces MIB [RFC2863] defines generic managed objects for
managing interfaces. Each logical interface (physical or virtual) managing interfaces. Each logical interface (physical or virtual)
has an ifEntry. Tunnels are handled by creating a logical interface has an ifEntry. Tunnels are handled by creating a logical interface
(ifEntry) for each tunnel. Each MAP-E tunnel endpoint also acts as a (ifEntry) for each tunnel. Each MAP-E tunnel endpoint also acts as a
virtual interface that has a corresponding entry in the Interface virtual interface that has a corresponding entry in the Interface
MIB. Those corresponding entries are indexed by ifIndex. MAP-E MIB MIB. Those corresponding entries are indexed by ifIndex. MAP-E MIB
is configurable on a per-interface basis, so it depends on several is configurable on a per-interface basis, so it depends on several
parts of the IF-MIB [RFC2863]. 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 MAP-E. multiple mapping rules in MAP-E.
According to the [RFC7597], the mapping rules are divided into two According to the [RFC7597], the mapping rules are divided into two
categories, which are Basic Mapping Rule (BMR), and Forwarding categories, which are Basic Mapping Rule (BMR), and Forwarding
Mapping Rule (FMR). Mapping Rule (FMR).
4.1.2. The mapSecurityCheck Subtree 4.1.2. The mapSecurityCheck Subtree
The mapSecurityCheck subtree provides statistics for the number of The mapSecurityCheck subtree provides statistics for the number of
invalid packets that have been identified. There are two kind of invalid packets that have been identified. There are two kind of
invalid packets which are defined in the [RFC7597]as below. invalid packets which are defined in the [RFC7597] as below.
- The Border Relay (BR) will validates the received packet's source - The Border Relay (BR) will validates the received packet's source
IPv6 address against the configured MAP domain rule and the IPv6 address against the configured MAP domain rule and the
destination IPv6 address against the configured BR IPv6 address. . destination IPv6 address against the configured BR IPv6 address.
- The MAP node (CE and BR) will check that the received packets' - The MAP node (CE and BR) will check that the received packets'
source IPv4 address and port is in the range derived from the source IPv4 address and port is in the range derived from the
matching MAP Rule. matching MAP Rule.
4.2. The mapMIBConformance Subtree 4.2. The mapMIBConformance Subtree
The mapMIBConformance subtree provides conformance information of MIB The mapMIBConformance subtree provides conformance information of MIB
objects. objects.
5. Definitions 5. Definitions
The following MIB module imports definitions from [RFC2578], The following MIB module imports definitions from [RFC2578],
[RFC2579],[RFC2580],[RFC2863], and [RFC4001]. [RFC2579], [RFC2580], [RFC2863], and [RFC4001].
MAP-E-MIB DEFINITIONS ::= BEGIN MAP-E-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2, MODULE-IDENTITY, OBJECT-TYPE, mib-2,
Unsigned32, Counter64 Unsigned32, Counter64
FROM SNMPv2-SMI --RFC2578 FROM SNMPv2-SMI --RFC2578
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC --RFC2579 FROM SNMPv2-TC --RFC2579
ifIndex ifIndex
FROM IF-MIB --RFC2863 FROM IF-MIB --RFC2863
InetAddressIPv6, InetAddressIPv4, InetAddressIPv6, InetAddressIPv4,
InetAddressPrefixLength InetAddressPrefixLength
FROM INET-ADDRESS-MIB --RFC4001 FROM INET-ADDRESS-MIB --RFC4001
OBJECT-GROUP, MODULE-COMPLIANCE OBJECT-GROUP, MODULE-COMPLIANCE
FROM SNMPv2-CONF; --RFC2580 FROM SNMPv2-CONF; --RFC2580
mapMIB MODULE-IDENTITY mapMIB MODULE-IDENTITY
LAST-UPDATED "201710300000Z" LAST-UPDATED "201711150000Z"
ORGANIZATION ORGANIZATION
"IETF Softwire Working Group" "IETF Softwire Working Group"
CONTACT-INFO CONTACT-INFO
"Yu Fu "Yu Fu
CNNIC CNNIC
No.4 South 4th Street, Zhongguancun No.4 South 4th Street, Zhongguancun
Beijing, P.R. China 100190 Beijing, P.R. China 100190
EMail: fuyu@cnnic.cn EMail: fuyu@cnnic.cn
Sheng Jiang Sheng Jiang
skipping to change at page 5, line 18 skipping to change at page 5, line 18
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 for "The MIB module is defined for management of objects for
MAP-E BRs or CEs." MAP-E BRs or CEs."
REVISION "201710300000Z" REVISION "201711150000Z"
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
::= { mib-2 xxx } ::= { mib-2 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 6, line 8 skipping to change at page 6, line 8
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Enumerates the type of the mapping rule. It "Enumerates the type of the mapping rule. It
defines three types of mapping rules here: defines three types of mapping rules here:
bmr: Basic Mapping Rule (Not Forwarding Mapping Rule), bmr: Basic Mapping Rule (Not Forwarding Mapping Rule),
fmr: Forwarding Mapping Rule (Not Basic Mapping Rule), fmr: Forwarding Mapping Rule (Not Basic Mapping Rule),
bmrAndfmr: Basic and Forwarding Mapping Rule. The Basic bmrAndfmr: Basic and Forwarding Mapping Rule. The Basic
Mapping Rule may also be a Forwarding Mapping Rule for Mapping Rule may also be a Forwarding Mapping Rule for
mesh mode." mesh mode."
REFERENCE "bmr, fmr: section 5 of RFC 7597. REFERENCE "bmr, fmr: section 5 of RFC 7597.
bmrAndfmr: section 5 of RFC 7597,section 4.1 of RFC bmrAndfmr: section 5 of RFC 7597, section 4.1
7598." of RFC 7598."
SYNTAX INTEGER { SYNTAX INTEGER {
bmr(1), bmr(1),
fmr(2), fmr(2),
bmrAndfmr(3) bmrAndfmr(3)
} }
mapRuleTable OBJECT-TYPE mapRuleTable OBJECT-TYPE
SYNTAX SEQUENCE OF MapRuleEntry SYNTAX SEQUENCE OF MapRuleEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 8, line 15 skipping to change at page 8, line 15
::= { mapRuleEntry 5 } ::= { mapRuleEntry 5 }
-- The object mapRuleBRIPv6Address is IPv6 specific and hence it does -- The object mapRuleBRIPv6Address is IPv6 specific and hence it does
-- not use the version agnostic InetAddress. -- not use the version agnostic InetAddress.
mapRuleBRIPv6Address OBJECT-TYPE mapRuleBRIPv6Address OBJECT-TYPE
SYNTAX InetAddressIPv6 SYNTAX InetAddressIPv6
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IPv6 address of the BR which will be "The IPv6 address of the BR which will be conveyed to CE.
conveyed to CE. If the BR IPv6 address is anycast, the If the BR IPv6 address is anycast, the relay must use
relay must use this anycast IPv6 address as the source this anycast IPv6 address as the source address in
address in packets relayed to CEs." packets relayed to CEs."
::= { mapRuleEntry 6 } ::= { mapRuleEntry 6 }
mapRulePSID OBJECT-TYPE mapRulePSID OBJECT-TYPE
SYNTAX RulePSID SYNTAX RulePSID
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The PSID value algorithmically identifies a set of "The PSID value algorithmically identifies a set of
ports assigned to a CE." ports assigned to a CE."
REFERENCE REFERENCE
skipping to change at page 9, line 24 skipping to change at page 9, line 24
"EA: section 3 of RFC 7597." "EA: section 3 of RFC 7597."
::= { mapRuleEntry 10 } ::= { mapRuleEntry 10 }
mapRuleType OBJECT-TYPE mapRuleType OBJECT-TYPE
SYNTAX RuleType SYNTAX RuleType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the type of mapping rule. "Indicates the type of mapping rule.
'1' represents a BMR. '1' represents a BMR.
'2' represents an FMR and '3' is for a BMR which '2' represents a FMR and '3' is for a BMR which
is also an FMR for mesh mode." is also an FMR for mesh mode."
REFERENCE REFERENCE
"bmr, fmr: section 5 of RFC 7597. "bmr, fmr: section 5 of RFC 7597.
bmrAndfmr: section 5 of RFC 7597,section 4.1 of RFC 7598." bmrAndfmr: section 5 of RFC 7597, section 4.1 of
RFC 7598."
::= { mapRuleEntry 11 } ::= { mapRuleEntry 11 }
mapSecurityCheckTable OBJECT-TYPE mapSecurityCheckTable OBJECT-TYPE
SYNTAX SEQUENCE OF MapSecurityCheckEntry SYNTAX SEQUENCE OF MapSecurityCheckEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
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 for MAP security checks. This table can be used for
statistics on the number of invalid packets that statistics on the number of invalid packets that
skipping to change at page 10, line 30 skipping to change at page 10, line 30
port within the range defined in the matching MAP port within the range defined in the matching MAP
rule." rule."
::= { mapSecurityCheckEntry 1 } ::= { mapSecurityCheckEntry 1 }
mapSecurityCheckInvalidv6 OBJECT-TYPE mapSecurityCheckInvalidv6 OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the number of received IPv6 packets which "Indicates the number of received IPv6 packets which
do not have a source or destination IPv6 address matching do not have a source or destination IPv6 address
a Basic Mapping Rule." matching a Basic Mapping Rule."
::= { 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 }
-- compliance statements -- compliance statements
mapMIBCompliance MODULE-COMPLIANCE mapMIBCompliance MODULE-COMPLIANCE
STATUS current STATUS current
skipping to change at page 13, line 19 skipping to change at page 13, line 19
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 principals (users) that have legitimate the objects only to those principals (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. Acknowledgements 8. Acknowledgements
The authors would like to thank for valuable comments from David The authors would like to thank for valuable comments from David
Harrington, Mark Townsley, Shishio Tsuchiya, Yong Cui, Suresh Harrington, Mark Townsley, Shishio Tsuchiya, Yong Cui, Suresh
Krishnan, Bert Wijnen, Ian Farrer and Juergen Schoenwaelder. Krishnan, Bert Wijnen, Ian Farrer and Juergen Schoenwaelder.
This document was produced using the xml2rfc tool [RFC7749]. This document was produced using the xml2rfc tool [RFC7991].
9. References 9. References
9.1. Normative 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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
skipping to change at page 15, line 10 skipping to change at page 15, line 10
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
Shell Transport Model for the Simple Network Management Shell Transport Model for the Simple Network Management
Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June
2009, <https://www.rfc-editor.org/info/rfc5592>. 2009, <https://www.rfc-editor.org/info/rfc5592>.
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
Model for the Simple Network Management Protocol (SNMP)", Model for the Simple Network Management Protocol (SNMP)",
STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011,
<https://www.rfc-editor.org/info/rfc6353>. <https://www.rfc-editor.org/info/rfc6353>.
[RFC7749] Reschke, J., "The "xml2rfc" Version 2 Vocabulary", [RFC7991] Hoffman, P., "The "xml2rfc" Version 3 Vocabulary",
RFC 7749, DOI 10.17487/RFC7749, February 2016, RFC 7991, DOI 10.17487/RFC7991, December 2016,
<https://www.rfc-editor.org/info/rfc7749>. <https://www.rfc-editor.org/info/rfc7991>.
Authors' Addresses Authors' Addresses
Yu Fu Yu Fu
CNNIC CNNIC
No.4 South 4th Street, Zhongguancun No.4 South 4th Street, Zhongguancun
Beijing 100190 Beijing 100190
P.R. China P.R. China
Email: fuyu@cnnic.cn Email: fuyu@cnnic.cn
 End of changes. 18 change blocks. 
25 lines changed or deleted 26 lines changed or added

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