rfc2162.txt

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

Network Working Group                                      C. Allocchio
Request for Comments: 2162                             I.N.F.N. - Italy
Obsoletes: 1405                                            January 1998
Category: Experimental


           MaXIM-11 - Mapping between X.400 / Internet mail
                                  and
                              Mail-11 mail

Status of this Memo

   This memo defines an Experimental Protocol for the Internet
   community.  It does not specify an Internet standard of any kind.
   Discussion and suggestions for improvement are requested.
   Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (1998).  All Rights Reserved.

Abstract

   This document describes a set of mappings which will enable inter
   working between systems operating the ISO/IEC 10021 - CCITT (now ITU)
   X.400 Recommendations on Message Handling Systems, and systems
   running the Mail-11 (also known as DECnet mail or VMSmail) protocol.
   The specifications are valid both within DECnet Phase IV and
   DECnet/OSI addressing and routing scheme.

   The complete scenario of X.400 / MIME / Mail-11 is also considered,
   in order to cover the possible complex cases arising in multiple
   gateway translations.

   This document covers mainly the X.400 O/R address to/from Mail-11
   address mapping and the RFC822 to/from Mail-11 ones; other mappings
   are based on MIXER specifications. Bodypart mappings are not
   specified in this document: MIXER and MIME-MHS specifications can be
   applied to map bodyparts between X.400, MIME and Mail-11, too. In
   fact MIME encoding can be used without modifications within Mail-11
   text bodyparts.

   This document obsoletes RFC 1405, which was a combined effort of
   TERENA Working Group on Messaging, and the IETF X.400 Ops Working
   Group. This update was prepared by IETF MIXER working group.






Allocchio                     Experimental                      [Page 1]

RFC 2162                        MaXIM-11                    January 1998


Chapter 1 - Introduction

1.1. X.400

   The standard referred shortly into this document as "X.400" relates
   to the ISO/IEC 10021 - CCITT 1984, 1988 and 1992 X.400 Series
   Recommendations covering the Message Oriented Text Interchange
   Service (MOTIS). This document covers the Inter Personal Messaging
   System (IPMS) only.

1.2. Mail-11

   Mail-11, also known as DECnet mail and often improperly referred as
   VMSmail, is the proprietary protocol implemented by Digital Equipment
   Corporation (DEC) to establish a real-time text messaging system
   among systems implementing the DECnet Phase IV and DECnet/OSI (CLNS)
   networking protocols.

1.3. RFC822 / MIME

   RFC822 was defined as a standard for personal messaging systems
   within the DARPA Internet and is now diffused on top of many
   different message transfer protocols, like SMTP, UUCP, BITNET, JNT
   Grey Book, CSnet. MIME specifications allows transport of non-textual
   information into RFC822 messages. Their mapping with X.400 is fully
   described in MIXER and MIME-MHS. In this document we will consider
   their relations with Mail-11, too.

1.4. The user community

   The community using MIME or X.400 messaging system is currently
   growing in the whole world, but there is still a number of very large
   communities using Mail-11 based messaging systems willing to
   communicate easily with X.400 based Message Handling Systems and with
   MIME based systems. Among these large DECnet based networks we can
   include the High Energy Physics network (HEPnet) and the Space
   Physics Analysis Network (SPAN).

   Many other local communities actively use internally Mail-11 mailing
   protocols. As any other "non standard" mail protocol, using non
   standard mapping techniques between Mail-11 and standard mail systems
   can produce unpredictable results.

   For these reasons a set of rules covering conversion between Mail-11
   and X.400 or MIME is described in this document.






Allocchio                     Experimental                      [Page 2]

RFC 2162                        MaXIM-11                    January 1998


   This document also covers the case of Mail-11 systems implementing
   the "foreign mail protocol" allowing Mail-11 to interface other mail
   systems, including RFC822 based system.

Chapter 2 - Message Elements

2.1. Service Elements

   Mail-11 protocol offers a very restricted set of elements composing a
   Inter Personal Message (IPM), whereas X.400 and RFC822/MIME
   specifications support a complex and large amount of service
   elements.  Considering the case where a message is relayed between
   two X.400 MHS or MIME Message Transport System (MTS) via a Mail-11
   messaging system this could result in a nearly complete loss of
   information.

   To minimise the inconvenience, any of the X.400 or MIME service
   elements which do not map directly into Mail-11 equivalent ones
   accordingly to this specification, will be included into Mail-11 text
   body parts as an additional RFC822-like header; this additional
   header will be inserted between the Mail-11 P2 headers (From:, To:,
   CC:, Subj:) and the other Mail-11 bodyparts. In particular, X.400
   elements will also be at first converted into textual representation
   before insertion.

   An example, where a multimedia message has been encoded into mail-11
   after having crossed also a MIME-MHS (MIXER conformant) gateway:

     From:  smtp%"[e-mail]"  "Erik"  18-OCT-1994 13:55:00.49
     To:    ALLOCCHIO
     CC:    smtp%"[e-mail]"
     Subj:  enjoy this nice picture!

     X400-Originator: [e-mail]
     X400-Recipients: [e-mail], [e-mail]
     Sender: Erik Newmann <[e-mail]>
     Organisation: SURFnet bv
     Mime-Version: 1.0
     Content-Type: multipart/mixed; boundary="----- =_aaaaaa0"
     Content-ID: <[e-mail]>

     ------- =_aaaaaa0
     Content-Type: text/plain; charset="us-ascii"
     Content-ID: <[e-mail]>

     look... you never saw this one!!
     I just include the picture in the next bodypart
     and I hope you get it fine.



Allocchio                     Experimental                      [Page 3]

RFC 2162                        MaXIM-11                    January 1998


     regards,

     Erik                                         (continues...)

     ------- =_aaaaaa0                            (continued...)
     Content-Type: image/gif
     Content-ID: <[e-mail]>
     Content-Description: a nice snapshot!
     Content-Transfer-Encoding: base64

     RAV8372FAASD83D721NSHDHD3ASDFJKHWEHKJHCBASDFA829CA8SDB29B132RBAKDFA
     9KSJ2KJAA0SDFNAL20DDKFALJ20AJDLFB239B9SC9B29BA9BDFADSDF03998ASDFASD

     ------- =_aaaaaa0

   We need, in fact, to consider also the case when a message originates
   from a network implementing RFC822/MIME protocols and is relayed via
   Mail-11 to an X.400 MHS, or vice versa.

   Whenever any X.400 element not covered in this specification needs to
   be converted into textual representation (to be included into a
   Mail-11 RFC822-like header or text bodypart) we will apply the rules
   specified in MIXER (X.400 to RFC822/MIME sections).

   Vice versa, MIXER specification (RFC822/MIME to X.400 sections) also
   gives the correct rules to convert from textual representations
   contained into Mail-11 RFC822-like header or bodyparts into X.400
   elements.

   On the other hand, RFC822/MIME headers not covered by this
   specification are included 'as they are' into Mail-11 RFC822-like
   header and bodyparts. The way back from Mail-11 to RFC822/MIME
   structure becomes thus straightforward.

   The above methods assures maximum transparency and minimal or null
   loss of information also when Mail-11 is involved.















Allocchio                     Experimental                      [Page 4]

RFC 2162                        MaXIM-11                    January 1998


2.2. Mail-11 service elements to X.400 service elements.

   All envelope (P1) and header (P2) Mail-11 service elements are
   supported in the conversion to X.400. Note that Mail-11 P1 is solely
   composed by P1-11.From and P1-11.To, and any other Mail-11 element
   belongs to Mail-11 P2:

        - P1-11.From
                maps to P1.Originator

        - P1-11.To
                maps to P1.Primary Recipient

        - P2-11.'From:'
                usually maps to P2.Originator (see section 2.6)

        - P2-11.'To:'
                maps to P2.Primary Recipient

        - P2-11.'CC:'
                maps to P2.Copy Recipient

        - P2-11.Date
                maps to P2.Submission Time Stamp

        - P2-11.'Subj:'
                maps to P2.Subject

   Any eventual RFC822-like text header in Mail-11 body part will be
   interpreted as specified into MIXER.

2.3. X.400 service elements to Mail-11 service elements

   The following X.400 service elements are supported directly into
   Mail-11 conversion:

        - P1.Originator
                maps to P1-11.'From:'

        - P1.Primary Recipients
                maps to P1-11.'To:'

        - P2.Originator
                usually maps to P2-11.'From:' (see section 2.6)

        - P2.Primary Recipients
                maps to P2-11.'To:'




Allocchio                     Experimental                      [Page 5]

RFC 2162                        MaXIM-11                    January 1998


        - P2.Copy Recipients
                maps to P2-11.'CC:'

        - P2.Submission Time Stamp
                maps to P2-11.Date

        - P2.Subject
                maps to P2-11.'Subj:'

   The following X.400 service element is partially supported into
   Mail-11 conversion:

        - P2.Blind Copy Recipient
                to ensure the required privacy, when a message contains
                a BCC address, the following actions occurs:
                - a new message is created, containing the body parts;
                - a new envelope is added to the new message, containing
                  the originator and the BCC recipient addresses only;
                - a note is added to the message informing the BCC
                  recipient about the fact that the message was a BCC;
                - the new message is delivered separately;
                - a note is added to the message delivered to TO and CC
                  recipients informing them about the fact that there
                  were some BCC recipients, too.

   Any other X.400 service element support is done accordingly to MIXER
   including the mapped element into the RFC822-like header into Mail-11
   body part.

2.4. Mail-11 service elements to RFC822/MIME service elements.

   All envelope (P1) and header (P2) Mail-11 service elements are
   supported in the conversion to RFC822/MIME:

        - P1-11.From
                maps to 822-MTS.Originator

        - P1-11.To
                maps to 822-MTS.Primary Recipient

        - P2-11.'From:'
                usually maps to 822.'From:' (see section 2.6)

        - P2-11.'To:'
                maps to 822.'To:'

        - P2-11.'CC:'
                maps to 822.'Cc:'



Allocchio                     Experimental                      [Page 6]

RFC 2162                        MaXIM-11                    January 1998


        - P2-11.Date
                maps to 822.'Date:'

        - P2-11.'Subj:'
                maps to 822.'Subject:'

   Any eventual RFC822-like text header in Mail-11 body part will be
   re-inserted into RFC822/MIME message 'as it is'.

2.5. RFC822/MIME service elements to Mail-11 service elements

   The following RFC822 service elements are supported directly into
   Mail-11 conversion:

        - 822-MTS.Originator
                maps to P1-11.From

        - 822-MTS.Primary Recipients
                maps to P1-11.To

        - 822.'From:'
                usually maps to P2-11.'From:' (see section 2.5)

        - 822.'To:'
                maps to P2-11.'To:'

        - 822.'Cc:'
                maps to P2-11.'CC:'

        - 822.'Date:'
                maps to P2-11.Date

        - 822.'Subject:'
                maps to P2-11.'Subj:'

















Allocchio                     Experimental                      [Page 7]

RFC 2162                        MaXIM-11                    January 1998


   The following RFC822 service element is partially supported into
   Mail-11 conversion:

        - 822.'Bcc:'
                to ensure the required privacy, when a message contains
                a BCC address, the following actions occurs:
                - a new message is created, containing the body parts;
                - a new envelope is added to the new message, containing
                  the originator and the BCC recipient addresses only;
                - a note is added to the message informing the BCC
                  recipient about the fact that the message was a BCC;
                - the new message is delivered separately;
                - a note is added to the message delivered to TO and CC
                  recipients informing them about the fact that there
                  were some BCC recipients, too.

   Any other RFC822/MIME service element support is done simply
   including the element 'as it is' into the RFC822-like header and into
   a Mail-11 body part.

2.6. Rules to define the Mail-11 P2-11.'From:' element

   Mail-11 User Agents (usually VMSmail) uses the P2-11.'From:' element
   as destination in case the REPLY command is issued, ignoring any
   other specification like 'Sender:' 'Reply-To:' 'Return-Path:' etc.
   Also a number of automatic responders uses this field only to address
   their messages.

   Is it thus essential to insert into this field the correct
   information, i.e. the correct address where, according to X.400 or
   RFC822 rules the REPLY command or any automatically generated message
   should go.

   The rules specified in RFC822, section 4.4.4 should be used as a
   selection criterion to define the content of this field.

   In particular, in case the P2-11.'From:' element is not generated
   from the P2.Originator (X.400) or from the 822.'From:' (RFC822), it
   is essential to preserve into a 'From:' record of the RFC822-like
   header the original information contained into the P2.Originator or
   822.'From:' fields.










Allocchio                     Experimental                      [Page 8]

RFC 2162                        MaXIM-11                    January 1998


   Vice versa, when converting from Mail-11 into X.400 or RFC822/MIME
   the information contained into the 'From:' field of the RFC822-like
   header (if present) will supersede the one contained into the Mail-11
   P2-11.'From:'. An example:

     From:  smtp%"[e-mail]"  "Erik"  18-OCT-1994 13:55:00.49
     To:    ALLOCCHIO
     CC:    smtp%"[e-mail]"
     Subj:  enjoy this nice picture!

     From: Erik Newmann <[e-mail]>
     Reply-To: [e-mail]
     Organisation: SURFnet bv
     Message-Id: <[e-mail]>

   when converting back into RFC822 the header will be:

     From: Erik Newmann <[e-mail]>
     Reply-To: [e-mail]
     To: [e-mail]
     Cc: [e-mail]
     Subject: enjoy this nice picture!
     Organisation: SURFnet bv