idnits 2.17.1 draft-ietf-hubmib-wis-mib-07.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3637 5 Title: Definitions of Managed Objects 6 for the Ethernet WAN Interface Sublayer 7 Author(s): C.M. Heard, Ed. 8 Status: Standards Track 9 Date: September 2003 10 Mailbox: heard@pobox.com 11 Pages: 37 12 Characters: 78785 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-hubmib-wis-mib-07.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3637.txt 19 This document defines a portion of the Management Information Base 20 (MIB) for use with network management protocols in TCP/IP based 21 internets. In particular, it defines objects for managing the 22 Ethernet Wide Area Network (WAN) Interface Sublayer (WIS). 24 The MIB module defined in this memo is an extension of the Synchronous 25 Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface 26 MIB and is implemented in conjunction with it and with the 27 Ethernet-like Interface MIB, the 802.3 Medium Attachment Unit MIB, the 28 Interfaces Group MIB, and the Inverted Stack Table MIB. 30 This document is a product of the Ethernet Interfaces and Hub MIB 31 Working Group of the IETF. 33 This is now a Proposed Standard Protocol. 35 This document specifies an Internet standards track protocol for 36 the Internet community, and requests discussion and suggestions 37 for improvements. Please refer to the current edition of the 38 "Internet Official Protocol Standards" (STD 1) for the 39 standardization state and status of this protocol. Distribution 40 of this memo is unlimited. 42 This announcement is sent to the IETF list and the RFC-DIST list. 43 Requests to be added to or deleted from the IETF distribution list 44 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 45 added to or deleted from the RFC-DIST distribution list should 46 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 48 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 49 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 50 help: ways_to_get_rfcs. For example: 52 To: rfc-info@RFC-EDITOR.ORG 53 Subject: getting rfcs 55 help: ways_to_get_rfcs 57 Requests for special distribution should be addressed to either the 58 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 59 specifically noted otherwise on the RFC itself, all RFCs are for 60 unlimited distribution.echo 61 Submissions for Requests for Comments should be sent to 62 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 63 Authors, for further information.