Remote Authentication Dial-In User Service (RADIUS) Usage for Simple Network Management Protocol (SNMP) Transport Models
RFC 5608
Document | Type | RFC - Proposed Standard (August 2009; Errata) | |
---|---|---|---|
Authors | David Nelson , Kaushik Narayan | ||
Last updated | 2020-01-21 | ||
Replaces | draft-narayan-isms-sshsm-radius | ||
Stream | Internent Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) htmlized with errata bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 5608 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Pasi Eronen | ||
Send notices to | (None) |
Network Working Group K. Narayan Request for Comments: 5608 Cisco Systems, Inc. Category: Standards Track D. Nelson Elbrys Networks, Inc. August 2009 Remote Authentication Dial-In User Service (RADIUS) Usage for Simple Network Management Protocol (SNMP) Transport Models Abstract This memo describes the use of a Remote Authentication Dial-In User Service (RADIUS) authentication and authorization service with Simple Network Management Protocol (SNMP) secure Transport Models to authenticate users and authorize creation of secure transport sessions. While the recommendations of this memo are generally applicable to a broad class of SNMP Transport Models, the examples focus on the Secure Shell (SSH) Transport Model. Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (c) 2009 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 in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may Narayan & Nelson Standards Track [Page 1] RFC 5608 RADIUS Usage for SNMP Transport Models August 2009 not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Table of Contents 1. Introduction ....................................................2 1.1. General ....................................................2 1.2. Requirements Language ......................................3 1.3. System Block Diagram .......................................3 1.4. RADIUS Operational Model ...................................3 1.5. RADIUS Usage with Secure Transports ........................5 1.6. Domain of Applicability ....................................5 1.7. SNMP Transport Models ......................................6 2. RADIUS Usage for SNMP Transport Models ..........................7 2.1. RADIUS Authentication for Transport Protocols ..............8 2.2. RADIUS Authorization for Transport Protocols ...............8 2.3. SNMP Service Authorization .................................9 3. Table of Attributes ............................................11 4. Security Considerations ........................................12 5. Acknowledgements ...............................................13 6. References .....................................................13 6.1. Normative References ......................................13 6.2. Informative References ....................................13 1. Introduction 1.1. General This memo describes the use of a Remote Authentication Dial-In User Service (RADIUS) authentication and authorization service by Simple Network Management Protocol (SNMP) secure Transport Models to authenticate users and authorize creation of secure transport sessions. While the recommendations of this memo are generally applicable to a broad class of SNMP Transport Models, the examples focus on the Secure Shell Transport Model. In the context of this document, a Network Access Server (NAS) is a network device or host that contains an SNMP engine implementation, utilizing SNMP Transport Models. It is customary in SNMP documents to indicate which subsystem performs specific processing tasks. In this document, we leave such decisions to the implementer, as is customary for RADIUS documents, and simply specify NAS behavior. Such processing would quite likely be implemented in the secure transport module.Show full document text