RE: [NTDP] Purpose of NTDP

"Craig Brown \(crbrown\)" <crbrown@cisco.com> Tue, 01 August 2006 08:27 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G7pbH-0000DZ-Vh; Tue, 01 Aug 2006 04:27:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G7pbG-0000CD-TZ for ntdp@ietf.org; Tue, 01 Aug 2006 04:27:38 -0400
Received: from ind-iport-1.cisco.com ([64.104.129.195]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G7pbF-0004ww-5p for ntdp@ietf.org; Tue, 01 Aug 2006 04:27:38 -0400
Received: from hkg-core-1.cisco.com ([64.104.123.94]) by ind-iport-1.cisco.com with ESMTP; 01 Aug 2006 14:15:12 -0700
X-IronPort-AV: i="4.07,200,1151910000"; d="scan'208"; a="72478181:sNHT70237204"
Received: from xbh-hkg-412.apac.cisco.com (xbh-hkg-412.cisco.com [64.104.123.69]) by hkg-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k718RW1L004042; Tue, 1 Aug 2006 16:27:32 +0800 (CST)
Received: from xmb-hkg-411.apac.cisco.com ([64.104.123.77]) by xbh-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 1 Aug 2006 16:27:31 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
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: Tue, 1 Aug 2006 16:27:29 +0800
Message-ID: <B4B37A0BBB6A0F43B07F12F1056472D60161EB5E@xmb-hkg-411.apac.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [NTDP] Purpose of NTDP
Thread-Index: Aca0Rqlr8SP6mL+tQRyedpdrTHCrYwAdJlagACI2y4A=
From: "Craig Brown \(crbrown\)" <crbrown@cisco.com>
To: "Loki Jorgenson" <ljorgenson@apparentnetworks.com>
X-OriginalArrivalTime: 01 Aug 2006 08:27:31.0793 (UTC) FILETIME=[552B1C10:01C6B544]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
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

Loki,

I can see the areas of controlling testing device and gathering data.
Can you expand the description of the other areas ?

Cheers,
Craig 

> -----Original Message-----
> From: Loki Jorgenson [mailto:ljorgenson@apparentnetworks.com] 
> Sent: Tuesday, August 01, 2006 2:30 AM
> To: Craig Brown (crbrown)
> Cc: ntdp@ietf.org
> Subject: 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