From mailman-bounces@ietf.org  Sat Jan  1 07:03:23 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13692
	for <disman-archive@lists.ietf.org>; Sat, 1 Jan 2005 07:03:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CkgNX-00064d-V1
	for disman-archive@lists.ietf.org; Sat, 01 Jan 2005 05:20:59 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: disman-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.19540.1104574046.4100.mailman@lists.ietf.org>
Date: Sat, 01 Jan 2005 05:07:26 -0500
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
Content-Transfer-Encoding: 7bit

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

**********************************************************************

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

*******************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for disman-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
disman@ietf.org                          hixour    
https://www1.ietf.org/mailman/options/disman/disman-archive%40lists.ietf.org


From disman-bounces@ietf.org  Sun Jan  9 17:26:28 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11244
	for <disman-archive@lists.ietf.org>; Sun, 9 Jan 2005 17:26:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CnlUX-00007E-UX; Sun, 09 Jan 2005 17:24:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CnlNq-0007WX-To
	for disman@megatron.ietf.org; Sun, 09 Jan 2005 17:18:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10798
	for <disman@ietf.org>; Sun, 9 Jan 2005 17:18:00 -0500 (EST)
Received: from pop-a065d05.pas.sa.earthlink.net ([207.217.121.249])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CnlbK-0002Dl-Ji
	for disman@ietf.org; Sun, 09 Jan 2005 17:31:58 -0500
Received: from h-69-3-26-232.snvacaid.dynamic.covad.net ([69.3.26.232]
	helo=oemcomputer)
	by pop-a065d05.pas.sa.earthlink.net with smtp (Exim 3.33 #1)
	id 1CnlNi-0006sn-00; Sun, 09 Jan 2005 14:17:55 -0800
Message-ID: <000301c4f699$2d3b32a0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Mreview \(E-mail\)" <mreview@ops.ietf.org>
References: <Pine.LNX.4.10.10501081838440.30242-100000@shell4.bayarea.net>
Date: Sun, 9 Jan 2005 12:00:51 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: Disman <disman@ietf.org>
Subject: [Disman] Re: [Fwd: Re: [RMONMIB] I-D
	ACTION:draft-ietf-rmonmib-raqmon-pdu-08.txt]
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Hi -

> From: "David T. Perkins" <dperkins@dsperkins.com>
> To: "C. M. Heard" <heard@pobox.com>
> Cc: "Mark Ellison" <ellison@ieee.org>; "Mreview (E-mail)" <mreview@ops.ietf.org>
> Sent: Saturday, January 08, 2005 6:58 PM
> Subject: Re: [Fwd: Re: [RMONMIB] I-D ACTION:draft-ietf-rmonmib-raqmon-pdu-08.txt]
...
>  5) lack of a usable log (RFC 3014 doesn't cut it)
...

If you care to spell out just what the problem with
RFC 3014 is, those comments would be most welcome on
the disman WG mailing list.  I would hope that you could be
a bit more precise than "just doesn't cut it," however.

Randy Presuhn
disman WG chair





From disman-bounces@ietf.org  Fri Jan 14 14:43:51 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08604
	for <disman-archive@lists.ietf.org>; Fri, 14 Jan 2005 14:43:50 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CpXBJ-00041w-Vr; Fri, 14 Jan 2005 14:32:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CpX50-0002ij-8t; Fri, 14 Jan 2005 14:25:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07248;
	Fri, 14 Jan 2005 14:25:53 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CpXJS-0001sU-FQ; Fri, 14 Jan 2005 14:40:53 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 14 Jan 2005 12:31:57 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com
	[171.71.163.17])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j0EJPEvl014441;
	Fri, 14 Jan 2005 11:25:15 -0800 (PST)
Received: from abierman-xp.cisco.com (sjc-vpn1-595.cisco.com [10.21.98.83])
	by mira-sjc5-c.cisco.com (MOS 3.4.5-GR) with ESMTP id BCT25669;
	Fri, 14 Jan 2005 11:25:16 -0800 (PST)
Message-Id: <4.3.2.7.2.20050114111849.02cacbe0@fedex.cisco.com>
X-Sender: abierman@fedex.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 14 Jan 2005 11:25:16 -0800
To: "Saverio Niccolini" <Saverio.Niccolini@netlab.nec.de>
From: Andy Bierman <abierman@cisco.com>
In-Reply-To: <F0DC7B6021F256408935B31D97FC727E518EAF@europa.office>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Cc: disman@ietf.org, ippm@ietf.org
Subject: [Disman] RE: [ippm] Way to store traceroutes
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

At 07:59 AM 1/14/2005, Saverio Niccolini wrote:
>Dear all,
>thanks a lot for your useful suggestions.

This work is already established in the DISMAN WG.  See RFC 2925,
or its update (in progress):
http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-06.txt

I strongly urge you to work with the DISMAN WG to resolve
perceived deficiencies with the RemOps MIB, rather than
create a spin-off MIB.

Andy



