As per Relevance of the word notification, we have this rfc below:
Network Working Group D.
Request for Comments: 2530 Cisco
Category: Standards Track March 1999
Indicating Supported Media Features
Extensions to DSN and
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
1.
There is a need in Internet mail and Internet fax for a recipient
indicate the media features it supports so that messages can
generated by senders without exceeding the recipient's abilities
This memo describes a format for generating Message
Notifications [RFC2298] and Delivery Status Notifications [RFC1894]
which contain such information. This information can be used
senders to avoid exceeding the recipient's capabilities when
subsequent messages
2.
The extensions described in this document can be used in
Disposition Notifications [RFC2298] or Delivery Status
[RFC1894], as appropriate for the implementation
Note that both DSNs and MDNs have drawbacks: DSNs are not
between all senders and receivers, and MDNs require the receiver
disclose message disposition information (or, if using the "denied
disposition-type, the time the disposition notification
generated).
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
document are to be interpreted as described in [RFC2119].
Wing Standards Track [Page 1]
RFC 2530 Media Features using DSN and MDN March 1999
3. Extensions for use by DSN and
The following extension is available to both DSN [RFC1894] and
[RFC2298] messages
For a DSN message, the following per-recipient fields are
(section 2.3 of [RFC1894]). For an MDN message, the
extension fields are defined (section 3.1 of [RFC2298]). Using
language of [RFC2234]:
extension-field = media-features
media-features = "Media-Accept-Features" ":"
media-feature-
media-feature-tags = <*text as defined below
with LWSP wrapping
The are defined in separate schema
which MUST utilize the language described in [SYNTAX]. The
MUST be registered following the registration requirements
[RFC2506].
3.1.
The following examples assume there is a schema document
defines the tags shown
3.1.1. Paper-size and
Assuming there is a schema document which describes the tags paper
size and color, the following example is valid
Media-Accept-Features: (& (paper-size=a4) (color=binary) )
3.1.2. UA-Media, Paper-size, and
Assuming there is a schema document which describes the tags paper
size, color, and grey
Media-Accept-Features: (& (| (paper-size=a4) (paper-size=letter) )
(| (& (color=grey) (dpi=200) (dpi-xyratio=200/100) )
(& (color=limited) (dpi=200) (dpi-xy=200/100) ) )
4. MTA Implmentation
If the recipient's MTA determines that a message cannot be processed
the recipient's MTA is strongly encouraged to reject the message
a status code of 5.6.1 [RFC1893]. This status code may be
Wing Standards Track [Page 2]
RFC 2530 Media Features using DSN and MDN March 1999
in response to the end-of-mail-data indicator if the MTA
reporting of enhanced error codes [RFC2034], or after
reception by generating a delivery failure DSN ("bounce").
5. Security
Inaccurate media feature information could cause a denial of service
causing subsequent messages to be sent which the recipient is
to process
The media feature information could be inaccurate due to a
attack (spoofed DSN or MDN) or misconfiguration
6.
The author thanks the members of the Internet Fax working group
assistance with this document, and especially Larry Masinter,
Klyne, and Ned Freed
7.
[RFC2506] Holtman, K., Mutz, A. and T. Hardie, "Media Feature
Registration Procedure", BCP 31, RFC 2506, March 1999.
[RFC1894] Moore, K. and G. Vaudreuil, "An Extensible Message
for Delivery Status Notifications", RFC 1894, January 1996.
[RFC2034] Freed, N., "SMTP Service Extension for Returning
Error Codes", RFC 2034, October 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2234] Crocker, D. and P. Overell, "Augmented BNF for
Specifications: ABNF", RFC 2234, November 1997.
[RFC2298] Fajman, R., "An Extensible Message Format for
Disposition Notifications", RFC 2298, March 1998.
[SYNTAX] Klyne, G., "A Syntax for Describing Media Feature Sets",
RFC 2533, March 1999.
Wing Standards Track [Page 3]
RFC 2530 Media Features using DSN and MDN March 1999
8. Author's
Dan
Cisco Systems, Inc
101 Cooper
Santa Cruz, CA 95060
Phone: +1 831 457 5200
Fax: +1 831 457 5208
EMail: dwing@cisco.
Wing Standards Track [Page 4]
RFC 2530 Media Features using DSN and MDN March 1999
9. Full Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Wing Standards Track [Page 5]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
