A BEEP Profile for SNMPv3 PDUs
draft-kaushik-tsms-beep-00
| Document | Type |
Withdrawn by Submitter Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Kaushik Narayan | ||
| Last updated | 2005-07-18 (Latest revision 2005-07-13) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Withdrawn by Submitter | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Transport Mapping Security Model (TSMS) describes a framework to provide a security for SNMPv3 by an underlying transport protocol. This document leverages the TMSM framework and describes the use of the Block Extensible Exchange Protocol (BEEP) for securing SNMPv3. This specification describes BEEP Transport Mapping Security Model. This document specifies the use of BEEP combined with SASL and TLS as transport for SNMP requests and responses. We define a URI and specify a BEEP profile to be used.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)