>We have tried to draft a "traceroute object" based on what we discussed
>on the list and what we had in mind. We think this will serve as a
>starting point of our information model.
>
>We have taken the disman draft as a starting point and we have erased
>some fields not useful in the scope of our draft (that we do not specify
>here), moreover we have added and changed other ones:
>
>NEW fields:
>1) traceRouteResultsLastGoodPathDuration (duration of single running of
>the last good traceroute path determination)
>2) traceRouteResultsLastRun (when the last traceroute with these
>characteristics was launched)
>3) traceRouteHopsASNumber (AS number of the hop)
>
>CHANGED fields:
>1) traceRouteProbeHistoryTime (timestamp of when the traceroute probe
>came back) was changed to traceRouteProbeHistorySentTime (timestamp of
>when the traceroute probe was sent)
>
>
>Please find here how the "traceroute object" looks like right now:
>
>--traceRouteObjects
>  |
>  +--traceRouteCtlTable
>  |  |
>  |  +--traceRouteCtlEntry
>  |     |
>  |     +--traceRouteCtlOwnerIndex
>  |     +--traceRouteCtlTestName
>  |     +--traceRouteCtlTargetAddressType
>  |     +--traceRouteCtlTargetAddress
>  |     +--traceRouteCtlByPassRouteTable
>  |     +--traceRouteCtlDataSize
>  |     +--traceRouteCtlTimeOut
>  |     +--traceRouteCtlProbesPerHop
>  |     +--traceRouteCtlPort
>  |     +--traceRouteCtlMaxTtl
>  |     +--traceRouteCtlDSField
>  |     +--traceRouteCtlSourceAddressType
>  |     +--traceRouteCtlSourceAddress
>  |     +--traceRouteCtlIfIndex
>  |     +--traceRouteCtlMiscOptions
>  |     +--traceRouteCtlMaxFailures
>  |     +--traceRouteCtlDontFragment
>  |     +--traceRouteCtlInitialTtl
>  |     +--traceRouteCtlDescr
>  |     +--traceRouteCtlMaxRows
>  |     +--traceRouteCtlCreateHopsEntries
>  |     +--traceRouteCtlType
>  |
>  +--traceRouteResultsTable
>  |  |
>  |  +--traceRouteResultsEntry
>  |     |
>  |     +--traceRouteResultsOperStatus
>  |     +--traceRouteResultsIpTgtAddrType
>  |     +--traceRouteResultsIpTgtAddr
>  |     +--traceRouteResultsTestAttempts
>  |     +--traceRouteResultsTestSuccesses
>  |     +--traceRouteResultsLastGoodPath
>  |     +--traceRouteResultsLastGoodPathDuration
>  |     +--traceRouteResultsLastRun
>  |
>  +--traceRouteProbeHistoryTable
>  |  |
>  |  +--traceRouteProbeHistoryEntry
>  |     |
>  |     +--traceRouteProbeHistoryIndex
>  |     +--traceRouteProbeHistoryHopIndex
>  |     +--traceRouteProbeHistoryProbeIndex
>  |     +--traceRouteProbeHistoryHAddrType
>  |     +--traceRouteProbeHistoryHAddr
>  |     +--traceRouteProbeHistoryResponse
>  |     +--traceRouteProbeHistoryStatus
>  |     +--traceRouteProbeHistorySentTime
>  |
>  +--traceRouteHopsTable
>     |
>     +--traceRouteHopsEntry
>        |
>        +--traceRouteHopsHopIndex
>        +--traceRouteHopsIpTgtAddressType
>        +--traceRouteHopsIpTgtAddress
>        +--traceRouteHopsASNumber
>        +--traceRouteHopsMinRtt
>        +--traceRouteHopsMaxRtt
>        +--traceRouteHopsAverageRtt
>        +--traceRouteHopsRttSumOfSquares
>        +--traceRouteHopsSentProbes
>        +--traceRouteHopsProbeResponses
>
>We believe that most of the fields are self-explaining, for the unclear
>ones please refer to the disman draft:
>http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-06.t
>xt
>
>Looking forward to receive your comments.
>
>Best regards,
>Saverio Niccolini
>
>============================================================
>Dr. Saverio Niccolini
>Research Staff Member
>Network Laboratories, NEC Europe Ltd.
>Kurfuerstenanlage 36, D-69115 Heidelberg
>Tel.     +49 (0)6221 90511-18
>Fax:     +49 (0)6221 90511-55
>e-mail:  saverio.niccolini@netlab.nec.de
>============================================================
>
>
>_______________________________________________
>ippm mailing list
>ippm@ietf.org 
>https://www1.ietf.org/mailman/listinfo/ippm 



From disman-bounces@ietf.org  Mon Jan 17 05:08:40 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22274
	for <disman-archive@lists.ietf.org>; Mon, 17 Jan 2005 05:08:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CqThY-0001FR-V7; Mon, 17 Jan 2005 05:01:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CqTZn-0000Rj-4e; Mon, 17 Jan 2005 04:53:35 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21089;
	Mon, 17 Jan 2005 04:53:32 -0500 (EST)
