< draft-ietf-fax-reporting-extensions-04.txt		draft-ietf-fax-reporting-extensions-05.txt >
	Fax Working Group Dan Wing		Fax Working Group Dan Wing
	Internet Draft Cisco Systems		Internet Draft Cisco Systems
	October 23, 1998		January 28, 1999
	Expires February 1999		Expires June 1999
	draft-ietf-fax-reporting-extensions-04.txt		draft-ietf-fax-reporting-extensions-05.txt
	Indicating Supported Media Features Using		Indicating Supported Media Features Using
	Extensions to DSN and MDN		Extensions to DSN and MDN
	Status of this memo		Status of this memo
	This document is an Internet-Draft. Internet-Drafts are working		This document is an Internet-Draft. Internet-Drafts are working
	documents of the Internet Engineering Task Force (IETF), its areas,		documents of the Internet Engineering Task Force (IETF), its areas,
	and its working groups. Note that other groups may also distribute		and its working groups. Note that other groups may also distribute
	working documents as Internet-Drafts.		working documents as Internet-Drafts.
	skipping to change at page 1, line 33 ¶		skipping to change at page 1, line 33 ¶
	To view the entire list of current Internet-Drafts, please check		To view the entire list of current Internet-Drafts, please check
	the "1id-abstracts.txt" listing contained in the Internet-Drafts		the "1id-abstracts.txt" listing contained in the Internet-Drafts
	Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net		Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net
	(Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au		(Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au
	(Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu		(Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu
	(US West Coast).		(US West Coast).
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (1998). All Rights Reserved.		Copyright (C) The Internet Society (1999). All Rights Reserved.
	1. Abstract		1. Abstract
	A device, unlike a workstation, is not generally extensible by		There is a need in Internet mail and Internet fax for a recipient to
	installing a new reader, plugin, or other software. There is a need		indicate the media features it supports so that messages can be
	in Internet mail for a recipient to indicate the media features it		generated by senders without exceeding the recipient's abilities.
	supports so that messages can be generated by senders without
	exceeding the recipient's abilities.
	This memo describes a format for generating Message Disposition		This memo describes a format for generating Message Disposition
	Notifications [RFC2298] and Delivery Status Notifications [RFC1894]		Notifications [RFC2298] and Delivery Status Notifications [RFC1894]
	which contain such information. This information can be used by		which contain such information. This information can be used by
	senders to avoid exceeding the recipient's capabilities when sending		senders to avoid exceeding the recipient's capabilities when sending
	subsequent messages.		subsequent messages.
	2. Introduction		2. Introduction
	The extensions described in this document can be used in Message		The extensions described in this document can be used in Message
	Disposition Notifications [RFC2298] or Delivery Status Notifications		Disposition Notifications [RFC2298] or Delivery Status Notifications
	[RFC1894], as appropriate for the implementation.		[RFC1894], as appropriate for the implementation.
	Note that both DSNs and MDNs have drawbacks: DSNs are not available		Note that both DSNs and MDNs have drawbacks: DSNs are not available
	between all senders and receivers, and MDNs require the receiver		between all senders and receivers, and MDNs require the receiver to
	disclose message disposition information (or, if using the "denied"		disclose message disposition information (or, if using the "denied"
	disposition-type, the time the dispostion notification was		disposition-type, the time the disposition notification was
	generated).		generated).
			The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
			"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
			document are to be interpreted as described in [RFC2119].
	3. Extensions for use by DSN and MDN		3. Extensions for use by DSN and MDN
	The following extension is available to both DSN [RFC1894] and MDN		The following extension is available to both DSN [RFC1894] and MDN
	[RFC2298] messages.		[RFC2298] messages.
	For a DSN message, the following per-recipient fields are defined		For a DSN message, the following per-recipient fields are defined
	(section 2.3 of [RFC1894]). For an MDN message, the following		(section 2.3 of [RFC1894]). For an MDN message, the following
	extension fields are defined (section 3.1 of [RFC2298]). Using		extension fields are defined (section 3.1 of [RFC2298]). Using
	the language of [RFC2234]:		the language of [RFC2234]:
	extension-field = media-features CRLF		extension-field = media-features CRLF
	media-features = "Accept-Features" ":"		media-features = "Media-Accept-Features" ":"
	media-feature-tags		media-feature-tags
	media-feature-tags = <*text as defined by other documents,		media-feature-tags = <*text as defined below,
	with LWSP wrapping)		with LWSP wrapping>
	The <media-feature-tags> are defined in separate schema documents		The <media-feature-tags> are defined in separate schema documents
	which MUST utilize the language described in [SYNTAX]. The		which MUST utilize the language described in [SYNTAX]. The
	schema MUST be registered following the registration requirements		schema MUST be registered following the registration requirements
	of [CONNEG-REG].		of [CONNEG-REG].
	3.1. Examples		3.1. Examples
	The following examples assume there is a schema document		The following examples assume there is a schema document
	which defines the tags shown.		which defines the tags shown.
	3.1.1. Paper-size and Color		3.1.1. Paper-size and Color
	Assuming there is a schema document which describes the		Assuming there is a schema document which describes the
	tags paper-size and color, the following example is valid:		tags paper-size and color, the following example is valid:
	Accept-Features: (& (paper-size=A4) (color<=256) )		Media-Accept-Features: (& (paper-size=a4) (color=binary) )
	3.1.2. UA-Media, Paper-size, and Color		3.1.2. UA-Media, Paper-size, and Color
	Assuming there is a schema document which describes the		Assuming there is a schema document which describes the
	tags paper-size, color, and grey:		tags paper-size, color, and grey:
	Accept-Features: (& (| (paper-size=(A4)) (paper-size=letter) )		Media-Accept-Features: (& (| (paper-size=a4) (paper-size=letter) )
	(| (& (grey=2) (dpi-x=200) (dpi-y=[100,200]) )		(| (& (color=grey) (dpi=200) (dpi-xyratio=200/100) )
	(& (color<=256) (dpi-x=200) (dpi-y=200) ) )		(& (color=limited) (dpi=200) (dpi-xy=200/100) ) )
	4. MTA Implmentation Recommendation		4. MTA Implmentation Recommendation
	If the recipient's MTA determines that a message cannot be processed,		If the recipient's MTA determines that a message cannot be processed,
	the recipient's MTA is strongly encouraged to reject the message with		the recipient's MTA is strongly encouraged to reject the message with
	a status code of 5.6.1 [RFC1893]. This status code may be returned		a status code of 5.6.1 [RFC1893]. This status code may be returned
	in response to the end-of-mail-data indicator if the MTA supports		in response to the end-of-mail-data indicator if the MTA supports
	reporting of enhanced error codes [RFC2034], or after message		reporting of enhanced error codes [RFC2034], or after message
	reception by generating a delivery failure DSN ("bounce").		reception by generating a delivery failure DSN ("bounce").
	skipping to change at page 3, line 45 ¶		skipping to change at page 3, line 47 ¶
	[CONNEG-REG] K. Holtman, A. Mutz, T. Hardie, "Media Feature Tag		[CONNEG-REG] K. Holtman, A. Mutz, T. Hardie, "Media Feature Tag
	Registration Procedure", Internet Draft, Work in Progress,		Registration Procedure", Internet Draft, Work in Progress,
	draft-ietf-conneg-feature-reg-XX.txt.		draft-ietf-conneg-feature-reg-XX.txt.
	[RFC1894] K. Moore, G. Vaudreuil, "An Extensible Message Format for		[RFC1894] K. Moore, G. Vaudreuil, "An Extensible Message Format for
	Delivery Status Notifications", RFC 1894, January 1996.		Delivery Status Notifications", RFC 1894, January 1996.
	[RFC2034] N. Freed, "SMTP Service Extension for Returning Enhanced		[RFC2034] N. Freed, "SMTP Service Extension for Returning Enhanced
	Error Codes", RFC 2034, October 1996.		Error Codes", RFC 2034, October 1996.
			[RFC2119] S. Bradner, "Key words for use in RFCs to Indicate
			Requirement Levels", RFC 2119, March 1997.
	[RFC2234] D. Crocker, P. Overell, "Augmented BNF for Syntax		[RFC2234] D. Crocker, P. Overell, "Augmented BNF for Syntax
	Specifications: ABNF", RFC 2234, November 1997.		Specifications: ABNF", RFC 2234, November 1997.
	[RFC2298] R. Fajman, "An Extensible Message Format for Message		[RFC2298] R. Fajman, "An Extensible Message Format for Message
	Disposition Notifications", RFC 2298, March 1998.		Disposition Notifications", RFC 2298, March 1998.
	[SYNTAX] G. Klyne, "A syntax for describing media feature sets",		[SYNTAX] G. Klyne, "A syntax for describing media feature sets",
	Internet Draft, Work in Progress,		Internet Draft, Work in Progress,
	draft-ietf-conneg-feature-syntax-XX.txt.		draft-ietf-conneg-feature-syntax-XX.txt.
	skipping to change at page 4, line 20 ¶		skipping to change at page 4, line 25 ¶
	Cisco Systems, Inc.		Cisco Systems, Inc.
	101 Cooper Street		101 Cooper Street
	Santa Cruz, CA 95060 USA		Santa Cruz, CA 95060 USA
	Phone: +1 831 457 5200		Phone: +1 831 457 5200
	Fax: +1 831 457 5208		Fax: +1 831 457 5208
	EMail: dwing@cisco.com		EMail: dwing@cisco.com
	9. Copyright		9. Copyright
	Copyright (C) The Internet Society 1998. All Rights Reserved.		Copyright (C) The Internet Society 1999. All Rights Reserved.
	This document and translations of it may be copied and furnished to		This document and translations of it may be copied and furnished to
	others, and derivative works that comment on or otherwise explain it		others, and derivative works that comment on or otherwise explain it
	or assist in its implmentation may be prepared, copied, published and		or assist in its implmentation may be prepared, copied, published and
	distributed, in whole or in part, without restriction of any kind,		distributed, in whole or in part, without restriction of any kind,
	provided that the above copyright notice and this paragraph are		provided that the above copyright notice and this paragraph are
	included on all such copies and derivative works. However, this		included on all such copies and derivative works. However, this
	document itself may not be modified in any way, such as by removing		document itself may not be modified in any way, such as by removing
	the copyright notice or references to the Internet Society or other		the copyright notice or references to the Internet Society or other
	Internet organizations, except as needed for the purpose of		Internet organizations, except as needed for the purpose of
End of changes. 15 change blocks.
	20 lines changed or deleted		26 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/