RFC 6137: The Network Trouble Ticket Data Model (NTTDM)
In plain English — editorial summary, not part of the RFC
Handling multiple sets of network trouble tickets (TTs) originating from different participants' inter-connected network environments poses a series of challenges for the involved institutions. A Grid is a good example of such a multi-domain project. Each of the participants follows different procedures for handling trouble in its domain, according to the local technical and linguistic profile. The TT systems of the participants collect, represent, and disseminate TT information in different formats. As a result, management of the daily workload by a central Network Operation Centre (NOC) is a challenge on its own. Normalization of TTs to a common format at the central NOC can ease presentation, storing, and handling of the TTs. In the present document, we provide a model for automating the collection and normalization of the TT received by multiple networks forming the Grid. Each of the participants is using its home TT system within its domain for handling trouble incidents, whereas the central NOC is gathering the tickets in the normalized format for repository and handling. XML is used as the common representation language. The model was defined and used as part of the networking support activity of the EGEE (Enabling Grids for E-sciencE) project. This document defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC6137
- Published
- February 2011
- Authors
- D. Zisiadis; S. Kopsidas; M. Tsavli; G. Cessieux
- Status
- EXPERIMENTAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 46
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2325Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2Current
April 1998
- RFC 6168Requirements for Management of Name Servers for the DNSCurrent
May 2011
- RFC 6041Forwarding and Control Element Separation (ForCES) Applicability StatementCurrent
October 2010
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 5706Guidelines for Considering Operations and Management of New Protocols and Protocol ExtensionsCurrent
November 2009
- RFC 7547Management of Networks with Constrained Devices: Problem Statement and RequirementsCurrent
May 2015
- RFC 7548Management of Networks with Constrained Devices: Use CasesCurrent
May 2015
- RFC 7630HMAC-SHA-2 Authentication Protocols in the User-based Security Model (USM) for SNMPv3Obsoleted
October 2015
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?