RFC 3806 on Printer Finishing MIB
rfc-editor@rfc-editor.org Thu, 17 June 2004 14:07 UTC
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00946 for <ietf-announce-archive@ietf.org>; Thu, 17 Jun 2004 10:07:04 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BaxXm-0004Mp-8n for ietf-announce-archive@ietf.org; Thu, 17 Jun 2004 10:07:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BaxVR-0003UK-00 for ietf-announce-archive@ietf.org; Thu, 17 Jun 2004 10:04:41 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1BaxTK-0002Wd-00; Thu, 17 Jun 2004 10:02:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bax6K-0007UE-Bi; Thu, 17 Jun 2004 09:38:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BahBW-0000PP-BU for ietf-announce@megatron.ietf.org; Wed, 16 Jun 2004 16:39:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14919 for <ietf-announce@ietf.org>; Wed, 16 Jun 2004 16:39:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BahBS-0001y0-B6 for ietf-announce@ietf.org; Wed, 16 Jun 2004 16:38:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BahAS-0001c3-00 for ietf-announce@ietf.org; Wed, 16 Jun 2004 16:37:57 -0400
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1Bah8i-00011h-00 for ietf-announce@ietf.org; Wed, 16 Jun 2004 16:36:09 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i5GKXtJ06199; Wed, 16 Jun 2004 13:33:55 -0700 (PDT)
Message-Id: <200406162033.i5GKXtJ06199@boreas.isi.edu>
To: IETF-Announce:;
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 16 Jun 2004 13:33:55 -0700
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Mailman-Approved-At: Thu, 17 Jun 2004 09:38:37 -0400
Cc: rfc-editor@rfc-editor.org
Subject: RFC 3806 on Printer Finishing MIB
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60
A new Request for Comments is now available in online RFC libraries.
RFC 3806
Title: Printer Finishing MIB
Author(s): R. Bergman, H. Lewis, I. McDonald
Status: Informational
Date: June 2004
Mailbox: Ron.Bergman@hitachi-ps.us, harryl@us.ibm.com,
imcdonald@sharplabs.com
Pages: 53
Characters: 109654
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-printmib-finishing-16.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3806.txt
This document defines a MIB module for the management of printer
finishing device subunits. The finishing device subunits applicable
to this MIB are an integral part of the Printer System. This MIB
applies only to a Finisher Device that is connected to a Printer
System.
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. 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.
_______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
- RFC 3806 on Printer Finishing MIB rfc-editor