<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.calhoun-capwap-taxonomy-recommendation" target="https://datatracker.ietf.org/doc/html/draft-calhoun-capwap-taxonomy-recommendation-01">
   <front>
      <title>CAPWAP Taxonomy Recommendations</title>
      <author initials="P. R." surname="Calhoun" fullname="Pat R. Calhoun">
         <organization>Cisco Systems</organization>
      </author>
      <date month="July" day="18" year="2005" />
      <abstract>
	 <t>   The IETF&#x27;s CAPWAP working group has documented various product
   architectures and has categorized the Centralized WLAN Architectures
   into two main buckets: Split and Local MAC.  While the document
   contains very relevant and useful information, what it does is list
   the architectural variants of these two buckets, but does not
   unambiguously define either the Split MAC or Local MAC architectures.
   In order for CAPWAP to be successful, it is crucial for the protocol
   evaluation team, and the working group, to agree on unambiguous
   terminology to describe these architectures.

   This document proposes terminology to unambiguously describe the
   relevant architectures found in the taxonomy document, for the
   purpose of initiating a discussion within the working group and to
   allow the protocol evaluation work to come to a fruitful conclusion.
   We conclude in this document that the architectures are very similar
   and could be supported via a single protocol.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-calhoun-capwap-taxonomy-recommendation-01" />
   
</reference>
