[MIB-DOCTORS] FW: RFC 4789 on Simple Network Management Protocol (SNMP) over IEEE 802Networks
"Romascanu, Dan \(Dan\)" <dromasca@avaya.com> Tue, 05 December 2006 14:34 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrbNF-0004ca-6p; Tue, 05 Dec 2006 09:34:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrbNE-0004cL-Ex for mib-doctors@ietf.org; Tue, 05 Dec 2006 09:34:20 -0500
Received: from co300216-ier2.net.avaya.com ([198.152.13.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrbNC-0000fM-U0 for mib-doctors@ietf.org; Tue, 05 Dec 2006 09:34:20 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id kB5EY65S017584 for <mib-doctors@ietf.org>; Tue, 5 Dec 2006 09:34:07 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 05 Dec 2006 16:34:06 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0BE0F4A6@is0004avexu1.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: RFC 4789 on Simple Network Management Protocol (SNMP) over IEEE 802Networks
Thread-Index: AccU6MFLcqS5UP6nTJmrXryS9F4ELADkYN6g
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: MIB Doctors <mib-doctors@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Subject: [MIB-DOCTORS] FW: RFC 4789 on Simple Network Management Protocol (SNMP) over IEEE 802Networks
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
Errors-To: mib-doctors-bounces@ietf.org
Congratulations to Juergen and thanks to everybody who helped with comments. Dan -----Original Message----- From: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org] Sent: Friday, December 01, 2006 2:58 AM To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Subject: RFC 4789 on Simple Network Management Protocol (SNMP) over IEEE 802Networks A new Request for Comments is now available in online RFC libraries. RFC 4789 Title: Simple Network Management Protocol (SNMP) over IEEE 802 Networks Author: J. Schoenwaelder, T. Jeffree Status: Standards Track Date: November 2006 Mailbox: j.schoenwaelder@iu-bremen.de, tony@jeffree.co.uk Pages: 9 Characters: 17839 I-D Tag: draft-schoenw-snmp-ether-02.txt URL: http://www.rfc-editor.org/rfc/rfc4789.txt This document specifies how Simple Network Management Protocol (SNMP) messages can be transmitted directly over IEEE 802 networks. This document obsoletes RFC 1089. [STANDARDS TRACK] This is now a Proposed Standard Protocol. STANDARDS TRACK: 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. 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. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ MIB-DOCTORS mailing list MIB-DOCTORS@ietf.org https://www1.ietf.org/mailman/listinfo/mib-doctors
- [MIB-DOCTORS] FW: RFC 4789 on Simple Network Mana… Romascanu, Dan (Dan)