From disman-bounces@ietf.org Sat Feb 11 17:17:47 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F833q-00007p-VR; Sat, 11 Feb 2006 17:17:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F833p-00007c-6G
	for disman@megatron.ietf.org; Sat, 11 Feb 2006 17:17:45 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02812
	for <disman@ietf.org>; Sat, 11 Feb 2006 17:16:01 -0500 (EST)
Received: from ihemail2.lucent.com ([192.11.222.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F83H2-0001z4-WF
	for disman@ietf.org; Sat, 11 Feb 2006 17:31:29 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id k1BMHZcY021902; 
	Sat, 11 Feb 2006 16:17:36 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <DVB4NVN0>; Sat, 11 Feb 2006 23:17:35 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155094D9FAA@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Juergen Quittek (E-mail)" <quittek@ccrle.nec.de>, "'Randy Presuhn'"
	<randy_presuhn@mindspring.com>
Subject: RE: [Disman] I-D ACTION:draft-ietf-disman-remops-mib-v2-07.txt 
Date: Sat, 11 Feb 2006 23:17:34 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Cc: 'Disman' <disman@ietf.org>
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

So coming back to this...
Randy, I don't think I ever got a proto-write-up as per

   draft-ietf-proto-wgchair-doc-shepherding-05.txt

did I?

For the document itself and the MIB modules:

  !! Missing citation for Informative reference:
  P096 L006: [RFC1812]   F. Baker, "Requirements for IP Version 4 Routers", RFC 1812,

  !! Missing citation for Informative reference:
  P096 L012: [RFC2474]   Nichols, K., Blake, S., Baker, F. and D. Black, "Definition

  !! Missing citation for Normative reference:
  P095 L038: [RFC2863]   McCloghrie, K. and F. Kastenholz, "The Interfaces Group

  !! Missing citation for Informative reference:
  P096 L016: [RFC3260]   D. Grossman, "New Terminology and Clarifications for

  !! Missing citation for Normative reference:
  P095 L041: [RFC3411]   Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture

  !! Missing citation for Normative reference:
  P095 L045: [RFC4001]   Daniele, M., Haberman, B., Routhier, S. and J. Schoenwaelder

Can fix with:

OLD:
4.  Definitions

4.1.  DISMAN-PING-MIB
NEW:
4.  Definitions

   The following MIB modules import from [RFC2863], [RFC3411] and [RFC4001].
   They also use the REFERENCE clause to reference [RFC1812], [RFC2474]
   and [RFC3260].


4.1.  DISMAN-PING-MIB

Further, I am not sure why there is a MIN-ACCESS for these:

W: f(ping.mi2), (1155,19) MIN-ACCESS value identical to access specified for "pi
ngResultsLastGoodProbe"
W: f(ping.mi2), (1164,19) MIN-ACCESS value identical to access specified for "pi
ngProbeHistoryTime"
W: f(ping.mi2), (1328,19) MIN-ACCESS value identical to access specified for "pi
ngResultsLastGoodProbe"
W: f(ping.mi2), (1337,19) MIN-ACCESS value identical to access specified for "pi
ngProbeHistoryTime"

Same for:

W: f(traceroute.mi2), (1303,19) MIN-ACCESS value identical to access specified f
or "traceRouteResultsLastGoodPath"
W: f(traceroute.mi2), (1325,19) MIN-ACCESS value identical to access specified f
or "traceRouteProbeHistoryTime"
W: f(traceroute.mi2), (1346,19) MIN-ACCESS value identical to access specified f
or "traceRouteHopsLastGoodProbe"
W: f(traceroute.mi2), (1526,19) MIN-ACCESS value identical to access specified f
or "traceRouteResultsLastGoodPath"
W: f(traceroute.mi2), (1547,19) MIN-ACCESS value identical to access specified f
or "traceRouteProbeHistoryTime"
W: f(traceroute.mi2), (1569,19) MIN-ACCESS value identical to access specified f
or "traceRouteHopsLastGoodProbe"

And for:
E: f(traceroute.mi2), (1010,16) Index item "traceRouteHopsHopIndex" must be defi
ned with syntax that includes a range

I wonder why we would not add a range (1..4294967295) I think that is what
the DESCRIPTION clause does say too.

Bert
		
> -----Original Message-----
> From: Wijnen, Bert (Bert) 
> Sent: Monday, January 16, 2006 12:04
> To: Randy Presuhn; Wijnen, Bert (Bert)
> Cc: Disman
> Subject: RE: [Disman] I-D 
> ACTION:draft-ietf-disman-remops-mib-v2-07.txt 
> 
> 
> OK, so unless you tell me otherwise, I am going to proceed
> on this document and assume WG consensus.
> 
> Bert
> 
> > -----Original Message-----
> > From: Randy Presuhn [mailto:randy_presuhn@mindspring.com]
> > Sent: Monday, January 16, 2006 08:54
> > To: Wijnen, Bert (Bert)
> > Cc: Disman
> > Subject: Re: [Disman] I-D 
> > ACTION:draft-ietf-disman-remops-mib-v2-07.txt 
> > 
> > 
> > Hi Bert -
> > 
> > > From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
> > > To: "Randy Presuhn (E-mail)" <randy_presuhn@mindspring.com>
> > > Sent: Thursday, January 12, 2006 8:14 AM
> > > Subject: FW: [Disman] I-D 
> > ACTION:draft-ietf-disman-remops-mib-v2-07.txt 
> > >
> > 
> > > Randy,
> > > is this now back on my plate, or does it need another check by WG?
> > > 
> > > We also still need to do IETF Last Call, and so we need to 
> > start hurry-ing 
> > > if we want to finish this before I step down in March.
> > ...
> > 
> > The changes were posted to the disman WG mailing list, and 
> > there was no dissent.
> > The request is for consideration as PROPOSED STANDARD.
> > We would have liked to have gone for DRAFT, but I was only able
> > to obtain adequate implementation reports for two of the three
> > MIB modules in this document.
> > 
> > Randy, disman chair
> > 
> > 
> > 
> > 
> 




From disman-bounces@ietf.org Sat Feb 11 21:39:00 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F878e-00088p-Dv; Sat, 11 Feb 2006 21:39:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F878d-00088h-1K
	for disman@megatron.ietf.org; Sat, 11 Feb 2006 21:38:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15863
	for <disman@ietf.org>; Sat, 11 Feb 2006 21:37:15 -0500 (EST)
Received: from kyoto.netlab.nec.de ([195.37.70.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F87Ls-0008MH-PJ
	for disman@ietf.org; Sat, 11 Feb 2006 21:52:45 -0500
Received: from [192.168.1.128] (HSI-KBW-085-216-002-068.hsi.kabelbw.de
	[85.216.2.68])
	by kyoto.netlab.nec.de (Postfix) with ESMTP id 310EA1BAC4D;
	Sun, 12 Feb 2006 03:40:20 +0100 (CET)
Date: Sun, 12 Feb 2006 03:37:39 +0100
From: Juergen Quittek <quittek@netlab.nec.de>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
	"'Randy Presuhn'" <randy_presuhn@mindspring.com>
Subject: RE: [Disman] I-D ACTION:draft-ietf-disman-remops-mib-v2-07.txt 
Message-ID: <5812C7074AC55786FF76FE45@753F3B888A9969457862729D>
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B155094D9FAA@nl0006exch001u.nl.lucent.com>
References: <7D5D48D2CAA3D84C813F5B154F43B155094D9FAA@nl0006exch001u.nl.lucent.com>
X-Mailer: Mulberry/3.1.6 (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: ded6070f7eed56e10c4f4d0d5043d9c7
Content-Transfer-Encoding: 7bit
Cc: 'Disman' <disman@ietf.org>
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 Bert,

--On 2/11/06 11:17 PM +0100 Wijnen, Bert (Bert) wrote:

> So coming back to this...
> Randy, I don't think I ever got a proto-write-up as per
>
>    draft-ietf-proto-wgchair-doc-shepherding-05.txt
>
> did I?
>
> For the document itself and the MIB modules:
>
>   !! Missing citation for Informative reference:
>   P096 L006: [RFC1812]   F. Baker, "Requirements for IP Version 4 Routers", RFC 1812,
>
>   !! Missing citation for Informative reference:
>   P096 L012: [RFC2474]   Nichols, K., Blake, S., Baker, F. and D. Black, "Definition
>
>   !! Missing citation for Normative reference:
>   P095 L038: [RFC2863]   McCloghrie, K. and F. Kastenholz, "The Interfaces Group
>
>   !! Missing citation for Informative reference:
>   P096 L016: [RFC3260]   D. Grossman, "New Terminology and Clarifications for
>
>   !! Missing citation for Normative reference:
>   P095 L041: [RFC3411]   Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture
>
>   !! Missing citation for Normative reference:
>   P095 L045: [RFC4001]   Daniele, M., Haberman, B., Routhier, S. and J. Schoenwaelder
>
> Can fix with:
>
> OLD:
> 4.  Definitions
>
> 4.1.  DISMAN-PING-MIB
> NEW:
> 4.  Definitions
>
>    The following MIB modules import from [RFC2863], [RFC3411] and [RFC4001].
>    They also use the REFERENCE clause to reference [RFC1812], [RFC2474]
>    and [RFC3260].

This looks like a good solution for the formal problem.
I added the paragraph that you suggested.

> 4.1.  DISMAN-PING-MIB
>
> Further, I am not sure why there is a MIN-ACCESS for these:
>
> W: f(ping.mi2), (1155,19) MIN-ACCESS value identical to access specified for "pi
> ngResultsLastGoodProbe"
> W: f(ping.mi2), (1164,19) MIN-ACCESS value identical to access specified for "pi
> ngProbeHistoryTime"
> W: f(ping.mi2), (1328,19) MIN-ACCESS value identical to access specified for "pi
> ngResultsLastGoodProbe"
> W: f(ping.mi2), (1337,19) MIN-ACCESS value identical to access specified for "pi
> ngProbeHistoryTime"

For pingProbeHistoryTime the DESCRIPTION clauses differ in the two compliance statements.
This also applies to traceRouteResultsLastGoodPath, traceRouteProbeHistoryTime, and
traceRouteHopsLastGoodProbe.

For pingResultsLastGoodProbe the  DESCRIPTION clauses are identical in both compliance
statements.  This looks like I made a mistake.  I suggest changing pingMinimumCompliance:
OLD:
        OBJECT pingResultsLastGoodProbe
        MIN-ACCESS  read-only
        DESCRIPTION
            "This object is mandatory for implementations that have
            access to a system clock and are capable of setting
            the values for DateAndTime objects.  It is RECOMMENDED
            that when this object is not supported that its values
            be reported as '0000000000000000'H."

WITH
        OBJECT pingResultsLastGoodProbe
        MIN-ACCESS  read-only
        DESCRIPTION
            "If the pingHistoryGroup is implemented, then this
            object is mandatory for implementations that have
            access to a system clock and are capable of setting
            the values for DateAndTime objects.  It is RECOMMENDED
            that when this object is not supported that its values
            be reported as '0000000000000000'H."


> Same for:
>
> W: f(traceroute.mi2), (1303,19) MIN-ACCESS value identical to access specified f
> or "traceRouteResultsLastGoodPath"
> W: f(traceroute.mi2), (1325,19) MIN-ACCESS value identical to access specified f
> or "traceRouteProbeHistoryTime"
> W: f(traceroute.mi2), (1346,19) MIN-ACCESS value identical to access specified f
> or "traceRouteHopsLastGoodProbe"
> W: f(traceroute.mi2), (1526,19) MIN-ACCESS value identical to access specified f
> or "traceRouteResultsLastGoodPath"
> W: f(traceroute.mi2), (1547,19) MIN-ACCESS value identical to access specified f
> or "traceRouteProbeHistoryTime"
> W: f(traceroute.mi2), (1569,19) MIN-ACCESS value identical to access specified f
> or "traceRouteHopsLastGoodProbe"

Please see above.

> And for:
> E: f(traceroute.mi2), (1010,16) Index item "traceRouteHopsHopIndex" must be defi
> ned with syntax that includes a range
>
> I wonder why we would not add a range (1..4294967295) I think that is what
> the DESCRIPTION clause does say too.

Yes, the range for the index was missing.

At other places in the document we use range (1..'ffffffff'h) instead of
(1..4294967295).  I suggest using it also here.

Thanks,

    Juergen



> Bert
> 		
>> -----Original Message-----
>> From: Wijnen, Bert (Bert)
>> Sent: Monday, January 16, 2006 12:04
>> To: Randy Presuhn; Wijnen, Bert (Bert)
>> Cc: Disman
>> Subject: RE: [Disman] I-D
>> ACTION:draft-ietf-disman-remops-mib-v2-07.txt
>>
>>
>> OK, so unless you tell me otherwise, I am going to proceed
>> on this document and assume WG consensus.
>>
>> Bert
>>
>> > -----Original Message-----
>> > From: Randy Presuhn [mailto:randy_presuhn@mindspring.com]
>> > Sent: Monday, January 16, 2006 08:54
>> > To: Wijnen, Bert (Bert)
>> > Cc: Disman
>> > Subject: Re: [Disman] I-D
>> > ACTION:draft-ietf-disman-remops-mib-v2-07.txt
>> >
>> >
>> > Hi Bert -
>> >
>> > > From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
>> > > To: "Randy Presuhn (E-mail)" <randy_presuhn@mindspring.com>
>> > > Sent: Thursday, January 12, 2006 8:14 AM
>> > > Subject: FW: [Disman] I-D
>> > ACTION:draft-ietf-disman-remops-mib-v2-07.txt
>> > >
>> >
>> > > Randy,
>> > > is this now back on my plate, or does it need another check by WG?
>> > >
>> > > We also still need to do IETF Last Call, and so we need to
>> > start hurry-ing
>> > > if we want to finish this before I step down in March.
>> > ...
>> >
>> > The changes were posted to the disman WG mailing list, and
>> > there was no dissent.
>> > The request is for consideration as PROPOSED STANDARD.
>> > We would have liked to have gone for DRAFT, but I was only able
>> > to obtain adequate implementation reports for two of the three
>> > MIB modules in this document.
>> >
>> > Randy, disman chair
>> >
>> >
>> >
>> >
>>
>
>






From disman-bounces@ietf.org Tue Feb 14 13:16:47 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F94jH-00025q-T2; Tue, 14 Feb 2006 13:16:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F94jG-00025l-CG
	for disman@megatron.ietf.org; Tue, 14 Feb 2006 13:16:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17863
	for <disman@ietf.org>; Tue, 14 Feb 2006 13:15:00 -0500 (EST)
Received: from kyoto.netlab.nec.de ([195.37.70.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F94x7-00036M-P6
	for disman@ietf.org; Tue, 14 Feb 2006 13:31:06 -0500
Received: from dhcp-18-188-3-114.dyn.mit.edu (h10393eddb33.dyn.mit.edu
	[18.188.3.114])
	by kyoto.netlab.nec.de (Postfix) with ESMTP id C6C491BAC4D;
	Tue, 14 Feb 2006 19:18:10 +0100 (CET)
Date: Tue, 14 Feb 2006 19:16:32 +0100
From: Juergen Quittek <quittek@netlab.nec.de>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
	"'Randy Presuhn'" <randy_presuhn@mindspring.com>
Subject: RE: [Disman] I-D ACTION:draft-ietf-disman-remops-mib-v2-07.txt 
Message-ID: <384108E36B15E36B27E835F0@dhcp-18-188-3-114.dyn.mit.edu>
In-Reply-To: <5812C7074AC55786FF76FE45@753F3B888A9969457862729D>
References: <7D5D48D2CAA3D84C813F5B154F43B155094D9FAA@nl0006exch001u.nl.lucent.com>
	<5812C7074AC55786FF76FE45@753F3B888A9969457862729D>
X-Mailer: Mulberry/3.1.6 (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: 140baa79ca42e6b0e2b4504291346186
Content-Transfer-Encoding: 7bit
Cc: 'Disman' <disman@ietf.org>
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 Bert,

I misunderstood your comment on the MIN-ACCESS clauses
for objects pingResultsLastGoodProbe, pingProbeHistoryTime,
traceRouteResultsLastGoodPath, traceRouteProbeHistoryTime, and
traceRouteHopsLastGoodProbe.

Now I see that they are just redundant.
I removed all of them from the compliance statements.

I will post a new version including all requested changes soon.

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


--On 2/12/06 3:37 AM +0100 Juergen Quittek wrote:

> Hi Bert,
>
> --On 2/11/06 11:17 PM +0100 Wijnen, Bert (Bert) wrote:
>
>> So coming back to this...
>> Randy, I don't think I ever got a proto-write-up as per
>>
>>    draft-ietf-proto-wgchair-doc-shepherding-05.txt
>>
>> did I?
>>
>> For the document itself and the MIB modules:
>>
>>   !! Missing citation for Informative reference:
>>   P096 L006: [RFC1812]   F. Baker, "Requirements for IP Version 4 Routers", RFC 1812,
>>
>>   !! Missing citation for Informative reference:
>>   P096 L012: [RFC2474]   Nichols, K., Blake, S., Baker, F. and D. Black, "Definition
>>
>>   !! Missing citation for Normative reference:
>>   P095 L038: [RFC2863]   McCloghrie, K. and F. Kastenholz, "The Interfaces Group
>>
>>   !! Missing citation for Informative reference:
>>   P096 L016: [RFC3260]   D. Grossman, "New Terminology and Clarifications for
>>
>>   !! Missing citation for Normative reference:
>>   P095 L041: [RFC3411]   Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture
>>
>>   !! Missing citation for Normative reference:
>>   P095 L045: [RFC4001]   Daniele, M., Haberman, B., Routhier, S. and J. Schoenwaelder
>>
>> Can fix with:
>>
>> OLD:
>> 4.  Definitions
>>
>> 4.1.  DISMAN-PING-MIB
>> NEW:
>> 4.  Definitions
>>
>>    The following MIB modules import from [RFC2863], [RFC3411] and [RFC4001].
>>    They also use the REFERENCE clause to reference [RFC1812], [RFC2474]
>>    and [RFC3260].
>
> This looks like a good solution for the formal problem.
> I added the paragraph that you suggested.
>
>> 4.1.  DISMAN-PING-MIB
>>
>> Further, I am not sure why there is a MIN-ACCESS for these:
>>
>> W: f(ping.mi2), (1155,19) MIN-ACCESS value identical to access specified for "pi
>> ngResultsLastGoodProbe"
>> W: f(ping.mi2), (1164,19) MIN-ACCESS value identical to access specified for "pi
>> ngProbeHistoryTime"
>> W: f(ping.mi2), (1328,19) MIN-ACCESS value identical to access specified for "pi
>> ngResultsLastGoodProbe"
>> W: f(ping.mi2), (1337,19) MIN-ACCESS value identical to access specified for "pi
>> ngProbeHistoryTime"
>
> For pingProbeHistoryTime the DESCRIPTION clauses differ in the two compliance statements.
> This also applies to traceRouteResultsLastGoodPath, traceRouteProbeHistoryTime, and
> traceRouteHopsLastGoodProbe.
>
> For pingResultsLastGoodProbe the  DESCRIPTION clauses are identical in both compliance
> statements.  This looks like I made a mistake.  I suggest changing pingMinimumCompliance:
> OLD:
>         OBJECT pingResultsLastGoodProbe
>         MIN-ACCESS  read-only
>         DESCRIPTION
>             "This object is mandatory for implementations that have
>             access to a system clock and are capable of setting
>             the values for DateAndTime objects.  It is RECOMMENDED
>             that when this object is not supported that its values
>             be reported as '0000000000000000'H."
>
> WITH
>         OBJECT pingResultsLastGoodProbe
>         MIN-ACCESS  read-only
>         DESCRIPTION
>             "If the pingHistoryGroup is implemented, then this
>             object is mandatory for implementations that have
>             access to a system clock and are capable of setting
>             the values for DateAndTime objects.  It is RECOMMENDED
>             that when this object is not supported that its values
>             be reported as '0000000000000000'H."
>
>
>> Same for:
>>
>> W: f(traceroute.mi2), (1303,19) MIN-ACCESS value identical to access specified f
>> or "traceRouteResultsLastGoodPath"
>> W: f(traceroute.mi2), (1325,19) MIN-ACCESS value identical to access specified f
>> or "traceRouteProbeHistoryTime"
>> W: f(traceroute.mi2), (1346,19) MIN-ACCESS value identical to access specified f
>> or "traceRouteHopsLastGoodProbe"
>> W: f(traceroute.mi2), (1526,19) MIN-ACCESS value identical to access specified f
>> or "traceRouteResultsLastGoodPath"
>> W: f(traceroute.mi2), (1547,19) MIN-ACCESS value identical to access specified f
>> or "traceRouteProbeHistoryTime"
>> W: f(traceroute.mi2), (1569,19) MIN-ACCESS value identical to access specified f
>> or "traceRouteHopsLastGoodProbe"
>
> Please see above.
>
>> And for:
>> E: f(traceroute.mi2), (1010,16) Index item "traceRouteHopsHopIndex" must be defi
>> ned with syntax that includes a range
>>
>> I wonder why we would not add a range (1..4294967295) I think that is what
>> the DESCRIPTION clause does say too.
>
> Yes, the range for the index was missing.
>
> At other places in the document we use range (1..'ffffffff'h) instead of
> (1..4294967295).  I suggest using it also here.
>
> Thanks,
>
>     Juergen
>
>
>
>> Bert
>> 		
>>> -----Original Message-----
>>> From: Wijnen, Bert (Bert)
>>> Sent: Monday, January 16, 2006 12:04
>>> To: Randy Presuhn; Wijnen, Bert (Bert)
>>> Cc: Disman
>>> Subject: RE: [Disman] I-D
>>> ACTION:draft-ietf-disman-remops-mib-v2-07.txt
>>>
>>>
>>> OK, so unless you tell me otherwise, I am going to proceed
>>> on this document and assume WG consensus.
>>>
>>> Bert
>>>
>>> > -----Original Message-----
>>> > From: Randy Presuhn [mailto:randy_presuhn@mindspring.com]
>>> > Sent: Monday, January 16, 2006 08:54
>>> > To: Wijnen, Bert (Bert)
>>> > Cc: Disman
>>> > Subject: Re: [Disman] I-D
>>> > ACTION:draft-ietf-disman-remops-mib-v2-07.txt
>>> >
>>> >
>>> > Hi Bert -
>>> >
>>> > > From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
>>> > > To: "Randy Presuhn (E-mail)" <randy_presuhn@mindspring.com>
>>> > > Sent: Thursday, January 12, 2006 8:14 AM
>>> > > Subject: FW: [Disman] I-D
>>> > ACTION:draft-ietf-disman-remops-mib-v2-07.txt
>>> > >
>>> >
>>> > > Randy,
>>> > > is this now back on my plate, or does it need another check by WG?
>>> > >
>>> > > We also still need to do IETF Last Call, and so we need to
>>> > start hurry-ing
>>> > > if we want to finish this before I step down in March.
>>> > ...
>>> >
>>> > The changes were posted to the disman WG mailing list, and
>>> > there was no dissent.
>>> > The request is for consideration as PROPOSED STANDARD.
>>> > We would have liked to have gone for DRAFT, but I was only able
>>> > to obtain adequate implementation reports for two of the three
>>> > MIB modules in this document.
>>> >
>>> > Randy, disman chair
>>> >
>>> >
>>> >
>>> >
>>>
>>
>>
>






From disman-bounces@ietf.org Thu Feb 16 13:14:16 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F9ndw-0006QR-Ne; Thu, 16 Feb 2006 13:14:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F9ndu-0006PA-W7; Thu, 16 Feb 2006 13:14:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17510;
	Thu, 16 Feb 2006 13:12:27 -0500 (EST)
Received: from pop04.mail.atl.earthlink.net ([207.69.200.28])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F9ns7-0007eF-Nt; Thu, 16 Feb 2006 13:29:00 -0500
Received: from mswamui-billy.atl.sa.earthlink.net ([209.86.224.27])
	by pop04.mail.atl.earthlink.net with esmtp (Exim 3.36 #10)
	id 1F9ndo-0004iE-00; Thu, 16 Feb 2006 13:14:08 -0500
Message-ID: <31341280.1140113648310.JavaMail.root@mswamui-billy.atl.sa.earthlink.net>
Date: Thu, 16 Feb 2006 10:14:08 -0800 (GMT-08:00)
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: disman@ietf.org, ltru@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: EarthLink Zoo Mail 1.0
X-Spam-Score: 0.1 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [Disman] Fw: New addresses for wg chairs
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randy Presuhn <randy_presuhn@mindspring.com>
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 -

Forwarded for your information. Of course, you may still reach WG chairs
directly.

Randy

>From: Sam Hartman <hartmans-ietf@mit.edu>
>Sent: Feb 16, 2006 9:37 AM
>To: wgchairs@ietf.org
>Subject: New addresses for wg chairs; adjust your mail filters
>
>
>
>Hi.
>
>The tools team has created some very useful aliases for reaching WG
>chairs.  They will be more useful if your spam filters actually accept the messages.
>
>
>wgname-chairs@tools.ietf.org will reach the chairs of wgname.  For
>example ipv6-chairs@tools.ietf.org will reach the chairs of the ipv6
>working group.
>
>ad-name-chairs@tools.ietf.org reaches all chairs of a given AD.  For
>example I can reach my chairs by sending to
>sam-hartman-chairs@tools.ietf.org.
>
>
>Thanks much for the availability of these aliases.
>
>P.S.  Future nomcoms are requested not to appoint Mr. or Ms. Krb Wg to
>the IESG.
>





From disman-bounces@ietf.org Fri Feb 17 09:48:51 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1FA6uh-0001Pu-C4; Fri, 17 Feb 2006 09:48:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1FA6ug-0001Nj-CN
	for disman@megatron.ietf.org; Fri, 17 Feb 2006 09:48:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01826
	for <disman@ietf.org>; Fri, 17 Feb 2006 09:01:41 -0500 (EST)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FA0ug-0001IW-9m
	for disman@ietf.org; Fri, 17 Feb 2006 03:24:36 -0500
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32])
	by hermes.iu-bremen.de (Postfix) with ESMTP id B0D3E4D339;
	Fri, 17 Feb 2006 09:09:19 +0100 (CET)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by localhost (demetrius [212.201.44.32]) (amavisd-new,
	port 10024) with ESMTP
	id 25309-01; Fri, 17 Feb 2006 09:09:18 +0100 (CET)
Received: from boskop.local (unknown [10.222.1.1])
	by hermes.iu-bremen.de (Postfix) with ESMTP id DBEEA4D29A;
	Fri, 17 Feb 2006 09:09:17 +0100 (CET)
Received: by boskop.local (Postfix, from userid 501)
	id 994C25FCD52; Fri, 17 Feb 2006 09:09:17 +0100 (CET)
Date: Fri, 17 Feb 2006 09:09:17 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
	Juergen Quittek <quittek@ccrle.nec.de>
Message-ID: <20060217080917.GA10233@boskop.local>
Mail-Followup-To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
	Juergen Quittek <quittek@ccrle.nec.de>, disman@ietf.org
References: <7D5D48D2CAA3D84C813F5B154F43B155094D9AF1@nl0006exch001u.nl.lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B155094D9AF1@nl0006exch001u.nl.lucent.com>
User-Agent: Mutt/1.5.10i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: disman@ietf.org
Subject: [Disman] Re: MIB Doctor review: publish
	draft-ietf-disman-remops-mib-v2-0 6.tx t
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
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

On Fri, Feb 10, 2006 at 12:28:11AM +0100, Wijnen, Bert (Bert) wrote:

> So did you check rev 7 to make sure you are happy.
> I am assuming so, but would appreciate an ack.
> 
> In your MIB doctor review, did you also do a smidiff 
> with the RFC versions, and are we OK on those?

Bert,

I did an smidiff and I actually wrote a compliance statement output
driver for smidump to be able to check the differences between
compliance statements.

I just took a quick look at the latest version (which is -08 I think)
and I found a few more nits that you might want to get fixed if still
possible and JQ can turn things around things quickly:

1) In the pingMIB MODULE-IDENTITY, it says twice:

                - changed DEFVAL of object pingCtlDescr from
                  DEFVAL { '00'H } to DEFVAL { ''H }

   I think saying this once should be good enough.

2) pingCompliancy -> pingCompliance

3) pingFullCompliancy -> pingFullCompliance

4) traceRoutecompliancy -> traceRouteCompliance

5) traceRouteFullCompliancy -> traceRouteFullCompliance

6) I would have liked to see text in the deprecated compliance that
   says why these were deprecated and what implementors should do
   about it (since comparing compliance statements is really a tedious
   task). I know this is mentioned in section 3.4 but you know that
   extracted MIB modules often have a life of their own.

    pingCompliance MODULE-COMPLIANCE
       STATUS  deprecated
       DESCRIPTION
               "The compliance statement for the DISMAN-PING-MIB. This
		compliance statement has been deprecated because the 
		group pingGroup and the pingTimeStampGroup have been
		split and deprecated. The pingFullCompliance statement
		is semantically identical to the deprecated pingCompliance 
		statement".

    traceRouteCompliance MODULE-COMPLIANCE
       STATUS  deprecated
       DESCRIPTION
               "The compliance statement for the DISMAN-TRACEROUTE-MIB.
		This compliance statement has been deprecated because
		the traceRouteGroup and the traceRouteTimeStampGroup
		have been split and deprecated. The traceRouteFullCompliance
		is semantically identical to the deprecated 
		traceRouteCompliance statement."

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany




From disman-bounces@ietf.org Fri Feb 17 14:50:17 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1FABcP-0000BG-29; Fri, 17 Feb 2006 14:50:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F9q4q-0003C2-IS; Thu, 16 Feb 2006 15:50:12 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03328;
	Thu, 16 Feb 2006 15:48:23 -0500 (EST)
Received: from willow.neustar.com ([209.173.53.84])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F9qJ7-0008Q9-C8; Thu, 16 Feb 2006 16:04:58 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k1GKo19W027153
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 16 Feb 2006 20:50:01 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1F9q4f-0003yH-PB; Thu, 16 Feb 2006 15:50:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1F9q4f-0003yH-PB@stiedprstage1.ietf.org>
Date: Thu, 16 Feb 2006 15:50:01 -0500
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
X-Mailman-Approved-At: Fri, 17 Feb 2006 14:50:15 -0500
Cc: disman@ietf.org
Subject: [Disman] I-D ACTION:draft-ietf-disman-remops-mib-v2-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

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Distributed Management Working Group of the IETF.

	Title		: Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations
	Author(s)	: J. Quittek, K. White
	Filename	: draft-ietf-disman-remops-mib-v2-08.txt
	Pages		: 97
	Date		: 2006-2-16
	
This memo defines Management Information Bases (MIBs) for performing
ping, traceroute and lookup operations at a host.  When managing a
network it is useful to be able to initiate and retrieve the results
of ping or traceroute operations when performed at a remote host.  A
Lookup capability is defined in order to enable resolution of either
an IP address to an DNS name or a DNS name to an IP address at a
remote host.

Currently, there are several enterprise-specific MIBs for performing
remote ping or traceroute operations.  The purpose of this memo is to
define a standards-based solution to enable interoperability.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-08.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-disman-remops-mib-v2-08.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-disman-remops-mib-v2-08.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2006-2-16140407.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-disman-remops-mib-v2-08.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-disman-remops-mib-v2-08.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-2-16140407.I-D@ietf.org>


--OtherAccess--

--NextPart--





From disman-bounces@ietf.org Fri Feb 17 15:02:44 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1FABoS-0002r5-TF; Fri, 17 Feb 2006 15:02:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1FABoQ-0002pQ-IK; Fri, 17 Feb 2006 15:02:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29598;
	Fri, 17 Feb 2006 15:00:54 -0500 (EST)
Received: from pop-knobcone.atl.sa.earthlink.net ([207.69.195.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FAC2r-0005kn-5g; Fri, 17 Feb 2006 15:17:41 -0500
Received: from h-64-105-34-171.snvacaid.dynamic.covad.net ([64.105.34.171]
	helo=oemcomputer)
	by pop-knobcone.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1FABoL-0007ZB-00; Fri, 17 Feb 2006 15:02:37 -0500
Message-ID: <001201c633fd$4a910bc0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <agentx@ietf.org>, "Disman" <disman@ietf.org>,
	"LTRU Working Group" <ltru@ietf.org>
Date: Fri, 17 Feb 2006 12:03:58 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [Disman] Fw: IETF Server Migration  Part 2. 
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 -

This is relevant to the operation of all three of these mailing lists.

Randy, list admin

----- Original Message ----- 
> From: "IETF Secretariat" <ietf-secretariat@ietf.org>
> To: "IETF Announcement list" <ietf-announce@ietf.org>
> Sent: Friday, February 17, 2006 5:52 AM
> Subject: IETF Server Migration Part 2. 
>
> Hi All,
> 
> NeuStar Secretariat Services will be migrating the IETF to new servers in
> accordance with the schedule below.  All work will be done on the weekends to
> minimize disruptions, but there are periods when services will be down.
> 
> As the second part of the IETF server migration, we will be installing new
> mailman servers over this weekend.  
> 
> We believe we are prepared for this move, but, as with all migrations of this
> size and complexity, there may be some glitches.  If you experience any
> difficulties over this period, or notice anything amiss with the mailing lists,
> then please send email to ietf-action@ietf.org and copy the IAD at iad@ietf.org.
>   In case of an emergency, please call the emergency
> number: +1 301-858-6268.
> 
> Migration Schedule with expected down times:
> 
> Feb 18:
>    a. Mailing List Services (www1.ietf.org)
>       - Down Time: 7:00 AM ET.
>       - Up Time: It could be as early as 03:00 PM ET. and as late as 
>                  7:00 AM ET., the next day depending on DNS propagation  
>                  latency. See note below.
>    b. Request Tracker Services (ticket.ietf.org)
>       - Down Time: 7:00 AM ET.
>       - Up Time: It could be as early as 03:00 PM ET. and as late as 
>                  7:00 AM ET., the next day depending on DNS propagation  
>                  latency. See note below.
> 
>       Please note that the down time for the RT system affects only those 
>       people who have accounts with the site.  One will stil be able to 
>       send a message to the Secretariat (ietf-action@ietf.org, etc).  
>       Messages will be hold up in the IETF mail server and released when 
>       the RT system is back in service.
> 
> If it becomes necessary to change these plans, then we will send a second
> message to the list with the updated schedule. 
> 
> Thanks.
> 
> IETF Secretariat.
> 
> Note: Most of the name servers will be updated and bring the services from our
> new servers within couple of hours after migrations.  However, depends on their
> network environment, some names servers may be updated a little later than
> others.
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce





From disman-bounces@ietf.org Sun Feb 19 19:59:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1-ext.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FAzOf-0000VB-TU; Sun, 19 Feb 2006 19:59:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FAzOe-0000Uz-J7
	for disman@ietf.org; Sun, 19 Feb 2006 19:59:24 -0500
Received: from kyoto.netlab.nec.de ([195.37.70.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FAzOe-00034S-4M
	for disman@ietf.org; Sun, 19 Feb 2006 19:59:24 -0500
Received: from [192.168.1.128] (HSI-KBW-085-216-002-068.hsi.kabelbw.de
	[85.216.2.68])
	by kyoto.netlab.nec.de (Postfix) with ESMTP id AAC371BAC4D;
	Mon, 20 Feb 2006 02:00:56 +0100 (CET)
Date: Mon, 20 Feb 2006 01:59:23 +0100
From: Juergen Quittek <quittek@netlab.nec.de>
To: j.schoenwaelder@iu-bremen.de, "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
	Juergen Quittek <quittek@ccrle.nec.de>
Message-ID: <CF33A0568F296127BCC81579@[192.168.1.128]>
In-Reply-To: <20060217080917.GA10233@boskop.local>
References: <7D5D48D2CAA3D84C813F5B154F43B155094D9AF1@nl0006exch001u.nl.lucent.com>
	<20060217080917.GA10233@boskop.local>
X-Mailer: Mulberry/3.1.6 (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: 10d3e4e3c32e363f129e380e644649be
Cc: disman@ietf.org
Subject: [Disman] Re: MIB Doctor review: publish
	draft-ietf-disman-remops-mib-v2-0 6.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>
Errors-To: disman-bounces@ietf.org

Hi Juergen,

Thanks for the review.
I posted a new version incorporating the changes described inline below.

--On 2/17/06 9:09 AM +0100 Juergen Schoenwaelder wrote:

> On Fri, Feb 10, 2006 at 12:28:11AM +0100, Wijnen, Bert (Bert) wrote:
>
>> So did you check rev 7 to make sure you are happy.
>> I am assuming so, but would appreciate an ack.
>>
>> In your MIB doctor review, did you also do a smidiff
>> with the RFC versions, and are we OK on those?
>
> Bert,
>
> I did an smidiff and I actually wrote a compliance statement output
> driver for smidump to be able to check the differences between
> compliance statements.
>
> I just took a quick look at the latest version (which is -08 I think)
> and I found a few more nits that you might want to get fixed if still
> possible and JQ can turn things around things quickly:
>
> 1) In the pingMIB MODULE-IDENTITY, it says twice:
>
>                 - changed DEFVAL of object pingCtlDescr from
>                   DEFVAL { '00'H } to DEFVAL { ''H }
>
>    I think saying this once should be good enough.

Agreed and fixed.

> 2) pingCompliancy -> pingCompliance

Fixed.

> 3) pingFullCompliancy -> pingFullCompliance

Fixed.

> 4) traceRoutecompliancy -> traceRouteCompliance

Fixed.

> 5) traceRouteFullCompliancy -> traceRouteFullCompliance

Fixed.

> 6) I would have liked to see text in the deprecated compliance that
>    says why these were deprecated and what implementors should do
>    about it (since comparing compliance statements is really a tedious
>    task). I know this is mentioned in section 3.4 but you know that
>    extracted MIB modules often have a life of their own.
>
>     pingCompliance MODULE-COMPLIANCE
>        STATUS  deprecated
>        DESCRIPTION
>                "The compliance statement for the DISMAN-PING-MIB. This
> 		compliance statement has been deprecated because the
> 		group pingGroup and the pingTimeStampGroup have been
> 		split and deprecated. The pingFullCompliance statement
> 		is semantically identical to the deprecated pingCompliance
> 		statement".

Done.

>     traceRouteCompliance MODULE-COMPLIANCE
>        STATUS  deprecated
>        DESCRIPTION
>                "The compliance statement for the DISMAN-TRACEROUTE-MIB.
> 		This compliance statement has been deprecated because
> 		the traceRouteGroup and the traceRouteTimeStampGroup
> 		have been split and deprecated. The traceRouteFullCompliance
> 		is semantically identical to the deprecated
> 		traceRouteCompliance statement."

Done.

Thank you for the constructive comments.

    Juergen Q.
-- 
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





From disman-bounces@ietf.org Mon Feb 20 02:50:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FB5oa-00086K-Hr; Mon, 20 Feb 2006 02:50:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FB5oZ-00086F-7U
	for disman@ietf.org; Mon, 20 Feb 2006 02:50:35 -0500
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FB5oY-0005jp-Ug
	for disman@ietf.org; Mon, 20 Feb 2006 02:50:35 -0500
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32])
	by hermes.iu-bremen.de (Postfix) with ESMTP id 1B2CE4D36C;
	Mon, 20 Feb 2006 08:50:34 +0100 (CET)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by localhost (demetrius [212.201.44.32]) (amavisd-new,
	port 10024) with ESMTP
	id 09128-09; Mon, 20 Feb 2006 08:50:32 +0100 (CET)
