<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.hares-rnp" target="https://datatracker.ietf.org/doc/html/draft-hares-rnp-00">
   <front>
      <title>Radio Network Protocol</title>
      <author initials="S." surname="Hares" fullname="Susan Hares">
         </author>
      <author initials="N." surname="Bhandaru" fullname="Nehru Bhandaru">
         <organization>NextHop Technologies</organization>
      </author>
      <date month="October" day="20" year="2005" />
      <abstract>
	 <t>   The CAPWAP problem statement describes a problem that needs to be
   addressed before a wireless LAN (WLAN) network designer can construct
   a solution composed of Wireless Termination Points (WTP) and Access
   Controllers (AC) from multiple, different vendors.  One of the
   primary goals is to find a solution that solves the interoperability
   between the two classes of devices (WTPs and ACs) which then enables
   an AC from one vendor to control and manage a WTP from another.  RNP
   is a protocol that supports the management of WTP&#x27;s Radio
   information, Session Parameters, Data Forwarding and interaction with
   the Wireless Portal.  The RNP protocol consists of five sub-
   protocols: RNP-DT (Data Tunneling), RNP-SM (Session Management),
   RNP-RC (Radio Control), RNP-DF (Data Forwarding), and RNP-WP
   (Wireless Portal).  The RTP protocol with it&#x27;s family of protocol
   provides a complete control situation for the CAPWAP environment.  In
   many ways, RNP provides a super set of the RNP requiremetns.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-hares-rnp-00" />
   
</reference>
