RE: [NTDP] Purpose of NTDP

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