Received: from kyoto.netlab.nec.de ([195.37.70.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CqTon-0008NW-DO; Mon, 17 Jan 2005 05:09:07 -0500
Received: from [10.1.1.171] (mito.netlab.nec.de [195.37.70.39])
	by kyoto.netlab.nec.de (Postfix) with ESMTP id E3BE41BAC9F;
	Mon, 17 Jan 2005 10:52:51 +0100 (CET)
Date: Mon, 17 Jan 2005 10:52:53 +0100
From: Juergen Quittek <quittek@netlab.nec.de>
To: Andy Bierman <abierman@cisco.com>,
        Saverio Niccolini <Saverio.Niccolini@netlab.nec.de>
Message-ID: <2147483647.1105959173@[10.1.1.171]>
In-Reply-To: <4.3.2.7.2.20050114111849.02cacbe0@fedex.cisco.com>
References: <4.3.2.7.2.20050114111849.02cacbe0@fedex.cisco.com>
X-Mailer: Mulberry/3.0.3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21be852dc93f0971708678c18d38c096
Content-Transfer-Encoding: 7bit
Cc: disman@ietf.org, ippm@ietf.org
Subject: [Disman] RE: [ippm] Way to store traceroutes
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Hi Andy,

--On 14.01.2005 20:25 Uhr +0100 Andy Bierman wrote:

> At 07:59 AM 1/14/2005, Saverio Niccolini wrote:
>> Dear all,
>> thanks a lot for your useful suggestions.
>
> This work is already established in the DISMAN WG.  See RFC 2925,
> or its update (in progress):
> http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-06.txt

Saverio and Sandra already had a look at the DISMAN-TRACEROUTE-MIB.

> I strongly urge you to work with the DISMAN WG to resolve
> perceived deficiencies with the RemOps MIB, rather than
> create a spin-off MIB.

As editor of draft-ietf-disman-remops-mib-v2-06.txt I wonder
what you consider as 'perceived deficiencies with the RemOps MIB'.

In the context of IPPM, there is certainly the deficiency, that
you can only store measurements that were performed locally and that
the tables for storing measurement results are read-only.

But anyway, does the IPPM WG plan to store traceroute results in a MIB?

Thanks,

    Juergen
-- 
Juergen Quittek        quittek@netlab.nec.de       Tel: +49 6221 90511-15
NEC Europe Ltd.,       Network Laboratories        Fax: +49 6221 90511-55
Kurfuersten-Anlage 36, 69115 Heidelberg, Germany   http://www.netlab.nec.de


> Andy
>
>
>
>> We have tried to draft a "traceroute object" based on what we discussed
>> on the list and what we had in mind. We think this will serve as a
>> starting point of our information model.
>>
>> We have taken the disman draft as a starting point and we have erased
>> some fields not useful in the scope of our draft (that we do not specify
>> here), moreover we have added and changed other ones:
>>
>> NEW fields:
>> 1) traceRouteResultsLastGoodPathDuration (duration of single running of
>> the last good traceroute path determination)
>> 2) traceRouteResultsLastRun (when the last traceroute with these
>> characteristics was launched)
>> 3) traceRouteHopsASNumber (AS number of the hop)
>>
>> CHANGED fields:
>> 1) traceRouteProbeHistoryTime (timestamp of when the traceroute probe
>> came back) was changed to traceRouteProbeHistorySentTime (timestamp of
>> when the traceroute probe was sent)
>>
>>
>> Please find here how the "traceroute object" looks like right now:
>>
>> --traceRouteObjects
>>  |
>>  +--traceRouteCtlTable
>>  |  |
>>  |  +--traceRouteCtlEntry
>>  |     |
>>  |     +--traceRouteCtlOwnerIndex
>>  |     +--traceRouteCtlTestName
>>  |     +--traceRouteCtlTargetAddressType
>>  |     +--traceRouteCtlTargetAddress
>>  |     +--traceRouteCtlByPassRouteTable
>>  |     +--traceRouteCtlDataSize
>>  |     +--traceRouteCtlTimeOut
>>  |     +--traceRouteCtlProbesPerHop
>>  |     +--traceRouteCtlPort
>>  |     +--traceRouteCtlMaxTtl
>>  |     +--traceRouteCtlDSField
>>  |     +--traceRouteCtlSourceAddressType
>>  |     +--traceRouteCtlSourceAddress
>>  |     +--traceRouteCtlIfIndex
>>  |     +--traceRouteCtlMiscOptions
>>  |     +--traceRouteCtlMaxFailures
>>  |     +--traceRouteCtlDontFragment
>>  |     +--traceRouteCtlInitialTtl
>>  |     +--traceRouteCtlDescr
>>  |     +--traceRouteCtlMaxRows
>>  |     +--traceRouteCtlCreateHopsEntries
>>  |     +--traceRouteCtlType
>>  |
>>  +--traceRouteResultsTable
>>  |  |
>>  |  +--traceRouteResultsEntry
>>  |     |
>>  |     +--traceRouteResultsOperStatus
>>  |     +--traceRouteResultsIpTgtAddrType
>>  |     +--traceRouteResultsIpTgtAddr
>>  |     +--traceRouteResultsTestAttempts
>>  |     +--traceRouteResultsTestSuccesses
>>  |     +--traceRouteResultsLastGoodPath
>>  |     +--traceRouteResultsLastGoodPathDuration
>>  |     +--traceRouteResultsLastRun
>>  |
>>  +--traceRouteProbeHistoryTable
>>  |  |
>>  |  +--traceRouteProbeHistoryEntry
>>  |     |
>>  |     +--traceRouteProbeHistoryIndex
>>  |     +--traceRouteProbeHistoryHopIndex
>>  |     +--traceRouteProbeHistoryProbeIndex
>>  |     +--traceRouteProbeHistoryHAddrType
>>  |     +--traceRouteProbeHistoryHAddr
>>  |     +--traceRouteProbeHistoryResponse
>>  |     +--traceRouteProbeHistoryStatus
>>  |     +--traceRouteProbeHistorySentTime
>>  |
>>  +--traceRouteHopsTable
>>     |
>>     +--traceRouteHopsEntry
>>        |
>>        +--traceRouteHopsHopIndex
>>        +--traceRouteHopsIpTgtAddressType
>>        +--traceRouteHopsIpTgtAddress
>>        +--traceRouteHopsASNumber
>>        +--traceRouteHopsMinRtt
>>        +--traceRouteHopsMaxRtt
>>        +--traceRouteHopsAverageRtt
>>        +--traceRouteHopsRttSumOfSquares
>>        +--traceRouteHopsSentProbes
>>        +--traceRouteHopsProbeResponses
>>
>> We believe that most of the fields are self-explaining, for the unclear
>> ones please refer to the disman draft:
>> http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-06.t
>> xt
>>
>> Looking forward to receive your comments.
>>
>> Best regards,
>> Saverio Niccolini
>>
>> ============================================================
>> Dr. Saverio Niccolini
>> Research Staff Member
>> Network Laboratories, NEC Europe Ltd.
>> Kurfuerstenanlage 36, D-69115 Heidelberg
>> Tel.     +49 (0)6221 90511-18
>> Fax:     +49 (0)6221 90511-55
>> e-mail:  saverio.niccolini@netlab.nec.de
>> ============================================================
>>
>>
>> _______________________________________________
>> ippm mailing list
>> ippm@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ippm
>
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www1.ietf.org/mailman/listinfo/ippm







From disman-bounces@ietf.org  Mon Jan 17 12:38:09 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27227
	for <disman-archive@lists.ietf.org>; Mon, 17 Jan 2005 12:38:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cqaec-0003nX-J9; Mon, 17 Jan 2005 12:27:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cqadg-0003c6-QL; Mon, 17 Jan 2005 12:26:04 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25392;
	Mon, 17 Jan 2005 12:26:01 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cqasl-0001bd-Eq; Mon, 17 Jan 2005 12:41:41 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 17 Jan 2005 09:29:43 -0800
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com
	[171.71.163.17])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j0HHPSl2009001;
	Mon, 17 Jan 2005 09:25:28 -0800 (PST)
Received: from abierman-xp.cisco.com (sjc-vpn1-481.cisco.com [10.21.97.225])
	by mira-sjc5-c.cisco.com (MOS 3.4.5-GR) with ESMTP id BCU45818;
	Mon, 17 Jan 2005 09:25:27 -0800 (PST)
Message-Id: <4.3.2.7.2.20050117092146.02038530@fedex.cisco.com>
X-Sender: abierman@fedex.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 17 Jan 2005 09:25:27 -0800
To: Henk Uijterwaal <henk@ripe.net>
From: Andy Bierman <abierman@cisco.com>
In-Reply-To: <6.2.0.14.2.20050117173544.02bc24b0@localhost>
References: <F0DC7B6021F256408935B31D97FC727E518EB0@europa.office>
	<F0DC7B6021F256408935B31D97FC727E518EB0@europa.office>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 325b777e1a3a618c889460b612a65510
Cc: disman@ietf.org, Saverio Niccolini <Saverio.Niccolini@netlab.nec.de>,
        ippm@ietf.org
Subject: [Disman] RE: [ippm] Way to store traceroutes
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

At 08:36 AM 1/17/2005, Henk Uijterwaal wrote:
>Saverio,
>
>>By the way, I do not know if the IPPM list agrees on this.
>>Does the IPPM charter want to define a MIB module for traceroute
>>measurements?
>
>Given the lack of interest in the previous MIB we discussed, and
>the lack of expertise to review any proposal, I'd say: NO.

And since this seems to be an extension to a standard developed in the 
DISMAN WG, if this work belongs anywhere in the IETF, it's DISMAN. 

>Henk

Andy






