RFC 1297: NOC Internal Integrated Trouble Ticket System Functional Specification Wishlist ("NOC TT REQUIREMENTS")
In plain English — editorial summary, not part of the RFC
This document explores competing uses, architectures, and desirable features of integrated internal trouble ticket systems for Network and other Operations Centers. This memo provides information for the Internet community. It does not specify an Internet standard.
Document record
- Document ID
- RFC1297
- Published
- January 1992
- Authors
- D. Johnson
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops-old
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1404A Model for Common Operational StatisticsObsoleted
January 1993
- RFC 2263SNMPv3 ApplicationsObsoleted
January 1998
- RFC 2477Criteria for Evaluating Roaming ProtocolsCurrent
January 1999
- RFC 2573SNMP ApplicationsObsoleted
April 1999
- RFC 2589Lightweight Directory Access Protocol (v3): Extensions for Dynamic Directory ServicesCurrent
May 1999
- RFC 2894Router Renumbering for IPv6Current
August 2000
- RFC 3413Simple Network Management Protocol (SNMP) ApplicationsCurrent
December 2002
- RFC 3416Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP)Current
December 2002
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?