RFC 6137 on The Network Trouble Ticket Data Model (NTTDM)

rfc-editor@rfc-editor.org Sat, 19 February 2011 02:19 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 0412A3A6D6D for <ietf-announce@core3.amsl.com>; Fri, 18 Feb 2011 18:19:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.435
X-Spam-Status: No, score=-102.435 tagged_above=-999 required=5 tests=[AWL=0.165, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id gYk8ldKAAdIX for <ietf-announce@core3.amsl.com>; Fri, 18 Feb 2011 18:19:31 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id CB5913A6D89 for <ietf-announce@ietf.org>; Fri, 18 Feb 2011 18:19:31 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 2D9A8E0710; Fri, 18 Feb 2011 18:20:07 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6137 on The Network Trouble Ticket Data Model (NTTDM)
From: rfc-editor@rfc-editor.org
Message-Id: <20110219022007.2D9A8E0710@rfc-editor.org>
Date: Fri, 18 Feb 2011 18:20:07 -0800 (PST)
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Feb 2011 02:19:33 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 6137

        Title:      The Network Trouble Ticket Data 
                    Model (NTTDM) 
        Author:     D. Zisiadis, Ed.,
                    S. Kopsidas, Ed.,
                    M. Tsavli, Ed.,
                    G. Cessieux, Ed.
        Status:     Experimental
        Stream:     Independent
        Date:       February 2011
        Mailbox:    dzisiadis@iti.gr, 
        Pages:      46
        Characters: 83462
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-dzis-nwg-nttdm-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6137.txt

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.

EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC