<pre>Network Working Group                                         T. Harding
Request for Comments: 3335                              Cyclone Commerce
Category: Standards Track                                    R. Drummond
                                                          Drummond Group
                                                                 C. Shih
                                                           Gartner Group
                                                          September 2002


                     <span class="h1">MIME-based Secure Peer-to-Peer</span>
              <span class="h1">Business Data Interchange over the Internet</span>

Status of this Memo

   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.

Copyright Notice

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

Abstract

   This document describes how to exchange structured business data
   securely using SMTP transport for Electronic Data Interchange, (EDI -
   either the American Standards Committee X12 or UN/EDIFACT, Electronic
   Data Interchange for Administration, Commerce and Transport), XML or
   other data used for business to business data interchange.  The data
   is packaged using standard MIME content-types.  Authentication and
   privacy are obtained by using Cryptographic Message Syntax (S/MIME)
   or OpenPGP security body parts.  Authenticated acknowledgements make
   use of multipart/signed replies to the original SMTP message.
















<span class="grey">Harding, et. al.            Standards Track                     [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


Table of Contents

   <a href="#section-1.0">1.0</a>   Introduction .................................................<a href="#page-3">3</a>
   <a href="#section-2.0">2.0</a>   Overview .....................................................<a href="#page-4">4</a>
   <a href="#section-2.1">2.1</a>   Purpose of a Security Guideline for MIME EDI .................<a href="#page-4">4</a>
   <a href="#section-2.2">2.2</a>   Definitions ..................................................<a href="#page-4">4</a>
   <a href="#section-2.2.1">2.2.1</a> Terms ........................................................<a href="#page-4">4</a>
   <a href="#section-2.2.2">2.2.2</a> The Secure Transmission Loop .................................<a href="#page-5">5</a>
   <a href="#section-2.2.3">2.2.3</a> Definition of Receipts .......................................<a href="#page-5">5</a>
   <a href="#section-2.3">2.3</a>   Assumptions ..................................................<a href="#page-6">6</a>
   <a href="#section-2.3.1">2.3.1</a> EDI Process Assumptions ......................................<a href="#page-6">6</a>
   <a href="#section-2.3.2">2.3.2</a> Flexibility Assumptions ......................................<a href="#page-7">7</a>
   <a href="#section-3.0">3.0</a>   Referenced RFCs and Their Contribution .......................<a href="#page-8">8</a>
   <a href="#section-3.1">3.1</a>   <a href="./rfc821">RFC 821</a> SMTP [<a href="#ref-7" title="&quot;Simple Mail Transfer Protocol&quot;">7</a>] .............................................<a href="#page-8">8</a>
   <a href="#section-3.2">3.2</a>   <a href="./rfc822">RFC 822</a> Text Message Format [<a href="#ref-3" title="&quot;Internet Message Format&quot;">3</a>] ..............................<a href="#page-8">8</a>
   <a href="#section-3.3">3.3</a>   <a href="./rfc1847">RFC 1847</a> MIME Security Multiparts [<a href="#ref-6" title="&quot;Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted&quot;">6</a>] ........................<a href="#page-8">8</a>
   <a href="#section-3.4">3.4</a>   <a href="./rfc1892">RFC 1892</a> Multipart/Report [<a href="#ref-9" title="&quot;The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages&quot;">9</a>] ................................<a href="#page-8">8</a>
   <a href="#section-3.5">3.5</a>   <a href="./rfc1767">RFC 1767</a> EDI Content [<a href="#ref-2" title="&quot;MIME Encapsulation of EDI Objects&quot;">2</a>] .....................................<a href="#page-9">9</a>
   <a href="#section-3.6">3.6</a>   <a href="./rfc2015">RFC 2015</a>, 3156, 2440 PGP/MIME [<a href="#ref-4" title="&quot;MIME Security With Pretty Good Privacy (PGP)&quot;">4</a>] ............................<a href="#page-9">9</a>
   <a href="#section-3.7">3.7</a>   <a href="./rfc2045">RFC 2045</a>, 2046, and 2049 MIME [<a href="#ref-1" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">1</a>] ............................<a href="#page-9">9</a>
   <a href="#section-3.8">3.8</a>   <a href="./rfc2298">RFC 2298</a> Message Disposition Notification [<a href="#ref-5" title="&quot;An Extensible Message Format for Message Disposition Notifications&quot;">5</a>] ................<a href="#page-9">9</a>
   3.9   <a href="./rfc2633">RFC 2633</a> and 2630 S/MIME Version 3 Message Specifications [<a href="#ref-8" title="&quot;S/MIME Version 3 Message Specification; Cryptographic Message Syntax&quot;">8</a>] 9
   <a href="#section-4.0">4.0</a>   Structure of an EDI MIME Message - Applicability .............<a href="#page-9">9</a>
   <a href="#section-4.1">4.1</a>   Introduction .................................................<a href="#page-9">9</a>
   <a href="#section-4.2">4.2</a>   Structure of an EDI MIME Message - PGP/MIME .................<a href="#page-10">10</a>
   <a href="#section-4.2.1">4.2.1</a> No Encryption, No Signature .................................<a href="#page-10">10</a>
   <a href="#section-4.2.2">4.2.2</a> No Encryption, Signature ....................................<a href="#page-10">10</a>
   <a href="#section-4.2.3">4.2.3</a> Encryption, No Signature ....................................<a href="#page-10">10</a>
   <a href="#section-4.2.4">4.2.4</a> Encryption, Signature .......................................<a href="#page-10">10</a>
   <a href="#section-4.3">4.3</a>   Structure of an EDI MIME Message - S/MIME ...................<a href="#page-10">10</a>
   <a href="#section-4.3.1">4.3.1</a> No encryption, No Signature..................................<a href="#page-10">10</a>
   <a href="#section-4.3.2">4.3.2</a> No encryption, Signature ....................................<a href="#page-10">10</a>
   <a href="#section-4.3.3">4.3.3</a> Encryption, No Signature ....................................<a href="#page-11">11</a>
   <a href="#section-4.3.4">4.3.4</a> Encryption, Signature .......................................<a href="#page-11">11</a>
   <a href="#section-5.0">5.0</a>   Receipts ....................................................<a href="#page-11">11</a>
   <a href="#section-5.1">5.1</a>   Introduction ................................................<a href="#page-11">11</a>
   <a href="#section-5.2">5.2</a>   Requesting a Signed Receipt .................................<a href="#page-13">13</a>
   <a href="#section-5.2.1">5.2.1</a> Additional Signed Receipt Considerations ....................<a href="#page-16">16</a>
   <a href="#section-5.3">5.3</a>   Message Disposition Notification Format .....................<a href="#page-17">17</a>
   <a href="#section-5.3.1">5.3.1</a> Message Disposition Notification Extensions .................<a href="#page-18">18</a>
   <a href="#section-5.3.2">5.3.2</a> Disposition Mode, Type, and Modifier Use ....................<a href="#page-19">19</a>
   <a href="#section-5.4">5.4</a>   Message Disposition Notification Processing .................<a href="#page-21">21</a>
   <a href="#section-5.4.1">5.4.1</a> Large File Processing .......................................<a href="#page-21">21</a>
   <a href="#section-5.4.2">5.4.2</a> Example .....................................................<a href="#page-22">22</a>
   <a href="#section-6.0">6.0</a>   Public Key Certificate Handling .............................<a href="#page-24">24</a>
   <a href="#section-6.1">6.1</a>   Near Term Approach ..........................................<a href="#page-24">24</a>
   <a href="#section-6.2">6.2</a>   Long Term Approach ..........................................<a href="#page-24">24</a>
   <a href="#section-7.0">7.0</a>   Security Considerations .....................................<a href="#page-25">25</a>



<span class="grey">Harding, et. al.            Standards Track                     [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


   <a href="#section-8.0">8.0</a>   Acknowledgments .............................................<a href="#page-26">26</a>
   <a href="#section-9.0">9.0</a>   References ..................................................<a href="#page-26">26</a>
   <a href="#appendix-I">Appendix I</a>ANA Registration Form ...................................<a href="#page-28">28</a>
   Authors' Addresses ................................................<a href="#page-28">28</a>
   Full Copyright Statement ..........................................<a href="#page-29">29</a>

<span class="h3"><a class="selflink" id="section-1.0" href="#section-1.0">1.0</a> Introduction</span>

   Previous work on Internet EDI focused on specifying MIME content
   types for EDI data ([<a href="#ref-2" title="&quot;MIME Encapsulation of EDI Objects&quot;">2</a>] <a href="./rfc1767">RFC 1767</a>).  This document expands on <a href="./rfc1767">RFC 1767</a>
   to specify use of a comprehensive set of data security features,
   specifically data privacy, data integrity/authenticity, non-
   repudiation of origin and non-repudiation of receipt.  This document
   also recognizes contemporary RFCs and is attempting to "re-invent" as
   little as possible.  While this document focuses specifically on EDI
   data, any other data type is also supported.

   With an enhancement in the area of "receipts", as described below
   (5.2), secure Internet MIME based EDI can be accomplished by using
   and complying with the following RFCs:

      -RFC 821 SMTP
      -RFC 822 Text Message Formats
      -RFC 1767 EDI Content Type
      -RFC 1847 Security Multiparts for MIME
      -RFC 1892 Multipart/Report
      -RFC 2015, 3156, 2440 MIME/PGP

      -RFC 2045 to 2049 MIME RFCs
      -RFC 2298 Message Disposition Notification
      -RFC 2630, 2633 S/MIME v3 Specification

   Our intent here is to define clearly and precisely how these are used
   together, and what is required by user agents to be compliant with
   this document.

   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 <a href="./rfc2119">RFC 2119</a>.












<span class="grey">Harding, et. al.            Standards Track                     [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


<span class="h3"><a class="selflink" id="section-2.0" href="#section-2.0">2.0</a> Overview</span>

<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> Purpose of a Security Guideline for MIME EDI</span>

   The purpose of these specifications is to ensure interoperability
   between EDI user agents, invoking some or all of the commonly
   expected security features.  This document is also NOT limited to
   strict EDI use, but applies to any electronic commerce application
   where business data needs to be exchanged over the Internet in a
   secure manner.

<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a> Definitions</span>

<span class="h4"><a class="selflink" id="section-2.2.1" href="#section-2.2.1">2.2.1</a> Terms</span>

   EDI                  Electronic Data Interchange

   EC                   Electronic Commerce

   Receipt              The functional message that is sent from a
                        receiver to a sender to acknowledge
                        receipt of an EDI/EC interchange.

   Signed Receipt       Same as above, but with a digital
                        signature.

   Message Disposition  The Internet messaging format used to
   Notification         convey a receipt.  This term is used
                        interchangeably with receipt.  A signed
                        MDN is a signed receipt.

   Non-repudiation of   NRR is a "legal event" that occurs when
   Receipt (NRR)        the original sender of an EDI/EC
                        interchange has verified the signed
                        receipt coming back from the receiver.
                        NRR IS NOT a functional or a technical
                        message.

   PGP/MIME             Digital envelope security based on the
                        Pretty Good Privacy (PGP) standard
                        (Zimmerman), integrated with MIME Security
                        Multiparts [<a href="#ref-6" title="&quot;Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted&quot;">6</a>].

   S/MIME               A format and protocol for adding
                        Cryptographic signature and/or encryption
                        services to Internet MIME messages.





<span class="grey">Harding, et. al.            Standards Track                     [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


<span class="h4"><a class="selflink" id="section-2.2.2" href="#section-2.2.2">2.2.2</a> The secure transmission loop</span>

   This document's focus is on the formats and protocols for exchanging
   EDI content that has had security applied to it using the Internet's
   messaging environment.

   The "secure transmission loop" for EDI involves one organization
   sending a signed and encrypted EDI interchange to another
   organization, requesting a signed receipt, followed later by the
   receiving organization sending this signed receipt back to the
   sending organization.  In other words, the following transpires:

     -The organization sending EDI/EC data signs and encrypts the data
      using either PGP/MIME or S/MIME.  In addition, the message will
      request a signed receipt to be returned to the sender of the
      message.

     -The receiving organization decrypts the message and verifies the
      signature, resulting in verified integrity of the data and
      authenticity of the sender.

     -The receiving organization then returns a signed receipt to the
      sending organization in the form of a message disposition
      notification message.  This signed receipt will contain the hash
      of the signature from the received message, indicating to the
      sender that the received message was verified and/or decrypted
      properly.

   The above describes functionality which, if implemented, would
   satisfy all security requirements.  This specification, however,
   leaves full flexibility for users to decide the degree to which they
   want to deploy those security features with their trading partners.

<span class="h4"><a class="selflink" id="section-2.2.3" href="#section-2.2.3">2.2.3</a> Definition of receipts</span>

   The term used for both the functional activity and message for
   acknowledging receipt of an EDI/EC interchange is receipt, or signed
   receipt.  The first term is used if the acknowledgment is for an
   interchange resulting in a receipt which is NOT signed.  The second
   term is used if the acknowledgment is for an interchange resulting in
   a receipt which IS signed.  The method used to request a receipt or a
   signed receipt is defined in <a href="./rfc2298">RFC 2298</a>, "An Extensible Message Format
   for Message Disposition Notifications".

   The "rule" is:

     - If a receipt is requested, explicitly specifying that the receipt
       be signed, then the receipt MUST be returned with a signature.



<span class="grey">Harding, et. al.            Standards Track                     [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


     - If a receipt is requested, explicitly specifying that the receipt
       be signed, but the recipient cannot support the requested
       protocol format or requested MIC algorithms, then a receipt,
       either signed or unsigned SHOULD  be returned.

     - If a signature is not explicitly requested, or if the signed
       receipt request parameter is not recognized by the UA, a receipt
       may or may not be returned.  This behavior is consistent with the
       MDN <a href="./rfc2298">RFC 2298</a>.

   A term often used in combination with receipts is "Non-Repudiation of
   Receipt (NRR).  NRR refers to a legal event which occurs only when
   the original sender of an interchange has verified the signed receipt
   coming back from recipient of the message.  Note that NRR is not
   possible without signatures.

<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>  Assumptions</span>

<span class="h4"><a class="selflink" id="section-2.3.1" href="#section-2.3.1">2.3.1</a> EDI Process Assumptions</span>

   -Encrypted object is an EDI Interchange
    This specification assumes that a typical EDI interchange is the
    lowest level object that will be subject to security services.

    In ANSI X12, this means anything between, and including segments ISA
    and IEA.  In EDIFACT, this means anything between, and including,
    segments UNA/UNB and UNZ.  In other words, the EDI interchanges
    including envelope segments remain intact and unreadable during
    secure transport.

   -EDI envelope headers are encrypted
    Congruent with the above statement, EDI envelope headers are NOT
    visible in the MIME package.  In order to optimize routing from
    existing commercial EDI networks (called Value Added Networks or
    VANs) to the Internet, work may need to be done in the future to
    define ways to pull out some of the envelope information to make
    them visible; however, this specification does not go into any
    detail on this.

   -X12.58 and UN/EDIFACT security considerations
    The most common EDI standards bodies, ANSI X12 and EDIFACT, have
    defined internal provisions for security.  X12.58 is the security
    mechanism for ANSI X12 and AUTACK provides security for EDIFACT.
    This specification DOES NOT dictate use or non-use of these security
    standards.  They are both fully compatible, though possibly
    redundant, with this specification.





<span class="grey">Harding, et. al.            Standards Track                     [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


<span class="h4"><a class="selflink" id="section-2.3.2" href="#section-2.3.2">2.3.2</a> Flexibility Assumptions</span>

   -Encrypted or unencrypted data

    This specification allows for EDI message exchange where the EDI
    data can either be un-protected or protected by means of encryption.

   -Signed or unsigned data

    This specification allows for EDI message exchange with or without
    digital signature of the original EDI transmission.

   -Use of receipt or not

    This specification allows for EDI message transmission with or
    without a request for receipt notification.  If a signed receipt
    notification  is requested however, a mic value is REQUIRED as part
    of the returned receipt, unless an error condition occurs in which a
    mic value cannot be returned.  In error cases, an un-signed receipt
    or MDN SHOULD be returned with the correct "disposition modifier"
    error value.

   -Formatting choices

    This specification defines the use of two methods for formatting EDI
    contents that have security applied to it:

    -PGP/MIME
    -S/MIME

    This specification relies on the guidelines set forth in <a href="./rfc2015">RFC</a>
    <a href="./rfc2015">2015</a>/3156/2440, as reflected in [<a href="#ref-4" title="&quot;MIME Security With Pretty Good Privacy (PGP)&quot;">4</a>] "MIME Security with Pretty Good
    Privacy" (PGP); OpenPGP Message Format, and <a href="./rfc2633">RFC 2633</a>/2630 [<a href="#ref-8" title="&quot;S/MIME Version 3 Message Specification; Cryptographic Message Syntax&quot;">8</a>]
    "S/MIME Version 3 Message Specification; Cryptographic Message
    Syntax".  PGP/MIME or S/MIME as defined in this Applicability
    statement.

   -Hash function, message digest choices

    When a signature is used, it is RECOMMENDED that the SHA1 hash
    algorithm be used for all outgoing messages, and that both MD5 and
    SHA1 be supported for incoming messages.

    In summary, the following eight permutations are possible in any
    given trading relationship:

    (1) Sender sends unencrypted data, does NOT request a receipt.




<span class="grey">Harding, et. al.            Standards Track                     [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


    (2) Sender sends unencrypted data, requests a signed or unsigned
        receipt.  The receiver sends back the signed or unsigned
        receipt.

    (3) Sender sends encrypted data, does NOT request a receipt.

    (4) Sender sends encrypted data, requests a signed or unsigned
        receipt.  The receiver sends back the signed or unsigned
        receipt.

    (5) Sender sends signed data, does NOT request a signed or unsigned
        receipt.

    (6) Sender sends signed data, requests a signed or unsigned receipt.
        Receiver sends back the signed or unsigned receipt.

    (7) Sender sends encrypted and signed data, does NOT request a
        signed or unsigned receipt.

    (8) Sender sends encrypted and signed data, requests a signed or
        unsigned receipt.  Receiver sends back the signed or unsigned
        receipt.

   NOTE: Users can choose any of the eight possibilities, but only
   example (8), when a signed receipt is requested, offers the whole
   suite of security features described in the "Secure transmission
   loop" above.

<span class="h3"><a class="selflink" id="section-3.0" href="#section-3.0">3.0</a> Referenced RFCs and Their Contribution</span>

<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> <a href="./rfc821">RFC 821</a> SMTP [<a href="#ref-7" title="&quot;Simple Mail Transfer Protocol&quot;">7</a>]</span>

   This is the core mail transfer standard that all MTAs need to adhere
   to.

<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> <a href="./rfc822">RFC 822</a> Text Message Format [<a href="#ref-3" title="&quot;Internet Message Format&quot;">3</a>]</span>

   Defines message header fields and the parts making up a message.

<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a> <a href="./rfc1847">RFC 1847</a> MIME Security Multiparts [<a href="#ref-6" title="&quot;Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted&quot;">6</a>]</span>

   This document defines security multiparts for MIME:
   multipart/encrypted and multipart/signed.

<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a> <a href="./rfc1892">RFC 1892</a> Multipart/report [<a href="#ref-9" title="&quot;The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages&quot;">9</a>]</span>

   This RFC defines the use of the multipart/report content type,
   something that the MDN <a href="./rfc2298">RFC 2298</a> builds upon.



<span class="grey">Harding, et. al.            Standards Track                     [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a> <a href="./rfc1767">RFC 1767</a> EDI Content [<a href="#ref-2" title="&quot;MIME Encapsulation of EDI Objects&quot;">2</a>]</span>

   This RFC defines the use of content type "application" for ANSI X12
   (application/EDI-X12), EDIFACT (application/EDIFACT) and mutually
   defined EDI (application/EDI-Consent).

<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a> <a href="./rfc2015">RFC 2015</a>, 3156, 2440 PGP/MIME [<a href="#ref-4" title="&quot;MIME Security With Pretty Good Privacy (PGP)&quot;">4</a>]</span>

   These RFCs define the use of content types "multipart/encrypted",
   "multipart/signed", "application/pgp encrypted" and
   "application/pgp-signature" for defining MIME PGP content.

<span class="h3"><a class="selflink" id="section-3.7" href="#section-3.7">3.7</a> <a href="./rfc2045">RFC 2045</a>, 2046, and 2049 MIME [<a href="#ref-1" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">1</a>]</span>

   These are the basic MIME standards, upon which all MIME related RFCs
   build, including this one.  Key contributions include definition of
   "content type", "sub-type" and "multipart", as well as encoding
   guidelines, which establishes 7-bit US-ASCII as the canonical
   character set to be used in Internet messaging.

<span class="h3"><a class="selflink" id="section-3.8" href="#section-3.8">3.8</a> <a href="./rfc2298">RFC 2298</a> Message Disposition Notification [<a href="#ref-5" title="&quot;An Extensible Message Format for Message Disposition Notifications&quot;">5</a>]</span>

   This Internet RFC defines how a message disposition notification
   (MDN) is requested, and the format and syntax of the MDN.  The MDN is
   the basis upon which receipts and signed receipts are defined in this
   specification.

<span class="h3"><a class="selflink" id="section-3.9" href="#section-3.9">3.9</a> <a href="./rfc2633">RFC 2633</a> and 2630 S/MIME Version 3 Message Specifications [<a href="#ref-8" title="&quot;S/MIME Version 3 Message Specification; Cryptographic Message Syntax&quot;">8</a>]</span>

   This specification describes how MIME shall carry CMS Objects.

<span class="h3"><a class="selflink" id="section-4.0" href="#section-4.0">4.0</a> Structure of an EDI MIME Message - Applicability</span>

<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a> Introduction</span>

   The structures below are described hierarchically in terms of which
   RFC's are applied to form the specific structure.  For details of how
   to code in compliance with all RFC's involved, turn directly to the
   RFC's referenced.

   Also, these structures describe the initial transmission only.
   Receipts, and requests for receipts are handled in <a href="#section-5">section 5</a>.









<span class="grey">Harding, et. al.            Standards Track                     [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a> Structure of an EDI MIME Message - PGP/MIME</span>

<span class="h4"><a class="selflink" id="section-4.2.1" href="#section-4.2.1">4.2.1</a> No Encryption, No Signature</span>

   -RFC822/2045
     -RFC1767 (application/EDIxxxx or /xml)

<span class="h4"><a class="selflink" id="section-4.2.2" href="#section-4.2.2">4.2.2</a> No Encryption, Signature</span>

   -RFC822/2045
     -RFC1847 (multipart/signed)
       -RFC1767 (application/EDIxxxx or /xml)
       -RFC2015/2440/3156 (application/pgp-signature)

<span class="h4"><a class="selflink" id="section-4.2.3" href="#section-4.2.3">4.2.3</a> Encryption, No Signature</span>

   -RFC822/2045
     -RFC1847 (multipart/encrypted)
       -RFC2015/2440/3156 (application/pgp-encrypted)
         -"Version: 1"
       -RFC2015/2440/3156 (application/octet-stream)
         -RFC1767 (application/EDIxxxx or /xml) (encrypted)

<span class="h4"><a class="selflink" id="section-4.2.4" href="#section-4.2.4">4.2.4</a> Encryption, Signature</span>

   -RFC822/2045
     -RFC1847 (multipart/encrypted)
       -RFC2015/2440/3156 (application/pgp-encrypted)
         -"Version: 1"
       -RFC2015/2440/3156 (application/octet-stream)
         -RFC1847 (multipart/signed)(encrypted)
           -RFC1767 (application/EDIxxxx or /xml)(encrypted)
           -RFC2015/2440/3156 (application/pgp-signature)(encrypted)

<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a> Structure of an EDI MIME Message - S/MIME</span>

<span class="h4"><a class="selflink" id="section-4.3.1" href="#section-4.3.1">4.3.1</a> No Encryption, No Signature</span>

   -RFC822/2045
     -RFC1767 (application/EDIxxxx or /xml)

<span class="h4"><a class="selflink" id="section-4.3.2" href="#section-4.3.2">4.3.2</a> No Encryption, Signature</span>

   -RFC822/2045
     -RFC1847 (multipart/signed)
       -RFC1767 (application/EDIxxxx or /xml)
       -RFC2633 (application/pkcs7-signature)




<span class="grey">Harding, et. al.            Standards Track                    [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


<span class="h4"><a class="selflink" id="section-4.3.3" href="#section-4.3.3">4.3.3</a> Encryption, No Signature</span>

   -RFC822/2045
     -RFC2633 (application/pkcs7-mime)
       -RFC1767 (application/EDIxxxx or /xml) (encrypted)

<span class="h4"><a class="selflink" id="section-4.3.4" href="#section-4.3.4">4.3.4</a> Encryption, Signature</span>

   -RFC822/2045
     -RFC2633 (application/pkcs7-mime)
       -RFC1847 (multipart/signed) (encrypted)
         -RFC1767 (application/EDIxxxx or /xml) (encrypted)
         -RFC2633 (application/pkcs7-signature) (encrypted)

<span class="h3"><a class="selflink" id="section-5.0" href="#section-5.0">5.0</a> Receipts</span>

<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a> Introduction</span>

   In order to support non-repudiation of receipt (NRR), a signed
   receipt, based on digitally signing a message disposition
   notification, is to be implemented by a receiving trading partner's
   UA (User Agent).  The message disposition notification, specified by
   <a href="./rfc2298">RFC 2298</a> is digitally signed by a receiving trading partner as part
   of a multipart/signed MIME message.

   The following support for signed receipts is REQUIRED:

   1) The ability to create a multipart/report; where the report-type =
      disposition-notification.

   2) The ability to calculate a message integrity check (MIC) on the
      received message.  The calculated MIC value will be returned to
      the sender of the message inside the signed receipt.

   4) The ability to create a multipart/signed content with the message
      disposition notification as the first body part, and the signature
      as the second body part.

   5) The ability to return the signed receipt to the sending trading
      partner.

   The signed receipt is used to notify a sending trading partner that
   requested the signed receipt that:

   1) The receiving trading partner acknowledges receipt of the sent EDI
      Interchange.





<span class="grey">Harding, et. al.            Standards Track                    [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


   2) If the sent message was signed, then the receiving trading partner
      has authenticated the sender of the EDI Interchange.

   3) If the sent message was signed, then the receiving trading partner
      has verified the integrity of the sent EDI Interchange.

   Regardless of whether the EDI Interchange was sent in S/MIME or
   PGP/MIME format, the receiving trading partner's UA MUST provide the
   following basic processing:

   1) If the sent EDI Interchange is encrypted, then the encrypted
      symmetric key and initialization vector (if applicable) is
      decrypted using the receiver's private key.

   2) The decrypted symmetric encryption key is then used to decrypt the
      EDI Interchange.

   3) The receiving trading partner authenticates signatures in a
      message using the sender's public key.  The authentication
      algorithm performs the following:

      a) The message integrity check (MIC or Message Digest), is
         decrypted using the sender's public key.

      b) A MIC on the signed contents (the MIME header and encoded EDI
         object, as per <a href="./rfc1767">RFC 1767</a>) in the message received is calculated
         using the same one-way hash function that the sending trading
         partner used.

      c) The MIC extracted from the message that was sent, and the MIC
         calculated using the same one-way hash function that the
         sending trading partner used is compared for equality.

   4) The receiving trading partner formats the MDN and sets the
      calculated MIC into the "Received-content-MIC" extension field.

   5) The receiving trading partner creates a multipart/signed MIME
      message according to <a href="./rfc1847">RFC 1847</a>.

   6) The MDN is the first part of the multipart/signed message, and the
      digital signature is created over this MDN, including its MIME
      headers.









<span class="grey">Harding, et. al.            Standards Track                    [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


   7) The second part of the multipart/signed message contains the
      digital signature.  The "protocol" option specified in the second
      part of the multipart/signed is as follows:

      S/MIME: protocol = "application/pkcs-7-signature"

      PGP/MIME: protocol = "application/pgp-signature"

   8) The signature information is formatted according to S/MIME or
      PGP/MIME specifications.

   The EDI Interchange and the <a href="./rfc1767">RFC 1767</a> MIME EDI content header, can
   actually be part of a multi-part MIME content-type.  When the EDI
   Interchange is part of a multi-part MIME content-type, the MIC MUST
   be calculated across the entire multi-part content, including the
   MIME headers.

   The signed MDN, when received by the sender of the EDI Interchange
   can be used by the sender:

   1) As an acknowledgment that the EDI Interchange sent, was delivered
      and acknowledged by the receiving trading partner.  The receiver
      does this by returning the original message id of the sent message
      in the MDN portion of the signed receipt.

   2) As an acknowledgment that the integrity of the EDI Interchange was
      verified by the receiving trading partner.  The receiver does this
      by returning the calculated MIC of the received EDI Interchange
      (and 1767 MIME headers) in the "Received-content-MIC" field of the
      signed MDN.

   3) As an acknowledgment that the receiving trading partner has
      authenticated the sender of the EDI Interchange.

   4) As a non-repudiation of receipt when the signed MDN is
      successfully verified by the sender with the receiving trading
      partner's public key and the returned mic value inside the MDN is
      the same as the digest of the original message.

<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a> Requesting a Signed Receipt</span>

   Message Disposition Notifications are requested as per <a href="./rfc2298">RFC 2298</a>,

   "An Extensible Message Format for Message Disposition Notification".
   A request that the receiving user agent issue a message disposition
   notification is made by placing the following header into the message
   to be sent:




<span class="grey">Harding, et. al.            Standards Track                    [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


   MDN-request-header = "Disposition-notification-to" ":"
                         mail-address

   The mail-address field is specified as an <a href="./rfc822">RFC 822</a> user@domain
   address, and is the return address for the message disposition
   notification.

   In addition to requesting a message disposition notification, a
   message disposition notification that is digitally signed, or what
   has been referred to as a signed receipt, can be requested by placing
   the following in the message header following the "Disposition-
   Notification-To" line.

   Disposition-notification-options =
         "Disposition-Notification-Options" ":"
         disposition-notification-parameters

   where

     disposition-notification-parameters =
                       parameter *(";" parameter)

   where

     parameter = attribute "=" importance ", " 1#value"

   where

     importance = "required" | "optional"

   So the Disposition-notification-options string could be:

     signed-receipt-protocol=optional, &lt;protocol symbol&gt;;
     signed-receipt-micalg=optional, &lt;micalg1&gt;, &lt;micalg2&gt;,...;

   The currently supported values for &lt;protocol symbol&gt; are
   "pkcs7-signature", for the S/MIME detached signature format, or
   "pgp-signature", for the pgp signature format.

   The currently supported values for MIC algorithm values are:

   Algorithm   Value
   used

   MD5         md5
   SHA-1       sha1





<span class="grey">Harding, et. al.            Standards Track                    [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


   (Historical Note:  Some early implementations of EDIINT emitted and
   expected "rsa-md5" and "rsa-sha1" for the micalg parameter.)
   Receiving agents SHOULD be able to recover gracefully from a micalg
   parameter value that they do not recognize.

   An example of a formatted options line would be as follows:

   Disposition-notification-options:
     signed-receipt-protocol=optional, pkcs7-signature;
     signed-receipt-micalg=optional, sha1, md5

   The semantics of the "signed-receipt-protocol" parameter is as
   follows:

   1) The "signed-receipt-protocol" parameter is used to request a
      signed receipt from the recipient trading partner.  The
      "signed-receipt-protocol" parameter also specifies the format in
      which the signed receipt should be returned to the requester.

      The "signed-receipt-micalg" parameter is a list of MIC algorithms
      preferred by the requester for use in signing the returned
      receipt.  The list of MIC algorithms should be honored by the
      recipient from left to right.

      Both the "signed-receipt-protocol" and the "signed-receipt-micalg"
      option parameters are REQUIRED when requesting a signed receipt.

   2) The "importance" attribute of "Optional" is defined in the MDN <a href="./rfc2298">RFC</a>
      <a href="./rfc2298">2298</a> and has the following meaning:

      Parameters with an importance of "Optional" permit a UA that does
      not understand the particular options parameter to still generate
      a MDN in response to a request for a MDN.  A UA that does not
      understand the "signed-receipt-protocol" parameter, or the
      "signed-receipt-micalg" will obviously not return a signed
      receipt.

      The importance of "Optional" is used for the signed receipt
      parameters because it is RECOMMENDED that an MDN be returned to
      the requesting trading partner even if the recipient could not
      sign it.

      The returned MDN will contain information on the disposition of
      the message as well as why the MDN could not be signed.  See the
      Disposition field in <a href="#section-5.3">section 5.3</a> for more information.






<span class="grey">Harding, et. al.            Standards Track                    [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


      Within an EDI trading relationship, if a signed receipt is
      expected and is not returned, then the validity of the transaction
      is up to the trading partners to resolve.  In general, if a signed
      receipt is required in the trading relationship and is not
      received, the transaction will likely not be considered valid.

<span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a> Additional Signed Receipt Considerations</span>

   The "rules" stated in <a href="#section-2.2.3">Section 2.2.3</a> for signed receipts are as
   follows:

   1) When a receipt is requested, explicitly specifying that the
      receipt be signed, then the receipt MUST be returned with a
      signature.

   2) When a receipt is requested, explicitly specifying that the
      receipt be signed, but the recipient cannot support either the
      requested protocol format, or requested MIC algorithms, then
      either a signed or unsigned receipt SHOULD be returned.

   3) When a signature is not explicitly requested, or if the signed
      receipt request parameter is not recognized by the UA, then no
      receipt, an unsigned receipt, or a signed receipt MAY be returned
      by the recipient.

   NOTE: For Internet EDI, it is RECOMMENDED that when a signature is
   not explicitly requested, or if parameters are not recognized, that
   the UA send back at a minimum, an unsigned receipt.  If a signed
   receipt however was always returned as a policy, whether requested or
   not, then any false unsigned receipts can be repudiated.

   When a request for a signed receipt is made, but there is an error in
   processing the contents of the message, a signed receipt MUST still
   be returned.  The request for a signed receipt SHALL still be
   honored, though the transaction itself may not be valid.  The reason
   for why the contents could not be processed MUST be set in the
   "disposition-field".

   When a request for a signed receipt is made, the
   "Received-content-MIC" MUST always be returned to the requester.
   The"Received-content-MIC" MUST be calculated as follows:

   - For any signed messages, the MIC to be returned is calculated on
     the <a href="./rfc1767">RFC1767</a> MIME header and content.  Canonicalization as specified
     in <a href="./rfc1848">RFC 1848</a> MUST be performed before the MIC is calculated, since
     the sender requesting the signed receipt was also REQUIRED to
     canonicalize.




