Re: I-D ACTION:draft-ietf-disman-remops-mib-v2-05.txt

Dear all,

This version -05 differs from version -04 only in the conformance
sections of the DISMAN-PING-MIB and the DISMAN-TRACEROUTE-MIB.

Deprecated compliance statements and object groups were added
to both conformance sections.

As discussed on this list before, it was wrong to delete the
old compliance statements and object groups from RFC 2925 that
are not in use anymore.  They are missing in version -04.
Now, in version -05 they appear again but with status 'deprecated'.

The deprecated compliance statements are
  - pingCompliance,
  - traceRouteCompliance.

The deprecated object groups are
  - pingGroup,
  - pingTimeStampGroup,
  - traceRouteGroup,
  - traceRouteTimeStampGroup.

Thanks,

    Juergen
-- 
Juergen Quittek        [email protected]       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 21.10.2004 15:33 h -0400 [email protected] 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-05.txt
> 	Pages		: 96
> 	Date		: 2004-10-21
> 	
> 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-05.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> [email protected] 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-05.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:
> 	[email protected].
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-disman-remops-mib-v2-05.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.