From ntdp-bounces@ietf.org Tue Jul 11 11:21:41 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0K3R-0006un-BX; Tue, 11 Jul 2006 11:21:41 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0K3Q-0006uM-By for ntdp@ietf.org; Tue, 11 Jul 2006 11:21:40 -0400 Received: from ind-iport-1.cisco.com ([64.104.129.195]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0K3N-0007cM-L5 for ntdp@ietf.org; Tue, 11 Jul 2006 11:21:40 -0400 Received: from hkg-core-1.cisco.com ([64.104.123.94]) by ind-iport-1.cisco.com with ESMTP; 11 Jul 2006 21:04:37 -0700 X-IronPort-AV: i="4.06,229,1149490800"; d="scan'208,217"; a="70968971:sNHT45818028" 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 k6BFLX1L023142 for ; Tue, 11 Jul 2006 23:21:33 +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.0); Tue, 11 Jul 2006 23:21:33 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 11 Jul 2006 23:20:24 +0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: IETF barBOF meeting - Tuesday @ 6pm Thread-Index: Acak/YfTEVYPcIZ4Twie+gZs/7EdXA== From: "Craig Brown \(crbrown\)" To: X-OriginalArrivalTime: 11 Jul 2006 15:21:33.0162 (UTC) FILETIME=[B11A74A0:01C6A4FD] X-Spam-Score: 0.0 (/) X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 Subject: [NTDP] IETF barBOF meeting - Tuesday @ 6pm 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0737897486==" Errors-To: ntdp-bounces@ietf.org This is a multi-part message in MIME format. --===============0737897486== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6A4FD.B106940E" This is a multi-part message in MIME format. ------_=_NextPart_001_01C6A4FD.B106940E Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, =20 We will have a barBOF at the Delta Hotel (IETF Host hotel) Bar at 6pm tonight. For those wanting to walk over together we will meet at the notice board at 5.45pm or meet at the bar at 6pm. If you are unable to attend and wish to catch up please drop me a note. =20 The purpose of the BOF will be to discuss the problem that we are trying to solve with NTDP. =20 Regards, Craig ------_=_NextPart_001_01C6A4FD.B106940E Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

We = will have a=20 barBOF at the Delta Hotel (IETF Host hotel) Bar at 6pm tonight. For = those=20 wanting to walk over together we will meet at the notice board at 5.45pm = or meet=20 at the bar at 6pm. If you are unable to attend and wish to catch up = please drop=20 me a note.

The = purpose of the=20 BOF will be to discuss the problem that we are trying to solve with=20 NTDP.

Regards,
Craig

------_=_NextPart_001_01C6A4FD.B106940E-- --===============0737897486== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ NTDP mailing list NTDP@ietf.org https://www1.ietf.org/mailman/listinfo/ntdp --===============0737897486==-- From ntdp-bounces@ietf.org Wed Jul 12 07:24:33 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0cpS-0007Ia-BY; Wed, 12 Jul 2006 07:24:30 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0cpR-0007IS-CC for ntdp@ietf.org; Wed, 12 Jul 2006 07:24:29 -0400 Received: from ind-iport-1.cisco.com ([64.104.129.195]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0cpO-0003Xo-PT for ntdp@ietf.org; Wed, 12 Jul 2006 07:24:29 -0400 Received: from hkg-core-1.cisco.com ([64.104.123.94]) by ind-iport-1.cisco.com with ESMTP; 12 Jul 2006 17:07:37 -0700 X-IronPort-AV: i="4.06,234,1149490800"; d="scan'208,217"; a="71048804:sNHT45157368" Received: from xbh-hkg-411.apac.cisco.com (xbh-hkg-411.cisco.com [64.104.123.72]) by hkg-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k6CBOI1R001955 for ; Wed, 12 Jul 2006 19:24:23 +0800 (CST) Received: from xmb-hkg-411.apac.cisco.com ([64.104.123.77]) by xbh-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.0); Wed, 12 Jul 2006 19:24:18 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 12 Jul 2006 19:24:18 +0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: barBOF minutes Thread-Index: AcalpbbB5MPSycGHTKyNKYGkmA95QA== From: "Craig Brown \(crbrown\)" To: X-OriginalArrivalTime: 12 Jul 2006 11:24:18.0942 (UTC) FILETIME=[B74299E0:01C6A5A5] X-Spam-Score: 0.0 (/) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 Subject: [NTDP] barBOF minutes 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1740145781==" Errors-To: ntdp-bounces@ietf.org This is a multi-part message in MIME format. --===============1740145781== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6A5A5.B73A94B5" This is a multi-part message in MIME format. ------_=_NextPart_001_01C6A5A5.B73A94B5 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable NTDP Bar BOF - July 11, 2006 =20 Discussions: =20 . Craig discussed the O&M Open Meeting topics in particular Harrington's new proposal and it's relation to NTDP . Fred discussed the requirements for network management in both production and testing environment . Further discussion on requirements for the control and configuration of protocols . Drank good beer =20 =20 Cheers, Craig ------_=_NextPart_001_01C6A5A5.B73A94B5 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

