rfc2156.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.

Kille                       Standards Track                    [Page 20]

RFC 2156                         MIXER                      January 1998


   Auto-forwarded Indication
      Supported as new RFC 822 header (Auto-Forwarded:).

   Basic Physical Rendition
      N/A (PDAU).

   Blind Copy Recipient Indication
      Supported.

   Body Part Encryption Indication
      Supported by use of a new RFC 822 header (Original-Encoded-
      Information-Types:), although in most cases it will not be
      possible to map the body part in question.

   Content Confidentiality
      Not supported.

   Content Integrity
      Not supported.

   Conversion Prohibition
      Supported. Operation defined in RFC 2157.

   Conversion Prohibition in Case of Loss of Information
      Supported.  Operation defined in RFC 2157.

   Counter Collection
      N/A (PDAU).

   Counter Collection with Advice
      N/A (PDAU).

   Cross Referencing Indication
      Supported.

   Deferred Delivery
      N/A (prior).  This service shall always be provided by the MTS
      prior to the gateway.  A new RFC 822 header (Deferred-Delivery:)
      is provided to transfer information on this service to the
      recipient.

   Deferred Delivery Cancellation
      N/A (local).

   Delivery Notification
      Supported.  This is performed at the gateway, but may be performed
      at the end system if the end system supports NOTARY.  Thus, a
      notification is sent by the gateway to the originator.



Kille                       Standards Track                    [Page 21]

RFC 2156                         MIXER                      January 1998


   Delivery via Bureaufax Service
      N/A (PDAU).

   Designation of Recipient by Directory Name
      N/A (local).

   Disclosure of Other Recipients
      Supported by use of a new RFC 822 header (X400-Recipients:).  This
      is descriptive information for the RFC 822 recipient, and is not
      reverse mappable.

   DL Expansion History Indication
      Supported by use of a new RFC 822 header (DL-Expansion-History:).

   DL Expansion Prohibited
      Distribution List means MTS supported distribution list, in the
      manner of X.400.  This service does not exist in the RFC 822
      world, although RFC 822 supports distribution list functionality.
      There is no SMTP leve control to prohibit distribution list
      expansion.   A MIXER gateway has two conformant options.  The
      first is not to gateway a message requesting DL expansion
      prohibition, as this control cannot be guaranteed.  This option
      supports the service, but may cause unacceptable level of message
      rejections. The second is to gateway the message on the basis that
      there is no distribution list service in RFC 822. RFC 1327 allowed
      only the second option.   If the first option is shown to be
      operationally effective, it may be the only option in future
      versions of MIXER.

   Express Mail Service
      N/A (PDAU).

   Expiry Date Indication
      Supported as new RFC 822 header (Expires:).  In general, no
      automatic action can be expected.

   Explicit Conversion
      N/A (prior).

   Forwarded IP Message Indication
      Supported.

   Grade of Delivery Selection
      Not Supported.  There is no equivalent service in RFC 822.

   Importance Indication
      Supported as new RFC 822 header (Importance:).




Kille                       Standards Track                    [Page 22]

RFC 2156                         MIXER                      January 1998


   Incomplete Copy Indication
      Supported as new RFC 822 header (Incomplete-Copy:).

   Language Indication
      Supported as new RFC 822 header (Content-Language:).

   Latest Delivery Designation
      Not supported.  A new RFC 822 header (Latest-Delivery-Time:) is
      provided, which may be used by the recipient for general
      information, but will not be acted on by the SMTP infrastrucuture.

   Message Flow Confidentiality
      Not supported.

   Message Origin Authentication
      N/A (reception).

   Message Security Labelling
      Not supported.

   Message Sequence Integrity
      Not supported.

   Multi-Destination Delivery Supported.

   Multi-part Body
      Supported.

   Non Receipt Notification Request
      Not supported.

   Non Repudiation of Delivery
      Not supported.

   Non Repudiation of Origin
      N/A (reception).

   Non Repudiation of Submission
      N/A (local).

   Obsoleting Indication
      Supported as new RFC 822 header (Supersedes:).

   Ordinary Mail
      N/A (PDAU).

   Originator Indication
      Supported.



Kille                       Standards Track                    [Page 23]

RFC 2156                         MIXER                      January 1998


   Originator Requested Alternate Recipient
      Not supported, but is placed as comment next to address (X400-
      Recipients:).

   Physical Delivery Notification by MHS
      N/A (PDAU).

   Physical Delivery Notification by PDS
      N/A (PDAU).

   Physical Forwarding Allowed
      Supported by use of a comment in a new RFC 822 header (X400-
      Recipients:), associated with the recipient in question.

   Physical Forwarding Prohibited
      Supported by use of a comment in a new RFC 822 header (X400-
      Recipients:), associated with the recipient in question.

   Prevention of Non-delivery notification
      Supported where SMTP and NOTARY are available.  In other cases
      formally supported, as delivery notifications cannot be generated
      by RFC 822.  In practice, errors will be returned as IP Messages,
      and so this service may appear not to be supported (see Non-
      delivery Notification).

   Primary and Copy Recipients Indication
      Supported

   Probe
      Supported at the gateway (i.e., the gateway services the probe).

   Probe Origin Authentication
      N/A (reception).

   Proof of Delivery
      Not supported.

   Proof of Submission
      N/A (local).

   Receipt Notification Request Indication
      Not supported.









Kille                       Standards Track                    [Page 24]

RFC 2156                         MIXER                      January 1998


   Redirection Disallowed by Originator
      Redirection means MTS supported redirection, in the manner of
      X.400.  This service does not exist in the RFC 822 world.  RFC 822
      redirection (e.g., aliasing) is regarded as an informal
      redirection mechanism, beyond the scope of this control.  Messages
      will be sent to RFC 822, irrespective of whether this service is
      requested. In practice, control of this service is not supported.

   Registered Mail
      N/A (PDAU).

   Registered Mail to Addressee in Person
      N/A (PDAU).

   Reply Request Indication
      Supported as comment next to address.

   Replying IP Message Indication
      Supported.

   Report Origin Authentication
      N/A (reception).

   Request for Forwarding Address
      N/A (PDAU).

   Requested Delivery Method
      N/A (local).   The service request is dealt with at submission
      time.  Any such request is made available through the gateway by
      use of a comment associated with the recipient in question.

   Return of Content
      Supported where SMTP and NOTARY are used. In principle for other
      situations, this is N/A, as non-delivery notifications are not
      supported.  In practice, most RFC 822 systems will return part or
      all of the content along with the IP Message indicating an error
      (see Non-delivery Notification).

   Sensitivity Indication
      Supported as new RFC 822 header (Sensitivity:).

   Special Delivery
      N/A (PDAU).

   Stored Message Deletion
      N/A (MS).





Kille                       Standards Track                    [Page 25]

RFC 2156                         MIXER                      January 1998


   Stored Message Fetching
      N/A (MS).

   Stored Message Listing
      N/A (MS).

   Stored Message Summary
      N/A (MS).

   Subject Indication
      Supported.

   Undeliverable Mail with Return of Physical Message
      N/A (PDAU).

   Use of Distribution List
      In principle this applies only to X.400 supported distribution
      lists (see DL Expansion Prohibited).  Theoretically, this service
      is N/A (prior).  In practice, because of informal RFC 822 lists,
      this service can be regarded as supported.

   Auto-Submitted Indication
      Supported

2.3.2.  Reception by X.400

2.3.2.1.  Standard Mandatory Services

   The following standard IPM mandatory user facilities are required for
   reception of RFC 822 originated mail by an X.400 UA.

   Content Type Indication

   Delivery Time Stamp Indication

   IP Message Identification

   Message Identification

   Non-delivery Notification

   Original Encoded Information Types Indication

   Submission Time Stamp Indication

   Typed Body





Kille                       Standards Track                    [Page 26]

RFC 2156                         MIXER                      January 1998


2.3.2.2.  Standard Optional Services

   The following standard IPM optional user facilities are required for
   reception of RFC 822 originated mail by an X.400 UA.

   Authorising User's Indication

   Blind Copy Recipient Indication

   Cross Referencing Indication

   Originator Indication

   Primary and Copy Recipients Indication

   Replying IP Message Indication

   Subject Indication

2.3.2.3.  New Services

   A new X.400 service "RFC 822 Header Field" is defined using the
   extension facilities.  This allows for any RFC 822 header field to be
   represented.  It may be present in RFC 822 originated messages which
   are received by an X.400 UA.

Chapter 3 Basic Mappings

3.1.  Notation