RFC 3997 on Internet Printing Protocol (IPP): Requirements for IPP Notifications
rfc-editor@rfc-editor.org Wed, 23 March 2005 00:37 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27921; Tue, 22 Mar 2005 19:37:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDtxc-0005g2-4u; Tue, 22 Mar 2005 19:43:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DDth4-0000u9-Ac; Tue, 22 Mar 2005 19:25:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DDth2-0000u4-I4 for ietf-announce@megatron.ietf.org; Tue, 22 Mar 2005 19:25:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25511 for <ietf-announce@ietf.org>; Tue, 22 Mar 2005 19:25:49 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDtmP-0004hq-83 for ietf-announce@ietf.org; Tue, 22 Mar 2005 19:31:25 -0500
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 j2N0Oqq02183; Tue, 22 Mar 2005 16:24:52 -0800 (PST)
Message-Id: <200503230024.j2N0Oqq02183@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 22 Mar 2005 16:24:52 -0800
X-ISI-4-39-6-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Cc: ipp@pwg.org, rfc-editor@rfc-editor.org
Subject: RFC 3997 on Internet Printing Protocol (IPP): Requirements for IPP Notifications
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-Score: -14.6 (--------------)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
A new Request for Comments is now available in online RFC libraries.
RFC 3997
Title: Internet Printing Protocol (IPP):
Requirements for IPP Notifications
Author(s): T. Hastings, Ed., R. K. deBry, H. Lewis
Status: Informational
Date: March 2005
Mailbox: hastings@cp10.es.xerox.com, debryro@uvsc.edu,
harryl@us.ibm.com
Pages: 17
Characters: 38185
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ipp-not-07.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3997.txt
This document is one of a set of documents that together describe
all aspects of the Internet Printing Protocol (IPP). IPP is an
application-level protocol that can be used for distributed printing
on the Internet. There are multiple parts to IPP, but the primary
architectural components are the Model, the Protocol, and an interface
to Directory Services. This document provides a statement of the
requirements for notifications as an optional part of an IPP Service.
This document is a product of the Internet Printing Protocol Working
Group of the IETF.
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.
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