draft-ietf-softwire-dslite-mib-08.txt   draft-ietf-softwire-dslite-mib-09.txt 
Internet Engineering Task Force Y. Fu Internet Engineering Task Force Y. Fu
Internet-Draft S. Jiang Internet-Draft S. Jiang
Intended status: Standards Track Huawei Technologies Co., Ltd Intended status: Standards Track Huawei Technologies Co., Ltd
Expires: August 12, 2015 J. Dong Expires: September 26, 2015 J. Dong
Y. Chen Y. Chen
Tsinghua University Tsinghua University
February 8, 2015 March 25, 2015
DS-Lite Management Information Base (MIB) DS-Lite Management Information Base (MIB)
draft-ietf-softwire-dslite-mib-08 draft-ietf-softwire-dslite-mib-09
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 Dual-Stack community. In particular, it defines managed objects for Dual-Stack
Lite (DS-Lite). Lite (DS-Lite).
Status of This Memo Status of This Memo
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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 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 August 12, 2015. This Internet-Draft will expire on September 26, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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 13 skipping to change at page 2, line 13
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. Requirements Language . . . . . . . . . . . . . . . . . . . . 2 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2
3. The Internet-Standard Management Framework . . . . . . . . . 3 3. The Internet-Standard Management Framework . . . . . . . . . 3
4. Relationship to the IF-MIB . . . . . . . . . . . . . . . . . 3 4. Relationship to the IF-MIB . . . . . . . . . . . . . . . . . 3
5. Difference from the IP tunnel MIB and NAT MIB . . . . . . . . 3 5. Difference from the IP tunnel MIB and NATV2-MIB . . . . . . . 3
6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4
6.1. The Object Group . . . . . . . . . . . . . . . . . . . . 4 6.1. The Object Group . . . . . . . . . . . . . . . . . . . . 4
6.1.1. The dsliteTunnel Subtree . . . . . . . . . . . . . . 5 6.1.1. The dsliteTunnel Subtree . . . . . . . . . . . . . . 5
6.1.2. The dsliteNAT Subtree . . . . . . . . . . . . . . . . 5 6.1.2. The dsliteNAT Subtree . . . . . . . . . . . . . . . . 5
6.1.3. The dsliteInfo Subtree . . . . . . . . . . . . . . . 5 6.1.3. The dsliteInfo Subtree . . . . . . . . . . . . . . . 5
6.2. The Notification Group . . . . . . . . . . . . . . . . . 5 6.2. The Notification Group . . . . . . . . . . . . . . . . . 5
6.2.1. The dsliteTrap Subtree . . . . . . . . . . . . . . . 5 6.2.1. The dsliteTrap Subtree . . . . . . . . . . . . . . . 5
6.3. The Conformance Group . . . . . . . . . . . . . . . . . . 5 6.3. The Conformance Group . . . . . . . . . . . . . . . . . . 5
7. MIB modules required for IMPORTS . . . . . . . . . . . . . . 5 7. MIB modules required for IMPORTS . . . . . . . . . . . . . . 5
8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5
skipping to change at page 2, line 50 skipping to change at page 2, line 50
customers. customers.
This document defines a portion of the Management Information Base This document defines a portion of the Management Information Base
(MIB) for using with network management protocols in the Internet (MIB) for using with network management protocols in the Internet
community. This MIB module may be used for configuration and community. This MIB module may be used for configuration and
monitoring devices in a Dual-Stack Lite scenario. monitoring devices in a Dual-Stack Lite scenario.
2. Requirements Language 2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
"OPTIONAL" in this document are to be interpreted as described in document are to be interpreted as described in [RFC2119] when they
appear in ALL CAPS. When these words are not in ALL CAPS (such as
[RFC2119] when they appear in ALL CAPS. When these words are not in "should" or "Should"), they have their usual English meanings, and
ALL CAPS (such as "should" or "Should"), they have their usual are not to be interpreted as [RFC2119] key words.
English meanings, and are not to be interpreted as [RFC2119] key
words.
3. The Internet-Standard Management Framework 3. 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 Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 3, line 43 skipping to change at page 3, line 41
The ifOperStatus in ifTable is used to represent whether the DS-Lite The ifOperStatus in ifTable is used to represent whether the DS-Lite
tunnel function has been originated. The ifInUcastPkts defined in tunnel function has been originated. The ifInUcastPkts defined in
ifTable will represent the number of IPv4 packets that have been ifTable will represent the number of IPv4 packets that have been
encapsulated into IPv6 packets sent to a B4. The ifOutUcastPkts encapsulated into IPv6 packets sent to a B4. The ifOutUcastPkts
defined in ifTable contains the number of IPv6 packets that can be defined in ifTable contains the number of IPv6 packets that can be
decapsulated to IPv4 in the virtual interface. Also, the IF-MIB decapsulated to IPv4 in the virtual interface. Also, the IF-MIB
defines ifMtu for the MTU of this tunnel interface, so DS-Lite MIB defines ifMtu for the MTU of this tunnel interface, so DS-Lite MIB
does not need to define the MTU for the tunnel. does not need to define the MTU for the tunnel.
5. Difference from the IP tunnel MIB and NAT MIB 5. Difference from the IP tunnel MIB and NATV2-MIB
The key technologies for DS-Lite are IP in IP (IPv4-in-IPv6) tunnels The key technologies for DS-Lite are IP in IP (IPv4-in-IPv6) tunnels
and NAT (IPv4 to IPv4 translation). and NAT (IPv4 to IPv4 translation).
Notes: According to section 5.2 of [RFC6333], DS-Lite only defines Notes: According to section 5.2 of [RFC6333], DS-Lite only defines
IPv4 in IPv6 tunnels at this moment, but other types of encapsulation IPv4 in IPv6 tunnels at this moment, but other types of encapsulation
could be defined in the future. So this DS-Lite MIB only supports IP could be defined in the future. So this DS-Lite MIB only supports IP
in IP encapsulation, if another RFC defined other tunnel types in the in IP encapsulation, if another RFC defined other tunnel types in the
future, this DS-Lite MIB will be updated then. future, this DS-Lite MIB will be updated then.
skipping to change at page 4, line 19 skipping to change at page 4, line 19
The IP Tunnel MIB [RFC4087] is designed for managing tunnels of any The IP Tunnel MIB [RFC4087] is designed for managing tunnels of any
type over IPv4 and IPv6 networks, therefore it supports IP in IP type over IPv4 and IPv6 networks, therefore it supports IP in IP
tunnels. In a DS-Lite scenario, the tunnel type is IP in IP, more tunnels. In a DS-Lite scenario, the tunnel type is IP in IP, more
precisely, is IPv4 in IPv6. Therefore, it is unnecessary to define a precisely, is IPv4 in IPv6. Therefore, it is unnecessary to define a
new object to describe tunnel type in DS-Lite MIB. new object to describe tunnel type in DS-Lite MIB.
However, the NATV2-MIB and IP Tunnel MIB together are not sufficient However, the NATV2-MIB and IP Tunnel MIB together are not sufficient
to support DS-Lite. This document describes the specific features to support DS-Lite. This document describes the specific features
for DS-Lite MIB, as below. for DS-Lite MIB, as below.
In a DS-Lite scenario, the Address Family Transition Router (AFTR) is In the DS-Lite scenario, the Address Family Transition Router (AFTR)
not only the tunnel end concentrator, but also a 4-4 translator. So is not only the tunnel end concentrator, but also a 4-4 translator.
as defined in [RFC6333] , when the IPv4 packets come back from the So as defined in [RFC6333] , when the IPv4 packets come back from the
Internet to AFTR, the AFTR knows how to reconstruct the IPv6 Internet to AFTR, the AFTR knows how to reconstruct the IPv6
encapsulation by doing a reverse lookup in the extended IPv4 NAT encapsulation by doing a reverse lookup in the extended IPv4 NAT
binding table. So the NAT binding table in the AFTR MUST be extended binding table. So the NAT binding table in the AFTR MUST be extended
to include the IPv6 address of the tunnel initiator. But the NAT to include the IPv6 address of the tunnel initiator. But the tunnel
binding entry defined in the NATV2-MIB are not extended by the object information defined in NATV2-MIB is on the address level. Because
definded for the tunnel initiator. Therefore, a combined MIB is the TUNNEL-MIB defined the objects on the view of interface, the DS-
Lite-MIB need define the tunnel objects to extend the NAT binding
entry by interface for accordance. Therefore, a combined MIB is
necessary. necessary.
The implementation of the IP Tunnel MIB is required for DS-Lite. The The implementation of the IP Tunnel MIB is required for DS-Lite. The
tunnelIfEncapsMethod in the tunnelIfEntry should be set to tunnelIfEncapsMethod in the tunnelIfEntry should be set to
dsLite("xx"), and a corresponding entry in the DS-Lite module will dsLite("xx"), and a corresponding entry in the DS-Lite module will
exist for every tunnelIfEntry with this tunnelIfEncapsMethod. The exist for every tunnelIfEntry with this tunnelIfEncapsMethod. The
tunnelIfRemoteInetAddress must be set to "::". tunnelIfRemoteInetAddress must be set to "::".
6. Structure of the MIB Module 6. Structure of the MIB Module
skipping to change at page 6, line 26 skipping to change at page 6, line 26
FROM IF-MIB FROM IF-MIB
InetAddress, InetAddressType, InetAddressPrefixLength, InetAddress, InetAddressType, InetAddressPrefixLength,
InetPortNumber InetPortNumber
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
ProtocolNumber, Natv2InstanceIndex, Natv2SubscriberIndex ProtocolNumber, Natv2InstanceIndex, Natv2SubscriberIndex
FROM NATV2-MIB; FROM NATV2-MIB;
dsliteMIB MODULE-IDENTITY dsliteMIB MODULE-IDENTITY
LAST-UPDATED "201502080000Z" -- February 08, 2015 LAST-UPDATED "201503250000Z" -- March 25, 2015
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 7, line 12 skipping to change at page 7, line 12
Beijing 100084 Beijing 100084
P.R. China P.R. China
Email: flashfoxmx@gmail.com " Email: flashfoxmx@gmail.com "
DESCRIPTION DESCRIPTION
"The MIB module is defined for management of object in the "The MIB module is defined for management of object in the
DS-Lite scenario. DS-Lite scenario.
Copyright (C) The Internet Society (2015). This version Copyright (C) The Internet Society (2015). This version
of this MIB module is part of RFC yyyy; see the RFC itself of this MIB module is part of RFC yyyy; see the RFC itself
for full legal notices. " for full legal notices. "
REVISION "201502080000Z" REVISION "201503250000Z"
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 }
--RFC Ed.: assigned by IANA, see section 10 for details --RFC Ed.: assigned by IANA, see section 10 for details
--Top level components of this MIB module --Top level components of this MIB module
dsliteMIBObjects OBJECT IDENTIFIER dsliteMIBObjects OBJECT IDENTIFIER
::= { dsliteMIB 1 } ::= { dsliteMIB 1 }
skipping to change at page 9, line 20 skipping to change at page 9, line 20
dsliteTunnelStartAddPreLen OBJECT-TYPE dsliteTunnelStartAddPreLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"IPv6 prefix length of the IP address for the "IPv6 prefix length of the IP address for the
start point of the tunnel." start point of the tunnel."
::= { dsliteTunnelEntry 4 } ::= { dsliteTunnelEntry 4 }
--dsliteNAT --dsliteNAT
--dsliteNATMapTable(The address pool defined by natv2PoolTable and natv2PoolRangeTable --dsliteNATMapTable(The address pool defined by
--natv2PoolTable and natv2PoolRangeTable
--in draft-perrault-behave-natv2-mib are sufficient) --in draft-perrault-behave-natv2-mib are sufficient)
--dsliteNATBindTable(NAPT) --dsliteNATBindTable(NAPT)
dsliteNATBindTable OBJECT-TYPE dsliteNATBindTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsliteNATBindEntry SYNTAX SEQUENCE OF DsliteNATBindEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information about currently "This table contains information about currently
active NAT binds in the NAT of AFTR. This table extends the active NAT binds in the NAT of AFTR. This table extends the
skipping to change at page 10, line 21 skipping to change at page 10, line 22
dsliteNATBindMappingProto ProtocolNumber, dsliteNATBindMappingProto ProtocolNumber,
dsliteNATBindMappingExtRealm SnmpAdminString, dsliteNATBindMappingExtRealm SnmpAdminString,
dsliteNATBindMappingExtAddressType InetAddressType, dsliteNATBindMappingExtAddressType InetAddressType,
dsliteNATBindMappingExtAddress InetAddress, dsliteNATBindMappingExtAddress InetAddress,
dsliteNATBindMappingExtPort InetPortNumber, dsliteNATBindMappingExtPort InetPortNumber,
dsliteNATBindMappingIntRealm SnmpAdminString, dsliteNATBindMappingIntRealm SnmpAdminString,
dsliteNATBindMappingIntAddressType InetAddressType, dsliteNATBindMappingIntAddressType InetAddressType,
dsliteNATBindMappingIntAddress InetAddress, dsliteNATBindMappingIntAddress InetAddress,
dsliteNATBindMappingIntPort InetPortNumber, dsliteNATBindMappingIntPort InetPortNumber,
dsliteNATBindMappingPool Unsigned32, dsliteNATBindMappingPool Unsigned32,
dsliteNATBindMappingMapBehavior NatBehaviorType, dsliteNATBindMappingMapBehavior INTEGER,
dsliteNATBindMappingFilterBehavior NatBehaviorType, dsliteNATBindMappingFilterBehavior INTEGER,
dsliteNATBindMappingAddressPooling NatPoolingType dsliteNATBindMappingAddressPooling NatPoolingType
} }
dsliteNATBindMappingInstanceIndex dsliteNATBindMappingInstanceIndex
SYNTAX Natv2InstanceIndex SYNTAX Natv2InstanceIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Index of the NAT instance that created this port map entry." "Index of the NAT instance that created this port map entry."
::= { dsliteNATBindEntry 1 } ::= { dsliteNATBindEntry 1 }
skipping to change at page 11, line 26 skipping to change at page 11, line 28
"The mapping's external address. If this is the undefined "The mapping's external address. If this is the undefined
address, all external addresses are mapped to the internal address, all external addresses are mapped to the internal
address." address."
::= { dsliteNATBindEntry 5 } ::= { dsliteNATBindEntry 5 }
dsliteNATBindMappingExtPort OBJECT-TYPE dsliteNATBindMappingExtPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mapping's assigned external port number. If this is zero, all "The mapping's assigned external port number. If this is zero,
external ports are mapped to the internal port." all external ports are mapped to the internal port."
::= { dsliteNATBindEntry 6 } ::= { dsliteNATBindEntry 6 }
dsliteNATBindMappingIntRealm OBJECT-TYPE dsliteNATBindMappingIntRealm OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The realm to which natMappingIntAddress belongs." "The realm to which natMappingIntAddress belongs."
::= { dsliteNATBindEntry 7 } ::= { dsliteNATBindEntry 7 }
skipping to change at page 20, line 23 skipping to change at page 20, line 24
This document was produced using the xml2rfc tool [RFC2629]. This document was produced using the xml2rfc tool [RFC2629].
12. References 12. References
12.1. Normative References 12.1. Normative References
[I-D.perrault-behave-natv2-mib] [I-D.perrault-behave-natv2-mib]
Perreault, S., Tsou, T., Sivakumar, S., and T. Taylor, Perreault, S., Tsou, T., Sivakumar, S., and T. Taylor,
"Definitions of Managed Objects for Network Address "Definitions of Managed Objects for Network Address
Translators (NAT)", draft-perrault-behave-natv2-mib-00 Translators (NAT)", draft-perrault-behave-natv2-mib-02
(work in progress), January 2015. (work in progress), February 2015.
[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, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
skipping to change at page 20, line 46 skipping to change at page 20, line 47
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network Management Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
December 2002. December 2002.
[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, February 2005. Addresses", RFC 4001, February 2005.
[RFC4008] Rohit, R., Srisuresh, P., Raghunarayan, R., Pai, N., and
C. Wang, "Definitions of Managed Objects for Network
Address Translators (NAT)", RFC 4008, March 2005.
[RFC4087] Thaler, D., "IP Tunnel MIB", RFC 4087, June 2005. [RFC4087] Thaler, D., "IP Tunnel MIB", RFC 4087, June 2005.
[RFC4787] Audet, F. and C. Jennings, "Network Address Translation
(NAT) Behavioral Requirements for Unicast UDP", BCP 127,
RFC 4787, January 2007.
[RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual-
Stack Lite Broadband Deployments Following IPv4 Stack Lite Broadband Deployments Following IPv4
Exhaustion", RFC 6333, August 2011. Exhaustion", RFC 6333, August 2011.
12.2. Informative References 12.2. Informative 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.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD
58, RFC 2579, April 1999. 58, RFC 2579, April 1999.
[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
June 1999. June 1999.
[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.
Authors' Addresses [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
Advanced Encryption Standard (AES) Cipher Algorithm in the
SNMP User-based Security Model", RFC 3826, June 2004.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
for the Simple Network Management Protocol (SNMP)", STD
78, RFC 5591, June 2009.
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
Shell Transport Model for the Simple Network Management
Protocol (SNMP)", RFC 5592, June 2009.
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
Model for the Simple Network Management Protocol (SNMP)",
STD 78, RFC 6353, July 2011.
Authors' Addresses
Yu Fu Yu Fu
Huawei Technologies Co., Ltd Huawei Technologies Co., Ltd
Q14, Huawei Campus, No.156 Beiqing Road Q14, Huawei Campus, No.156 Beiqing Road
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
 End of changes. 19 change blocks. 
33 lines changed or deleted 53 lines changed or added

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