bk99.de entertain the web since 1997

bk99.de
RFC · MonitoringStandard explained

RFC 1157: SNMP: Monitoring network devices uniformly

Summary

RFC 1157 defines SNMPv1 for reading and changing standardised management information. A shared model made vendor-independent monitoring practical. Simple management interfaces still need strong security boundaries.

Ideas

  • Managers ask agents for objects of a MIB.
  • Object identifiers address measurement and configuration values hierarchically.
  • Traps report events without a prior query.

Facts

  • RFC 1157 replaces RFC 1098.

Remarks

  • RFC 1157 has historic status and should not be used as a current implementation guideline.

Recommendations

  • Use SNMPv3 with authentication and encryption today.
  • Allow management access only from controlled networks.

References

Read the RFC at the RFC Editor

Search the Web Archive

Hostblogger · 2005

Matching subjective server outages against monitoring data

Manuel Schmitt describes a customer who reports frequent outages, although monitoring shows continuous availability and no fault had been reported before. The operator’s monitoring showed the server as permanently reachable. The customer had not reported any individual faults beforehand.

RFC · 2014

RFC 7258: Pervasive monitoring is an attack

RFC 7258 explicitly declares large-scale passive monitoring a form of attack that protocol design must take into account. Threat models have to include powerful global observers. Encryption by default changes privacy for the whole network.

RFC · 2026

RFC 9846: TLS 1.3: The consolidated current specification

RFC 9846 replaces RFC 8446 and consolidates TLS 1.3 with the corrections and updates published up to then. Security standards occasionally need a consolidated new edition instead of many scattered updates. Superseding the document changes the reference, not the goal of a smaller, secure protocol.