>>Best regards,
>>Saverio
>>
>>> -----Original Message-----
>>> From: Juergen Quittek [mailto:quittek@netlab.nec.de]
>>> Sent: 17 January 2005 10:53
>>> To: Andy Bierman; Saverio Niccolini
>>> Cc: disman@ietf.org; ippm@ietf.org
>>> Subject: RE: [ippm] Way to store traceroutes
>>>
>>> Hi Andy,
>>>
>>> --On 14.01.2005 20:25 Uhr +0100 Andy Bierman wrote:
>>>
>>> > At 07:59 AM 1/14/2005, Saverio Niccolini wrote:
>>> >> Dear all,
>>> >> thanks a lot for your useful suggestions.
>>> >
>>> > This work is already established in the DISMAN WG.  See RFC 2925,
>>> > or its update (in progress):
>>> > http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-
>>> 06.txt
>>>
>>> Saverio and Sandra already had a look at the DISMAN-TRACEROUTE-MIB.
>>>
>>> > I strongly urge you to work with the DISMAN WG to resolve
>>> > perceived deficiencies with the RemOps MIB, rather than
>>> > create a spin-off MIB.
>>>
>>> As editor of draft-ietf-disman-remops-mib-v2-06.txt I wonder
>>> what you consider as 'perceived deficiencies with the RemOps MIB'.
>>>
>>> In the context of IPPM, there is certainly the deficiency, that
>>> you can only store measurements that were performed locally and that
>>> the tables for storing measurement results are read-only.
>>>
>>> But anyway, does the IPPM WG plan to store traceroute results in a
>>MIB?
>>>
>>> Thanks,
>>>
>>>     Juergen
>>> --
>>> Juergen Quittek        quittek@netlab.nec.de       Tel: +49 6221
>>90511-15
>>> NEC Europe Ltd.,       Network Laboratories        Fax: +49 6221
>>90511-55
>>> Kurfuersten-Anlage 36, 69115 Heidelberg, Germany
>>> http://www.netlab.nec.de
>>>
>>>
>>> > Andy
>>> >
>>> >
>>> >
>>> >> We have tried to draft a "traceroute object" based on what we
>>discussed
>>> >> on the list and what we had in mind. We think this will serve as a
>>> >> starting point of our information model.
>>> >>
>>> >> We have taken the disman draft as a starting point and we have
>>erased
>>> >> some fields not useful in the scope of our draft (that we do not
>>> specify
>>> >> here), moreover we have added and changed other ones:
>>> >>
>>> >> NEW fields:
>>> >> 1) traceRouteResultsLastGoodPathDuration (duration of single
>>running of
>>> >> the last good traceroute path determination)
>>> >> 2) traceRouteResultsLastRun (when the last traceroute with these
>>> >> characteristics was launched)
>>> >> 3) traceRouteHopsASNumber (AS number of the hop)
>>> >>
>>> >> CHANGED fields:
>>> >> 1) traceRouteProbeHistoryTime (timestamp of when the traceroute
>>probe
>>> >> came back) was changed to traceRouteProbeHistorySentTime (timestamp
>>of
>>> >> when the traceroute probe was sent)
>>> >>
>>> >>
>>> >> Please find here how the "traceroute object" looks like right now:
>>> >>
>>> >> --traceRouteObjects
>>> >>  |
>>> >>  +--traceRouteCtlTable
>>> >>  |  |
>>> >>  |  +--traceRouteCtlEntry
>>> >>  |     |
>>> >>  |     +--traceRouteCtlOwnerIndex
>>> >>  |     +--traceRouteCtlTestName
>>> >>  |     +--traceRouteCtlTargetAddressType
>>> >>  |     +--traceRouteCtlTargetAddress
>>> >>  |     +--traceRouteCtlByPassRouteTable
>>> >>  |     +--traceRouteCtlDataSize
>>> >>  |     +--traceRouteCtlTimeOut
>>> >>  |     +--traceRouteCtlProbesPerHop
>>> >>  |     +--traceRouteCtlPort
>>> >>  |     +--traceRouteCtlMaxTtl
>>> >>  |     +--traceRouteCtlDSField
>>> >>  |     +--traceRouteCtlSourceAddressType
>>> >>  |     +--traceRouteCtlSourceAddress
>>> >>  |     +--traceRouteCtlIfIndex
>>> >>  |     +--traceRouteCtlMiscOptions
>>> >>  |     +--traceRouteCtlMaxFailures
>>> >>  |     +--traceRouteCtlDontFragment
>>> >>  |     +--traceRouteCtlInitialTtl
>>> >>  |     +--traceRouteCtlDescr
>>> >>  |     +--traceRouteCtlMaxRows
>>> >>  |     +--traceRouteCtlCreateHopsEntries
>>> >>  |     +--traceRouteCtlType
>>> >>  |
>>> >>  +--traceRouteResultsTable
>>> >>  |  |
>>> >>  |  +--traceRouteResultsEntry
>>> >>  |     |
>>> >>  |     +--traceRouteResultsOperStatus
>>> >>  |     +--traceRouteResultsIpTgtAddrType
>>> >>  |     +--traceRouteResultsIpTgtAddr
>>> >>  |     +--traceRouteResultsTestAttempts
>>> >>  |     +--traceRouteResultsTestSuccesses
>>> >>  |     +--traceRouteResultsLastGoodPath
>>> >>  |     +--traceRouteResultsLastGoodPathDuration
>>> >>  |     +--traceRouteResultsLastRun
>>> >>  |
>>> >>  +--traceRouteProbeHistoryTable
>>> >>  |  |
>>> >>  |  +--traceRouteProbeHistoryEntry
>>> >>  |     |
>>> >>  |     +--traceRouteProbeHistoryIndex
>>> >>  |     +--traceRouteProbeHistoryHopIndex
>>> >>  |     +--traceRouteProbeHistoryProbeIndex
>>> >>  |     +--traceRouteProbeHistoryHAddrType
>>> >>  |     +--traceRouteProbeHistoryHAddr
>>> >>  |     +--traceRouteProbeHistoryResponse
>>> >>  |     +--traceRouteProbeHistoryStatus
>>> >>  |     +--traceRouteProbeHistorySentTime
>>> >>  |
>>> >>  +--traceRouteHopsTable
>>> >>     |
>>> >>     +--traceRouteHopsEntry
>>> >>        |
>>> >>        +--traceRouteHopsHopIndex
>>> >>        +--traceRouteHopsIpTgtAddressType
>>> >>        +--traceRouteHopsIpTgtAddress
>>> >>        +--traceRouteHopsASNumber
>>> >>        +--traceRouteHopsMinRtt
>>> >>        +--traceRouteHopsMaxRtt
>>> >>        +--traceRouteHopsAverageRtt
>>> >>        +--traceRouteHopsRttSumOfSquares
>>> >>        +--traceRouteHopsSentProbes
>>> >>        +--traceRouteHopsProbeResponses
>>> >>
>>> >> We believe that most of the fields are self-explaining, for the
>>unclear
>>> >> ones please refer to the disman draft:
>>> >>
>>http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-
>>> 06.t
>>> >> xt
>>> >>
>>> >> Looking forward to receive your comments.
>>> >>
>>> >> Best regards,
>>> >> Saverio Niccolini
>>> >>
>>> >> ============================================================
>>> >> Dr. Saverio Niccolini
>>> >> Research Staff Member
>>> >> Network Laboratories, NEC Europe Ltd.
>>> >> Kurfuerstenanlage 36, D-69115 Heidelberg
>>> >> Tel.     +49 (0)6221 90511-18
>>> >> Fax:     +49 (0)6221 90511-55
>>> >> e-mail:  saverio.niccolini@netlab.nec.de
>>> >> ============================================================
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> ippm mailing list
>>> >> ippm@ietf.org
>>> >> https://www1.ietf.org/mailman/listinfo/ippm
>>> >
>>> > _______________________________________________
>>> > ippm mailing list
>>> > ippm@ietf.org
>>> > https://www1.ietf.org/mailman/listinfo/ippm
>>>
>>>
>>>
>>
>>
>>_______________________________________________
>>ippm mailing list
>>ippm@ietf.org
>>https://www1.ietf.org/mailman/listinfo/ippm
>
>------------------------------------------------------------------------------
>Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.net
>RIPE Network Coordination Centre          http://www.amsterdamned.org/~henk
>P.O.Box 10096          Singel 258         Phone: +31.20.5354414
>1001 EB Amsterdam      1016 AB Amsterdam  Fax: +31.20.5354445
>The Netherlands        The Netherlands    Mobile: +31.6.55861746
>------------------------------------------------------------------------------
>
>Look here junior, don't you be so happy.
>And for Heaven's sake, don't you be so sad.                 (Tom Verlaine) 
>
>_______________________________________________
>ippm mailing list
>ippm@ietf.org https://www1.ietf.org/mailman/listinfo/ippm