Received: from boskop.local (unknown [10.222.1.1])
	by hermes.iu-bremen.de (Postfix) with ESMTP id 82C2E4D159;
	Mon, 20 Feb 2006 08:50:32 +0100 (CET)
Received: by boskop.local (Postfix, from userid 501)
	id 38D516024E1; Mon, 20 Feb 2006 08:50:33 +0100 (CET)
Date: Mon, 20 Feb 2006 08:50:32 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Juergen Quittek <quittek@netlab.nec.de>
Message-ID: <20060220075032.GB27248@boskop.local>
Mail-Followup-To: Juergen Quittek <quittek@netlab.nec.de>,
	"Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
	Juergen Quittek <quittek@ccrle.nec.de>, disman@ietf.org
References: <7D5D48D2CAA3D84C813F5B154F43B155094D9AF1@nl0006exch001u.nl.lucent.com>
	<20060217080917.GA10233@boskop.local>
	<CF33A0568F296127BCC81579@[192.168.1.128]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CF33A0568F296127BCC81579@[192.168.1.128]>
User-Agent: Mutt/1.5.10i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: "Wijnen, Bert \(Bert\)" <bwijnen@lucent.com>, disman@ietf.org,
	Juergen Quittek <quittek@ccrle.nec.de>
Subject: [Disman] Re: MIB Doctor review: publish
	draft-ietf-disman-remops-mib-v2-0 6.txt
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
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>
Errors-To: disman-bounces@ietf.org

