RFC 2530 on Media Features using DSN and MDN
RFC Editor <rfc-ed@ISI.EDU> Fri, 12 March 1999 19:55 UTC
Received: by ietf.org (8.9.1a/8.9.1a) id OAA12576 for ietf-123-outbound.10@ietf.org; Fri, 12 Mar 1999 14:55:02 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12392 for <all-ietf@ietf.org>; Fri, 12 Mar 1999 14:47:51 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id LAA14220; Fri, 12 Mar 1999 11:47:52 -0800 (PST)
Message-Id: <199903121947.LAA14220@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2530 on Media Features using DSN and MDN
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 12 Mar 1999 11:47:51 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2530: Title: Indicating Supported Media Features Using Extensions to DSN and MDN Author(s): D. Wing Status: Proposed Standard Date: March 1999 Mailbox: dwing@cisco.com Pages: 5 Characters: 7824 Updates/Obsoletes/See Also: None I-D Tag: draft-ietf-fax-reporting-extensions-05.txt URL: ftp://ftp.isi.edu/in-notes/rfc2530.txt This memo describes a format for generating Message Disposition Notifications [RFC2298] and Delivery Status Notifications [RFC1894] which contain such information. This information can be used by senders to avoid exceeding the recipient's capabilities when sending subsequent messages. This document is a product of the Internet Fax 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 Alegre Ramos 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.
- RFC 2530 on Media Features using DSN and MDN RFC Editor