From mailman-bounces@ietf.org Wed Dec 1 08:37:46 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27852 for ; Wed, 1 Dec 2004 08:37:46 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZSbR-0006VW-ME for disman-archive@lists.ietf.org; Wed, 01 Dec 2004 06:24:57 -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: Date: Wed, 01 Dec 2004 05:45:16 -0500 Precedence: bulk X-BeenThere: mailman@lists.ietf.org X-Mailman-Version: 2.1.5 List-Id: Mailman site list 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 Tue Dec 14 17:09:27 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27666 for ; Tue, 14 Dec 2004 17:09:27 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CeKks-0004wK-3i; Tue, 14 Dec 2004 17:02:50 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CeJj4-0000wV-BZ; Tue, 14 Dec 2004 15:56:54 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16759; Tue, 14 Dec 2004 15:56:52 -0500 (EST) Message-Id: <200412142056.PAA16759@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Tue, 14 Dec 2004 15:56:52 -0500 X-Mailman-Approved-At: Tue, 14 Dec 2004 17:02:48 -0500 Cc: disman@ietf.org Subject: [Disman] I-D ACTION:draft-ietf-disman-remops-mib-v2-06.txt X-BeenThere: disman@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Distributed Management List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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-06.txt Pages : 97 Date : 2004-12-14 This memo defines Management Information Bases (MIBs) for performing remote ping, traceroute and lookup operations at a remote 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 resolving of either an IP address to an DNS name or an 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-06.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-06.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-06.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: <2004-12-14151239.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-disman-remops-mib-v2-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-disman-remops-mib-v2-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-12-14151239.I-D@ietf.org> --OtherAccess-- --NextPart-- From disman-bounces@ietf.org Sun Dec 19 10:50:06 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10647 for ; Sun, 19 Dec 2004 10:50: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 1Cg3Hp-0006pR-Ej; Sun, 19 Dec 2004 10:47:57 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cg3Gi-0006bC-6j for disman@megatron.ietf.org; Sun, 19 Dec 2004 10:46:48 -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 KAA10388 for ; Sun, 19 Dec 2004 10:46:45 -0500 (EST) Received: from kyoto.netlab.nec.de ([195.37.70.21]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cg3Pm-00048K-Sd for disman@ietf.org; Sun, 19 Dec 2004 10:56:11 -0500 Received: from dialin-145-254-222-064.arcor-ip.net (dialin-145-254-222-064.arcor-ip.net [145.254.222.64]) by kyoto.netlab.nec.de (Postfix) with ESMTP id 45D791BACA7 for ; Sun, 19 Dec 2004 16:46:13 +0100 (CET) Date: Sun, 19 Dec 2004 16:46:14 +0100 From: Juergen Quittek To: disman@ietf.org Message-ID: <2147483647.1103474774@dialin-145-254-222-064.arcor-ip.net> In-Reply-To: <200412142056.PAA16759@ietf.org> References: <200412142056.PAA16759@ietf.org> 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.2 (/) X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955 Content-Transfer-Encoding: 7bit Subject: [Disman] Re: I-D ACTION:draft-ietf-disman-remops-mib-v2-06.txt X-BeenThere: disman@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Distributed Management List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: disman-bounces@ietf.org Errors-To: disman-bounces@ietf.org Content-Transfer-Encoding: 7bit Dear all, This version contains just a few minor fixes based on comments from Randy. There is only one modification that I would like to mention explicitly. Please find it described at the end of this message. 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 14.12.2004 15:56 h -0500 Internet-Drafts@ietf.org wrote: > 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-06.txt > Pages : 97 > Date : 2004-12-14 > > This memo defines Management Information Bases (MIBs) for performing > remote ping, traceroute and lookup operations at a remote 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 > resolving of either an IP address to an DNS name or an 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-06.txt ======================================= changes from version -05 to version -06 ======================================= ======================================================================== 33. Slighly ambiguous description of pingCtlMaxRows, traceRouteCtlMaxRows ======================================================================== Problem Description: ------------------------------------------------------------------------ The description of the semantics of objects pingCtlMaxRows and traceRouteCtlMaxRows is slightly ambiguous. The respective semantics are described in Sections 3.1.4 and 3.2.4, in the DESCRIPTION clauses of the objects and in the DESCRIPTION classes of the respective history tables. Some phrases are not clear about whether the MaxRows value applies to all rows in the respective table or only to the number of rows corresponding to the entry containing the MaxRows value. ======================================================================== Suggested solution: ------------------------------------------------------------------------ Clarify the descriptions. ======================================================================== Status: solution committed ======================================================================== From disman-bounces@ietf.org Tue Dec 21 15:00:27 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13482 for ; Tue, 21 Dec 2004 15:00:27 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cgq95-0004Eq-Ua; Tue, 21 Dec 2004 14:58:11 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cgq3p-0002YB-Da for disman@megatron.ietf.org; Tue, 21 Dec 2004 14:52:45 -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 OAA11555; Tue, 21 Dec 2004 14:52:43 -0500 (EST) Received: from pop-a065c28.pas.sa.earthlink.net ([207.217.121.205]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgqDL-0005NJ-NS; Tue, 21 Dec 2004 15:02:36 -0500 Received: from h-69-3-25-136.snvacaid.dynamic.covad.net ([69.3.25.136] helo=oemcomputer) by pop-a065c28.pas.sa.earthlink.net with smtp (Exim 3.33 #1) id 1Cgq3g-0003Ze-00; Tue, 21 Dec 2004 11:52:36 -0800 Message-ID: <007601c4e796$b0383200$7f1afea9@oemcomputer> From: "Randy Presuhn" To: "Wijnen, Bert \(Bert\)" References: <7D5D48D2CAA3D84C813F5B154F43B1550604E7D1@nl0006exch001u.nl.lucent.com> <2147483647.1103654673@[10.1.1.171]> Date: Tue, 21 Dec 2004 11:53:05 -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: 5011df3e2a27abcc044eaa15befcaa87 Cc: Disman , iesg-secretary@ietf.org Subject: [Disman] Request to publish draft-ietf-disman-remops-mib-v2-06.txt X-BeenThere: disman@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Distributed Management List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: disman-bounces@ietf.org Errors-To: disman-bounces@ietf.org Hi Bert - Yes, as disman WG chair I'm requesting that you take http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-06.txt to the IESG for consideration as PROPOSED STANDARD. This would obsolete RFC 2925. It went through an extended WG last call period, and no issues remain to be resolved. The most significant change is the additional conformance material for the ping capability, added to meet the needs of the ipcdn working group. 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 > From: "Juergen Quittek" > To: "Wijnen, Bert (Bert)" > Cc: "Randy Presuhn" > Sent: Tuesday, December 21, 2004 9:44 AM > Subject: RE: remaining remops MIBs issue > > Bert, > > Thanks a lot! > > I will make a note on the nit and make sure that it will be fixed latest > during the 48 hours call. > > Randy, can we now go on with the I-D and pass it to Bert for AD > and IESG review? > > Thanks, > > Juergen > > > --On 21.12.2004 16:22 Uhr +0100 Wijnen, Bert (Bert) wrote: > > > I think that your security considerations section > > is fine. I can't speak for the security ADs themselves, > > but I see no problem. > > > > One nit: > > insecure environments it is RECOMMENDED that the MIBs defined within > > this memo not be supported. > > > > s/MIBs/MIB modules/ > > > > But it is really a nit. > > > > Bert > > > > > > > >> -----Original Message----- > >> From: Juergen Quittek [mailto:quittek@netlab.nec.de] > >> Sent: Sunday, December 19, 2004 16:55 > >> To: bwijnen@lucent.com > >> Cc: Randy Presuhn > >> Subject: remaining remops MIBs issue > >> > >> > >> Hi Bert, > >> > >> There is one remaining issue concerning the remops MIB modules. > >> The Section on security considerations does not exactly match > >> the boilerplate. > >> > >> The boilerplate requests each writeable object to be discussed > >> individually concerning its security threats. However, the > >> remops MIB modules are full of writeable objects and I think > >> the Security Considerations are much better to read, if the > >> section is structured per threat rather than per object. > >> > >> Could you please check if you share this view and if this > >> 'violation' of the guidelines for MIB modules is acceptable > >> in case of this document. Please find it at > >> >> mib-v2-06.txt>. > >> > >> 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 > > > > From disman-bounces@ietf.org Fri Dec 24 10:33:16 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23161 for ; Fri, 24 Dec 2004 10:33:16 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ChrPJ-0002MQ-6C; Fri, 24 Dec 2004 10:31:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ChrLM-0001oR-Rz for disman@megatron.ietf.org; Fri, 24 Dec 2004 10:27:05 -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 KAA22834; Fri, 24 Dec 2004 10:27:02 -0500 (EST) Received: from mito.netlab.nec.de ([195.37.70.39] helo=venus.office) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ChrVT-0004vD-5z; Fri, 24 Dec 2004 10:37:31 -0500 Received: by venus.office (Postfix on SuSE Linux eMail Server 3.0, from userid 30) id 4BEAC1B2A10; Fri, 24 Dec 2004 16:26:30 +0100 (CET) X-Accept-Language: de, en X-Priority: 3 (Normal) X-Mailer: SKYRiXgreen_3.1 NGMime_4.2.45 references: <7D5D48D2CAA3D84C813F5B154F43B1550604E7D1@nl0006exch001u.nl.lucent.com><2147483647.1103654673@[10.1.1.171]> <007601c4e796$b0383200$7f1afea9@oemcomputer> From: "Juergen Quittek" MIME-Version: 1.0 subject: Re: [Disman] Request to publish draft-ietf-disman-remops-mib-v2-06.txt To: "Randy Presuhn" content-type: text/plain; charset="iso-8859-1" date: Fri, 24 Dec 2004 16:26:30 +0100 Message-Id: <20041224152630.4BEAC1B2A10@venus.office> X-Spam-Score: 0.0 (/) X-Scan-Signature: 36fb765c89ed47dab364ab702a78e8fd Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id KAA22834 Cc: "Wijnen, Bert \(Bert\)" , Disman , iesg-secretary@ietf.org X-BeenThere: disman@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Distributed Management List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: disman-bounces@ietf.org Errors-To: disman-bounces@ietf.org Content-Transfer-Encoding: quoted-printable Bert, It might be helpful to you to check the differences between RFC 2925=20 and the current draft version -06. Please find the complete change log at ftp://ftp.netlab.nec.de/pub/internet-drafts/changes-rfc2925-06.txt Merry Christmas, Juergen > Hi Bert - >=20 > Yes, as disman WG chair I'm requesting that you take > http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-06.= txt > to the IESG for consideration as PROPOSED STANDARD. > This would obsolete RFC 2925. It went through an extended > WG last call period, and no issues remain to be resolved. > The most significant change is the additional conformance material > for the ping capability, added to meet the needs of the ipcdn > working group. >=20 > 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. >=20 > Randy >=20 > > From: "Juergen Quittek" > > To: "Wijnen, Bert (Bert)" > > Cc: "Randy Presuhn" > > Sent: Tuesday, December 21, 2004 9:44 AM > > Subject: RE: remaining remops MIBs issue > > >=20 > > Bert, > > > > Thanks a lot! > > > > I will make a note on the nit and make sure that it will be fixed lat= est > > during the 48 hours call. > > > > Randy, can we now go on with the I-D and pass it to Bert for AD > > and IESG review? > > > > Thanks, > > > > Juergen > > > > > > --On 21.12.2004 16:22 Uhr +0100 Wijnen, Bert (Bert) wrote: > > > > > I think that your security considerations section > > > is fine. I can't speak for the security ADs themselves, > > > but I see no problem. > > > > > > One nit: > > > insecure environments it is RECOMMENDED that the MIBs defined with= in > > > this memo not be supported. > > > > > > s/MIBs/MIB modules/ > > > > > > But it is really a nit. > > > > > > Bert > > > > > > > > > > > >> -----Original Message----- > > >> From: Juergen Quittek [mailto:quittek@netlab.nec.de] > > >> Sent: Sunday, December 19, 2004 16:55 > > >> To: bwijnen@lucent.com > > >> Cc: Randy Presuhn > > >> Subject: remaining remops MIBs issue > > >> > > >> > > >> Hi Bert, > > >> > > >> There is one remaining issue concerning the remops MIB modules. > > >> The Section on security considerations does not exactly match > > >> the boilerplate. > > >> > > >> The boilerplate requests each writeable object to be discussed > > >> individually concerning its security threats. However, the > > >> remops MIB modules are full of writeable objects and I think > > >> the Security Considerations are much better to read, if the > > >> section is structured per threat rather than per object. > > >> > > >> Could you please check if you share this view and if this > > >> 'violation' of the guidelines for MIB modules is acceptable > > >> in case of this document. Please find it at > > >> > >> mib-v2-06.txt>. > > >> > > >> 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 > > > > > > > > >=20 >=20 >=20 >=20 --=20 =84=08 =10