On Mon, Feb 20, 2006 at 01:59:23AM +0100, Juergen Quittek wrote:

> Thanks for the review.
> I posted a new version incorporating the changes described inline below.

Thanks. I think we are now done with this document and it is back in
Bert's hands.

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany




From disman-bounces@ietf.org Wed Feb 22 22:40:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FC7Kv-00082p-FW; Wed, 22 Feb 2006 22:40:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FC0vz-000517-03; Wed, 22 Feb 2006 15:50:03 -0500
Received: from willow.neustar.com ([209.173.53.84])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FC0vy-00070b-Ag; Wed, 22 Feb 2006 15:50:02 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k1MKo29W009081
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 22 Feb 2006 20:50:02 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FC0vx-0004QZ-Vt; Wed, 22 Feb 2006 15:50:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1FC0vx-0004QZ-Vt@stiedprstage1.ietf.org>
Date: Wed, 22 Feb 2006 15:50:01 -0500
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
X-Mailman-Approved-At: Wed, 22 Feb 2006 22:40:10 -0500
Cc: disman@ietf.org
Subject: [Disman] I-D ACTION:draft-ietf-disman-remops-mib-v2-09.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>
Errors-To: disman-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Distributed Management Working Group of the IETF.

	Title		: Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations
	Author(s)	: J. Quittek, K. White
	Filename	: draft-ietf-disman-remops-mib-v2-09.txt
	Pages		: 97
	Date		: 2006-2-22
	