From disman-bounces@ietf.org  Mon Jan 17 13:14:55 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00895
	for <disman-archive@lists.ietf.org>; Mon, 17 Jan 2005 13:14:55 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CqbJd-0002tV-VG; Mon, 17 Jan 2005 13:09:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CqWZA-0001us-Fe; Mon, 17 Jan 2005 08:05:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01913;
	Mon, 17 Jan 2005 08:05:07 -0500 (EST)
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CqWoC-0003fE-TL; Mon, 17 Jan 2005 08:20:42 -0500
Received: from europa.office (europa.office [10.1.1.2])
	by smtp0.netlab.nec.de (Postfix) with ESMTP
	id 4A4BDD96D; Mon, 17 Jan 2005 13:51:17 +0100 (CET)
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
Date: Mon, 17 Jan 2005 14:03:42 +0100
Message-ID: <F0DC7B6021F256408935B31D97FC727E518EB0@europa.office>
Thread-Topic: [ippm] Way to store traceroutes
Thread-Index: AcT8elJQiTEyHdb6SZ6YuQ3oIhMxaQAGhuqg
From: "Saverio Niccolini" <Saverio.Niccolini@netlab.nec.de>
To: "Andy Bierman" <abierman@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a0534e6179a1e260079328e8b03c7901
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 17 Jan 2005 13:09:24 -0500
Cc: disman@ietf.org, ippm@ietf.org
Subject: [Disman] RE: [ippm] Way to store traceroutes
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Hi Andy,
the purpose of our draft is to define a file format in order to store
traceroute measurements and not a MIB module.
The confusion is maybe created by the fact that we just kept the names
from the disman draft-RFC in order to facilitate comprehension of the
fields itself.

By the way, I do not know if the IPPM list agrees on this.
Does the IPPM charter want to define a MIB module for traceroute
measurements?

Best regards,
Saverio

