RFC 2670 on DOCSIS RF Interface MIB

RFC Editor <rfc-ed@ISI.EDU> Mon, 30 August 1999 19:06 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11597; Mon, 30 Aug 1999 15:06:28 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id PAA05694 for ietf-123-outbound.10@ietf.org; Mon, 30 Aug 1999 15:05:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id OAA05592 for <all-ietf@loki.ietf.org>; Mon, 30 Aug 1999 14:49:13 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10935 for <all-ietf@ietf.org>; Mon, 30 Aug 1999 14:43:45 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id LAA16402; Mon, 30 Aug 1999 11:43:45 -0700 (PDT)
Message-Id: <199908301843.LAA16402@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2670 on DOCSIS RF Interface MIB
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 30 Aug 1999 11:43:44 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        RFC 2670:

        Title:	    Radio Frequency (RF) Interface Management
                    Information Base for MCNS/DOCSIS compliant 
                    RF interfaces
        Author(s):  M. St. Johns, Ed.
        Status:     Standards Track
	Date:       August 1999
        Mailbox:    stjohns@corp.home.net
        Pages:      72
        Characters: 141238
	Updates:    
        I-D Tag:    draft-ietf-ipcdn-rf-interface-mib-07.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2670.txt


This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it defines a basic set of managed objects for
SNMP-based management of MCNS/DOCSIS compliant Radio Frequency (RF)
interfaces.

This document is a product of the IP over Cable Data Network 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.
ftp://ftp.isi.edu/in-notes/rfc2670.txt"><ftp://ftp.isi.edu/in-notes/rfc2670.txt>