<span class="grey">Harding, et. al.            Standards Track                    [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


   - For encrypted, unsigned messages, the MIC to be returned is
     calculated on the decrypted <a href="./rfc1767">RFC 1767</a> MIME header and content.  The
     content after decryption MUST be canonicalized before the MIC is
     calculated.

   - For unsigned, unencrypted messages, the MIC MUST be calculated over
     the message contents prior to Content-Transfer-Encoding and without
     the MIME or any other <a href="./rfc822">RFC 822</a> headers, since these are sometimes
     altered or reordered by MTAs.

<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a> Message Disposition Notification Format</span>

   The format of a message disposition notification is specified in <a href="./rfc2298">RFC</a>
   <a href="./rfc2298">2298</a>.  For use in Internet EDI, the following format will be used:

   - content-type - per <a href="./rfc1892">RFC 1892</a> and the <a href="./rfc2298">RFC 2298</a> specification

   - reporting-ua-field - per <a href="./rfc2298">RFC 2298</a> specification

   - MDN-gateway-field - per <a href="./rfc2298">RFC 2298</a> specification

   - original-recipient-field - per <a href="./rfc2298">RFC 2298</a> specification

   - final-recipient-field - per <a href="./rfc2298">RFC 2298</a> specification

   - original-message-id-field - per <a href="./rfc2298">RFC 2298</a> specification

   - disposition-field  - the following "disposition-mode" values SHOULD
                          be used for Internet EDI:

     "automatic-action" - The disposition described by the disposition
                          type was a result of an automatic action,
                          rather than an explicit instruction by the
                          user for this message.

     "manual-action"    - The disposition described by the disposition
                          type was a result of an explicit instruction
                          by the user rather than some sort of
                          automatically performed action.

     "MDN-sent-automatically" - The MDN was sent because the UA had
                                previously been configured to do so.

     "MDN-sent-manually" - The user explicitly gave permission for this
                           particular MDN to be sent.
                           "MDN-sent-manually" is meaningful with
                           "manual-action", but not with
                           "automatic-action".



<span class="grey">Harding, et. al.            Standards Track                    [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


   - disposition-field - the following "disposition-type" values SHOULD
                         be used for Internet EDI:

     "processed" - The message has been processed in some manner (e.g.,
                   printed, faxed, forwarded, gatewayed) without being
                   displayed to the user.  The user may or may not see
                   the message later.

     "failed" -  A failure occurred that prevented the proper generation
                 of an MDN.  More information about the cause of the
                 failure may be contained in a Failure field.  The
                 "failed" disposition type is not to be used for the
                 situation in which there is some problem in processing
                 the message other than interpreting the request for an
                 MDN.  The "processed" or other disposition type with
                 appropriate disposition modifiers is to be used in such
                 situations.

   - disposition-field - the following "disposition-modifier" values
                         SHOULD be used for Internet EDI:

     "error" -  An error of some sort occurred that prevented successful
                processing of the message.  Further information is
                contained in an Error field.

     "warning" - The message was successfully processed but some sort of
                 exceptional condition occurred.  Further Information is
                 contained in a Warning field.

<span class="h4"><a class="selflink" id="section-5.3.1" href="#section-5.3.1">5.3.1</a> Message Disposition Notification Extensions</span>

   The following "extension field" will be added in order to support
   signed receipts for <a href="./rfc1767">RFC 1767</a> MIME content type and multipart MIME
   content types that include the <a href="./rfc1767">RFC 1767</a> MIME content type.  The
   extension field" defined below follows the "disposition-field" in the
   MDN.

   The "Received-content-MIC" extension field is set when the integrity
   of the received message is verified.  The MIC is the base64 encoded
   quantity computed over the received message with a hash function.
   For details of "what" the "Received-content-MIC" should be calculated
   over, see <a href="#section-5.2.1">Section 5.2.1</a>.  The algorithm used to calculate the
   "Received-content-MIC" value MUST be the same as the "micalg" value
   used by the sender in the multipart/signed message.  When no
   signature is received, or the mic-alg parameter is not supported then
   it is RECOMMENDED that the SHA1 algorithm be used to calculate the
   MIC on the received message or message contents.




<span class="grey">Harding, et. al.            Standards Track                    [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


   This field is set only when the contents of the message are processed
   successfully.  This field is used in conjunction with the recipient's
   signature on the MDN in order for the sender to verify "non-
   repudiation of receipt".

   - extension field = "Received-content-MIC"  ":"  MIC

     where:

     &lt;MIC&gt; = &lt;base64MicValue&gt; "," &lt;micalg&gt;

     &lt;base64MicValue&gt; = the result of one way hash function, base64
                        encoded.

     &lt; micalg&gt; = the micalg value defined in <a href="./rfc1847">RFC1847</a>, an IANA
                 registered MIC algorithm ID token.

<span class="h4"><a class="selflink" id="section-5.3.2" href="#section-5.3.2">5.3.2</a> Disposition Mode, Type, and Modifier Use</span>

   Guidelines for use of the "disposition-mode", "disposition-type", and
   "disposition-modifier" fields within Internet EDI are discussed in
   this section.  The "disposition-mode", "disposition-type', and
   "disposition-modifier' fields are described in detail in <a href="./rfc2298">RFC 2298</a>.
   The "disposition-mode', "disposition-type" and "disposition-modifier"
   values SHOULD be used as follows:

<span class="h5"><a class="selflink" id="section-5.3.2.1" href="#section-5.3.2.1">5.3.2.1</a> Successful Processing</span>

   When the request for a receipt or signed receipt, and the received
   message contents are successfully processed by the receiving EDI UA,
   a receipt or MDN SHOULD be returned with the "disposition-type" set
   to there is no explicit way for a user to control the sending of the
   MDN, then the first part of the "disposition-mode" should be set to
   "automatic-action".  When the MDN is being sent under user
   configurable control, then the first part of the "disposition-mode"
   should be set to "manual-action".  Since a request for a signed
   receipt should always be honored, the user MUST not be allowed to
   configure the UA to not send a signed receipt when the sender
   requests one.

   The second part of the "disposition-mode" is set to "MDN-sent-
   manually" if the user gave explicit permission for the MDN to be
   sent.  Again, the user MUST not be allowed to explicitly refuse to
   send a signed receipt when the sender requests one.  The second part
   of the "disposition-mode" is set to "MDN-sent-automatically" whenever
   the EDI UA sends the MDN automatically, regardless of whether the
   sending was under a user's, administrator's, or under software
   control.



<span class="grey">Harding, et. al.            Standards Track                    [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


   Since EDI content is generally handled automatically by the EDI UA, a
   request for a receipt or signed receipt will generally return the
   following in the "disposition-field":

     Disposition: automatic-action/MDN-sent-automatically; processed

   Note this specification does not restrict the use of the
   "disposition-mode" to just automatic actions.  Manual actions are
   valid as long as it is kept in mind that a request for a signed
   receipt MUST be honored.

<span class="h5"><a class="selflink" id="section-5.3.2.2" href="#section-5.3.2.2">5.3.2.2</a> Unprocessed Content</span>

   The request for a signed receipt requires the use of two
   "disposition-notification-options", which specify the protocol format
   of the returned signed receipt, and the MIC algorithm used to
   calculate the mic over the message contents.  The "disposition-field"
   values that should be used in the case where the message content is
   being rejected or ignored, for instance if the EDI UA determines that
   a signed receipt cannot be returned because it does not support the
   requested protocol format, so the EDI UA chooses not to process the
   message contents itself, should be specified in the MDN
   "disposition-field" as follows:

   Disposition: "disposition-mode";
     failed/Failure: unsupported format

   The syntax of the "failed" "disposition-type" is general, allowing
   the sending of any textual information along with the "failed"
   "disposition-type".  For use in Internet EDI, the following "failed"
   values are defined:

   "Failure: unsupported format" "Failure: unsupported MIC-algorithms"

<span class="h5"><a class="selflink" id="section-5.3.2.3" href="#section-5.3.2.3">5.3.2.3</a> Content Processing Errors</span>

   When errors occur processing the received message content, the
   "disposition-field" should be set to the "processed" "disposition-
   type" value and the "error" "disposition-modifier" value.  For use in
   Internet EDI, the following "error" "disposition-modifier" values are
   defined:

   "Error: decryption-failed" - the receiver could not decrypt the
                                message contents.

   "Error: authentication-failed" - the receiver could not authenticate
                                    the sender.




<span class="grey">Harding, et. al.            Standards Track                    [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


   "Error: integrity-check-failed" - the receiver could not verify
                                     content integrity.

   "Error: unexpected-processing-error" - a catch-all for any additional
                                          processing errors.

   An example of how the "disposition-field" would look when content
   processing errors are detected is as follows:

   Disposition: "disposition-mode";
     processed/Error: decryption-failed

<span class="h5"><a class="selflink" id="section-5.3.2.4" href="#section-5.3.2.4">5.3.2.4</a> Content Processing Warnings</span>

   Situations arise in EDI where even if a trading partner cannot be
   authenticated correctly, the trading partners still agree to continue
   processing the EDI transactions.  Transaction reconciliation is done
   between the trading partners at a later time.  In the content
   processing warning situations as described above, the "disposition-
   field" SHOULD be set to the "processed" "disposition-type" value, and
   the "warning" "disposition-modifier" value.  For use in Internet EDI,
   the following "warning" "disposition-modifier" values are defined:

   "Warning: authentication-failed, processing continued"

   An example of how the "disposition-field" would look when content
   processing warnings are detected is as follows:

   Disposition: "disposition-mode"; processed/Warning:
                 authentication-failed, processing continued

<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a> Message Disposition Notification Processing</span>

<span class="h4"><a class="selflink" id="section-5.4.1" href="#section-5.4.1">5.4.1</a> Large File Processing</span>

   Large EDI Interchanges sent via SMTP can be automatically fragmented
   by some message transfer agents.  A subtype of message/partial, is
   defined in <a href="./rfc2045">RFC 2045</a> [<a href="#ref-1" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">1</a>] to allow large objects to be delivered as
   separate pieces of mail and to be automatically reassembled by the
   receiving user agent.  Using message/partial, can help alleviate
   fragmentation of large messages by different message transfer agents,
   but does not completely eliminate the problem.  It is still possible
   that a piece of a partial message, upon re-assembly, may prove to
   contain a partial message as well.  This is allowed by the Internet
   standards, and it is the responsibility of the user agent to
   reassemble the fragmented pieces.





<span class="grey">Harding, et. al.            Standards Track                    [Page 21]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


   It is RECOMMENDED that the size of the EDI Interchange sent via SMTP
   be configurable so that if fragmentation is needed, then
   message/partial can be used to send the large EDI Interchange in
   smaller pieces.  <a href="./rfc2045">RFC 2045</a> [<a href="#ref-1" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">1</a>] defines the use of Content-Type:
   message/partial.

   Note: Support of the message/partial content type for use in Internet
   EDI is OPTIONAL and in the absence of knowledge that the recipient
   supports partial it SHOULD NOT be used.

   The receiving UA is required to re-assemble the original message
   before sending the message disposition notification to the original
   sender of the message.  A message disposition notification is used to
   specify the disposition of the entire message that was sent, and
   should not be returned by a processing UA until the entire message is
   received, even if the received message requires re-assembling.

<span class="h4"><a class="selflink" id="section-5.4.2" href="#section-5.4.2">5.4.2</a> Example</span>

   The following is an example of a signed receipt returned by a UA
   after successfully processing a MIME EDI content type.  The sending
   trading partner has requested a return signed receipt.

   This example follows the S/MIME application/pkcs-7-signature format.

   NOTE: This example is provided as an illustration only, and is not
   considered part of the protocol specification.  If an example
   conflicts with the protocol definitions specified above or in the
   other referenced RFCs, the example is wrong.

        To: &lt;recipient email&gt;
        Subject:
        From: &lt;sender email&gt;
        Date: &lt;date&gt;
        Mime-Version: 1.0
        Content-Type: multipart/signed; boundary="separator";
          micalg=sha1; protocol="application/pkcs7-signature"

        --separator
      &amp; Content-Type:  multipart/report; report-type=disposition
      &amp;   notification;  boundary="xxxxx"
      &amp;
      &amp; --xxxxx
      &amp; Content-Type: text/plain
      &amp;
      &amp; The message sent to Recipient &lt;Recipient@cyclonesoftware.com&gt;
      &amp; has been received, the EDI Interchange was successfully
      &amp; decrypted and its integrity was verified.  In addition, the



<span class="grey">Harding, et. al.            Standards Track                    [Page 22]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


      &amp; sender of the message, Sender &lt;Edi_Sender@cyclonesoftware.com&gt;
      &amp; was authenticated as the originator of the message.  There is
      &amp; no guarantee however that the EDI Interchange was
      &amp; syntactically correct, or was received by the EDI
      &amp; application.
      &amp;
      &amp; --xxxxx
      &amp; Content-Type:  message/disposition-notification
      &amp;
      &amp; Reporting-UA: Interchange.cyclonesoftware.com (CI 2.2)
      &amp; Original-Recipient: <a href="./rfc822">rfc822</a>; Edi_Recipient@cyclonesoftware.com
      &amp; Final-Recipient: <a href="./rfc822">rfc822</a>;  Edi_Recipient@cyclonesoftware.com
      &amp; Original-Message-ID: &lt;17759920005.12345@cyclonesoftware.com &gt;
      &amp; Disposition: automatic-action/MDN-sent-automatically; processed
      &amp; Received-content-MIC: Q2hlY2sgSW50XwdyaXRIQ, sha1
      &amp;
      &amp; --xxxxx
      &amp; Content-Type: message/rfc822
      &amp;
      &amp; To: &lt;recipient email&gt;
      &amp; Subject:
      &amp;
      &amp;  [additional header fields go here]
      &amp;
      &amp; --xxxxx--

        --separator
        Content-Type: application/pkcs7-signature; name=smime.p7s;
        Content-Transfer-Encoding: base64
        Content-Disposition: attachment; filename=smime.p7s

        MIIHygYJKoZIhvcNAQcDoIIHuzCCB7cCAQAxgfIwge8CAQAwg
        ZgwgYMxFjAUBgNVBAMTDVRlcnJ5IEhhcmRpbmcxEDAOBgNVBA
        oTB0NZQ0xPTkUxDDAKBgNVBAsTA04vQTEQMA4GA1UEBxMHU=

      --separator--

   Notes:

   -The lines preceded with "&amp;" is what the signature is calculated
    over.

    (For details on how to prepare the multipart/signed with protocol =
    "application/pkcs7-signature" see the "S/MIME Message Specification,
    PKCS Security Services for MIME".)






<span class="grey">Harding, et. al.            Standards Track                    [Page 23]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


   Note: As specified by <a href="./rfc1892">RFC 1892</a> [<a href="#ref-9" title="&quot;The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages&quot;">9</a>], returning the original or
   portions of the original message in the third body part of the
   multipart/report is not required.  This is an optional body part.  It
   is RECOMMENDED that the received headers from the original message be
   placed in the third body part, as they can be helpful in tracking
   problems.

   Also note that the textual first body part of the multipart/report
   can be used to include a more detailed explanation of the error
   conditions reported by the disposition headers.  The first body part
   of the multipart/report when used in this way, allows a person to
   better diagnose a problem in detail.

<span class="h3"><a class="selflink" id="section-6.0" href="#section-6.0">6.0</a> Public Key Certificate Handling</span>

<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a> Near Term Approach</span>

   In the near term, the exchange of public keys and certification of
   these keys must be handled as part of the process of establishing a
   trading partnership.  The UA and/or EDI application interface must
   maintain a database of public keys used for encryption or signatures,
   in addition to the mapping between EDI trading partner ID and <a href="./rfc822">RFC 822</a>
   [<a href="#ref-3" title="&quot;Internet Message Format&quot;">3</a>] email address.  The procedures for establishing a trading
   partnership and configuring the secure EDI messaging system might
   vary among trading partners and software packages.

   For systems which make use of X.509 certificates, it is RECOMMENDED
   that trading partners self-certify each other if an agreed upon
   certification authority is not used.  It is highly RECOMMENDED that
   when trading partners are using S/MIME, that they also exchange
   public key certificates using the recommendations specified in the
   S/MIME Version 3 Message Specification.  The message formats and
   S/MIME conformance requirements for certificate exchange are
   specified in this document.

   This applicability statement does NOT require the use of a
   certification authority.  The use of a certification authority is
   therefore OPTIONAL.

<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a> Long Term Approach</span>

   In the long term, additional Internet-EDI standards may be developed
   to simplify the process of establishing a trading partnership,
   including the third party authentication of trading partners, as well
   as attributes of the trading relationship.






<span class="grey">Harding, et. al.            Standards Track                    [Page 24]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


<span class="h3"><a class="selflink" id="section-7.0" href="#section-7.0">7.0</a> Security Considerations</span>

   This entire document is concerned with secure transport of business
   to business data, and considers both privacy and authentication
   issues.

   Extracted from S/MIME Version 2 Message Specification:

   40-bit encryption is considered weak by most cryptographers.  Using
   weak cryptography offers little actual security over sending plain
   text.  However, other features of S/MIME, such as the specification
   of tripleDES or AES and the ability to announce stronger
   cryptographic capabilities to parties with whom you communicate,
   allow senders to create messages that use strong encryption.  Using
   weak cryptography is never recommended unless the only alternative is
   no cryptography.  When feasible, sending and receiving agents should
   inform senders and recipients the relative cryptographic strength of
   messages.

   Extracted from S/MIME Version 2 Certificate Handling:

   When processing certificates, there are many situations where the
   processing might fail.  Because the processing may be done by a user
   agent, a security gateway, or other program, there is no single way
   to handle such failures.  Just because the methods to handle the
   failures has not been listed, however, the reader should not assume
   that they are not important.  The opposite is true:  if a certificate
   is not provably valid and associated with the message, the processing
   software should take immediate and noticeable steps to inform the end
   user about it.

   Some of the many places where signature and certificate checking
   might fail include:

   - no certificate chain leads to a trusted CA
   - no ability to check the CRL for a certificate
   - an invalid CRL was received
   - the CRL being checked is expired
   - the certificate is expired
   - the certificate has been revoked

   There are certainly other instances where a certificate may be
   invalid, and it is the responsibility of the processing software to
   check them all thoroughly, and to decide what to do if the check
   fails.






<span class="grey">Harding, et. al.            Standards Track                    [Page 25]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


<span class="h3"><a class="selflink" id="section-8.0" href="#section-8.0">8.0</a> Acknowledgments</span>

   Many thanks go out to the previous authors of the MIME-based Secure
   EDI IETF Draft:  Mats Jansson.

   The authors would like to extend special thanks to Carl Hage, Jun
   Ding, Dale Moberg, and Karen Rosenthal for providing the team with
   valuable, and very thorough feedback.  Without participants like
   those cited above, these efforts become hard to complete in a way
   useful to the users and implementers of the technology.

   In addition, the authors would like to thank Harald Alvestrand, Jim
   Galvin, and Roger Fajman for their guidance and input.

<span class="h3"><a class="selflink" id="section-9.0" href="#section-9.0">9.0</a> References</span>

   [<a id="ref-1">1</a>]  Borenstein, N. and N. Freed, "Multipurpose Internet Mail
        Extensions (MIME) Part One: Format of Internet Message Bodies",
        <a href="./rfc2045">RFC 2045</a>, November 1996.

        Borenstein, N. and N. Freed, "Multipurpose Internet Mail
        Extensions (MIME) Part Two: Media Types", <a href="./rfc2046">RFC 2046</a>, November
        1996.

        Borenstein, N. and N. Freed, "Multipurpose Internet Mail
        Extensions (MIME) Part Five: Conformance Criteria and Examples",
        <a href="./rfc2049">RFC 2049</a>, November 1996.

   [<a id="ref-2">2</a>]  Crocker, D., "MIME Encapsulation of EDI Objects", <a href="./rfc1767">RFC 1767</a>,
        March 1995.

   [<a id="ref-3">3</a>]  Resnick, P., "Internet Message Format", <a href="./rfc2822">RFC 2822</a>, April 2001.

   [<a id="ref-4">4</a>]  Elkins, M., "MIME Security With Pretty Good Privacy (PGP)", <a href="./rfc2015">RFC</a>
        <a href="./rfc2015">2015</a>, October 1996.

        Callas, J., Donnerhacke, L., Finney, H. and R.Thayer "OpenPGP
        Message Format", <a href="./rfc2440">RFC 2440</a>, November 1998.

        Elkins, M., Del Torto, D., Levien, R. and T. Roessler "MIME
        Security with OpenPGP", <a href="./rfc3156">RFC 3156</a>, August 2001.

   [<a id="ref-5">5</a>]  Fajman, R., "An Extensible Message Format for Message
        Disposition Notifications", <a href="./rfc2298">RFC 2298</a>, March 1998.

   [<a id="ref-6">6</a>]  Galvin, J., Murphy, S., Crocker, S. and N. Freed,  "Security
        Multiparts for MIME: Multipart/Signed and Multipart/Encrypted",
        <a href="./rfc1847">RFC 1847</a>, October 1995.



<span class="grey">Harding, et. al.            Standards Track                    [Page 26]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


   [<a id="ref-7">7</a>]  Klensin, J., "Simple Mail Transfer Protocol",  <a href="./rfc2821">RFC 2821</a>, April
        1982.

   [<a id="ref-8">8</a>]  Ramsdell, B., "S/MIME Version 3 Message Specification;
        Cryptographic Message Syntax", <a href="./rfc2633">RFC 2633</a>, June 1999.

        Housley, R., "Cryptographic Message Syntax", <a href="./rfc2630">RFC 2630</a>, June
        1999.

   [<a id="ref-9">9</a>]  Vaudreuil, G., "The Multipart/Report Content Type for the
        Reporting of Mail System Administrative Messages", <a href="./rfc1892">RFC 1892</a>,
        January 1996.







































<span class="grey">Harding, et. al.            Standards Track                    [Page 27]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


Appendix IANA Registration Form

<span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a> IANA registration of the signed-receipt-protocol content</span>
    disposition parameter

      Parameter-name: signed-receipt-protocol
      Syntax: See <a href="#section-5.2">section 5.2</a> of this document
      Specification: See <a href="#section-5.2">section 5.2</a> of this document

<span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a> IANA registration of the signed-receipt-micalg content</span>
    disposition parameter

      Parameter-name: signed-receipt-micalg
      Syntax: See <a href="#section-5.2">section 5.2</a> of this document
      Specification: See <a href="#section-5.2">section 5.2</a> of this document

<span class="h3"><a class="selflink" id="appendix-A.3" href="#appendix-A.3">A.3</a> IANA registration of the Received-content-MIC MDN extension</span>
    field name

      Extension field name: Received-content-MIC
      Syntax: See <a href="#section-5.3.1">section 5.3.1</a> of this document
      Specification: See <a href="#section-5.3.1">section 5.3.1</a> of this document

Authors' Addresses

   Terry Harding
   Cyclone Commerce
   8388 E. Hartford Drive
   Scottsdale, Arizona 85255, USA

   EMail: tharding@cyclonecommerce.com


   Chuck Shih
   Gartner Group
   251 River Oaks Parkway
   San Jose, CA 95134-1913 USA

   EMail: chuck.shih@gartner.com


   Rik Drummond
   Drummond Group
   P.O. Box 101567
   Ft. Worth, TX 76105 USA

   EMail: rik@drummondgroup.com




<span class="grey">Harding, et. al.            Standards Track                    [Page 28]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
<span class="grey"><a href="./rfc3335">RFC 3335</a>                 MIME-based Secure EDI            September 2002</span>


Full Copyright Statement

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

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.  v This
   document and the information contained herein is provided on an "AS
   IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
   FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
   LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL
   NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY
   OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.




















Harding, et. al.            Standards Track                    [Page 29]
</pre>