A BEEP Profile for SNMPv3 PDUs
draft-kaushik-isms-btsm-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Kaushik Narayan | ||
| Last updated | 2005-07-14 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
In response to the need for a security model for SNMP that integrates with other device security models, we specify the use of BEEP combined with SASL and TLS as a transport for SNMP requests and responses. We define a URI and specify a BEEP profile to be used, and we relate our work to the Transport Mapping Security Model.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)