This memo defines Management Information Bases (MIBs) for performing
ping, traceroute and lookup operations at a host.  When managing a
network it is useful to be able to initiate and retrieve the results
of ping or traceroute operations when performed at a remote host.  A
Lookup capability is defined in order to enable resolution of either
an IP address to an DNS name or a DNS name to an IP address at a
remote host.

Currently, there are several enterprise-specific MIBs for performing
remote ping or traceroute operations.  The purpose of this memo is to
define a standards-based solution to enable interoperability.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-09.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-disman-remops-mib-v2-09.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-disman-remops-mib-v2-09.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2006-2-22125859.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-disman-remops-mib-v2-09.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-disman-remops-mib-v2-09.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-2-22125859.I-D@ietf.org>


--OtherAccess--

--NextPart--





From disman-bounces@ietf.org Thu Feb 23 15:21:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FCMxe-0007za-Em; Thu, 23 Feb 2006 15:21:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FCMxd-0007zK-Fq; Thu, 23 Feb 2006 15:21:13 -0500
Received: from oak.neustar.com ([209.173.53.70])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FCMxd-00032f-8X; Thu, 23 Feb 2006 15:21:13 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k1NKLDBX011788
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 23 Feb 2006 20:21:13 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FCMxd-0001dO-0y; Thu, 23 Feb 2006 15:21:13 -0500
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1FCMxd-0001dO-0y@stiedprstage1.ietf.org>
Date: Thu, 23 Feb 2006 15:21:13 -0500
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: disman@ietf.org
Subject: [Disman] 
 Last Call: 'Definitions of Managed Objects for Remote Ping, 
 Traceroute, and Lookup Operations' to Proposed Standard 
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org
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>
Errors-To: disman-bounces@ietf.org

The IESG has received a request from the Distributed Management WG to consider the following document:

- 'Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup 
   Operations '
   <draft-ietf-disman-remops-mib-v2-09.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2006-03-09.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-09.txt





From disman-bounces@ietf.org Thu Feb 23 22:42:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FCTqO-0006zN-MY; Thu, 23 Feb 2006 22:42:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FCQXT-0004kS-FE
	for disman@ietf.org; Thu, 23 Feb 2006 19:10:27 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCQXT-00043p-4P
	for disman@ietf.org; Thu, 23 Feb 2006 19:10:27 -0500
Received: from sj-core-4.cisco.com ([171.68.223.138])
	by sj-iport-5.cisco.com with ESMTP; 23 Feb 2006 16:10:27 -0800
X-IronPort-AV: i="4.02,142,1139212800"; 
	d="scan'208"; a="257484840:sNHT34354592"
Received: from vtg-um-e2k7.sj21ad.cisco.com (vtg-um-e2k7.cisco.com
	[171.70.93.79])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k1O0APXf014730;
	Thu, 23 Feb 2006 16:10:26 -0800 (PST)
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: Thu, 23 Feb 2006 16:10:24 -0800
Message-ID: <6CF1217966D48442AD2A788E8DE45E648EB76C@vtg-um-e2k7.sj21ad.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D ACTION:draft-ietf-disman-remops-mib-v2-09.txt 
thread-index: AcY4DIOROSqma3hYTnKKfTijLP+31gAdnk3gAAvHCMAACOcRIA==
From: "Kumar, Rajesh" <rkumar@cisco.com>
To: <wkenneth@us.ibm.com>, <quittek@netlab.nec.de>,
	"Randy Presuhn" <randy_presuhn@mindspring.com>,
	"Bert Wijnen" <bwijnen@lucent.com>,
	"David Kessens" <david.kessens@nokia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
X-Mailman-Approved-At: Thu, 23 Feb 2006 22:42:11 -0500
Cc: "Dinesh Goyal \(digoyal\)" <digoyal@cisco.com>,
	"Azita Kia \(akia\)" <akia@cisco.com>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>, "Liu ,
	Jenny" <jzliu@cisco.com>, Jon Heaton <jheaton@cisco.com>,
	"Biskner, Robert" <rbiskner@cisco.com>, "Lantz,
	Keith" <klantz@cisco.com>, Jim Whitten <jiwhitte@cisco.com>,
	"Wing, Dan" <dwing@cisco.com>, "Mostafa, Mohamed" <mmostafa@cisco.com>,
	Sachin Saswade <sachins@cisco.com>, disman@ietf.org,
	"Randy Ethier \(rethier\)" <rethier@cisco.com>
Subject: [Disman] RE: I-D ACTION:draft-ietf-disman-remops-mib-v2-09.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>
Errors-To: disman-bounces@ietf.org

Kenneth and Juergen,

Congratulatons on your internet draft on reporting ping/traceroute
results being in last call.

Basically, it is a good draft. I  do have one concern. When you do a UDP
or ICMP traceroute from any node, yoy typically get three delay
approximations for each stimulus-response with increasing TTLs. Granted
that this is an approximation, I did not see a mechanism for reporting
this inforation in your internet draft. Maybe I missed it and it is
there?

Best regards,

Rajesh Kumar


> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Wednesday, February 22, 2006 3:50 PM
> To: i-d-announce@ietf.org
> Cc: disman@ietf.org
> Subject: I-D ACTION:draft-ietf-disman-remops-mib-v2-09.txt=20
>=20
> A New Internet-Draft is available from the on-line=20
> Internet-Drafts directories.
> This draft is a work item of the Distributed Management=20
> Working Group of the IETF.
>=20
> 	Title		: Definitions of Managed Objects for Remote
> Ping, Traceroute, and Lookup Operations
> 	Author(s)	: J. Quittek, K. White
> 	Filename	: draft-ietf-disman-remops-mib-v2-09.txt
> 	Pages		: 97
> 	Date		: 2006-2-22
> =09
> This memo defines Management Information Bases (MIBs) for=20
> performing ping, traceroute and lookup operations at a host. =20
> When managing a network it is useful to be able to initiate=20
> and retrieve the results of ping or traceroute operations=20
> when performed at a remote host.  A Lookup capability is=20
> defined in order to enable resolution of either an IP address=20
> to an DNS name or a DNS name to an IP address at a remote host.
>=20
> Currently, there are several enterprise-specific MIBs for=20
> performing remote ping or traceroute operations.  The purpose=20
> of this memo is to define a standards-based solution to=20
> enable interoperability.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-m
> ib-v2-09.t
> xt
>=20
> To remove yourself from the I-D Announcement list, send a=20
> message to i-d-announce-request@ietf.org with the word=20
> unsubscribe in the body of the message. =20
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>=20
>=20
> Internet-Drafts are also available by anonymous FTP. Login=20
> with the username "anonymous" and a password of your e-mail=20
> address. After logging in, type "cd internet-drafts" and then
> 	"get draft-ietf-disman-remops-mib-v2-09.txt".
>=20
> A list of Internet-Drafts directories can be found in=20
> http://www.ietf.org/shadow.html or=20
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=20
>=20
> Internet-Drafts can also be obtained by e-mail.
>=20
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-disman-remops-mib-v2-09.txt".
> =09
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant=20
> mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 	=09
> 	=09
> Below is the data which will enable a MIME compliant mail=20
> reader implementation to automatically retrieve the ASCII=20
> version of the Internet-Draft.
>=20




From disman-bounces@ietf.org Fri Feb 24 22:08:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FCpmx-0002Ad-WC; Fri, 24 Feb 2006 22:08:08 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FCfSo-0004ru-JR
	for disman@ietf.org; Fri, 24 Feb 2006 11:06:38 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCfSo-0008DK-0D
	for disman@ietf.org; Fri, 24 Feb 2006 11:06:38 -0500
Received: from sj-core-3.cisco.com ([171.68.223.137])
	by sj-iport-4.cisco.com with ESMTP; 24 Feb 2006 08:06:39 -0800
X-IronPort-AV: i="4.02,144,1139212800"; 
	d="scan'208"; a="1779446526:sNHT36091592"
Received: from vtg-um-e2k7.sj21ad.cisco.com (vtg-um-e2k7.cisco.com
	[171.70.93.79])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id k1OG6auh016966;
	Fri, 24 Feb 2006 08:06:36 -0800 (PST)
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: Fri, 24 Feb 2006 08:06:35 -0800
Message-ID: <6CF1217966D48442AD2A788E8DE45E648EB801@vtg-um-e2k7.sj21ad.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D ACTION:draft-ietf-disman-remops-mib-v2-09.txt 
thread-index: AcY5W9hVI+cptkf7T5Cja9lF7Zg7IwAAE+5Q
From: "Kumar, Rajesh" <rkumar@cisco.com>
To: "Juergen Quittek" <quittek@netlab.nec.de>, <wkenneth@us.ibm.com>,
	"Randy Presuhn" <randy_presuhn@mindspring.com>,
	"Bert Wijnen" <bwijnen@lucent.com>,
	"David Kessens" <david.kessens@nokia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21be852dc93f0971708678c18d38c096
X-Mailman-Approved-At: Fri, 24 Feb 2006 22:08:07 -0500
Cc: "Dinesh Goyal \(digoyal\)" <digoyal@cisco.com>,
	"Azita Kia \(akia\)" <akia@cisco.com>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>, "Liu ,
	Jenny" <jzliu@cisco.com>, Jon Heaton <jheaton@cisco.com>,
	"Biskner, Robert" <rbiskner@cisco.com>, "Lantz,
	Keith" <klantz@cisco.com>, Jim Whitten <jiwhitte@cisco.com>,
	"Wing, Dan" <dwing@cisco.com>, "Mostafa, Mohamed" <mmostafa@cisco.com>,
	Sachin Saswade <sachins@cisco.com>, disman@ietf.org,
	"Randy Ethier \(rethier\)" <rethier@cisco.com>