> -----Original Message-----
> From: Juergen Quittek [mailto:quittek@netlab.nec.de]
> Sent: 17 January 2005 10:53
> To: Andy Bierman; Saverio Niccolini
> Cc: disman@ietf.org; ippm@ietf.org
> Subject: RE: [ippm] Way to store traceroutes
>=20
> Hi Andy,
>=20
> --On 14.01.2005 20:25 Uhr +0100 Andy Bierman wrote:
>=20
> > At 07:59 AM 1/14/2005, Saverio Niccolini wrote:
> >> Dear all,
> >> thanks a lot for your useful suggestions.
> >
> > This work is already established in the DISMAN WG.  See RFC 2925,
> > or its update (in progress):
> > http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-
> 06.txt
>=20
> Saverio and Sandra already had a look at the DISMAN-TRACEROUTE-MIB.
>=20
> > I strongly urge you to work with the DISMAN WG to resolve
> > perceived deficiencies with the RemOps MIB, rather than
> > create a spin-off MIB.
>=20
> As editor of draft-ietf-disman-remops-mib-v2-06.txt I wonder
> what you consider as 'perceived deficiencies with the RemOps MIB'.
>=20
> In the context of IPPM, there is certainly the deficiency, that
> you can only store measurements that were performed locally and that
> the tables for storing measurement results are read-only.
>=20
> But anyway, does the IPPM WG plan to store traceroute results in a
MIB?
>=20
> Thanks,
>=20
>     Juergen
> --
> Juergen Quittek        quittek@netlab.nec.de       Tel: +49 6221
90511-15
> NEC Europe Ltd.,       Network Laboratories        Fax: +49 6221
90511-55
> Kurfuersten-Anlage 36, 69115 Heidelberg, Germany
> http://www.netlab.nec.de
>=20
>=20
> > Andy
> >
> >
> >
> >> We have tried to draft a "traceroute object" based on what we
discussed
> >> on the list and what we had in mind. We think this will serve as a
> >> starting point of our information model.
> >>
> >> We have taken the disman draft as a starting point and we have
erased
> >> some fields not useful in the scope of our draft (that we do not
> specify
> >> here), moreover we have added and changed other ones:
> >>
> >> NEW fields:
> >> 1) traceRouteResultsLastGoodPathDuration (duration of single
running of
> >> the last good traceroute path determination)
> >> 2) traceRouteResultsLastRun (when the last traceroute with these
> >> characteristics was launched)
> >> 3) traceRouteHopsASNumber (AS number of the hop)
> >>
> >> CHANGED fields:
> >> 1) traceRouteProbeHistoryTime (timestamp of when the traceroute
probe
> >> came back) was changed to traceRouteProbeHistorySentTime (timestamp
of
> >> when the traceroute probe was sent)
> >>
> >>
> >> Please find here how the "traceroute object" looks like right now:
> >>
> >> --traceRouteObjects
> >>  |
> >>  +--traceRouteCtlTable
> >>  |  |
> >>  |  +--traceRouteCtlEntry
> >>  |     |
> >>  |     +--traceRouteCtlOwnerIndex
> >>  |     +--traceRouteCtlTestName
> >>  |     +--traceRouteCtlTargetAddressType
> >>  |     +--traceRouteCtlTargetAddress
> >>  |     +--traceRouteCtlByPassRouteTable
> >>  |     +--traceRouteCtlDataSize
> >>  |     +--traceRouteCtlTimeOut
> >>  |     +--traceRouteCtlProbesPerHop
> >>  |     +--traceRouteCtlPort
> >>  |     +--traceRouteCtlMaxTtl
> >>  |     +--traceRouteCtlDSField
> >>  |     +--traceRouteCtlSourceAddressType
> >>  |     +--traceRouteCtlSourceAddress
> >>  |     +--traceRouteCtlIfIndex
> >>  |     +--traceRouteCtlMiscOptions
> >>  |     +--traceRouteCtlMaxFailures
> >>  |     +--traceRouteCtlDontFragment
> >>  |     +--traceRouteCtlInitialTtl
> >>  |     +--traceRouteCtlDescr
> >>  |     +--traceRouteCtlMaxRows
> >>  |     +--traceRouteCtlCreateHopsEntries
> >>  |     +--traceRouteCtlType
> >>  |
> >>  +--traceRouteResultsTable
> >>  |  |
> >>  |  +--traceRouteResultsEntry
> >>  |     |
> >>  |     +--traceRouteResultsOperStatus
> >>  |     +--traceRouteResultsIpTgtAddrType
> >>  |     +--traceRouteResultsIpTgtAddr
> >>  |     +--traceRouteResultsTestAttempts
> >>  |     +--traceRouteResultsTestSuccesses
> >>  |     +--traceRouteResultsLastGoodPath
> >>  |     +--traceRouteResultsLastGoodPathDuration
> >>  |     +--traceRouteResultsLastRun
> >>  |
> >>  +--traceRouteProbeHistoryTable
> >>  |  |
> >>  |  +--traceRouteProbeHistoryEntry
> >>  |     |
> >>  |     +--traceRouteProbeHistoryIndex
> >>  |     +--traceRouteProbeHistoryHopIndex
> >>  |     +--traceRouteProbeHistoryProbeIndex
> >>  |     +--traceRouteProbeHistoryHAddrType
> >>  |     +--traceRouteProbeHistoryHAddr
> >>  |     +--traceRouteProbeHistoryResponse
> >>  |     +--traceRouteProbeHistoryStatus
> >>  |     +--traceRouteProbeHistorySentTime
> >>  |
> >>  +--traceRouteHopsTable
> >>     |
> >>     +--traceRouteHopsEntry
> >>        |
> >>        +--traceRouteHopsHopIndex
> >>        +--traceRouteHopsIpTgtAddressType
> >>        +--traceRouteHopsIpTgtAddress
> >>        +--traceRouteHopsASNumber
> >>        +--traceRouteHopsMinRtt
> >>        +--traceRouteHopsMaxRtt
> >>        +--traceRouteHopsAverageRtt
> >>        +--traceRouteHopsRttSumOfSquares
> >>        +--traceRouteHopsSentProbes
> >>        +--traceRouteHopsProbeResponses
> >>
> >> We believe that most of the fields are self-explaining, for the
unclear
> >> ones please refer to the disman draft:
> >>
http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-
> 06.t
> >> xt
> >>
> >> Looking forward to receive your comments.
> >>
> >> Best regards,
> >> Saverio Niccolini
> >>
> >> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >> Dr. Saverio Niccolini
> >> Research Staff Member
> >> Network Laboratories, NEC Europe Ltd.
> >> Kurfuerstenanlage 36, D-69115 Heidelberg
> >> Tel.     +49 (0)6221 90511-18
> >> Fax:     +49 (0)6221 90511-55
> >> e-mail:  saverio.niccolini@netlab.nec.de
> >> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >>
> >>
> >> _______________________________________________
> >> ippm mailing list
> >> ippm@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/ippm
> >
> > _______________________________________________
> > ippm mailing list
> > ippm@ietf.org
> > https://www1.ietf.org/mailman/listinfo/ippm
>=20
>=20
>=20




From disman-bounces@ietf.org  Mon Jan 17 13:16:06 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01116
	for <disman-archive@lists.ietf.org>; Mon, 17 Jan 2005 13:16:06 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CqbJe-0002ti-D2; Mon, 17 Jan 2005 13:09:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CqZse-0002Hw-AU; Mon, 17 Jan 2005 11:37:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21616;
	Mon, 17 Jan 2005 11:37:25 -0500 (EST)
Received: from postman.ripe.net ([193.0.0.199])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cqa7j-0000SL-HA; Mon, 17 Jan 2005 11:53:04 -0500
Received: by postman.ripe.net (Postfix, from userid 8)
	id B560924F5E; Mon, 17 Jan 2005 17:36:56 +0100 (CET)
Received: from birch.ripe.net (birch.ripe.net [193.0.1.96])
	by postman.ripe.net (Postfix) with ESMTP
	id 93DE924F57; Mon, 17 Jan 2005 17:36:55 +0100 (CET)
Received: from Geir.ripe.net (cow.ripe.net [193.0.1.239])
	by birch.ripe.net (8.12.10/8.11.6) with ESMTP id j0HGasZt017684;
	Mon, 17 Jan 2005 17:36:55 +0100
Message-Id: <6.2.0.14.2.20050117173544.02bc24b0@localhost>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
Date: Mon, 17 Jan 2005 17:36:48 +0100
To: "Saverio Niccolini" <Saverio.Niccolini@netlab.nec.de>,
        "Andy Bierman" <abierman@cisco.com>
From: Henk Uijterwaal <henk@ripe.net>
In-Reply-To: <F0DC7B6021F256408935B31D97FC727E518EB0@europa.office>
References: <F0DC7B6021F256408935B31D97FC727E518EB0@europa.office>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00
X-RIPE-Spam-Status: N 0.000431 / -5.9
X-RIPE-Signature: 63d2c5d4a80ed0dd047f4bf2a33fe854
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e367d58950869b6582535ddf5a673488
X-Mailman-Approved-At: Mon, 17 Jan 2005 13:09:24 -0500
Cc: disman@ietf.org, ippm@ietf.org
Subject: [Disman] RE: [ippm] Way to store traceroutes
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Saverio,

>By the way, I do not know if the IPPM list agrees on this.
>Does the IPPM charter want to define a MIB module for traceroute
>measurements?

Given the lack of interest in the previous MIB we discussed, and
the lack of expertise to review any proposal, I'd say: NO.

Henk





