From owner-snmpconf@seymour39.snmp.com Thu Apr 1 11:26:42 2004 Received: from seymour39.snmp.com (seymour39.snmp.com [192.147.142.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19458 for ; Thu, 1 Apr 2004 11:26:42 -0500 (EST) Received: (from majordomo@localhost) by seymour39.snmp.com (8.9.3p2-20030922/m.030206) id LAA13074 for snmpconf-outgoing; Thu, 1 Apr 2004 11:20:21 -0500 (EST) Message-Id: <200404011553.KAA08555@seymour39.snmp.com> To: snmpconf@snmp.com Subject: snmpconf quarterly list instructions mailing Date: Thu, 01 Apr 2004 10:53:24 -0500 From: Steve Moulton Sender: owner-snmpconf@snmp.com Precedence: bulk Reply-To: snmpconf@snmp.com The snmpconf list is for discussing the business of the Configuration Management using SNMP (snmpconf) working group of the IETF. This working group is an open forum for raising and discussing issues related to network device configuration management and SNMP. To remove yourself from the snmpconf discussion list, send a message to snmpconf-request@majordomo.snmp.com containing just the word unsubscribe in the message body (not in the subject). If you have subscribed at an address other than your email from address, send the message unsubscribe address-to-unsubscribe. A http archive is available at http://www.snmp.com/snmpconf/mailing-list/index.html Please send any questions or comments about the management of this list to owner-snmpconf@majordomo.snmp.com. *************************************************************************** Note Well All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to * the IETF plenary session, * any IETF working group or portion thereof, * the IESG, or any member thereof on behalf of the IESG, * the IAB or any member thereof on behalf of the IAB, * any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, * the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions. *************************************************************************** From owner-snmpconf@seymour39.snmp.com Wed Apr 14 09:39:44 2004 Received: from seymour39.snmp.com (seymour39.snmp.com [192.147.142.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24036 for ; Wed, 14 Apr 2004 09:39:44 -0400 (EDT) Received: (from majordomo@localhost) by seymour39.snmp.com (8.9.3p2-20030922/m.030206) id JAA11566 for snmpconf-outgoing; Wed, 14 Apr 2004 09:26:36 -0400 (EDT) Message-Id: <200404132321.i3DNL7N07942@boreas.isi.edu> To: IETF-Announce: ; Subject: snmpconf RFC 3747 on The Differentiated Services Configuration MIB Cc: rfc-editor@rfc-editor.org, snmpconf@snmp.com From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Tue, 13 Apr 2004 16:21:07 -0700 X-ISI-4-28-6-MailScanner: Found to be clean X-MailScanner-From: rfc-ed@isi.edu Sender: owner-snmpconf@snmp.com Precedence: bulk Reply-To: snmpconf@snmp.com --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3747 Title: The Differentiated Services Configuration MIB Author(s): H. Hazewinkel, Ed., D. Partain, Ed. Status: Standards Track Date: April 2004 Mailbox: harrie@inet.it, David.Partain@ericsson.com Pages: 24 Characters: 51659 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-snmpconf-diffpolicy-09.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3747.txt This memo describes a MIB module that provides a conceptual layer between high-level "network-wide" policy definitions that effect configuration of the Differentiated Services (diffserv) subsystem and the instance-specific information that would include such details as the parameters for all the queues associated with each interface in a system. This essentially provides an interface for configuring differentiated services at a conceptually higher layer than that of the Differentiated Services MIB. This document is a product of the Configuration Management with SNMP Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <040413161835.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3747 --OtherAccess Content-Type: Message/External-body; name="rfc3747.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <040413161835.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart--