RE: [NTDP] Purpose of NTDP

"Loki Jorgenson" <ljorgenson@apparentnetworks.com> Mon, 31 July 2006 16:29 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G7aeT-0001yv-59; Mon, 31 Jul 2006 12:29:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G7aeR-0001yl-Jw for ntdp@ietf.org; Mon, 31 Jul 2006 12:29:55 -0400
Received: from relay.jaalam.net ([209.139.228.35]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G7aeQ-00005h-Ab for ntdp@ietf.org; Mon, 31 Jul 2006 12:29:55 -0400
Received: from jsrvr8.jaalam.net ([172.16.128.105]) by relay.jaalam.net (SMSSMTP 4.1.0.19) with SMTP id M2006073109295207519 for <ntdp@ietf.org>; Mon, 31 Jul 2006 09:29:52 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NTDP] Purpose of NTDP
Date: Mon, 31 Jul 2006 09:29:51 -0700
Message-ID: <F09324DCDD2F5D488EAC603D6B299DC701E6F185@jsrvr8.jaalam.net>
In-Reply-To: <B4B37A0BBB6A0F43B07F12F1056472D60161E64F@xmb-hkg-411.apac.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [NTDP] Purpose of NTDP
Thread-Index: Aca0Rqlr8SP6mL+tQRyedpdrTHCrYwAdJlag
From: "Loki Jorgenson" <ljorgenson@apparentnetworks.com>
To: "Craig Brown \(crbrown\)" <crbrown@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: ntdp@ietf.org
X-BeenThere: ntdp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: define standards for the purpose of scripting of network testing equipment <ntdp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ntdp>, <mailto:ntdp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ntdp>
List-Post: <mailto:ntdp@ietf.org>
List-Help: <mailto:ntdp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ntdp>, <mailto:ntdp-request@ietf.org?subject=subscribe>
Errors-To: ntdp-bounces@ietf.org

Craig - I would request that we expand the scope sufficiently to include
the complete cycle required to support auto-diagnostic processes.  In my
view, the ability to gather information about the network, analyze it
and then direct it is essential and missing from any other charter.

Something like
   o control testing devices
   o gather data
   o analyze data
   o generate outcome
   o remediate/provision by issuing state or configuration requests

All of the above except that last appears within scope so far.  Some
sort of explicit relationship to Netconf-or-similar might be sufficient.
However, the linkage between "outcome" and "requests" should at least be
supported if not defiend - possibly that looks like some sort of API to
a network device management system.

I would like to address any implicit assumption that the output of such
an automatically managed system of testing devices would be consumed by
a human.

Loki Jorgenson
Chief Scientist
Apparent Networks

e   ljorgenson@ApparentNetworks.com
t   604 433 2333 ext 105
f   604 433 2311
m   604 250-4642
w   www.ApparentNetworks.com

-----Original Message-----
From: Craig Brown (crbrown) [mailto:crbrown@cisco.com] 
Sent: Sunday, July 30, 2006 7:12 PM
To: ntdp@ietf.org
Subject: [NTDP] Purpose of NTDP


It was raised at the last IETF meeting that this alias has been lacking
a statement of purpose. The objective of this alias is to discuss and
propose a solution for how we manage a network testing devices. It can
be considered that these devices are similar to any device in the
network and from some perspectives that's true. The intent therefore is
to further identify the unique areas of these devices and define how
that part is managed. 

A proposed charter ....

_______________________________________________
NTDP mailing list
NTDP@ietf.org
https://www1.ietf.org/mailman/listinfo/ntdp