>Best regards,
>Saverio
>
> > -----Original Message-----
> > From: Juergen Quittek [mailto:quittek@netlab.nec.de]
> > Sent: 17 January 2005 10:53
> > To: Andy Bierman; Saverio Niccolini
> > Cc: disman@ietf.org; ippm@ietf.org
> > Subject: RE: [ippm] Way to store traceroutes
> >
> > Hi Andy,
> >
> > --On 14.01.2005 20:25 Uhr +0100 Andy Bierman wrote:
> >
> > > At 07:59 AM 1/14/2005, Saverio Niccolini wrote:
> > >> Dear all,
> > >> thanks a lot for your useful suggestions.
> > >
> > > This work is already established in the DISMAN WG.  See RFC 2925,
> > > or its update (in progress):
> > > http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-
> > 06.txt
> >
> > Saverio and Sandra already had a look at the DISMAN-TRACEROUTE-MIB.
> >
> > > I strongly urge you to work with the DISMAN WG to resolve
> > > perceived deficiencies with the RemOps MIB, rather than
> > > create a spin-off MIB.
> >
> > As editor of draft-ietf-disman-remops-mib-v2-06.txt I wonder
> > what you consider as 'perceived deficiencies with the RemOps MIB'.
> >
> > In the context of IPPM, there is certainly the deficiency, that
> > you can only store measurements that were performed locally and that
> > the tables for storing measurement results are read-only.
> >
> > But anyway, does the IPPM WG plan to store traceroute results in a
>MIB?
> >
> > Thanks,
> >
> >     Juergen
> > --
> > Juergen Quittek        quittek@netlab.nec.de       Tel: +49 6221
>90511-15
> > NEC Europe Ltd.,       Network Laboratories        Fax: +49 6221
>90511-55
> > Kurfuersten-Anlage 36, 69115 Heidelberg, Germany
> > http://www.netlab.nec.de
> >
> >
> > > Andy
> > >
> > >
> > >
> > >> We have tried to draft a "traceroute object" based on what we
>discussed
> > >> on the list and what we had in mind. We think this will serve as a
> > >> starting point of our information model.
> > >>
> > >> We have taken the disman draft as a starting point and we have
>erased
> > >> some fields not useful in the scope of our draft (that we do not
> > specify
> > >> here), moreover we have added and changed other ones:
> > >>
> > >> NEW fields:
> > >> 1) traceRouteResultsLastGoodPathDuration (duration of single
>running of
> > >> the last good traceroute path determination)
> > >> 2) traceRouteResultsLastRun (when the last traceroute with these
> > >> characteristics was launched)
> > >> 3) traceRouteHopsASNumber (AS number of the hop)
> > >>
> > >> CHANGED fields:
> > >> 1) traceRouteProbeHistoryTime (timestamp of when the traceroute
>probe
> > >> came back) was changed to traceRouteProbeHistorySentTime (timestamp
>of
> > >> when the traceroute probe was sent)
> > >>
> > >>
> > >> Please find here how the "traceroute object" looks like right now:
> > >>
> > >> --traceRouteObjects
> > >>  |
> > >>  +--traceRouteCtlTable
> > >>  |  |
> > >>  |  +--traceRouteCtlEntry
> > >>  |     |
> > >>  |     +--traceRouteCtlOwnerIndex
> > >>  |     +--traceRouteCtlTestName
> > >>  |     +--traceRouteCtlTargetAddressType
> > >>  |     +--traceRouteCtlTargetAddress
> > >>  |     +--traceRouteCtlByPassRouteTable
> > >>  |     +--traceRouteCtlDataSize
> > >>  |     +--traceRouteCtlTimeOut
> > >>  |     +--traceRouteCtlProbesPerHop
> > >>  |     +--traceRouteCtlPort
> > >>  |     +--traceRouteCtlMaxTtl
> > >>  |     +--traceRouteCtlDSField
> > >>  |     +--traceRouteCtlSourceAddressType
> > >>  |     +--traceRouteCtlSourceAddress
> > >>  |     +--traceRouteCtlIfIndex
> > >>  |     +--traceRouteCtlMiscOptions
> > >>  |     +--traceRouteCtlMaxFailures
> > >>  |     +--traceRouteCtlDontFragment
> > >>  |     +--traceRouteCtlInitialTtl
> > >>  |     +--traceRouteCtlDescr
> > >>  |     +--traceRouteCtlMaxRows
> > >>  |     +--traceRouteCtlCreateHopsEntries
> > >>  |     +--traceRouteCtlType
> > >>  |
> > >>  +--traceRouteResultsTable
> > >>  |  |
> > >>  |  +--traceRouteResultsEntry
> > >>  |     |
> > >>  |     +--traceRouteResultsOperStatus
> > >>  |     +--traceRouteResultsIpTgtAddrType
> > >>  |     +--traceRouteResultsIpTgtAddr
> > >>  |     +--traceRouteResultsTestAttempts
> > >>  |     +--traceRouteResultsTestSuccesses
> > >>  |     +--traceRouteResultsLastGoodPath
> > >>  |     +--traceRouteResultsLastGoodPathDuration
> > >>  |     +--traceRouteResultsLastRun
> > >>  |
> > >>  +--traceRouteProbeHistoryTable
> > >>  |  |
> > >>  |  +--traceRouteProbeHistoryEntry
> > >>  |     |
> > >>  |     +--traceRouteProbeHistoryIndex
> > >>  |     +--traceRouteProbeHistoryHopIndex
> > >>  |     +--traceRouteProbeHistoryProbeIndex
> > >>  |     +--traceRouteProbeHistoryHAddrType
> > >>  |     +--traceRouteProbeHistoryHAddr
> > >>  |     +--traceRouteProbeHistoryResponse
> > >>  |     +--traceRouteProbeHistoryStatus
> > >>  |     +--traceRouteProbeHistorySentTime
> > >>  |
> > >>  +--traceRouteHopsTable
> > >>     |
> > >>     +--traceRouteHopsEntry
> > >>        |
> > >>        +--traceRouteHopsHopIndex
> > >>        +--traceRouteHopsIpTgtAddressType
> > >>        +--traceRouteHopsIpTgtAddress
> > >>        +--traceRouteHopsASNumber
> > >>        +--traceRouteHopsMinRtt
> > >>        +--traceRouteHopsMaxRtt
> > >>        +--traceRouteHopsAverageRtt
> > >>        +--traceRouteHopsRttSumOfSquares
> > >>        +--traceRouteHopsSentProbes
> > >>        +--traceRouteHopsProbeResponses
> > >>
> > >> We believe that most of the fields are self-explaining, for the
>unclear
> > >> ones please refer to the disman draft:
> > >>
>http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-
> > 06.t
> > >> xt
> > >>
> > >> Looking forward to receive your comments.
> > >>
> > >> Best regards,
> > >> Saverio Niccolini
> > >>
> > >> ============================================================
> > >> Dr. Saverio Niccolini
> > >> Research Staff Member
> > >> Network Laboratories, NEC Europe Ltd.
> > >> Kurfuerstenanlage 36, D-69115 Heidelberg
> > >> Tel.     +49 (0)6221 90511-18
> > >> Fax:     +49 (0)6221 90511-55
> > >> e-mail:  saverio.niccolini@netlab.nec.de
> > >> ============================================================
> > >>
> > >>
> > >> _______________________________________________
> > >> ippm mailing list
> > >> ippm@ietf.org
> > >> https://www1.ietf.org/mailman/listinfo/ippm
> > >
> > > _______________________________________________
> > > ippm mailing list
> > > ippm@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/ippm
> >
> >
> >
>
>
>_______________________________________________
>ippm mailing list
>ippm@ietf.org
>https://www1.ietf.org/mailman/listinfo/ippm

