Internet Engineering Task Force K. Moeltner INTERNET-DRAFT J. Nguyen Intended Status: Informational R. Cole Expires: May 10, 2013 US Army CERDEC November 6, 2012 MANET Radio Management Model draft-moeltner-manet-radio-mgmt-models-00 Abstract The MANET Working Group is developing management interfaces, i.e., Management Information Base (MIB) modules, for its control protocols, e.g., Neighborhood Discovery Protocol (NHDP), Simplified Multicast Forwarding (SMF), etc. The NETMOD Working group is developing a set of standard YANG modules for the basic configuration management of standard IP capable devices. Future IP capable radio networks will rely upon these and other modules for their management. The convergence of these activities requires the development of a conceptual radio management model to help promote a consistent set of modules for the configuration, monitoring and notification management of typical wireless radio devices. This document provides such a framework. Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and 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/1id-abstracts.html The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Moeltner, et el. Expires May 10, 2013 [Page 1] INTERNET DRAFT MANET Radio Management Model November 6, 2012 Copyright and License Notice Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 2 Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3 Radio Management Model . . . . . . . . . . . . . . . . . . . . 3 3.1 Non-multiplexed Management Model . . . . . . . . . . . . . 4 3.2 Downward Multiplexed Radio Management Model . . . . . . . . 7 3.3 Upward Multiplexed Radio Management Model . . . . . . . . . 8 4 Next Steps . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5 Security Considerations . . . . . . . . . . . . . . . . . . . . 11 6 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 11 7 References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 7.1 Normative References . . . . . . . . . . . . . . . . . . . 11 7.2 Informative References . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 Moeltner, et el. Expires May 10, 2013 [Page 2] INTERNET DRAFT MANET Radio Management Model November 6, 2012 1 Introduction Current wireless radio devices employed for military, emergency services or other networking domains are rather complex devices. These devices range from simple MAC level and below networking devices, which provide interfaces to IP routers, to extremely complex networking devices consisting of applications running on hosts which are logically connected to embedded routers with multiple (sometimes hierarchical) wireless interfaces. Currently, the proprietary management interfaces to these devices are monolithic, ill-logically organized and providing an inconsistent set of objects and services. This document intends to promote a standard radio management model to help in the development of standard models (i.e., YANG and MIB modules) for management of a broad set of radio devices. 1.1 Terminology 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 Objective Breaking down the structure of the radio into functional layers allows radio systems to define management modules that are logically compartmentalized, straightforward and practical in size. In this manner, we also allow for modules that are agile enough to let radios of varied levels of complexity to tailor precisely which modules are needed for their management based upon their capability set. Conforming to this model would also provide for configuration consistency across platforms. This in turn would simplify other aspects of configuration management including compatibility, training, isolation, troubleshooting, procurement, and technology evolution. Furthermore, we can avoid redundancy by leveraging existing modules that fulfill the functionality represented by the layer. 3 Radio Management Model This section defines the radio management model. We define three radio management models to represent the functional layers of a radio as it relates to the function performed and protocols used. The first of these models shows a standard top down layering of functionality with network interfaces communicating on a 1-to-1 basis. This would depict a radio functioning as a router with a single interface out of a single antenna. The other models Moeltner, et el. Expires May 10, 2013 [Page 3] INTERNET DRAFT MANET Radio Management Model November 6, 2012 represent a 1-to-many and a many-to-1 router interface to antenna configurations as identified in following subsections. 3.1 Non-multiplexed Management Model At the top level of the model is the application layer. Multiple running applications are supported with a standard being defined that can be extended to include parameters specific to the individual application. These applications map to the hosts on the next layer down. Again, multiple hosts running on a radio are supported in this model. Moeltner, et el. Expires May 10, 2013 [Page 4] INTERNET DRAFT MANET Radio Management Model November 6, 2012 +--------+ +-----+ | | | | +--------+ _m | | | | | | | | +--------+ _2 |----+ <-> | | | | | | | | Appl_1 |----+ | | | | | M | +--------+ | a | | n | +------------------+ +------------------+ | a | | | | | | g | | Host_1 | ... | Host_ n | <-> | e | | | | | | m | +------------------+ +------------------+ | e | | n | +--------------------------------------------------+ | t | | | | | | Router | <-> | M | | | | o | +--------------------------------------------------+ | d | | u | +--------------------------------------------------+ | l | | MAC | <-> | e | +--------------------------------------------------+ | | . . | | +-------+--------+-------+-----------------+-------+ | | | Slot_1| | Slot_s| Frequency Mgmt | Slot_r| <-> | | +-------+--------+-------+-----------------+-------+ +-----+ Figure 1. Non-multiplexed MAC Radio Model The routing and MAC layers includes all parameters necessary for network routing and wireless medium access (e.g. address tables, MAC addresses). The Frequency Mgmt layer handles basic frequency band definitions (e.g. power level). In this model, no virtual interfaces are represented, i.e. the router interface maps to a single device (MAC and Physical antenna) interface, e.g. gr0. Running alongside these layers and interacting with each is an associated management module. Management modules will exist within actual radio implementations and provide configuration, state, performance and notification management of all aspects of the radio implementation. Several of the layers within the conceptual radio model presented here have already been codified into management modules through SMIv2 [RFC2578] or YANG [RFC6020]. For example, within SMI numerous modules Moeltner, et el. Expires May 10, 2013 [Page 5] INTERNET DRAFT MANET Radio Management Model November 6, 2012 covering a significant number of functional areas have already been standardized. Some of these include (but are not limited to): - Application - SYSAPPL-MIB [RFC2287] - Host - HOST-RESOURCES-MIB [RFC2790] - Standard MIB-II - [RFC1213] (which includes tcpTable (updated in [RFC4022]), udpTable (updated in [RFC4113]), ipForwarding (updated in [RFC4293]), ifTable, atTable, etc, providing management interfaces to broad networking functionality of all IP-capable devices.) - Various control protocol MIBs, e.g. OSPF-MIB [RFC4750], NHDP-MIB [I-D.ietf-manet-nhdp-mib], SMF-MIB [I-D.ietf-manet-smf-mib], etc. The netmod community has several drafts submitted which would establish YANG counterparts to these modules. These include Routing [I-D.ietf-netmod-routing-cfg], System Management [I-D.ietf-netmod- system-mgmt], and Interface Configuration [I-D.ietf-netmod- interfaces-cfg]. Moeltner, et el. Expires May 10, 2013 [Page 6] INTERNET DRAFT MANET Radio Management Model November 6, 2012 3.2 Downward Multiplexed Radio Management Model +--------+ +-----+ | | | | +--------+ _m | | | | | | | | +--------+ _2 |----+ <-> | | | | | | | | Appl_1 |----+ | | | | | M | +--------+ | a | | n | +------------------+ +------------------+ | a | | | | | | g | | Host_1 | ... | Host_ n | <-> | e | | | | | | m | +------------------+ +------------------+ | e | | n | +--------------------------------------------------+ | t | | | | | | Router | <-> | M | | | | o | +--------------------------------------------------+ | d | | u | +-----------+ +---------+ | l | | DSA MAC | | MAC | <-> | e | +-----------+ . . . +---------+ | | | VIF_1 | | VIF_k | <-> | | +-----------+ +---------+ | | . . . . | | . .............. . . | | . . . . | | +-------+ +-------+ . . | | | MAC_1 | | MAC_j | . . | | +-------+ ... +-------+ . . | | | RIF_1 | | RIF_j | . . | | +-------+ +-------+ . . | | . . . . . . | | +-------+--------+-------+--------------+---------+ | | | Slot_1| | Slot_s| Freq Mgmt | Slot_r | <-> | | +-------+--------+-------+--------------+---------+ +-----+ Figure 2. Downward multiplexed MAC (DSA) In the "Downward Multiplexed Radio Management" model, the router sees one or multiple interfaces, e.g. dsa0, dsa1, etc. Each interface is a collection of real interfaces, one for each antenna system. This is representative of, for example, a Dynamic Spectrum Access Moeltner, et el. Expires May 10, 2013 [Page 7] INTERNET DRAFT MANET Radio Management Model November 6, 2012 implementation. Here the router interface is managed by a high level MAC protocol (e.g. the DSA MAC) which manages data receipt and transmission over multiple real interfaces operating on different frequencies with separate instances of MACs (e.g. MAC 1 to MAC-j). These types of downward multiplexed interfaces can be defined within the context of the ifInterfaceTable of the IF-MIB [RFC2863] and the draft interface YANG module. [I-D.ietf-netmod-interfaces-cfg] The IF-MIB defines an interface to the router and how the interface to the router relates to the interfaces on the network. These relationships are expressed using a stack table with pointers to map to interfaces. The ifStackTable can also be used to represent the relationship of multiple interfaces to a single interface. Using this data structure, we can express the architectures of the downward and upward multiplexing radio models. The draft interface YANG module seeks to define the framework of a corresponding data structure for this mapping in YANG. 3.3 Upward Multiplexed Radio Management Model In the "Upward Multiplexed Radio Management" model, the router sees one or more physical interfaces, e.g. eth0, eth1, etc. Multiplexed on the physical interfaces are a set of virtual interfaces, (for example, of type PPPoE, e.g. vir0.0, vir0.1, ...) This is representative of a radio to router interface on Ethernet where each radio/router pair discovered establish a PPPoE connection forming a virtual interface on the router. Moeltner, et el. Expires May 10, 2013 [Page 8] INTERNET DRAFT MANET Radio Management Model November 6, 2012 +--------+ +-----+ | | | | +--------+ _m | | | | | | | | +--------+ _2 |----+ <-> | | | | | | | | Appl_1 |----+ | | | | | M | +--------+ | a | | n | +------------------+ +------------------+ | a | | | | | | g | | Host_1 | ... | Host_ n | <-> | e | | | | | | m | +------------------+ +------------------+ | e | | n | +--------------------------------------------------+ | t | | | | | | Router | <-> | M | | | | o | +--------------------------------------------------+ | d | | u | +-------+ +-------+ +-------+ | l | | MAC_1 | | MAC_j | | MAC | <-> | e | +-------+ . . . +-------+ +-------+ | | | VIF_1 | | VIF_j | | VIF_k | <-> | | +-------+ +-------+ +-------+ | | . . . . | | ......... ......... . . | | . . . . . | | . +--------+ . . | | . | MAC | . . | | . +--------+ . . | | . | RIF | . . | | . +--------+ . . | | . . . . . | | +-------+--------+--------+----------------+-------+ | | | | Slot_1 | Slot_s | Freq Mgmt | Slot_r| <-> | | +-------+--------+--------+----------------+-------+ +-----+ Figure 3. Upward Multiplexed MAC 4 Next Steps There is a need for the development of standardized MAC layer modules for wireless networks along with their management modules. The modules for managing these protocols for the most part do not exist, Moeltner, et el. Expires May 10, 2013 [Page 9] INTERNET DRAFT MANET Radio Management Model November 6, 2012 with 802.11 being the exception [IEEE802dot11-MIB]. The structure of our standard model would represent a device using this standard. Another effort would be the development of a standard frequency interface to manage the frequency across multiple MACs. By writing this document, we are looking to develop commonality of a management model within the radio vendor community. This commonality will improve systems interoperability, improve management, and reduce the training and support cost incurred by the consumer communities for these IP networking devices. Moeltner, et el. Expires May 10, 2013 [Page 10] INTERNET DRAFT MANET Radio Management Model November 6, 2012 5 Security Considerations This document specifies a framework for standardizing the development of radio management models. It does not raise or consider any protocol-specific security issues. 6 IANA Considerations This memo includes no request to IANA. 7 References 7.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., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2287] Krupczak, C. and J. Saperia, "Definitions of System-Level Managed Objects for Applications", RFC 2287, February 1998. [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, October 2010. [RFC2790] Waldbusser, S. and P. Grillo, "Host Resources MIB", RFC 2790, March 2000. [RFC1213] McCloghrie, K. and M. Rose, "Management Information Base for Network Management of TCP/IP-based internets:MIB-II", STD 17, RFC 1213, March 1991. [RFC4022] Raghunarayan, R., Ed., "Management Information Base for the Transmission Control Protocol (TCP)", RFC 4022, March 2005. [RFC4113] Fenner, B. and J. Flick, "Management Information Base for the User Datagram Protocol (UDP)", RFC 4113, June 2005. [RFC4293] Routhier, S., Ed., "Management Information Base for the Internet Protocol (IP)", RFC 4293, April 2006. Moeltner, et el. Expires May 10, 2013 [Page 11] INTERNET DRAFT MANET Radio Management Model November 6, 2012 [RFC4750] Joyal, D., Ed., Galecki, P., Ed., Giacalone, S., Ed., Coltun, R., and F. Baker, "OSPF Version 2 Management Information Base", RFC 4750, December 2006. [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000. [I-D.ietf-manet-nhdp-mib] U. Herberg, R. Cole, I. Chakeres, "Definition of Managed Objects for the Neighborhood Discovery Protocol", draft- ietf-manet-nhdp-mib-19 (Work in Progress), September 2012. [I-D.ietf-manet-smf-mib] R. Cole, Ed., "Definition of Managed Objects for the Manet Simplified Multicast Framework Relay Set Process", draft- ietf-manet-smf-mib-05 (Work in Progress), November 2012. [I-D.ietf-netmod-routing-cfg] L. Lhotka, "A YANG Data Model for Routing Configuration", draft-ietf-netmod-routing-cfg-05 (Work in Progress), October 2012. [I-D.ietf-netmod-interfaces-cfg] Bjorklund, M., "A YANG Data Model for Interface Management", draft-ietf-netmod-interfaces-cfg-07 (Work in Progress), October 2012. [I-D.ietf-netmod-system-mgmt] Bierman, A. and Bjorklund, M., "YANG Data Model for System Management", draft-ietf-netmod-system-mgmt-03 (Work in Progress), September 2012. [IEEE802dot11-MIB] Institute of Electrical and Electronics Engineers, "Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications", IEEE Standard 802.11, March 2012. 7.2 Informative References [RFC3418] Presuhn, R., Ed., "Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3418, December 2002. [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, June 2011. Moeltner, et el. Expires May 10, 2013 [Page 12] INTERNET DRAFT MANET Radio Management Model November 6, 2012 Authors' Addresses Kimberly Moeltner US Army CERDEC 6010 Frankford Street Aberdeen Proving Ground, Maryland USA Phone: +1 443 395 5639 Email: kimberly.i.moeltner.civ@mail.mil James Nguyen US Army CERDEC 6010 Frankford Street Aberdeen Proving Ground, Maryland USA Phone: +1 443 395 5628 Email: james.h.nguyen4.civ@mail.mil Robert G. Cole US Army CERDEC 6010 Frankford Street Aberdeen Proving Ground, Maryland USA Phone: +1 443 395 8744 Email: robert.g.cole@us.army.mil Moeltner, et el. Expires May 10, 2013 [Page 13]