NTDP = Bar BOF -=20 July 11, 2006

Discussions:

. = Craig=20 discussed the O&M Open Meeting topics in particular = Harrington's new=20 proposal and it's relation to NTDP

. = Fred discussed=20 the requirements for network management in both production and testing=20 environment

. = Further=20 discussion on requirements for the control and configuration of=20 protocols

. = Drank good=20 beer

Cheers,

Craig

------_=_NextPart_001_01C6A5A5.B73A94B5-- --===============1740145781== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ NTDP mailing list NTDP@ietf.org https://www1.ietf.org/mailman/listinfo/ntdp --===============1740145781==-- From ntdp-bounces@ietf.org Wed Jul 12 07:49:27 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0dDb-00024r-JX; Wed, 12 Jul 2006 07:49:27 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0dDa-00024m-FP for ntdp@ietf.org; Wed, 12 Jul 2006 07:49:26 -0400 Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0dDZ-0005vB-8w for ntdp@ietf.org; Wed, 12 Jul 2006 07:49:26 -0400 Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 12 Jul 2006 07:49:25 -0400 X-IronPort-AV: i="4.06,234,1149480000"; d="scan'208"; a="92472838:sNHT27856020" Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k6CBnOj4030495 for ; Wed, 12 Jul 2006 07:49:24 -0400 Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k6CBnO7t020743 for ; Wed, 12 Jul 2006 07:49:24 -0400 (EDT) Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 12 Jul 2006 07:49:24 -0400 Received: from [10.2.190.248] ([10.82.209.103]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 12 Jul 2006 07:49:23 -0400 In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <26B8C5D9-8D1F-4BBC-93F6-ACD28399EF78@cisco.com> Content-Transfer-Encoding: 7bit From: Fred Baker Subject: Re: [NTDP] barBOF minutes Date: Wed, 12 Jul 2006 07:49:20 -0400 To: "Craig Brown \(crbrown\)" X-Mailer: Apple Mail (2.752.2) X-OriginalArrivalTime: 12 Jul 2006 11:49:24.0319 (UTC) FILETIME=[3888E6F0:01C6A5A9] DKIM-Signature: a=rsa-sha1; q=dns; l=124; t=1152704965; x=1153568965; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:Fred=20Baker=20 |Subject:Re=3A=20[NTDP]=20barBOF=20minutes |To:=22Craig=20Brown=20\(crbrown\)=22=20; X=v=3Dcisco.com=3B=20h=3D9ayQHQe+p12ugNvo2kqC0gUC34c=3D; b=fz+usCXRI5J7FAPhwC7HazsAQ6EdX9iWdOrcZy/gXzfVJn7FBdaRhQC16dkqQ5nyQZrqZ1g6 tu2fPg5YffoXQswlrSfs3BnXxTHOWZWL3wz6MXwsziuVYW9wfqFSh06w; Authentication-Results: rtp-dkim-1.cisco.com; header.From=fred@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ntdp-bounces@ietf.org On Jul 12, 2006, at 7:24 AM, Craig Brown ((crbrown)) wrote: > . Drank good beer The bar bof was very successful... _______________________________________________ NTDP mailing list NTDP@ietf.org https://www1.ietf.org/mailman/listinfo/ntdp From ntdp-bounces@ietf.org Wed Jul 12 10:04:14 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0fJy-00038T-2F; Wed, 12 Jul 2006 10:04:10 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0fJw-00038L-46 for ntdp@ietf.org; Wed, 12 Jul 2006 10:04:08 -0400 Received: from mail.gmx.de ([213.165.64.21] helo=mail.gmx.net) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G0fJu-0006Zu-M1 for ntdp@ietf.org; Wed, 12 Jul 2006 10:04:08 -0400 Received: (qmail invoked by alias); 12 Jul 2006 14:04:05 -0000 Received: from h01fd-net84db.lab.risq.net (EHLO [132.219.1.253]) [132.219.1.253] by mail.gmx.net (mp043) with SMTP; 12 Jul 2006 16:04:05 +0200 X-Authenticated: #29516787 Message-ID: <44B50157.2060309@gmx.net> Date: Wed, 12 Jul 2006 10:04:07 -0400 From: Hannes Tschofenig User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Craig Brown (crbrown)" Subject: Re: [NTDP] barBOF minutes References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Spam-Score: 0.1 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ntdp-bounces@ietf.org Could you provide us a bit more details? What requirements have been discussed? Craig Brown (crbrown) wrote: > NTDP Bar BOF - July 11, 2006 > > Discussions: > > . Craig discussed the O&M Open Meeting topics in particular Harrington's > new proposal and it's relation to NTDP > . Fred discussed the requirements for network management in both > production and testing environment > . Further discussion on requirements for the control and configuration > of protocols > . Drank good beer > > > Cheers, > Craig > > > ------------------------------------------------------------------------ > > _______________________________________________ > NTDP mailing list > NTDP@ietf.org > https://www1.ietf.org/mailman/listinfo/ntdp _______________________________________________ NTDP mailing list NTDP@ietf.org https://www1.ietf.org/mailman/listinfo/ntdp From ntdp-bounces@ietf.org Sat Jul 15 03:20:27 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G1eRt-0007Gq-SO; Sat, 15 Jul 2006 03:20:25 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G1eRt-0007Gg-5I for ntdp@ietf.org; Sat, 15 Jul 2006 03:20:25 -0400 Received: from ind-iport-1.cisco.com ([64.104.129.195]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G1eRr-00056s-Ev for ntdp@ietf.org; Sat, 15 Jul 2006 03:20:25 -0400 Received: from hkg-core-1.cisco.com ([64.104.123.94]) by ind-iport-1.cisco.com with ESMTP; 15 Jul 2006 13:04:12 -0700 X-IronPort-AV: i="4.06,245,1149490800"; d="scan'208"; a="71258967:sNHT24415880" 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 k6F7KH1N010215; Sat, 15 Jul 2006 15:20:19 +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); Sat, 15 Jul 2006 15:20:17 +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] barBOF minutes Date: Sat, 15 Jul 2006 15:20:17 +0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [NTDP] barBOF minutes Thread-Index: AcalvZKuLb+ei0TlTJuzUGb7u3jqiQBAm1pA From: "Craig Brown \(crbrown\)" To: "Hannes Tschofenig" X-OriginalArrivalTime: 15 Jul 2006 07:20:17.0973 (UTC) FILETIME=[1FCD4650:01C6A7DF] X-Spam-Score: 0.0 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ntdp-bounces@ietf.org Yes, I will compile details once I return from IETF. Cheers, Craig=20 > -----Original Message----- > From: Hannes Tschofenig [mailto:Hannes.Tschofenig@gmx.net]=20 > Sent: Thursday, July 13, 2006 12:04 AM > To: Craig Brown (crbrown) > Cc: ntdp@ietf.org > Subject: Re: [NTDP] barBOF minutes >=20 > Could you provide us a bit more details? > What requirements have been discussed? >=20 >=20 > Craig Brown (crbrown) wrote: > > NTDP Bar BOF - July 11, 2006 > > =20 > > Discussions: > > =20 > > . Craig discussed the O&M Open Meeting topics in particular=20 > > Harrington's new proposal and it's relation to NTDP . Fred=20 > discussed=20 > > the requirements for network management in both production=20 > and testing=20 > > environment . Further discussion on requirements for the=20 > control and=20 > > configuration of protocols . Drank good beer > > =20 > > =20 > > Cheers, > > Craig > >=20 > >=20 > >=20 > ---------------------------------------------------------------------- > > -- > >=20 > > _______________________________________________ > > NTDP mailing list > > NTDP@ietf.org > > https://www1.ietf.org/mailman/listinfo/ntdp >=20 _______________________________________________ NTDP mailing list NTDP@ietf.org https://www1.ietf.org/mailman/listinfo/ntdp From ntdp-bounces@ietf.org Sun Jul 30 22:12:01 2006 Received: from [127.0.0.1] (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 [10.91.34.44] (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 ([64.104.129.195]) 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 ([64.104.123.94]) 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 [64.104.123.69]) by hkg-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k6V2Bh1N013846 for ; Mon, 31 Jul 2006 10:11:48 +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); 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: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Purpose of NTDP Thread-Index: Aca0Rqlr8SP6mL+tQRyedpdrTHCrYw== From: "Craig Brown \(crbrown\)" To: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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.=20 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 client. 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?=09 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 (http://www.ietf.org/html.charters/netconf-charter.html) b. Use Native XML structures over HTTPS such as XCAP (http://www.jdrosen.net/simple_acap.html) I am interested in your feedback and if it resolves the comments of stating the purpose. _______________________________________________ NTDP mailing list NTDP@ietf.org https://www1.ietf.org/mailman/listinfo/ntdp From ntdp-bounces@ietf.org Mon Jul 31 12:29:58 2006 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 ; 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: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [NTDP] Purpose of NTDP Thread-Index: Aca0Rqlr8SP6mL+tQRyedpdrTHCrYwAdJlag From: "Loki Jorgenson" To: "Craig Brown \(crbrown\)" 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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]=20 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.=20 A proposed charter .... _______________________________________________ NTDP mailing list NTDP@ietf.org https://www1.ietf.org/mailman/listinfo/ntdp