Subject: [Disman] RE: I-D ACTION:draft-ietf-disman-remops-mib-v2-09.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>
Errors-To: disman-bounces@ietf.org

Dear Juergen,
It does answer my question. You might want to add this clarifying text
in the document.

Thanks for the quick response.

Rajesh=20

> -----Original Message-----
> From: Juergen Quittek [mailto:quittek@netlab.nec.de]=20
> Sent: Friday, February 24, 2006 8:03 AM
> To: Kumar, Rajesh; wkenneth@us.ibm.com; Randy Presuhn; Bert=20
> Wijnen; David Kessens
> Cc: Jon Heaton; Jim Whitten; Azita Kia (akia); Biskner,=20
> Robert; Mostafa, Mohamed; Liu , Jenny; Michael Hammer=20
> (mhammer); Randy Ethier (rethier); Dinesh Goyal (digoyal);=20
> Sachin Saswade; Wing, Dan; Lantz, Keith; disman@ietf.org
> Subject: RE: I-D ACTION:draft-ietf-disman-remops-mib-v2-09.txt=20
>=20
> Dear Rajesh,
>=20
> Thanks for the comment.
>=20
> --On 2/23/06 4:10 PM -0800 Kumar, Rajesh wrote:
> >
> > Kenneth and Juergen,
> >
> > Congratulatons on your internet draft on reporting ping/traceroute=20
> > results being in last call.
> >
> > Basically, it is a good draft. I  do have one concern. When=20
> you do a=20
> > UDP or ICMP traceroute from any node, yoy typically get three delay=20
> > approximations for each stimulus-response with increasing TTLs.=20
> > Granted that this is an approximation, I did not see a=20
> mechanism for=20
> > reporting this inforation in your internet draft. Maybe I missed it=20
> > and it is there?
>=20
> It is indeed important to store and make available all these=20
> measured values.
>=20
> The DISMAN-TRACEROUTE-MIB contains the information you are=20
> looking for in the traceRouteProbeHistoryTable.
>=20
> For clarifying terminology: In the draft a traceroute test=20
> includes sending several probes with different hopCount (TTL) values.
>=20
> Table traceRouteProbeHistoryTable contains one entry per probe.
> Entries are indexed (among other indices) by
>              traceRouteProbeHistoryHopIndex,
>              traceRouteProbeHistoryProbeIndex.
>=20
> Now, if you configure the MIB module to perform three=20
> traceroute probes per hop that deliver three delay=20
> approximations, then this table will contain three entries=20
> with the same value for traceRouteProbeHistoryHopIndex but=20
> with different values for traceRouteProbeHistoryProbeIndex. =20
> Each of these entries will contain one of the delay approximations.
>=20
> Does this answers your question?
>=20
> Thanks,
>=20
>     Juergen
> --=20
> Juergen Quittek        quittek@netlab.nec.de       Tel: +49=20
> 6221 90511-15
> NEC Europe Ltd.,       Network Laboratories        Fax: +49=20
> 6221 90511-55
> Kurfuersten-Anlage 36, 69115 Heidelberg, Germany  =20
> http://www.netlab.nec.de
>=20
> >
> > Best regards,
> >
> > Rajesh Kumar
> >
> >
> >> -----Original Message-----
> >> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> >> Sent: Wednesday, February 22, 2006 3:50 PM
> >> To: i-d-announce@ietf.org
> >> Cc: disman@ietf.org
> >> Subject: I-D ACTION:draft-ietf-disman-remops-mib-v2-09.txt
> >>
> >> A New Internet-Draft is available from the on-line Internet-Drafts=20
> >> directories.
> >> This draft is a work item of the Distributed Management=20
> Working Group=20
> >> of the IETF.
> >>
> >> 	Title		: Definitions of Managed Objects for Remote
> >> Ping, Traceroute, and Lookup Operations
> >> 	Author(s)	: J. Quittek, K. White
> >> 	Filename	: draft-ietf-disman-remops-mib-v2-09.txt
> >> 	Pages		: 97
> >> 	Date		: 2006-2-22
> >> =09
> >> This memo defines Management Information Bases (MIBs) for=20
> performing=20
> >> ping, traceroute and lookup operations at a host.
> >> When managing a network it is useful to be able to initiate and=20
> >> retrieve the results of ping or traceroute operations when=20
> performed=20
> >> at a remote host.  A Lookup capability is defined in order=20
> to enable=20
> >> resolution of either an IP address to an DNS name or a DNS=20
> name to an=20
> >> IP address at a remote host.
> >>
> >> Currently, there are several enterprise-specific MIBs for=20
> performing=20
> >> remote ping or traceroute operations.  The purpose of this=20
> memo is to=20
> >> define a standards-based solution to enable interoperability.
> >>
> >> A URL for this Internet-Draft is:
> >> http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-m
> >> ib-v2-09.t
> >> xt
> >>
> >> To remove yourself from the I-D Announcement list, send a=20
> message to=20
> >> i-d-announce-request@ietf.org with the word unsubscribe in=20
> the body=20
> >> of the message.
> >> You can also visit=20
> >> https://www1.ietf.org/mailman/listinfo/I-D-announce
> >> to change your subscription settings.
> >>
> >>
> >> Internet-Drafts are also available by anonymous FTP. Login=20
> with the=20
> >> username "anonymous" and a password of your e-mail address. After=20
> >> logging in, type "cd internet-drafts" and then
> >> 	"get draft-ietf-disman-remops-mib-v2-09.txt".
> >>
> >> A list of Internet-Drafts directories can be found in=20
> >> http://www.ietf.org/shadow.html or=20
> >> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >>
> >>
> >> Internet-Drafts can also be obtained by e-mail.
> >>
> >> Send a message to:
> >> 	mailserv@ietf.org.
> >> In the body type:
> >> 	"FILE /internet-drafts/draft-ietf-disman-remops-mib-v2-09.txt".
> >> =09
> >> NOTE:	The mail server at ietf.org can return the document in
> >> 	MIME-encoded form by using the "mpack" utility.  To use this
> >> 	feature, insert the command "ENCODING mime" before the "FILE"
> >> 	command.  To decode the response(s), you will need "munpack" or
> >> 	a MIME-compliant mail reader.  Different MIME-compliant=20
> mail readers
> >> 	exhibit different behavior, especially when dealing with
> >> 	"multipart" MIME messages (i.e. documents which have been split
> >> 	up into multiple messages), so check your local documentation on
> >> 	how to manipulate these messages.
> >> 	=09
> >> 	=09
> >> Below is the data which will enable a MIME compliant mail reader=20
> >> implementation to automatically retrieve the ASCII version of the=20
> >> Internet-Draft.
> >>
>=20




From disman-bounces@ietf.org Fri Feb 24 22:08:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FCpmx-0002AY-S7; Fri, 24 Feb 2006 22:08:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FCfPi-0002ul-8T
	for disman@ietf.org; Fri, 24 Feb 2006 11:03:26 -0500
