RE: [ipcdn] RFC 4323 on Data Over Cable System Interface SpecificationQuality of Service Management Information Base (DOCSIS-QoS MIB)

Mike and Will,

   Thanks for all the work you both did on the ipcdn qos mib and many thanks to all of you who contributed to this work.

Jean-François
> -----Original Message-----
> From: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org]
> Sent: Wednesday, January 25, 2006 6:51 PM
> To: ietf-announce@ietf.org
> Cc: ipcdn@ietf.org; rfc-editor@rfc-editor.org
> Subject: [ipcdn] RFC 4323 on Data Over Cable System Interface
> SpecificationQuality of Service Management Information Base (DOCSIS-
> QoS MIB)
> 
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>         RFC 4323
> 
>         Title:      Data Over Cable System Interface Specification
>                     Quality of Service Management Information Base
>                     (DOCSIS-QoS MIB)
>         Author(s):  M. Patrick, W. Murwin
>         Status:     Standards Track
>         Date:       January 2006
>         Mailbox:    michael.patrick@motorola.com,
>                     w.murwin@motorola.com
>         Pages:      89
>         Characters: 197285
>         Updates/Obsoletes/SeeAlso:    None
> 
>         I-D Tag:    draft-ietf-ipcdn-qos-mib-12.txt
> 
>         URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4323.txt
> 
> 
> This document defines a basic set of managed objects for SNMP-based
> management of extended QoS features of Cable Modems (CMs) and Cable
> Modem Termination Systems (CMTSs) conforming to the Data over Cable
> System (DOCSIS) specifications versions 1.1 and 2.0.
> 
> 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.
> 
> 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.

_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn