[NTDP] Purpose of NTDP

"Craig Brown \(crbrown\)" <crbrown@cisco.com> Mon, 31 July 2006 02:11 UTC

Received: from [] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G7NG9-0003w3-Lr; Sun, 30 Jul 2006 22:11:57 -0400
Received: from [] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G7NG8-0003vv-Mw for ntdp@ietf.org; Sun, 30 Jul 2006 22:11:56 -0400
Received: from ind-iport-1.cisco.com ([]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G7NG4-0003cp-23 for ntdp@ietf.org; Sun, 30 Jul 2006 22:11:56 -0400
Received: from hkg-core-1.cisco.com ([]) by ind-iport-1.cisco.com with ESMTP; 31 Jul 2006 07:59:10 -0700
X-IronPort-AV: i="4.07,196,1151910000"; d="scan'208"; a="72339204:sNHT25501704"
Received: from xbh-hkg-412.apac.cisco.com (xbh-hkg-412.cisco.com []) by hkg-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k6V2Bh1N013846 for <ntdp@ietf.org>; Mon, 31 Jul 2006 10:11:48 +0800 (CST)
Received: from xmb-hkg-411.apac.cisco.com ([]) by xbh-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 31 Jul 2006 10:11:43 +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
Date: Mon, 31 Jul 2006 10:11:41 +0800
Message-ID: <B4B37A0BBB6A0F43B07F12F1056472D60161E64F@xmb-hkg-411.apac.cisco.com>
Thread-Topic: Purpose of NTDP
Thread-Index: Aca0Rqlr8SP6mL+tQRyedpdrTHCrYw==
From: "Craig Brown \(crbrown\)" <crbrown@cisco.com>
To: <ntdp@ietf.org>
X-OriginalArrivalTime: 31 Jul 2006 02:11:43.0323 (UTC) FILETIME=[AAD1E2B0:01C6B446]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Subject: [NTDP] Purpose of NTDP
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

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 is to create a new specification for the automatic
control of devices that generate and analyze traffic and/or emulate
network protocols for the testing of a network or a specific network
device. To perform either network or a network device specific testing,
a tester will use a product to generate traffic, emulate routing
protocols and emulate network end points, such as a network host or HTTP

The discussion points are:

	1. What are the requirements?
	2. How are they unique for this situation?
	3. What areas would use this specifications?
	4. Are there any similar specifications available today?	
	5. Are there any supporters of this specification?
	6. What are implementation options based on existing/proposed
standards? Some existing proposals are:
		a. Use NETCONF as the transport model and create the
data modeling based on previous experiences
		b. Use Native XML structures over HTTPS such as XCAP

I am interested in your feedback and if it resolves the comments of
stating the purpose.

NTDP mailing list