Received: from kyoto.netlab.nec.de ([195.37.70.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCfPc-00085Z-L4
	for disman@ietf.org; Fri, 24 Feb 2006 11:03:26 -0500
Received: from [10.1.1.171] (mito.netlab.nec.de [195.37.70.39])
	by kyoto.netlab.nec.de (Postfix) with ESMTP id B62F91BAC4D;
	Fri, 24 Feb 2006 17:04:53 +0100 (CET)
Date: Fri, 24 Feb 2006 17:03:19 +0100
From: Juergen Quittek <quittek@netlab.nec.de>
To: "Kumar, Rajesh" <rkumar@cisco.com>, wkenneth@us.ibm.com,
	Randy Presuhn <randy_presuhn@mindspring.com>,
	Bert Wijnen <bwijnen@lucent.com>, David Kessens <david.kessens@nokia.com>
Message-ID: <5C2FC64EAB7980F0927E8266@[10.1.1.171]>
In-Reply-To: <6CF1217966D48442AD2A788E8DE45E648EB76C@vtg-um-e2k7.sj21ad.cisco.com>
References: <6CF1217966D48442AD2A788E8DE45E648EB76C@vtg-um-e2k7.sj21ad.cisco.com>
X-Mailer: Mulberry/3.1.6 (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: 68ba2b07ef271dba6ee42a93832cfa4c
X-Mailman-Approved-At: Fri, 24 Feb 2006 22:08:07 -0500
Cc: "Dinesh Goyal \(digoyal\)" <digoyal@cisco.com>,
	"Azita Kia \(akia\)" <akia@cisco.com>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>, "Liu ,
	Jenny" <jzliu@cisco.com>, Jon Heaton <jheaton@cisco.com>,
	"Biskner, Robert" <rbiskner@cisco.com>, "Lantz,
	Keith" <klantz@cisco.com>, Jim Whitten <jiwhitte@cisco.com>,
	"Wing, Dan" <dwing@cisco.com>, "Mostafa, Mohamed" <mmostafa@cisco.com>,
	Sachin Saswade <sachins@cisco.com>, disman@ietf.org,
	"Randy Ethier \(rethier\)" <rethier@cisco.com>
Subject: [Disman] RE: I-D ACTION:draft-ietf-disman-remops-mib-v2-09.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>
Errors-To: disman-bounces@ietf.org

Dear Rajesh,

Thanks for the comment.

--On 2/23/06 4:10 PM -0800 Kumar, Rajesh wrote:
>
> Kenneth and Juergen,
>
> Congratulatons on your internet draft on reporting ping/traceroute
> results being in last call.
>
> Basically, it is a good draft. I  do have one concern. When you do a UDP
> or ICMP traceroute from any node, yoy typically get three delay
> approximations for each stimulus-response with increasing TTLs. Granted
> that this is an approximation, I did not see a mechanism for reporting
> this inforation in your internet draft. Maybe I missed it and it is
> there?

It is indeed important to store and make available all these measured
values.

The DISMAN-TRACEROUTE-MIB contains the information you are looking
for in the traceRouteProbeHistoryTable.

For clarifying terminology: In the draft a traceroute test includes
sending several probes with different hopCount (TTL) values.

Table traceRouteProbeHistoryTable contains one entry per probe.
Entries are indexed (among other indices) by
             traceRouteProbeHistoryHopIndex,
             traceRouteProbeHistoryProbeIndex.

Now, if you configure the MIB module to perform three traceroute
probes per hop that deliver three delay approximations, then this
table will contain three entries with the same value for
traceRouteProbeHistoryHopIndex but with different values for
traceRouteProbeHistoryProbeIndex.  Each of these entries will
contain one of the delay approximations.

Does this answers your question?

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

>
> Best regards,
>
> Rajesh Kumar
>
>
>> -----Original Message-----
>> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
>> Sent: Wednesday, February 22, 2006 3:50 PM
>> To: i-d-announce@ietf.org
>> Cc: disman@ietf.org
>> Subject: I-D ACTION:draft-ietf-disman-remops-mib-v2-09.txt
>>
>> A New Internet-Draft is available from the on-line
>> Internet-Drafts directories.
>> This draft is a work item of the Distributed Management
>> Working Group of the IETF.
>>
>> 	Title		: Definitions of Managed Objects for Remote
>> Ping, Traceroute, and Lookup Operations
>> 	Author(s)	: J. Quittek, K. White
>> 	Filename	: draft-ietf-disman-remops-mib-v2-09.txt
>> 	Pages		: 97
>> 	Date		: 2006-2-22
>> 	
>> This memo defines Management Information Bases (MIBs) for
>> performing ping, traceroute and lookup operations at a host.
>> When managing a network it is useful to be able to initiate
>> and retrieve the results of ping or traceroute operations
>> when performed at a remote host.  A Lookup capability is
>> defined in order to enable resolution of either an IP address
>> to an DNS name or a DNS name to an IP address at a remote host.
>>
>> Currently, there are several enterprise-specific MIBs for
>> performing remote ping or traceroute operations.  The purpose
>> of this memo is to define a standards-based solution to
>> enable interoperability.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-m
>> ib-v2-09.t
>> xt
>>
>> To remove yourself from the I-D Announcement list, send a
>> message to i-d-announce-request@ietf.org with the word
>> unsubscribe in the body of the message.
>> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
>> to change your subscription settings.
>>
>>
>> Internet-Drafts are also available by anonymous FTP. Login
>> with the username "anonymous" and a password of your e-mail
>> address. After logging in, type "cd internet-drafts" and then
>> 	"get draft-ietf-disman-remops-mib-v2-09.txt".
>>
>> A list of Internet-Drafts directories can be found in
>> http://www.ietf.org/shadow.html or
>> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>>
>> Internet-Drafts can also be obtained by e-mail.
>>
>> Send a message to:
>> 	mailserv@ietf.org.
>> In the body type:
>> 	"FILE /internet-drafts/draft-ietf-disman-remops-mib-v2-09.txt".
>> 	
>> NOTE:	The mail server at ietf.org can return the document in
>> 	MIME-encoded form by using the "mpack" utility.  To use this
>> 	feature, insert the command "ENCODING mime" before the "FILE"
>> 	command.  To decode the response(s), you will need "munpack" or
>> 	a MIME-compliant mail reader.  Different MIME-compliant
>> mail readers
>> 	exhibit different behavior, especially when dealing with
>> 	"multipart" MIME messages (i.e. documents which have been split
>> 	up into multiple messages), so check your local documentation on
>> 	how to manipulate these messages.
>> 		
>> 		
>> Below is the data which will enable a MIME compliant mail
>> reader implementation to automatically retrieve the ASCII
>> version of the Internet-Draft.
>>






From disman-bounces@ietf.org Tue Feb 28 19:12:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FEExB-0007oV-2t; Tue, 28 Feb 2006 19:12:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FEEcq-0002Eo-4R; Tue, 28 Feb 2006 18:51:29 -0500
Received: from fall-pradero.atl.sa.earthlink.net ([207.69.195.104])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FEEcn-0005qE-0u; Tue, 28 Feb 2006 18:51:26 -0500
Received: from pop-satin.atl.sa.earthlink.net ([207.69.195.63])
	by fall-pradero.atl.sa.earthlink.net with esmtp (Exim 4.34)
	id 1FEEcm-00051n-G2; Tue, 28 Feb 2006 18:51:24 -0500
Received: from h-64-105-34-111.snvacaid.dynamic.covad.net ([64.105.34.111]
	helo=oemcomputer)
	by pop-satin.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1FECAd-0000nu-00; Tue, 28 Feb 2006 16:14:11 -0500
Message-ID: <002601c63cac$313d9a00$6401a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Bill Fenner" <fenner@gmail.com>, <j.schoenwaelder@iu-bremen.de>,
	"Tom.Petch" <sisyphus@dial.pipex.com>, "Bill Strahm" <bill@strahm.net>,
	"iesg" <iesg@ietf.org>, "ietf" <ietf@ietf.org>
References: <tslslq7wau2.fsf@cz.mit.edu><E1FCMxd-0001dO-0y@stiedprstage1.ietf.org><44023E4E.7040800@strahm.net>
	<030b01c63b92$de534160$0601a8c0@pc6><20060227131418.GA5269@boskop.local>
	<ed6d469d0602272248s437302ceu9b28b6bddc6f79b7@mail.gmail.com>
Date: Tue, 28 Feb 2006 13:16:02 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: Disman <disman@ietf.org>
Subject: [Disman] Re: Last Call: 'Definitions of Managed Objects for Remote
	Ping, Traceroute, and Lookup Operations' to Proposed Standard
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>
Errors-To: disman-bounces@ietf.org

Hi -

If the document gives a false impression that the values of
traceRouteHopsHopIndex could be interpreted as hop numbers,
an editorial change to dispel that notion would make sense.
(Likewise, if "consecutive integers starting at one" was the intent, and
is what current implementations actually do, then we should say so.)

I can see how the last two sentences of the last paragraph of
the DESCRIPTION might lead to such a reading.  Does
someone have some replacement text they'd like to propose
to make things clearer?

Randy, disman chair

----- Original Message ----- 
From: "Bill Fenner" <fenner@gmail.com>
To: <j.schoenwaelder@iu-bremen.de>; "Tom.Petch" <sisyphus@dial.pipex.com>; "Bill Strahm" <bill@strahm.net>; "iesg" <iesg@ietf.org>;
"ietf" <ietf@ietf.org>
Sent: Monday, February 27, 2006 10:48 PM
Subject: Re: Last Call: 'Definitions of Managed Objects for Remote Ping,Traceroute, and Lookup Operations' to Proposed Standard


Juergen,

  I assumed, from reading in traceRouteHopsHopIndex about the behavior
when a path changes, that the only safe thing for a manager to do is
to read the hops from the table and render them to the user in order
of increasing traceRouteHopsHopIndex but without necessarily showing
the traceRouteHopsHopIndex to the user -- that it was perfectly
reasonable for hops 1,2,3,4 of a 4-hop path to be numbered 1,8,12,35
(assuming that they started 1,2,3,4 but there were lots of path
changes during the test).

  I think some people are assuming that the intention was that the
values should be 1,2,3,4 (i.e., HopIndex == hop number) and that's why
they're asking for a different definition.  Perhaps the right
direction could be to clarify that there is no connection between the
value of HopIndex and traceroute hop, other than the ordering.

  Bill

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf






