draft-ietf-capwap-802dot11-mib-04.txt   draft-ietf-capwap-802dot11-mib-05.txt 
Internet Engineering Task Force Y. Shi, Ed. Internet Engineering Task Force Y. Shi, Ed.
Internet-Draft H3C Tech. Co., Ltd Internet-Draft Hangzhou H3C Tech. Co., Ltd.
Intended status: Standards Track D. Perkins, Ed. Intended status: Standards Track D. Perkins, Ed.
Expires: December 1, 2009 SNMPinfo Expires: February 14, 2010 SNMPinfo
C. Elliott, Ed. C. Elliott, Ed.
Cisco Systems, Inc. Cisco Systems, Inc.
Y. Zhang, Ed. Y. Zhang, Ed.
Fortinet, Inc. Fortinet, Inc.
May 30, 2009 August 13, 2009
CAPWAP Protocol Binding MIB for IEEE 802.11 CAPWAP Protocol Binding MIB for IEEE 802.11
draft-ietf-capwap-802dot11-mib-04 draft-ietf-capwap-802dot11-mib-05
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF 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), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 1, 2009. This Internet-Draft will expire on February 14, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 31 skipping to change at page 2, line 31
5.2. Requirements and Constraints . . . . . . . . . . . . . . . 5 5.2. Requirements and Constraints . . . . . . . . . . . . . . . 5
5.3. Mechanism of Reusing Wireless Binding MIB Module . . . . . 6 5.3. Mechanism of Reusing Wireless Binding MIB Module . . . . . 6
6. Structure of MIB Module . . . . . . . . . . . . . . . . . . . 6 6. Structure of MIB Module . . . . . . . . . . . . . . . . . . . 6
7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 6 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 6
7.1. Relationship to SNMPv2-MIB Module . . . . . . . . . . . . 7 7.1. Relationship to SNMPv2-MIB Module . . . . . . . . . . . . 7
7.2. Relationship to IF-MIB Module . . . . . . . . . . . . . . 7 7.2. Relationship to IF-MIB Module . . . . . . . . . . . . . . 7
7.3. Relationship to CAPWAP-BASE-MIB Module . . . . . . . . . . 7 7.3. Relationship to CAPWAP-BASE-MIB Module . . . . . . . . . . 7
7.4. Relationship to MIB Module in IEEE 802.11 Standard . . . . 7 7.4. Relationship to MIB Module in IEEE 802.11 Standard . . . . 7
7.5. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 8 7.5. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 8
8. Example of CAPWAP-DOT11-MIB Module Usage . . . . . . . . . . . 8 8. Example of CAPWAP-DOT11-MIB Module Usage . . . . . . . . . . . 8
9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 13 9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 14
10. Security Considerations . . . . . . . . . . . . . . . . . . . 20 10. Security Considerations . . . . . . . . . . . . . . . . . . . 21
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
11.1. IANA Considerations for CAPWAP-DOT11-MIB Module . . . . . 21 11.1. IANA Considerations for CAPWAP-DOT11-MIB Module . . . . . 22
11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 21 11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 22
12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 21 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 22
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 21 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 22
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22
14.1. Normative References . . . . . . . . . . . . . . . . . . . 21 14.1. Normative References . . . . . . . . . . . . . . . . . . . 22
14.2. Informative References . . . . . . . . . . . . . . . . . . 23 14.2. Informative References . . . . . . . . . . . . . . . . . . 23
Appendix A. Appendix A. Changes between -04 and -03 . . . . . . . 23 Appendix A. Appendix A. Changes between -05 and -04 . . . . . . . 24
1. Introduction 1. Introduction
The CAPWAP Protocol [RFC5415] defines a standard, interoperable The CAPWAP Protocol [RFC5415] defines a standard, interoperable
protocol, which enables an Access Controller (AC) to manage a protocol, which enables an Access Controller (AC) to manage a
collection of Wireless Termination Points(WTPs). CAPWAP supports the collection of Wireless Termination Points(WTPs). CAPWAP supports the
use of various wireless technologies by the WTPs, with one specified use of various wireless technologies by the WTPs, with one specified
in the CAPWAP Protocol Binding for IEEE 802.11 [RFC5416]. in the CAPWAP Protocol Binding for IEEE 802.11 [RFC5416].
This document defines a MIB module that can be used to manage CAPWAP This document defines a MIB module that can be used to manage CAPWAP
skipping to change at page 8, line 22 skipping to change at page 8, line 22
7.5. MIB Modules Required for IMPORTS 7.5. MIB Modules Required for IMPORTS
The following MIB modules are required for IMPORTS: SNMPv2-SMI The following MIB modules are required for IMPORTS: SNMPv2-SMI
[RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB
[RFC2863] and CAPWAP-BASE-MIB [I-D.ietf-capwap-base-mib]. [RFC2863] and CAPWAP-BASE-MIB [I-D.ietf-capwap-base-mib].
8. Example of CAPWAP-DOT11-MIB Module Usage 8. Example of CAPWAP-DOT11-MIB Module Usage
1) Create a WTP profile 1) Create a WTP profile
Suppose the WTP's serial identifier is '12345678'. Creates a WTP Suppose the WTP's base MAC address is '00:01:01:01:01:00'. Creates a
profile for it through the CapwapBaseWtpProfileTable WTP profile for it through the CapwapBaseWtpProfileTable
[I-D.ietf-capwap-base-mib] as follows: [I-D.ietf-capwap-base-mib] as follows:
In CapwapBaseWtpProfileTable In CapwapBaseWtpProfileTable
{ {
capwapBaseWtpProfileId = 1, capwapBaseWtpProfileId = 1,
capwapBaseWtpProfileName = 'WTP Profile 12345678', capwapBaseWtpProfileName = 'WTP Profile 123456',
capwapBaseWtpProfileWTPSerialId = '12345678', capwapBaseWtpProfileWtpMacAddr = '00:01:01:01:01:00',
capwapBaseWtpProfileWTPModelNumber = 'WTP123', capwapBaseWtpProfileWTPModelNumber = 'WTP123',
capwapBaseWtpProfileWtpName = 'WTP 12345678', capwapBaseWtpProfileWtpName = 'WTP 123456',
capwapBaseWtpProfileWtpLocation = 'office', capwapBaseWtpProfileWtpLocation = 'office',
capwapBaseWtpProfileWtpStaticIpEnable = true(1), capwapBaseWtpProfileWtpStaticIpEnable = true(1),
capwapBaseWtpProfileWtpStaticIpType = ipv4(1), capwapBaseWtpProfileWtpStaticIpType = ipv4(1),
capwapBaseWtpProfileWtpStaticIp = '192.168.0.100', capwapBaseWtpProfileWtpStaticIp = '192.168.0.100',
capwapBaseWtpProfileWtpNetmask = '255.255.255.0', capwapBaseWtpProfileWtpNetmask = '255.255.255.0',
capwapBaseWtpProfileWtpGateway = '192.168.0.1', capwapBaseWtpProfileWtpGateway = '192.168.0.1',
capwapBaseWtpProfileWtpFallbackEnable = true(1), capwapBaseWtpProfileWtpFallbackEnable = true(1),
capwapBaseWtpProfileWtpEchoInterval = 30, capwapBaseWtpProfileWtpEchoInterval = 30,
capwapBaseWtpProfileWtpIdleTimeout = 300, capwapBaseWtpProfileWtpIdleTimeout = 300,
capwapBaseWtpProfileWtpMaxDiscoveryInterval = 20, capwapBaseWtpProfileWtpMaxDiscoveryInterval = 20,
skipping to change at page 9, line 31 skipping to change at page 9, line 31
In ifTable In ifTable
{ {
ifIndex = 10, ifIndex = 10,
ifDescr = 'WTP Virtual Radio Interface', ifDescr = 'WTP Virtual Radio Interface',
ifType = xxx, ifType = xxx,
RFC Editor - please replace xxx with the value RFC Editor - please replace xxx with the value
allocated by IANA for IANAifType of WTP Virtual Radio Interface allocated by IANA for IANAifType of WTP Virtual Radio Interface
ifMtu = 0, ifMtu = 0,
ifSpeed = 0, ifSpeed = 0,
ifPhysAddress = '000000', ifPhysAddress = '00:00:00:00:00:00',
ifAdminStatus = true(1), ifAdminStatus = true(1),
ifOperStatus = false(0), ifOperStatus = false(0),
ifLastChange = 0, ifLastChange = 0,
ifInOctets = 0, ifInOctets = 0,
ifInUcastPkts = 0, ifInUcastPkts = 0,
ifInDiscards = 0, ifInDiscards = 0,
ifInErrors = 0, ifInErrors = 0,
ifInUnknownProtos = 0, ifInUnknownProtos = 0,
ifOutOctets = 0, ifOutOctets = 0,
ifOutUcastPkts = 0, ifOutUcastPkts = 0,
skipping to change at page 10, line 35 skipping to change at page 11, line 8
This configuration is made on the AC through the IEEE 802.11 MIB This configuration is made on the AC through the IEEE 802.11 MIB
module. module.
The following shows an example of configuring parameters for a WTP The following shows an example of configuring parameters for a WTP
Virtual Radio Interface with ifIndex 10 through the Virtual Radio Interface with ifIndex 10 through the
Dot11OperationTable [IEEE.802-11.2007]. Dot11OperationTable [IEEE.802-11.2007].
In Dot11OperationTable In Dot11OperationTable
{ {
ifIndex = 10, ifIndex = 10,
dot11MACAddress = '000000', dot11MACAddress = '00:00:00:00:00:00',
dot11RTSThreshold = 2347, dot11RTSThreshold = 2347,
dot11ShortRetryLimit = 7, dot11ShortRetryLimit = 7,
dot11LongRetryLimit = 4, dot11LongRetryLimit = 4,
dot11FragmentationThreshold = 256, dot11FragmentationThreshold = 256,
dot11MaxTransmitMSDULifetime = 512, dot11MaxTransmitMSDULifetime = 512,
dot11MaxReceiveLifetime = 512, dot11MaxReceiveLifetime = 512,
dot11ManufacturerID = 'capwap', dot11ManufacturerID = 'capwap',
dot11ProductID = 'capwap' dot11ProductID = 'capwap'
dot11CAPLimit = 2,
dot11HCCWmin = 0,
dot11HCCWmax = 0,
dot11HCCAIFSN = 1,
dot11ADDBAResponseTimeout = 1,
dot11ADDTSResponseTimeout = 1,
dot11ChannelUtilizationBeaconInterval = 50,
dot11ScheduleTimeout = 10,
dot11DLSResponseTimeout = 10,
dot11QAPMissingAckRetryLimit = 1,
dot11EDCAAveragingPeriod = 5
} }
4) Configure a WLAN Profile 4) Configure a WLAN Profile
WLAN configuration is made on the AC through the CAPWAP-DOT11-MIB WLAN configuration is made on the AC through the CAPWAP-DOT11-MIB
Module, and IEEE 802.11 MIB module. Module, and IEEE 802.11 MIB module.
The first step is to create a WLAN Profile Interface through the The first step is to create a WLAN Profile Interface through the
CAPWAP-DOT11-MIB module on the AC. CAPWAP-DOT11-MIB module on the AC.
skipping to change at page 11, line 37 skipping to change at page 12, line 21
In ifTable In ifTable
{ {
ifIndex = 20, ifIndex = 20,
ifDescr = 'WLAN Profile Interface', ifDescr = 'WLAN Profile Interface',
ifType = xxx, ifType = xxx,
RFC Editor - please replace xxx with the value RFC Editor - please replace xxx with the value
allocated by IANA for IANAifType of 'WLAN Profile Interface' allocated by IANA for IANAifType of 'WLAN Profile Interface'
ifMtu = 0, ifMtu = 0,
ifSpeed = 0, ifSpeed = 0,
ifPhysAddress = '000000', ifPhysAddress = '00:00:00:00:00:00',
ifAdminStatus = true(1), ifAdminStatus = true(1),
ifOperStatus = true(1), ifOperStatus = true(1),
ifLastChange = 0, ifLastChange = 0,
ifInOctets = 0, ifInOctets = 0,
ifInUcastPkts = 0, ifInUcastPkts = 0,
ifInDiscards = 0, ifInDiscards = 0,
ifInErrors = 0, ifInErrors = 0,
ifInUnknownProtos = 0, ifInUnknownProtos = 0,
ifOutOctets = 0, ifOutOctets = 0,
ifOutUcastPkts = 0, ifOutUcastPkts = 0,
skipping to change at page 13, line 44 skipping to change at page 14, line 29
OBJECT-GROUP, MODULE-COMPLIANCE OBJECT-GROUP, MODULE-COMPLIANCE
FROM SNMPv2-CONF FROM SNMPv2-CONF
MODULE-IDENTITY, OBJECT-TYPE, mib-2, Unsigned32 MODULE-IDENTITY, OBJECT-TYPE, mib-2, Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI
ifIndex, InterfaceIndex ifIndex, InterfaceIndex
FROM IF-MIB FROM IF-MIB
CapwapBaseMacTypeTC, CapwapBaseTunnelModeTC CapwapBaseMacTypeTC, CapwapBaseTunnelModeTC
FROM CAPWAP-BASE-MIB; FROM CAPWAP-BASE-MIB;
capwapDot11MIB MODULE-IDENTITY capwapDot11MIB MODULE-IDENTITY
LAST-UPDATED "200905300000Z" -- May 30th, 2009 LAST-UPDATED "200908130000Z" -- August 13th, 2009
ORGANIZATION "IETF Control And Provisioning of Wireless Access ORGANIZATION "IETF Control And Provisioning of Wireless Access
Points (CAPWAP) Working Group Points (CAPWAP) Working Group
http://www.ietf.org/html.charters/capwap-charter.html" http://www.ietf.org/html.charters/capwap-charter.html"
CONTACT-INFO CONTACT-INFO
"General Discussion: capwap@frascone.com "General Discussion: capwap@frascone.com
To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap
Yang Shi
H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian Yang Shi (editor)
District,Beijing,China(100085) Hangzhou H3C Tech. Co., Ltd.
Email: young@h3c.com Beijing R&D Center of H3C, Digital Technology Plaza,
NO.9 Shangdi 9th Street,Haidian District,
Beijing
China(100085)
Phone: +86 010 82775276
EMail: young@h3c.com
David T. Perkins David T. Perkins
228 Bayview Dr 228 Bayview Dr
San Carlos, CA 94070 San Carlos, CA 94070
USA USA
Phone: +1 408 394-8702 Phone: +1 408 394-8702
Email: dperkins@snmpinfo.com Email: dperkins@snmpinfo.com
Chris Elliott Chris Elliott
Cisco Systems, Inc. Cisco Systems, Inc.
7025 Kit Creek Rd., P.O. Box 14987 7025 Kit Creek Rd., P.O. Box 14987
Research Triangle Park 27709 Research Triangle Park 27709
USA USA
Phone: +1 919-392-2146 Phone: +1 919-392-2146
Email: chelliot@cisco.com Email: chelliot@cisco.com
Yong Zhang Yong Zhang
Fortinet, Inc. Fortinet, Inc.
skipping to change at page 14, line 38 skipping to change at page 15, line 26
USA USA
Email: yzhang@fortinet.com" Email: yzhang@fortinet.com"
DESCRIPTION DESCRIPTION
"Copyright (C) 2009 The Internet Society. This version of "Copyright (C) 2009 The Internet Society. This version of
the MIB module is part of RFC xxx; see the RFC itself the MIB module is part of RFC xxx; see the RFC itself
for full legal notices. for full legal notices.
This MIB module contains managed object definitions for This MIB module contains managed object definitions for
CAPWAP Protocol binding for IEEE 802.11." CAPWAP Protocol binding for IEEE 802.11."
REVISION "200905300000Z" REVISION "200908130000Z"
DESCRIPTION DESCRIPTION
"Initial version, published as RFC xxx" "Initial version, published as RFC xxx"
::= { mib-2 xxx } ::= { mib-2 xxx }
-- Textual conventions -- Textual conventions
CapwapDot11WlanIdTC ::= TEXTUAL-CONVENTION CapwapDot11WlanIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 21, line 42 skipping to change at page 22, line 30
Require IANA to assign a ifType for the WLAN Profile Interface. Require IANA to assign a ifType for the WLAN Profile Interface.
Require IANA to assign a ifType for the WLAN BSS Interface. Require IANA to assign a ifType for the WLAN BSS Interface.
12. Contributors 12. Contributors
This MIB module is based on contributions from Long Gao. This MIB module is based on contributions from Long Gao.
13. Acknowledgements 13. Acknowledgements
The authors wish to thank David Harrington, Fei Fang, Xuebin Zhu, Hao The authors wish to thank David Harrington, Abhijit Choudhury, Fei
Song, Yu Liu, Sachin Dutta, Yujin Zhao, Haitao Zhang, Hao Song. Fang, Xuebin Zhu, Hao Song, Yu Liu, Sachin Dutta, Yujin Zhao, Haitao
Zhang, Hao Wang.
14. References 14. References
14.1. Normative References 14.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs [RFC2119] Bradner, S., "Key words for use in RFCs
to Indicate Requirement Levels", BCP 14, to Indicate Requirement Levels", BCP 14,
RFC 2119, March 1997. RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed.,
skipping to change at page 22, line 30 skipping to change at page 23, line 20
Interfaces Group MIB", RFC 2863, Interfaces Group MIB", RFC 2863,
June 2000. June 2000.
[RFC3418] Presuhn, R., "Management Information Base [RFC3418] Presuhn, R., "Management Information Base
(MIB) for the Simple Network Management (MIB) for the Simple Network Management
Protocol (SNMP)", STD 62, RFC 3418, Protocol (SNMP)", STD 62, RFC 3418,
December 2002. December 2002.
[I-D.ietf-capwap-base-mib] Shi, Y., Perkins, D., Elliott, C., and Y. [I-D.ietf-capwap-base-mib] Shi, Y., Perkins, D., Elliott, C., and Y.
Zhang, "CAPWAP Protocol Base MIB", Zhang, "CAPWAP Protocol Base MIB",
draft-ietf-capwap-base-mib-04 (work in draft-ietf-capwap-base-mib-05 (work in
progress), February 2009. progress), May 2009.
[RFC5415] Calhoun, P., Montemurro, M., and D. [RFC5415] Calhoun, P., Montemurro, M., and D.
Stanley, "Control And Provisioning of Stanley, "Control And Provisioning of
Wireless Access Points (CAPWAP) Protocol Wireless Access Points (CAPWAP) Protocol
Specification", RFC 5415, March 2009. Specification", RFC 5415, March 2009.
[RFC5416] Calhoun, P., Montemurro, M., and D. [RFC5416] Calhoun, P., Montemurro, M., and D.
Stanley, "Control and Provisioning of Stanley, "Control and Provisioning of
Wireless Access Points (CAPWAP) Protocol Wireless Access Points (CAPWAP) Protocol
Binding for IEEE 802.11", RFC 5416, Binding for IEEE 802.11", RFC 5416,
skipping to change at page 23, line 18 skipping to change at page 24, line 9
[RFC3410] Case, J., Mundy, R., Partain, D., and B. [RFC3410] Case, J., Mundy, R., Partain, D., and B.
Stewart, "Introduction and Applicability Stewart, "Introduction and Applicability
Statements for Internet-Standard Statements for Internet-Standard
Management Framework", RFC 3410, Management Framework", RFC 3410,
December 2002. December 2002.
[RFC4347] Rescorla, E. and N. Modadugu, "Datagram [RFC4347] Rescorla, E. and N. Modadugu, "Datagram
Transport Layer Security", RFC 4347, Transport Layer Security", RFC 4347,
April 2006. April 2006.
Appendix A. Appendix A. Changes between -04 and -03 Appendix A. Appendix A. Changes between -05 and -04
1) To close the issue 67 "Dot11 MIB should add a new Terminology WLAN All the issues are tracked by
Profile" http://www.capwap.org/cgi-bin/roundup.cgi/MIB/
-------------------------------------------------------------- 1)Issue 71: For Dot11 MIB, some bugs detected post-WGLC but pre-IESG
Add a new section 5.1. WLAN Profile, update the section 8, update The editor's address is updated. Also, update the WTP id in the
the related MIB objects, replace the "WLAN Service Interface" with section 8.
"WLAN Profile Interface".
2)Issue 73: For the example section in the Base and Dot11 MIB, the
Dot11OperationTable is incorrect
In the draft version 04, the Dot11OperationTable follows the IEEE
802.11-1999 instead of IEEE 802.11-2007. It is incorrect. The draft
version 05 is updated according to IEEE 802.11-2007.
Authors' Addresses Authors' Addresses
Yang Shi (editor) Yang Shi (editor)
H3C Tech. Co., Ltd Hangzhou H3C Tech. Co., Ltd.
Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian District, Beijing R&D Center of H3C, Digital Technology Plaza,
NO.9 Shangdi 9th Street,Haidian District,
Beijing Beijing
China(100085) China(100085)
Phone: +86 010 82775276 Phone: +86 010 82775276
EMail: young@h3c.com EMail: young@h3c.com
David Perkins (editor) David Perkins (editor)
SNMPinfo SNMPinfo
288 Quailbrook Ct San Carlos, 288 Quailbrook Ct San Carlos,
CA 94070 CA 94070
 End of changes. 25 change blocks. 
43 lines changed or deleted 66 lines changed or added

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