draft-ietf-softwire-map-mib-09.txt   draft-ietf-softwire-map-mib-10.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: November 28, 2017 B. Liu Expires: March 19, 2018 B. Liu
Huawei Technologies Co., Ltd Huawei Technologies Co., Ltd
J. Dong J. Dong
Y. Chen Y. Chen
Tsinghua University Tsinghua University
May 27, 2017 September 15, 2017
Definitions of Managed Objects for MAP-E Definitions of Managed Objects for MAP-E
draft-ietf-softwire-map-mib-09 draft-ietf-softwire-map-mib-10
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 using with network management protocols in the Internet for using with network management protocols in the Internet
community. In particular, it defines managed objects for MAP community. In particular, it defines managed objects for MAP
encapsulation (MAP-E) mode. encapsulation (MAP-E) mode.
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 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 November 28, 2017. This Internet-Draft will expire on March 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
(http://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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . 2 2. The Internet-Standard Management Framework . . . . . . . . . 2
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Structure of the MIB Module . . . . . . . . . . . . . . . . . 3 4. Structure of the MIB Module . . . . . . . . . . . . . . . . . 3
4.1. The mapMIBObjects . . . . . . . . . . . . . . . . . . . . 3 4.1. The mapMIBObjects . . . . . . . . . . . . . . . . . . . . 3
4.1.1. The mapRule Subtree . . . . . . . . . . . . . . . . . 3 4.1.1. The mapRule Subtree . . . . . . . . . . . . . . . . . 3
4.1.2. The mapSecurityCheck Subtree . . . . . . . . . . . . 3 4.1.2. The mapSecurityCheck Subtree . . . . . . . . . . . . 3
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 . . . . . . . . . . . . . . . . . . . 12
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 . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
Mapping of Address and Port (MAP) [RFC7597] is a stateless mechanism Mapping of Address and Port with Encapsulation (MAP-E) [RFC7597] is a
for running IPv4 over IPv6-only infrastructure. In particular, it stateless mechanism for running IPv4 over IPv6-only infrastructure.
includes two mode, translation mode or encapsulation mode. For the In particular, it includes two mode, translation mode or
encapsulation mode, it provides an automatic tunnelling mechanism for encapsulation mode. For the encapsulation mode, it provides an
providing IPv4 connectivity service to end users over a service automatic tunnelling mechanism for providing IPv4 connectivity
provider's IPv6 network service to end users over a service provider's IPv6 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 network management protocols in the Internet (MIB) for use with network management protocols in the Internet
community. This MIB module would be used for monitoring the devices community. This MIB module would be used for monitoring the devices
in the MAP scenario, especially, for the encapsulation mode. 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
skipping to change at page 3, line 41 skipping to change at page 3, line 41
divided into two categories, which are Basic Mapping Rule (BMR), and divided into two categories, which are Basic Mapping Rule (BMR), and
Forwarding Mapping Rule (FMR). Forwarding Mapping Rule (FMR).
4.1.2. The mapSecurityCheck Subtree 4.1.2. The mapSecurityCheck Subtree
The mapSecurityCheck subtree is to statistic the number of invalid The mapSecurityCheck subtree is to statistic 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 MAP specification [RFC7597]as below. packets which are defined in the MAP specification [RFC7597]as below.
- The Border Relay (BR) will perform a validation of the consistency - The Border Relay (BR) will perform a validation of the consistency
of the source IPv6 address and source port number for the packet of the source IPv6 address and destination IPv6 address for the
using Basic Mapping Rule (BMR). packet using Basic Mapping Rule (BMR).
- The Customer Edge (CE) will check that MAP received packets' - The Map node (CE and BR) will check that the received packets'
transport-layer destination port number is in the range configured by source IPv4 address and port is in the range derived from the
MAP for the CE. 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 "201705270000Z" LAST-UPDATED "201709150000Z"
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 21 skipping to change at page 5, line 23
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 "201705270000Z" REVISION "201709150000Z"
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 5, line 46 skipping to change at page 5, line 48
-- ============================================================== -- ==============================================================
-- Textual Conventions used in this MIB module -- Textual Conventions used in this MIB module
-- ============================================================== -- ==============================================================
RulePSID ::= TEXTUAL-CONVENTION RulePSID ::= TEXTUAL-CONVENTION
DISPLAY-HINT "0x:" DISPLAY-HINT "0x:"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"It represents the PSID represented in the hexadecimal version "It represents the PSID represented in the hexadecimal version
so as to display it more clearly." so as to display it more clearly."
SYNTAX OCTET STRING (SIZE (4)) SYNTAX OCTET STRING (SIZE (2))
RuleType ::= TEXTUAL-CONVENTION RuleType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This enumeration provides the type of the mapping rule. There "This enumeration provides the type of the mapping rule. It
are two types of mapping rules: Basic Mapping Rule (BMR) and defines tree types of mapping rules here:
Forwarding Mapping Rule (FMR)." bmr: Basic Mapping Rule (Not Forwarding Mapping Rule),
REFERENCE "bmr, fmr: section 5 of RFC 7597" fmr: Forwarding Mapping Rule (Not Basic Mapping Rule),
bmrAndfmr: Basic and Forwarding Mapping Rule. The Basic
Mapping Rule may also be a Forwarding Mapping Rule for
mesh mode."
REFERENCE "bmr, fmr: section 5 of RFC 7597.
bmrAndfmr: section 5 of RFC 7597,section 4.1 of RFC
7598."
SYNTAX INTEGER { SYNTAX INTEGER {
bmr(1), bmr(1),
fmr(2) fmr(2),
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
DESCRIPTION DESCRIPTION
"The (conceptual) table containing rule Information of "The (conceptual) table containing rule Information of
specific mapping rule. It can also be used for row specific mapping rule. It can also be used for row
creation." creation."
skipping to change at page 7, line 4 skipping to change at page 7, line 14
mapRuleOffset Unsigned32, mapRuleOffset Unsigned32,
mapRuleEALen Unsigned32, mapRuleEALen Unsigned32,
mapRuleType RuleType mapRuleType RuleType
} }
mapRuleID OBJECT-TYPE mapRuleID OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An identifier used to distinguish the multiple mapping "A unique identifier used to distinguish mapping
rule which is unique with each CE in the same BR." rules."
::= { mapRuleEntry 1 } ::= { mapRuleEntry 1 }
-- The object mapRuleIPv6Prefix is IPv6 specific and hence it does -- The object mapRuleIPv6Prefix is IPv6 specific and hence it does
-- not use the version agnostic InetAddress. -- not use the version agnostic InetAddress.
mapRuleIPv6Prefix OBJECT-TYPE mapRuleIPv6Prefix OBJECT-TYPE
SYNTAX InetAddressIPv6 SYNTAX InetAddressIPv6
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 8, line 16 skipping to change at page 8, line 26
-- 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
relay must use this anycast IPv6 address as the source
address in 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 8, line 45 skipping to change at page 9, line 8
"The bit length value of the number of significant bits in "The bit length value of the number of significant bits in
the PSID field. When it is set to 0, the PSID the PSID field. When it is set to 0, the PSID
field is to be ignored." field is to be ignored."
::= { mapRuleEntry 8 } ::= { mapRuleEntry 8 }
mapRuleOffset OBJECT-TYPE mapRuleOffset OBJECT-TYPE
SYNTAX Unsigned32(0..15) SYNTAX Unsigned32(0..15)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Bit length value of the number of significant bits in "The number of the mapRuleOffset is 6 by default as to
the PSID field. When it is set to 0, the PSID exclude the System ports (0-1023). It is provided via
field is to be ignored." the Rule Port Mapping Parameters in the Basic Mapping
Rule."
DEFVAL {6}
::= { mapRuleEntry 9 } ::= { mapRuleEntry 9 }
mapRuleEALen OBJECT-TYPE mapRuleEALen OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32(0..48)
MAX-ACCESS read-only MAX-ACCESS read-only
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."
REFERENCE REFERENCE
"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
"It represents the type of the mapping rule. the value of "It represents the type of the mapping rule. The value of
1 means it is a bmr; the value 2 means it is a fmr." 1 means it is a bmr, the value 2 means it is a fmr, the
REFERENCE value 3 means that the bmr is also a fmr for mesh mode."
"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 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 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."
skipping to change at page 10, line 6 skipping to change at page 10, line 24
SEQUENCE { SEQUENCE {
mapSecurityCheckInvalidv4 Counter64, mapSecurityCheckInvalidv4 Counter64,
mapSecurityCheckInvalidv6 Counter64 mapSecurityCheckInvalidv6 Counter64
} }
mapSecurityCheckInvalidv4 OBJECT-TYPE mapSecurityCheckInvalidv4 OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The CE SHOULD check that MAP received packets' "The Map node (CE and BR) will check that the received
transport-layer destination port number is in the range packets'source IPv4 address and port is in the range
configured by MAP for the CE. So this object indicate derived from matching MAP Rule.So this object indicate
the number of the invalid IPv4 packets received by the the number of the invalid IPv4 packets received by the
MAP." MAP domain."
::= { 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
"The BR MUST perform a validation of the consistency of "The BR will perform a validation of the consistency
the source IPv6 address and source port number for the of the source IPv6 address and destination IPv6 address
packet using BMR. So this object indicate the number of for the packet using Basic Mapping Rule (BMR). So this
the invalid IPv6 packets received by the BR." 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 }
-- compliance statements -- compliance statements
mapMIBCompliance MODULE-COMPLIANCE mapMIBCompliance MODULE-COMPLIANCE
STATUS current STATUS current
skipping to change at page 13, line 20 skipping to change at page 13, line 39
This document was produced using the xml2rfc tool [RFC2629]. This document was produced using the xml2rfc tool [RFC2629].
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,
<http://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, Version 2 (SMIv2)", STD 58, RFC 2578,
DOI 10.17487/RFC2578, April 1999, DOI 10.17487/RFC2578, April 1999,
<http://www.rfc-editor.org/info/rfc2578>. <https://www.rfc-editor.org/info/rfc2578>.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, STD 58, RFC 2579, DOI 10.17487/RFC2579, April 1999,
<http://www.rfc-editor.org/info/rfc2579>. <https://www.rfc-editor.org/info/rfc2579>.
[RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Conformance Statements for SMIv2", Schoenwaelder, Ed., "Conformance Statements for SMIv2",
STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999,
<http://www.rfc-editor.org/info/rfc2580>. <https://www.rfc-editor.org/info/rfc2580>.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000,
<http://www.rfc-editor.org/info/rfc2863>. <https://www.rfc-editor.org/info/rfc2863>.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, DOI 10.17487/RFC4001, February 2005, Addresses", RFC 4001, DOI 10.17487/RFC4001, February 2005,
<http://www.rfc-editor.org/info/rfc4001>. <https://www.rfc-editor.org/info/rfc4001>.
[RFC7597] Troan, O., Ed., Dec, W., Li, X., Bao, C., Matsushima, S., [RFC7597] Troan, O., Ed., Dec, W., Li, X., Bao, C., Matsushima, S.,
Murakami, T., and T. Taylor, Ed., "Mapping of Address and Murakami, T., and T. Taylor, Ed., "Mapping of Address and
Port with Encapsulation (MAP-E)", RFC 7597, Port with Encapsulation (MAP-E)", RFC 7597,
DOI 10.17487/RFC7597, July 2015, DOI 10.17487/RFC7597, July 2015,
<http://www.rfc-editor.org/info/rfc7597>. <https://www.rfc-editor.org/info/rfc7597>.
[RFC7598] Mrugalski, T., Troan, O., Farrer, I., Perreault, S., Dec,
W., Bao, C., Yeh, L., and X. Deng, "DHCPv6 Options for
Configuration of Softwire Address and Port-Mapped
Clients", RFC 7598, DOI 10.17487/RFC7598, July 2015,
<https://www.rfc-editor.org/info/rfc7598>.
9.2. Informative References 9.2. Informative References
[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
DOI 10.17487/RFC2629, June 1999, DOI 10.17487/RFC2629, June 1999,
<http://www.rfc-editor.org/info/rfc2629>. <https://www.rfc-editor.org/info/rfc2629>.
[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, Standard Management Framework", RFC 3410,
DOI 10.17487/RFC3410, December 2002, DOI 10.17487/RFC3410, December 2002,
<http://www.rfc-editor.org/info/rfc3410>. <https://www.rfc-editor.org/info/rfc3410>.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management (USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414, Protocol (SNMPv3)", STD 62, RFC 3414,
DOI 10.17487/RFC3414, December 2002, DOI 10.17487/RFC3414, December 2002,
<http://www.rfc-editor.org/info/rfc3414>. <https://www.rfc-editor.org/info/rfc3414>.
[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
Advanced Encryption Standard (AES) Cipher Algorithm in the Advanced Encryption Standard (AES) Cipher Algorithm in the
SNMP User-based Security Model", RFC 3826, SNMP User-based Security Model", RFC 3826,
DOI 10.17487/RFC3826, June 2004, DOI 10.17487/RFC3826, June 2004,
<http://www.rfc-editor.org/info/rfc3826>. <https://www.rfc-editor.org/info/rfc3826>.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
for the Simple Network Management Protocol (SNMP)", for the Simple Network Management Protocol (SNMP)",
STD 78, RFC 5591, DOI 10.17487/RFC5591, June 2009, STD 78, RFC 5591, DOI 10.17487/RFC5591, June 2009,
<http://www.rfc-editor.org/info/rfc5591>. <https://www.rfc-editor.org/info/rfc5591>.
[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, <http://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,
<http://www.rfc-editor.org/info/rfc6353>. <https://www.rfc-editor.org/info/rfc6353>.
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. 40 change blocks. 
63 lines changed or deleted 83 lines changed or added

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