------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre          http://www.amsterdamned.org/~henk
P.O.Box 10096          Singel 258         Phone: +31.20.5354414
1001 EB Amsterdam      1016 AB Amsterdam  Fax: +31.20.5354445
The Netherlands        The Netherlands    Mobile: +31.6.55861746
------------------------------------------------------------------------------

Look here junior, don't you be so happy.
And for Heaven's sake, don't you be so sad.                 (Tom Verlaine) 




From disman-bounces@ietf.org  Mon Jan 17 17:53:10 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02222
	for <disman-archive@lists.ietf.org>; Mon, 17 Jan 2005 17:53:10 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CqfeS-0005Pp-6G; Mon, 17 Jan 2005 17:47:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CqfaB-0004Yp-C2
	for disman@megatron.ietf.org; Mon, 17 Jan 2005 17:42:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01540
	for <disman@ietf.org>; Mon, 17 Jan 2005 17:42:44 -0500 (EST)
Received: from pop-a065d05.pas.sa.earthlink.net ([207.217.121.249])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CqfpJ-0004U5-RO
	for disman@ietf.org; Mon, 17 Jan 2005 17:58:26 -0500
Received: from h-66-167-205-141.snvacaid.dynamic.covad.net ([66.167.205.141]
	helo=oemcomputer)
	by pop-a065d05.pas.sa.earthlink.net with smtp (Exim 3.33 #1)
	id 1Cqfa9-00000d-00
	for disman@ietf.org; Mon, 17 Jan 2005 14:42:45 -0800
Message-ID: <013001c4fce6$043e83e0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman" <disman@ietf.org>
Date: Mon, 17 Jan 2005 14:43:51 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 0.1 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Subject: [Disman] Fw: Approval to Post Version -00 Internet-Drafts for the
	62nd IETFMeeting in Minneapolis, MN 
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Hi -

My internet access in the first half of February will be very limited, possibly zero.
If you intend to submit something as a draft-ietf-disman-* internet draft,
please let me know before January 30.  Absent substantial
discussion on the WG mailing list, the only things I will consider accepting
as WG documents are updates to our existing RFCs.

Randy Presuhn
disman WG chair

> From: "Internet-Drafts Administrator" <internet-drafts@ietf.org>
> To: "Working Group Chairs" <wgchairs@ietf.org>
> Sent: Friday, January 14, 2005 6:56 AM
> Subject: Approval to Post Version -00 Internet-Drafts for the 62nd IETFMeeting in Minneapolis, MN
>

> Dear IETF Working Group Chairs:
>
> In order to expedite the processing of the many version -00 I-Ds that
> the Secretariat  receives before an IETF meeting, we ask that you please
> notify the Secretariat prior to the initial submission cutoff date of all
> version -00 I-Ds that you expect to approve for posting as WG documents.
> Please send the filenames of your approved -00 I-Ds to internet-drafts@ietf.org
> by no later than five (5) business days prior to the cutoff date for -00 submissions,
> or by Monday, February 7th at 9:00 AM ET for the 62nd IETF Meeting. Please include
> the word "Approved I-Ds" in the "Subject" field. This procedure will help to ensure
> that version -00 I-Ds are posted in a timely manner, allowing more time for review
> by the public.
>
> Thank you for your cooperation in this matter.
>
> The Internet-Drafts Administrator





From disman-bounces@ietf.org  Wed Jan 19 17:10:51 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02485
	for <disman-archive@lists.ietf.org>; Wed, 19 Jan 2005 17:10:51 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CrO17-0000hj-Qs; Wed, 19 Jan 2005 17:09:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CrNzd-0000Uy-56
	for disman@megatron.ietf.org; Wed, 19 Jan 2005 17:08:01 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02246
	for <disman@ietf.org>; Wed, 19 Jan 2005 17:07:58 -0500 (EST)
Received: from pop-a065d23.pas.sa.earthlink.net ([207.217.121.254])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CrOFA-0000pQ-7P
	for disman@ietf.org; Wed, 19 Jan 2005 17:24:04 -0500
Received: from h-69-3-91-8.snvacaid.dynamic.covad.net ([69.3.91.8]
	helo=oemcomputer)
	by pop-a065d23.pas.sa.earthlink.net with smtp (Exim 3.33 #1)
	id 1CrNzX-00004U-00
	for disman@ietf.org; Wed, 19 Jan 2005 14:07:56 -0800
Message-ID: <005601c4fe73$57568a80$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman" <disman@ietf.org>
Date: Wed, 19 Jan 2005 14:07:42 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Subject: [Disman] disman WG session in Minneapolis?
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Hi -

Does anyone see a need for a meeting slot for the disman WG in Minneapolis?
If I don't see rationale and support on this list for a meeting, my plan is to
not request a slot.  Due to my own travel plans, I need to reach a decision
by January 30.

Randy

> From: "Harald Alvestrand" <harald@alvestrand.no>
> To: "IETF Announcement list" <ietf-announce@ietf.org>
> Sent: Wednesday, January 19, 2005 2:05 AM
> Subject: BOF scheduling for IETF 62
>

> Folks,
> I would like to draw your attention to two things about scheduling of BOFs at
> the IETF 62 meeting.
>
> FIRST - we've advanced the deadline for scheduling a bit this year. The
> scheduling deadline for "normal" requests is February 7.
> We also have an "absolutely latest" deadline for those things that pop up at the
> last moment, but we're going to ask you to try VERY hard to get all the "normal"
> things in by Feb 7, so that we can get the schedule firmed up at an earlier date
> than usual.
>
> The WG chairs know this, of course, but the people who want to arrange BOFs in
> Minneapolis may not have noticed the dates yet.
>
> SECOND - we're resurrecting the procedure that we had up until March 2003 of
> sending all BOF agendas to the IETF-announce list and to the new-work list (our
> contacts in other organizations).
> This, again, means that the earlier you have the agenda ready, the better!
>
> Reminder: ALL BOFs must be scheduled via the ADs!
>
> See you in Minneapolis!
>
>                          Harald
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce





