One document matched: draft-yangshi-capwap-802dot11-mib-00.txt
Internet-Draft Yang Shi
<draft-yangshi-capwap-802dot11-mib-00.txt> Hangzhou H3C Tech. Co., Ltd
Intended status: Standards Track D. Perkins
Expires: January 31, 2008 SNMPinfo
July 31, 2007
CAPWAP Protocol Binding MIB for IEEE 802.11
<draft-yangshi-capwap-802dot11-mib-00.txt>
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling the Control
And Provisioning of Wireless Access Points (CAPWAP) Protocol for
802.11 wireless binding.
Shi, Perkins Expires January 31, 2008 [Page 1]
Internet-Draft CAPWAP Protocol Binding MIB for IEEE 802.11 31 July 2007
Table of Contents
1. Introduction .................................................. 1
2. The Internet-Standard Management Framework .................... 1
3. Terminology ................................................... 1
4. Feature Checklist ............................................. 1
5. Outline ....................................................... 1
6. Brief Description of MIB Objects .............................. 1
6.1. capwapDot11WLANConfigTable ............................... 1
6.2. capwapDot11WLANBSSTable .................................. 1
7. CAPWAP MIB Definitions binding for 802.11 ..................... 1
8. Security Considerations ....................................... 1
9. IANA Considerations ........................................... 1
9.1. IANA Considerations for CAPWAP-DOT11-MIB ................. 1
9.2. IANA Considerations for iftype ........................... 1
10. Acknowledgements ............................................. 1
11. References ................................................... 1
Authors' Addresses ................................................ 1
Intellectual Property and Copyright Statements .................... 1
1. Introduction
Current work is under way in the IETF to specify the CAPWAP Protocol
[I-D.ietf-capwap-protocol-specification], which enables an Access
Controller (AC) to manage a collection of Wireless Termination Points
(WTPs). CAPWAP supports the use of various wireless technologies by
the WTPs, with one being specified in the 802.11 binding document [I-
D.ietf-capwap-protocol-binding-ieee80211].
This document defines a MIB module that can be used to manage CAPWAP
implementations for 802.11 wireless binding. This MIB module covers
both configuration for WLAN and a way to reuse 802.11 MIB standard in
series defined by IEEE 802.11 WG.
The CAPWAP MIB document [I-D.yangshi-capwap-base-mib] defines a MIB
module that can be used to manage the base CAPWAP protocol.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed
Shi, Perkins Expires January 31, 2008 [Page 2]
Internet-Draft CAPWAP Protocol Binding MIB for IEEE 802.11 31 July 2007
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].
3. Terminology
This document uses terminology from the document describing the
CAPWAP Protocol specification for 802.11 binding [I-D.ietf-capwap-
protocol-binding-ieee80211]. Besides terminology defined in the IEEE
802.11 standard and CAPWAP specification, a important conception is
WLAN. In the document, WLAN refers to a logical component
instantiated on a WTP device. A single physical WTP may operate a
number of WLANs. Each Basic Service Set Identifier (BSSID) and its
constituent wireless terminal radios is denoted as a distinct WLAN on
a physical WTP. To support physical WTP with multiple WLANs is an
important feature for 802.11 binding, and it is also for MIB design.
4. Feature Checklist
The CAPWAP Protocol MIB module (CAPWAP-DOT11-MIB) is designed to
satisfy the following requirements and constraints:
- From AC to centrally manage and monitor WTPs;
- The MIB module could easily reuse current and future 802.11 MIB
standard in series defined by IEEE 802.11 WG. The MIB module
provides a way to access MIB objects defined these MIBs, and not
require to redefine them.
- The MIB module supports to configure WLAN;
- The MIB module supports to keep PHY WTP and virtual AP mapping
relationship;
- The MIB module could be used for agent at either AC or WTP sides;
5. Outline
According to [I-D.yangshi-capwap-base-mib], it will use easily reuse
802.11 MIB object for radio configuration and statistic. The CAPWAP-
DOT11-MIB will provide a way to configure WLAN, also could easily
reuse current and future 802.11 MIB standards.
The main steps are as follow: - Create interface of 'WTP radio
Shi, Perkins Expires January 31, 2008 [Page 3]
Internet-Draft CAPWAP Protocol Binding MIB for IEEE 802.11 31 July 2007
template' iftype, as specified
in [IANAifType-MIB], then configure
beacon interval these kinds parameter through 802.11 MIB and
other 802.11 MIB (for example, 802.11e).
- Create interface of 'WLAN Template interface' iftype, then
configure AuthType these kinds parameter for a WLAN through 802.11
MIB and other 802.11 MIB (for example, 802.11i).
- Add/Delete WLAN will create/delete the interface of
'WLAN BSS interface' iftype. Each of them will corresponding to
a WLAN service on a PHY radio.
6. Brief Description of MIB Objects
Sections 6.1 - 6.2 describe objects pertaining to CAPWAP. The MIB
objects were derived from the CAPWAP protocol 802.11 binding document
[I-D.ietf-capwap-protocol-binding-ieee80211].
6.1. capwapDot11WLANConfigTable
The WTPs table is used for providing configuration such as MAC type
and so on for WLANs. The MIB object capwapDot11WLANTemplateIfIndex
as a ifIndex, which as a iftype of 'WLAN Template interface' provides
a way to reuse current 802.11 MIB. For example, according to CAPWAP
Binding for IEEE 802.11 Auth Type for a WLAN. In 802.11 MIB, it has
MIB object dot11AuthenticationAlgorithm in the
dot11AuthenticationAlgorithmsTable which use ifIndex as index. As
CAPWAP-DOT11-MIB use capwapDot11WLANTemplateIfIndex, it could easily
reuse dot11AuthenticationAlgorithm object. It is same for other
802.11 MIBs reuse.
6.2. capwapDot11WLANBSSTable
The table provides a way to create or delete the interface of CAPWAP
add WLAN or delete WLAN message. Each interface corresponding to a
WLAN service on a PHY radio. The first index is the ifIndex from
[RFC2863].
7. CAPWAP MIB Definitions binding for 802.11
CAPWAP-DOT11-MIB DEFINITIONS ::= BEGIN
IMPORTS
RowStatus, TEXTUAL-CONVENTION
FROM SNMPv2-TC
Shi, Perkins Expires January 31, 2008 [Page 4]
Internet-Draft CAPWAP Protocol Binding MIB for IEEE 802.11 31 July 2007
OBJECT-GROUP, MODULE-COMPLIANCE
FROM SNMPv2-CONF
MODULE-IDENTITY, OBJECT-TYPE, mib-2, Unsigned32, Integer32
FROM SNMPv2-SMI
ifIndex
FROM IF-MIB
CapwapWTPMACType, CapwapWTPTunnelMode
FROM CAPWAP-MIB;
capwapDot11MIB MODULE-IDENTITY
LAST-UPDATED "200707310000Z" -- July 31, 2007
ORGANIZATION "IETF CAPWAP working Group"
CONTACT-INFO
"Yang Shi
H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian
District,Beijing,China
Email: young@h3c.com
David T. Perkins
228 Bayview Dr
San Carlos, CA 94070
USA
Phone: +1 408 394-8702
Email: dperkins@snmpinfo.com"
DESCRIPTION
"Copyright (C) 2007 The Internet Society. This version of
the MIB module is part of RFC xxx; see the RFC itself
for full legal notices.
This MIB module contains managed object definitions for
the IEEE 802.11 bindings for the CAPWAP Protocol."
REVISION "200707310000Z"
DESCRIPTION
"Initial version, published as RFC xxx"
::= { mib-2 999902 }
-- EdNote: Replace ZZZ with a real OID once it is
-- allocated & remove this note.
-- Textual conventions
CapwapDot11WLANTemplateIfIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents the TC for a ifindex of 'WLAN Tempalte Interface'
Shi, Perkins Expires January 31, 2008 [Page 5]
Internet-Draft CAPWAP Protocol Binding MIB for IEEE 802.11 31 July 2007
logical interface type."
SYNTAX Integer32 (1..2147483647)
CapwapDot11WLANBSSIfIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents the TC for a ifindex of 'WLAN BSS Interface'
logical interface type."
SYNTAX Unsigned32
CapwapDot11WLANId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents the TC for WLAN Id."
SYNTAX Unsigned32
-- Top level components of this MIB
capwapDot11Objects OBJECT IDENTIFIER
::= { capwapDot11MIB 1 }
capwapDot11Conformance OBJECT IDENTIFIER
::= { capwapDot11MIB 2 }
capwapDot11Notifications OBJECT IDENTIFIER
::= { capwapDot11MIB 0 }
-- capwapDot11WLANConfigTable Table
capwapDot11WLANConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapDot11WLANConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The table provides the configuration for WLAN."
::= { capwapDot11Objects 1 }
capwapDot11WLANConfigEntry OBJECT-TYPE
SYNTAX CapwapDot11WLANConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry contains the configuration parameters for a specific
WLAN."
INDEX { capwapDot11WLANTemplateIfIndex }
::= { capwapDot11WLANConfigTable 1 }
CapwapDot11WLANConfigEntry ::= SEQUENCE {
Shi, Perkins Expires January 31, 2008 [Page 6]
Internet-Draft CAPWAP Protocol Binding MIB for IEEE 802.11 31 July 2007
capwapDot11WLANTemplateIfIndex CapwapDot11WLANTemplateIfIndex,
capwapDot11WLANId CapwapDot11WLANId,
capwapWTPMACType CapwapWTPMACType,
capwapWTPTunnelMode CapwapWTPTunnelMode,
capwapDot11WLANConfigRowStatus RowStatus
}
capwapDot11WLANTemplateIfIndex OBJECT-TYPE
SYNTAX CapwapDot11WLANTemplateIfIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Represents the ifindex for a interface of 'WLAN Template
interface' interface type.
Before WTPs connect to AC and get configuration, administrator
will prepare configuration for them. For WLAN related
configuration, administrator could create a logical interface
of 'WLAN Template interface' interface type, and
configure WLAN parameter under it.
For example, according to CAPWAP Binding for IEEE 802.11
'6.1. IEEE 802.11 Add WLAN', administrator could configure
specify Auth Type for a WLAN.
The 'WLAN Template interface' provides a way to
uniquely identify each WLAN by logical at AC side.
As most MIBs use ifindex to identify a interface for
configuration and statistic data, for example,
dot11AuthenticationAlgorithmsTable in 802.11 MIB use ifindex
as index, and dot11AuthenticationAlgorithm object is for
Auth Type mentioned in the CAPWAP '6.1. IEEE 802.11 Add WLAN',
With the way of 'WLAN Template interface', it will easily
reuse MIB table like dot11AuthenticationAlgorithmsTable, while
only care for other configurations like capwapWTPTunnelMode."
::= { capwapDot11WLANConfigEntry 1 }
capwapDot11WLANId OBJECT-TYPE
SYNTAX CapwapDot11WLANId
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the WLAN id for a WLAN which has a
capwapDot11WLANTemplateIfIndex interface corresponding to it."
REFERENCE
"Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11,
RFC xxx."
::= { capwapDot11WLANConfigEntry 2 }
capwapWTPMACType OBJECT-TYPE
SYNTAX CapwapWTPMACType
Shi, Perkins Expires January 31, 2008 [Page 7]
Internet-Draft CAPWAP Protocol Binding MIB for IEEE 802.11 31 July 2007
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents specifies whether the WTP should run the WLAN in
Local or Split MAC modes."
REFERENCE
"Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11,
RFC xxx."
::= { capwapDot11WLANConfigEntry 3 }
capwapWTPTunnelMode OBJECT-TYPE
SYNTAX CapwapWTPTunnelMode
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents the frame tunneling type to be used for 802.11 data
frames from all stations associated with the WLAN."
REFERENCE
"Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11,
RFC xxx."
::= { capwapDot11WLANConfigEntry 4 }
capwapDot11WLANConfigRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or delete a row in
this table."
::= { capwapDot11WLANConfigEntry 5 }
-- End of capwapDot11WLANConfigTable Table
-- capwapDot11WLANBSSTable Table
capwapDot11WLANBSSTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapDot11WLANBSSEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The table provides a way to create or delete the
interface of 'WLAN BSS interface' iftype. The operation is
corresponding the CAPWAP add WLAN or delete WLAN message.
Each interface corresponding to a WLAN service on a PHY radio."
REFERENCE
"Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11,
RFC xxx."
Shi, Perkins Expires January 31, 2008 [Page 8]
Internet-Draft CAPWAP Protocol Binding MIB for IEEE 802.11 31 July 2007
::= { capwapDot11Objects 2 }
capwapDot11WLANBSSEntry OBJECT-TYPE
SYNTAX CapwapDot11WLANBSSEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry contains information of each BSS for a specific
radio.
The ifIndex corresponding to index to interface of
'WTP radio template' type.
Each PHY radio will bind to a logical interface of
'WTP radio template' type.
The PHY address for interface of 'WTP radio template' type
will be base BSSID address for PHY radio."
INDEX { ifIndex, capwapDot11WLANTemplateIfIndex }
::= { capwapDot11WLANBSSTable 1 }
CapwapDot11WLANBSSEntry ::=
SEQUENCE {
capwapDot11WLANBSSIfIndex CapwapDot11WLANBSSIfIndex,
capwapDot11WLANBSSRowStatus RowStatus
}
capwapDot11WLANBSSIfIndex OBJECT-TYPE
SYNTAX CapwapDot11WLANBSSIfIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents a ifIndex for a interface of
'WLAN BSS interface' iftype. Each capwapDot11WLANBSSIfIndex will
corresponding to a WLAN service on the PHY radio which is
identified by ifIndex.
When CapwapWTPMACType is localMAC(1), the interface of
'WLAN BSS interface' will be created at AP side.
The AP will use interface for local data forwarding.
When CapwapWTPMACType is splitMAC(2), the interface of
'WLAN BSS interface' will be created at AC side.
The AC will use it for split data forwarding.
The PHY address for capwapDot11WLANBSSIfIndex is BSSID.
While manufacturers are free to assign BSSIDs using any
arbitrary mechanism, it is advised that where possible the
BSSIDs are assigned as a contiguous block.
When assigned as a block, implementations can still assign
any of the available BSSIDs to any WLAN. One possible method
is for the WTP to assign the address using the following
Shi, Perkins Expires January 31, 2008 [Page 9]
Internet-Draft CAPWAP Protocol Binding MIB for IEEE 802.11 31 July 2007
algorithm: base BSSID address + WLAN ID."
REFERENCE
"Section 2.4. of CAPWAP Protocol Binding for IEEE 802.11,
RFC xxx."
::= { capwapDot11WLANBSSEntry 1 }
capwapDot11WLANBSSRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or delete a row in
this table."
::= { capwapDot11WLANBSSEntry 2 }
-- End of capwapDot11WLANBSSTable Table
-- Conformance statements
capwapDot11Groups OBJECT IDENTIFIER
::= { capwapDot11Conformance 1 }
capwapDot11Compliances OBJECT IDENTIFIER
::= { capwapDot11Conformance 2 }
-- Object groups
capwapDot11WLANConfigGroup OBJECT-GROUP
OBJECTS {
capwapDot11WLANId,
capwapWTPMACType,
capwapWTPTunnelMode,
capwapDot11WLANConfigRowStatus
}
STATUS current
DESCRIPTION
"The collection of objects which are used to configure
property of WLAN."
::= { capwapDot11Groups 1 }
capwapDot11WLANBSSGroup OBJECT-GROUP
OBJECTS {
capwapDot11WLANBSSIfIndex,
capwapDot11WLANBSSRowStatus
}
STATUS current
Shi, Perkins Expires January 31, 2008 [Page 10]
Internet-Draft CAPWAP Protocol Binding MIB for IEEE 802.11 31 July 2007
DESCRIPTION
"The collection of objects which are used to configure
WLAN BSS."
::= { capwapDot11Groups 2 }
-- Compliance statements
capwapDot11Compliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for ACs that support WTPs
supporting 802.11 bindings."
MODULE -- this module
MANDATORY-GROUPS { capwapDot11WLANConfigGroup,
capwapDot11WLANBSSGroup }
::= { capwapDot11Compliances 1 }
END
8. Security Considerations
There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their
sensitivity/vulnerability:
- Unauthorized changes to the capwapDot11WLANConfigTable and
capwapDot11WLANBSSTable may disrupt allocation of
resources in the network.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
Shi, Perkins Expires January 31, 2008 [Page 11]
Internet-Draft CAPWAP Protocol Binding MIB for IEEE 802.11 31 July 2007
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
9. IANA Considerations
9.1. IANA Considerations for CAPWAP-DOT11-MIB
The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
capwapDot11MIB { mib-2 XXX }
Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX"
(here and in the MIB module) with the assigned value and to remove
this note.
9.2. IANA Considerations for iftype
Require IANA to assign a iftype for 'WLAN Template interface' type.
Require IANA to assign a iftype for 'WLAN BSS interface' type.
10. Acknowledgements
The authors wish to thank Margaret Wasserman, David Harrington, Long
Gao, Sachin Dutta, Yujin Zhao, Haitao Zhang, and Xiansen Cai.
11. References
11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Shi, Perkins Expires January 31, 2008 [Page 12]
Internet-Draft CAPWAP Protocol Binding MIB for IEEE 802.11 31 July 2007
Rose, M., and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999.
[IANAifType-MIB]
Internet Assigned Numbers Authority (IANA), "IANAifType
Textual Convention definition",
http://www.iana.org/assignments/ianaiftype-mib.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000.
[I-D.ietf-capwap-protocol-specification]
Pat Calhoun, "CAPWAP Protocol Specification",
draft-ietf-capwap-protocol-specification
(work in progress), June 2007.
[I-D.ietf-capwap-protocol-binding-ieee80211]
Pat Calhoun, "CAPWAP Protocol Binding for IEEE 802.11",
draft-ietf-capwap-protocol-binding-ieee80211
(work in progress), June 2007.
[I-D.yangshi-capwap-base-mib]
Yang Shi, "CAPWAP Protocol Base MIB ",
draft-yangshi-capwap-base-mib (work in progress),
July 2007.
11.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
Authors' Addresses
Yang Shi
H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian
District,Beijing,China(100085)
Email: young@h3c.com
David T. Perkins
288 Quailbrook Ct
San Carlos, CA 94070
USA
Phone: +1 408 394-8702
Shi, Perkins Expires January 31, 2008 [Page 13]
Internet-Draft CAPWAP Protocol Binding MIB for IEEE 802.11 31 July 2007
Email: dperkins@snmpinfo.com
Shi, Perkins Expires January 31, 2008 [Page 14]
Internet-Draft CAPWAP Protocol Binding MIB for IEEE 802.11 31 July 2007
Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Shi, Perkins Expires January 31, 2008 [Page 15]
| PAFTECH AB 2003-2026 | 2026-04-24 01:16:31 |