From wwwrun@rfc-editor.org  Thu Dec 26 00:59:12 2013
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: simple@ietfa.amsl.com
Delivered-To: simple@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A82E21AD69E for <simple@ietfa.amsl.com>; Thu, 26 Dec 2013 00:59:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rOg8hTe34es4 for <simple@ietfa.amsl.com>; Thu, 26 Dec 2013 00:59:11 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 2505E1ACC81 for <simple@ietf.org>; Thu, 26 Dec 2013 00:59:11 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 554AB7FC37E; Thu, 26 Dec 2013 00:59:00 -0800 (PST)
To: eburger@standardstrack.com, hisham.khartabil@gmail.com, rlb@ipv.sx, gonzalo.camarillo@ericsson.com, hisham.khartabil@gmail.com, ben@nostrum.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20131226085903.554AB7FC37E@rfc-editor.org>
Date: Thu, 26 Dec 2013 00:59:00 -0800 (PST)
Cc: rfc-editor@rfc-editor.org, simple@ietf.org, niket.kumar@intel.com
Subject: [Simple] [Editorial Errata Reported] RFC5438 (3850)
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple/>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Dec 2013 08:59:12 -0000

The following errata report has been submitted for RFC5438,
"Instant Message Disposition Notification (IMDN)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5438&eid=3850

--------------------------------------
Type: Editorial
Reported by: Niket Kumar <niket.kumar@intel.com>

Section: 8.3

Original Text
-------------
   The aggregated IMDN is constructed using the multipart/mixed MIME
   type and including as individual payloads all the IMDNS that were
   received as message/imdn+xml.

   Below is an example of aggregated IMDNs.

   From: Bob <im:bob@example.com>
   To: Alice <im:alice@example.com>
   NS: imdn <urn:ietf:params:imdn>
   imdn.Message-ID: d834jied93rf
   Content-type: multipart/mixed;
                      boundary="imdn-boundary"
   Content-Disposition: notification
   Content-length: ...

   --imdn-boundary
   Content-type: message/imdn+xml

   <?xml version="1.0" encoding="UTF-8"?>
   <imdn xmlns="urn:ietf:params:xml:ns:imdn">
         <message-id>34jk324j</message-id>
         <datetime>2008-04-04T12:16:49-05:00</datetime>
        <recipient-uri>im:bob@example.com</recipient-uri>
         <original-recipient-uri
           >im:bob@example.com</original-recipient-uri>
         <delivery-notification>
            <status>
               <delivered/>
            </status>
         </delivery-notification>
       </imdn>

   --imdn-boundary
   Content-type: message/imdn+xml

   <?xml version="1.0" encoding="UTF-8"?>
   <imdn xmlns="urn:ietf:params:xml:ns:imdn">
         <message-id>34jk324j</message-id>
         <datetime>2008-04-04T12:16:49-05:00</datetime>
        <recipient-uri>im:bob@example.com</recipient-uri>
         <original-recipient-uri
            >im:bob@example.com</original-recipient-uri>
         <display-notification>
            <status>
               <displayed/>
            </status>
         </display-notification>
       </imdn>

   --imdn-boundary


Corrected Text
--------------
   The aggregated IMDN is constructed using the multipart/mixed MIME
   type and including as individual payloads all the IMDNS that were
   received as message/imdn+xml.

   Below is an example of aggregated IMDNs.

   From: Bob <im:bob@example.com>
   To: Alice <im:alice@example.com>
   NS: imdn <urn:ietf:params:imdn>
   imdn.Message-ID: d834jied93rf
   Content-type: multipart/mixed;
                      boundary="imdn-boundary"
   Content-Disposition: notification
   Content-length: ...

   --imdn-boundary
   Content-type: message/imdn+xml

   <?xml version="1.0" encoding="UTF-8"?>
   <imdn xmlns="urn:ietf:params:xml:ns:imdn">
         <message-id>34jk324j</message-id>
         <datetime>2008-04-04T12:16:49-05:00</datetime>
        <recipient-uri>im:bob@example.com</recipient-uri>
         <original-recipient-uri
           >im:bob@example.com</original-recipient-uri>
         <delivery-notification>
            <status>
               <delivered/>
            </status>
         </delivery-notification>
       </imdn>

   --imdn-boundary
   Content-type: message/imdn+xml

   <?xml version="1.0" encoding="UTF-8"?>
   <imdn xmlns="urn:ietf:params:xml:ns:imdn">
         <message-id>34jk324j</message-id>
         <datetime>2008-04-04T12:16:49-05:00</datetime>
        <recipient-uri>im:bob@example.com</recipient-uri>
         <original-recipient-uri
            >im:bob@example.com</original-recipient-uri>
         <display-notification>
            <status>
               <displayed/>
            </status>
         </display-notification>
       </imdn>

   --imdn-boundary--


Notes
-----
The last multipart MIME boundary should have a "--" at the end. In the above example it should be "--imdn-boundary--" instead of "--imdn-boundary"

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC5438 (draft-ietf-simple-imdn-10)
--------------------------------------
Title               : Instant Message Disposition Notification (IMDN)
Publication Date    : February 2009
Author(s)           : E. Burger, H. Khartabil
Category            : PROPOSED STANDARD
Source              : SIP for Instant Messaging and Presence Leveraging Extensions
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG

From eburger@standardstrack.com  Thu Dec 26 05:17:29 2013
Return-Path: <eburger@standardstrack.com>
X-Original-To: simple@ietfa.amsl.com
Delivered-To: simple@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2D221AD8DB for <simple@ietfa.amsl.com>; Thu, 26 Dec 2013 05:17:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.122
X-Spam-Level: 
X-Spam-Status: No, score=-1.122 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xK5oLHPR1Pm7 for <simple@ietfa.amsl.com>; Thu, 26 Dec 2013 05:17:28 -0800 (PST)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.215.108]) by ietfa.amsl.com (Postfix) with ESMTP id B0A691ADF48 for <simple@ietf.org>; Thu, 26 Dec 2013 05:17:27 -0800 (PST)
Received: from cpe-74-76-226-118.nycap.res.rr.com ([74.76.226.118]:54215 helo=[192.168.1.120]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80.1) (envelope-from <eburger@standardstrack.com>) id 1VwAoJ-00038I-Hp; Thu, 26 Dec 2013 05:17:17 -0800
Content-Type: multipart/signed; boundary="Apple-Mail=_D1A0AF29-8835-401C-8A87-C1A739851EC5"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <20131226085903.554AB7FC37E@rfc-editor.org>
Date: Thu, 26 Dec 2013 08:17:09 -0500
Message-Id: <42E4AC5D-9E4C-4E76-BF86-43C8A69C6803@standardstrack.com>
References: <20131226085903.554AB7FC37E@rfc-editor.org>
To: RFC Errata System <rfc-editor@rfc-editor.org>, niket.kumar@intel.com
X-Mailer: Apple Mail (2.1827)
X-OutGoing-Spam-Status: No, score=-2.9
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Get-Message-Sender-Via: biz104.inmotionhosting.com: authenticated_id: eburger+standardstrack.com/only user confirmed/virtual account not confirmed
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: Ben Campbell <ben@nostrum.com>, simple@ietf.org, Khartabil Hisham <hisham.khartabil@gmail.com>
Subject: Re: [Simple] [Editorial Errata Reported] RFC5438 (3850)
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple/>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Dec 2013 13:17:29 -0000

--Apple-Mail=_D1A0AF29-8835-401C-8A87-C1A739851EC5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

WFM. Good catch. Thanks.

On Dec 26, 2013, at 3:59 AM, RFC Errata System =
<rfc-editor@rfc-editor.org> wrote:

> The following errata report has been submitted for RFC5438,
> "Instant Message Disposition Notification (IMDN)".
>=20
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=3D5438&eid=3D3850
>=20
> --------------------------------------
> Type: Editorial
> Reported by: Niket Kumar <niket.kumar@intel.com>
>=20
> Section: 8.3
>=20
> Original Text
> -------------
>   The aggregated IMDN is constructed using the multipart/mixed MIME
>=20
>   type and including as individual payloads all the IMDNS that were
>=20
>   received as message/imdn+xml.
>=20
>=20
>=20
>   Below is an example of aggregated IMDNs.
>=20
>=20
>=20
>   From: Bob <im:bob@example.com>
>=20
>   To: Alice <im:alice@example.com>
>=20
>   NS: imdn <urn:ietf:params:imdn>
>=20
>   imdn.Message-ID: d834jied93rf
>=20
>   Content-type: multipart/mixed;
>=20
>                      boundary=3D"imdn-boundary"
>=20
>   Content-Disposition: notification
>=20
>   Content-length: ...
>=20
>=20
>=20
>   --imdn-boundary
>=20
>   Content-type: message/imdn+xml
>=20
>=20
>=20
>   <?xml version=3D"1.0" encoding=3D"UTF-8"?>
>=20
>   <imdn xmlns=3D"urn:ietf:params:xml:ns:imdn">
>=20
>         <message-id>34jk324j</message-id>
>=20
>         <datetime>2008-04-04T12:16:49-05:00</datetime>
>=20
>        <recipient-uri>im:bob@example.com</recipient-uri>
>=20
>         <original-recipient-uri
>=20
>> im:bob@example.com</original-recipient-uri>
>=20
>         <delivery-notification>
>=20
>            <status>
>=20
>               <delivered/>
>=20
>            </status>
>=20
>         </delivery-notification>
>=20
>       </imdn>
>=20
>=20
>=20
>   --imdn-boundary
>=20
>   Content-type: message/imdn+xml
>=20
>=20
>=20
>   <?xml version=3D"1.0" encoding=3D"UTF-8"?>
>=20
>   <imdn xmlns=3D"urn:ietf:params:xml:ns:imdn">
>=20
>         <message-id>34jk324j</message-id>
>=20
>         <datetime>2008-04-04T12:16:49-05:00</datetime>
>=20
>        <recipient-uri>im:bob@example.com</recipient-uri>
>=20
>         <original-recipient-uri
>=20
>> im:bob@example.com</original-recipient-uri>
>=20
>         <display-notification>
>=20
>            <status>
>=20
>               <displayed/>
>=20
>            </status>
>=20
>         </display-notification>
>=20
>       </imdn>
>=20
>=20
>=20
>   --imdn-boundary
>=20
>=20
>=20
> Corrected Text
> --------------
>   The aggregated IMDN is constructed using the multipart/mixed MIME
>=20
>   type and including as individual payloads all the IMDNS that were
>=20
>   received as message/imdn+xml.
>=20
>=20
>=20
>   Below is an example of aggregated IMDNs.
>=20
>=20
>=20
>   From: Bob <im:bob@example.com>
>=20
>   To: Alice <im:alice@example.com>
>=20
>   NS: imdn <urn:ietf:params:imdn>
>=20
>   imdn.Message-ID: d834jied93rf
>=20
>   Content-type: multipart/mixed;
>=20
>                      boundary=3D"imdn-boundary"
>=20
>   Content-Disposition: notification
>=20
>   Content-length: ...
>=20
>=20
>=20
>   --imdn-boundary
>=20
>   Content-type: message/imdn+xml
>=20
>=20
>=20
>   <?xml version=3D"1.0" encoding=3D"UTF-8"?>
>=20
>   <imdn xmlns=3D"urn:ietf:params:xml:ns:imdn">
>=20
>         <message-id>34jk324j</message-id>
>=20
>         <datetime>2008-04-04T12:16:49-05:00</datetime>
>=20
>        <recipient-uri>im:bob@example.com</recipient-uri>
>=20
>         <original-recipient-uri
>=20
>> im:bob@example.com</original-recipient-uri>
>=20
>         <delivery-notification>
>=20
>            <status>
>=20
>               <delivered/>
>=20
>            </status>
>=20
>         </delivery-notification>
>=20
>       </imdn>
>=20
>=20
>=20
>   --imdn-boundary
>=20
>   Content-type: message/imdn+xml
>=20
>=20
>=20
>   <?xml version=3D"1.0" encoding=3D"UTF-8"?>
>=20
>   <imdn xmlns=3D"urn:ietf:params:xml:ns:imdn">
>=20
>         <message-id>34jk324j</message-id>
>=20
>         <datetime>2008-04-04T12:16:49-05:00</datetime>
>=20
>        <recipient-uri>im:bob@example.com</recipient-uri>
>=20
>         <original-recipient-uri
>=20
>> im:bob@example.com</original-recipient-uri>
>=20
>         <display-notification>
>=20
>            <status>
>=20
>               <displayed/>
>=20
>            </status>
>=20
>         </display-notification>
>=20
>       </imdn>
>=20
>=20
>=20
>   --imdn-boundary--
>=20
>=20
>=20
> Notes
> -----
> The last multipart MIME boundary should have a "--" at the end. In the =
above example it should be "--imdn-boundary--" instead of =
"--imdn-boundary"
>=20
> Instructions:
> -------------
> This errata is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary.=20
>=20
> --------------------------------------
> RFC5438 (draft-ietf-simple-imdn-10)
> --------------------------------------
> Title               : Instant Message Disposition Notification (IMDN)
> Publication Date    : February 2009
> Author(s)           : E. Burger, H. Khartabil
> Category            : PROPOSED STANDARD
> Source              : SIP for Instant Messaging and Presence =
Leveraging Extensions
> Area                : Real-time Applications and Infrastructure
> Stream              : IETF
> Verifying Party     : IESG


--Apple-Mail=_D1A0AF29-8835-401C-8A87-C1A739851EC5
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJSvCxVAAoJEDY/T2tCIPW3/64P+wSOGXpXhiX6zwg7BcDtJ0eq
gMkDvg+2zfI1dT13I29g7U9757xx3oedr8QABSMNPcKxnV/xpriIGxGLBoFX/4Fw
D+1AjWRqyv9OvFU7ex2DbK09SS7zYuB1E8qKJPn1A0cvJxErWaWjXMcttXITJcFi
S580s93X/+CiUxs2y4RmgEUISn+oNauChX7lwO/pAwwy9xwz4P0hfXkK/qowN8Fi
za9TVkoQjTDOo2oWPwbPdMiT+EKY2fjd3N/Ahd0psEYAzVJYm4VpsEYaqQHrXoN/
3u+q98JFqPn3Ubt3L27GHFQF1fBZJhY46AEGZi6Bi4mJGmacm2PJvr7sbJknF+Jj
U353QQakNoPaBXqZ6JhO2kYVZSqCnF84Pwqo1muPW413Cfs0XzoqOBW1EhiqIgwT
L1fzVM+SVYouFidRgAsFqPjGZzYlzegaMJkkdt/y0p+xHjII0hQvTubKcyTnURu7
0Unx6Rb/4MhcMceQl69Tcm7AdVQf7FPB9zQHApn0dpkKucSpTCg0WX7iGlbL60CF
j5kKWZXTRfuJ2cmuBkpbuMOgsgBnBhGC8gJYNCfev0/BSR6KcF7/AgiuiTjronmB
AtMqyEP75hnoegbXATLZMHzIyXB653cehqznhHmBkSS/s5Q0ZnCkyOb0y+OyDok1
Sb18+7Dg4x9QI8OKjDbV
=1Ut0
-----END PGP SIGNATURE-----

--Apple-Mail=_D1A0AF29-8835-401C-8A87-C1A739851EC5--

From wwwrun@rfc-editor.org  Fri Dec 27 09:42:00 2013
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: simple@ietfa.amsl.com
Delivered-To: simple@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3A861AC440; Fri, 27 Dec 2013 09:42:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xpYZaEINLVkt; Fri, 27 Dec 2013 09:41:59 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id EC1971A1F63; Fri, 27 Dec 2013 09:41:58 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 5584B7FC38D; Fri, 27 Dec 2013 09:41:53 -0800 (PST)
To: niket.kumar@intel.com, eburger@standardstrack.com, hisham.khartabil@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20131227174153.5584B7FC38D@rfc-editor.org>
Date: Fri, 27 Dec 2013 09:41:53 -0800 (PST)
Cc: rfc-editor@rfc-editor.org, iesg@ietf.org, simple@ietf.org
Subject: [Simple] [Errata Verified] RFC5438 (3850)
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple/>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Dec 2013 17:42:01 -0000

The following errata report has been verified for RFC5438,
"Instant Message Disposition Notification (IMDN)". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5438&eid=3850

--------------------------------------
Status: Verified
Type: Editorial

Reported by: Niket Kumar <niket.kumar@intel.com>
Date Reported: 2013-12-26
Verified by: Richard Barnes (IESG)

Section: 8.3

Original Text
-------------
   The aggregated IMDN is constructed using the multipart/mixed MIME
   type and including as individual payloads all the IMDNS that were
   received as message/imdn+xml.

   Below is an example of aggregated IMDNs.

   From: Bob <im:bob@example.com>
   To: Alice <im:alice@example.com>
   NS: imdn <urn:ietf:params:imdn>
   imdn.Message-ID: d834jied93rf
   Content-type: multipart/mixed;
                      boundary="imdn-boundary"
   Content-Disposition: notification
   Content-length: ...

   --imdn-boundary
   Content-type: message/imdn+xml

   <?xml version="1.0" encoding="UTF-8"?>
   <imdn xmlns="urn:ietf:params:xml:ns:imdn">
         <message-id>34jk324j</message-id>
         <datetime>2008-04-04T12:16:49-05:00</datetime>
        <recipient-uri>im:bob@example.com</recipient-uri>
         <original-recipient-uri
           >im:bob@example.com</original-recipient-uri>
         <delivery-notification>
            <status>
               <delivered/>
            </status>
         </delivery-notification>
       </imdn>

   --imdn-boundary
   Content-type: message/imdn+xml

   <?xml version="1.0" encoding="UTF-8"?>
   <imdn xmlns="urn:ietf:params:xml:ns:imdn">
         <message-id>34jk324j</message-id>
         <datetime>2008-04-04T12:16:49-05:00</datetime>
        <recipient-uri>im:bob@example.com</recipient-uri>
         <original-recipient-uri
            >im:bob@example.com</original-recipient-uri>
         <display-notification>
            <status>
               <displayed/>
            </status>
         </display-notification>
       </imdn>

   --imdn-boundary


Corrected Text
--------------
   The aggregated IMDN is constructed using the multipart/mixed MIME
   type and including as individual payloads all the IMDNS that were
   received as message/imdn+xml.

   Below is an example of aggregated IMDNs.

   From: Bob <im:bob@example.com>
   To: Alice <im:alice@example.com>
   NS: imdn <urn:ietf:params:imdn>
   imdn.Message-ID: d834jied93rf
   Content-type: multipart/mixed;
                      boundary="imdn-boundary"
   Content-Disposition: notification
   Content-length: ...

   --imdn-boundary
   Content-type: message/imdn+xml

   <?xml version="1.0" encoding="UTF-8"?>
   <imdn xmlns="urn:ietf:params:xml:ns:imdn">
         <message-id>34jk324j</message-id>
         <datetime>2008-04-04T12:16:49-05:00</datetime>
        <recipient-uri>im:bob@example.com</recipient-uri>
         <original-recipient-uri
           >im:bob@example.com</original-recipient-uri>
         <delivery-notification>
            <status>
               <delivered/>
            </status>
         </delivery-notification>
       </imdn>

   --imdn-boundary
   Content-type: message/imdn+xml

   <?xml version="1.0" encoding="UTF-8"?>
   <imdn xmlns="urn:ietf:params:xml:ns:imdn">
         <message-id>34jk324j</message-id>
         <datetime>2008-04-04T12:16:49-05:00</datetime>
        <recipient-uri>im:bob@example.com</recipient-uri>
         <original-recipient-uri
            >im:bob@example.com</original-recipient-uri>
         <display-notification>
            <status>
               <displayed/>
            </status>
         </display-notification>
       </imdn>

   --imdn-boundary--


Notes
-----
The last multipart MIME boundary should have a "--" at the end. In the above example it should be "--imdn-boundary--" instead of "--imdn-boundary"

--------------------------------------
RFC5438 (draft-ietf-simple-imdn-10)
--------------------------------------
Title               : Instant Message Disposition Notification (IMDN)
Publication Date    : February 2009
Author(s)           : E. Burger, H. Khartabil
Category            : PROPOSED STANDARD
Source              : SIP for Instant Messaging and Presence Leveraging Extensions
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG

From rlb@ipv.sx  Fri Dec 27 09:42:28 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: simple@ietfa.amsl.com
Delivered-To: simple@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB5671ADFDD for <simple@ietfa.amsl.com>; Fri, 27 Dec 2013 09:42:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yhCLFHJji_Pf for <simple@ietfa.amsl.com>; Fri, 27 Dec 2013 09:42:26 -0800 (PST)
Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by ietfa.amsl.com (Postfix) with ESMTP id 115F51A1F63 for <simple@ietf.org>; Fri, 27 Dec 2013 09:42:25 -0800 (PST)
Received: by mail-ob0-f182.google.com with SMTP id wp4so9630778obc.13 for <simple@ietf.org>; Fri, 27 Dec 2013 09:42:20 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=eqn5+6Fu4XNUqIkCaflD7h5D0a1xHKKg9fKqEZlhLMs=; b=IQM2zRxWOOKTZS6Rn6xmzFpfChBjWP2vHkE0zt7QgSyPrPLXn9LdqSJTmESJ6MSovh OIE24elQFxRZQdyrWUNvZAjJrYnyw4mQhGi9K2bwI4fsnjo7PI2d4e+vZivyGdVFCKri DD4k+BBAAKmn0kYMV/gmLZyqNu2GV1NnTCMEu2S4IOjaepSeBEtl8B3ktPxcKk2ANPFn zn4/PgicOpJmYMt7lVlkgvVQRisSwGKXEH/yX6Mk6QCTWjNBDQRi341N4ZRNOQUbyjyB k1kCta3tBo4iDAuQekpdgqY7INK6FScax4uXi6jyLMCyAX6U2okpDqLu3LrgUfUrqDBJ MAWQ==
X-Gm-Message-State: ALoCoQmR4V94NTdYny6E1gE0nKVy2ez0XyH/oFKOqwhTg9rJVlyM9F3K4NKQhETYmvEg3rrGwUaH
MIME-Version: 1.0
X-Received: by 10.182.113.195 with SMTP id ja3mr10095858obb.46.1388166140179;  Fri, 27 Dec 2013 09:42:20 -0800 (PST)
Received: by 10.60.54.65 with HTTP; Fri, 27 Dec 2013 09:42:20 -0800 (PST)
In-Reply-To: <42E4AC5D-9E4C-4E76-BF86-43C8A69C6803@standardstrack.com>
References: <20131226085903.554AB7FC37E@rfc-editor.org> <42E4AC5D-9E4C-4E76-BF86-43C8A69C6803@standardstrack.com>
Date: Fri, 27 Dec 2013 12:42:20 -0500
Message-ID: <CAL02cgRCViRekRixeGBEgmE397rQ_gnbNXxbVsiPcGSbzgQWew@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Eric Burger <eburger@standardstrack.com>
Content-Type: multipart/alternative; boundary=089e013d0db0acc86c04ee879d6b
Cc: Ben Campbell <ben@nostrum.com>, simple@ietf.org, Khartabil Hisham <hisham.khartabil@gmail.com>, RFC Errata System <rfc-editor@rfc-editor.org>, niket.kumar@intel.com
Subject: Re: [Simple] [Editorial Errata Reported] RFC5438 (3850)
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple/>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Dec 2013 17:42:29 -0000

--089e013d0db0acc86c04ee879d6b
Content-Type: text/plain; charset=ISO-8859-1

Thanks, Eric.  I have marked this as Verified.


On Thu, Dec 26, 2013 at 8:17 AM, Eric Burger <eburger@standardstrack.com>wrote:

> WFM. Good catch. Thanks.
>
> On Dec 26, 2013, at 3:59 AM, RFC Errata System <rfc-editor@rfc-editor.org>
> wrote:
>
> > The following errata report has been submitted for RFC5438,
> > "Instant Message Disposition Notification (IMDN)".
> >
> > --------------------------------------
> > You may review the report below and at:
> > http://www.rfc-editor.org/errata_search.php?rfc=5438&eid=3850
> >
> > --------------------------------------
> > Type: Editorial
> > Reported by: Niket Kumar <niket.kumar@intel.com>
> >
> > Section: 8.3
> >
> > Original Text
> > -------------
> >   The aggregated IMDN is constructed using the multipart/mixed MIME
> >
> >   type and including as individual payloads all the IMDNS that were
> >
> >   received as message/imdn+xml.
> >
> >
> >
> >   Below is an example of aggregated IMDNs.
> >
> >
> >
> >   From: Bob <im:bob@example.com>
> >
> >   To: Alice <im:alice@example.com>
> >
> >   NS: imdn <urn:ietf:params:imdn>
> >
> >   imdn.Message-ID: d834jied93rf
> >
> >   Content-type: multipart/mixed;
> >
> >                      boundary="imdn-boundary"
> >
> >   Content-Disposition: notification
> >
> >   Content-length: ...
> >
> >
> >
> >   --imdn-boundary
> >
> >   Content-type: message/imdn+xml
> >
> >
> >
> >   <?xml version="1.0" encoding="UTF-8"?>
> >
> >   <imdn xmlns="urn:ietf:params:xml:ns:imdn">
> >
> >         <message-id>34jk324j</message-id>
> >
> >         <datetime>2008-04-04T12:16:49-05:00</datetime>
> >
> >        <recipient-uri>im:bob@example.com</recipient-uri>
> >
> >         <original-recipient-uri
> >
> >> im:bob@example.com</original-recipient-uri>
> >
> >         <delivery-notification>
> >
> >            <status>
> >
> >               <delivered/>
> >
> >            </status>
> >
> >         </delivery-notification>
> >
> >       </imdn>
> >
> >
> >
> >   --imdn-boundary
> >
> >   Content-type: message/imdn+xml
> >
> >
> >
> >   <?xml version="1.0" encoding="UTF-8"?>
> >
> >   <imdn xmlns="urn:ietf:params:xml:ns:imdn">
> >
> >         <message-id>34jk324j</message-id>
> >
> >         <datetime>2008-04-04T12:16:49-05:00</datetime>
> >
> >        <recipient-uri>im:bob@example.com</recipient-uri>
> >
> >         <original-recipient-uri
> >
> >> im:bob@example.com</original-recipient-uri>
> >
> >         <display-notification>
> >
> >            <status>
> >
> >               <displayed/>
> >
> >            </status>
> >
> >         </display-notification>
> >
> >       </imdn>
> >
> >
> >
> >   --imdn-boundary
> >
> >
> >
> > Corrected Text
> > --------------
> >   The aggregated IMDN is constructed using the multipart/mixed MIME
> >
> >   type and including as individual payloads all the IMDNS that were
> >
> >   received as message/imdn+xml.
> >
> >
> >
> >   Below is an example of aggregated IMDNs.
> >
> >
> >
> >   From: Bob <im:bob@example.com>
> >
> >   To: Alice <im:alice@example.com>
> >
> >   NS: imdn <urn:ietf:params:imdn>
> >
> >   imdn.Message-ID: d834jied93rf
> >
> >   Content-type: multipart/mixed;
> >
> >                      boundary="imdn-boundary"
> >
> >   Content-Disposition: notification
> >
> >   Content-length: ...
> >
> >
> >
> >   --imdn-boundary
> >
> >   Content-type: message/imdn+xml
> >
> >
> >
> >   <?xml version="1.0" encoding="UTF-8"?>
> >
> >   <imdn xmlns="urn:ietf:params:xml:ns:imdn">
> >
> >         <message-id>34jk324j</message-id>
> >
> >         <datetime>2008-04-04T12:16:49-05:00</datetime>
> >
> >        <recipient-uri>im:bob@example.com</recipient-uri>
> >
> >         <original-recipient-uri
> >
> >> im:bob@example.com</original-recipient-uri>
> >
> >         <delivery-notification>
> >
> >            <status>
> >
> >               <delivered/>
> >
> >            </status>
> >
> >         </delivery-notification>
> >
> >       </imdn>
> >
> >
> >
> >   --imdn-boundary
> >
> >   Content-type: message/imdn+xml
> >
> >
> >
> >   <?xml version="1.0" encoding="UTF-8"?>
> >
> >   <imdn xmlns="urn:ietf:params:xml:ns:imdn">
> >
> >         <message-id>34jk324j</message-id>
> >
> >         <datetime>2008-04-04T12:16:49-05:00</datetime>
> >
> >        <recipient-uri>im:bob@example.com</recipient-uri>
> >
> >         <original-recipient-uri
> >
> >> im:bob@example.com</original-recipient-uri>
> >
> >         <display-notification>
> >
> >            <status>
> >
> >               <displayed/>
> >
> >            </status>
> >
> >         </display-notification>
> >
> >       </imdn>
> >
> >
> >
> >   --imdn-boundary--
> >
> >
> >
> > Notes
> > -----
> > The last multipart MIME boundary should have a "--" at the end. In the
> above example it should be "--imdn-boundary--" instead of "--imdn-boundary"
> >
> > Instructions:
> > -------------
> > This errata is currently posted as "Reported". If necessary, please
> > use "Reply All" to discuss whether it should be verified or
> > rejected. When a decision is reached, the verifying party (IESG)
> > can log in to change the status and edit the report, if necessary.
> >
> > --------------------------------------
> > RFC5438 (draft-ietf-simple-imdn-10)
> > --------------------------------------
> > Title               : Instant Message Disposition Notification (IMDN)
> > Publication Date    : February 2009
> > Author(s)           : E. Burger, H. Khartabil
> > Category            : PROPOSED STANDARD
> > Source              : SIP for Instant Messaging and Presence Leveraging
> Extensions
> > Area                : Real-time Applications and Infrastructure
> > Stream              : IETF
> > Verifying Party     : IESG
>
>

--089e013d0db0acc86c04ee879d6b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks, Eric. =A0I have marked this as Verified.<div class=
=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu, Dec 26, 2013 at=
 8:17 AM, Eric Burger <span dir=3D"ltr">&lt;<a href=3D"mailto:eburger@stand=
ardstrack.com" target=3D"_blank">eburger@standardstrack.com</a>&gt;</span> =
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">WFM. Good catch. Thanks.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On Dec 26, 2013, at 3:59 AM, RFC Errata System &lt;<a href=3D"mailto:rfc-ed=
itor@rfc-editor.org">rfc-editor@rfc-editor.org</a>&gt; wrote:<br>
<br>
&gt; The following errata report has been submitted for RFC5438,<br>
&gt; &quot;Instant Message Disposition Notification (IMDN)&quot;.<br>
&gt;<br>
&gt; --------------------------------------<br>
&gt; You may review the report below and at:<br>
&gt; <a href=3D"http://www.rfc-editor.org/errata_search.php?rfc=3D5438&amp;=
eid=3D3850" target=3D"_blank">http://www.rfc-editor.org/errata_search.php?r=
fc=3D5438&amp;eid=3D3850</a><br>
&gt;<br>
&gt; --------------------------------------<br>
&gt; Type: Editorial<br>
&gt; Reported by: Niket Kumar &lt;<a href=3D"mailto:niket.kumar@intel.com">=
niket.kumar@intel.com</a>&gt;<br>
&gt;<br>
&gt; Section: 8.3<br>
&gt;<br>
&gt; Original Text<br>
&gt; -------------<br>
&gt; =A0 The aggregated IMDN is constructed using the multipart/mixed MIME<=
br>
&gt;<br>
&gt; =A0 type and including as individual payloads all the IMDNS that were<=
br>
&gt;<br>
&gt; =A0 received as message/imdn+xml.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =A0 Below is an example of aggregated IMDNs.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =A0 From: Bob &lt;<a href=3D"mailto:im%3Abob@example.com">im:bob@examp=
le.com</a>&gt;<br>
&gt;<br>
&gt; =A0 To: Alice &lt;<a href=3D"mailto:im%3Aalice@example.com">im:alice@e=
xample.com</a>&gt;<br>
&gt;<br>
&gt; =A0 NS: imdn &lt;urn:ietf:params:imdn&gt;<br>
&gt;<br>
&gt; =A0 imdn.Message-ID: d834jied93rf<br>
&gt;<br>
&gt; =A0 Content-type: multipart/mixed;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0boundary=3D&quot;imdn-bound=
ary&quot;<br>
&gt;<br>
&gt; =A0 Content-Disposition: notification<br>
&gt;<br>
&gt; =A0 Content-length: ...<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =A0 --imdn-boundary<br>
&gt;<br>
&gt; =A0 Content-type: message/imdn+xml<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =A0 &lt;?xml version=3D&quot;1.0&quot; encoding=3D&quot;UTF-8&quot;?&g=
t;<br>
&gt;<br>
&gt; =A0 &lt;imdn xmlns=3D&quot;urn:ietf:params:xml:ns:imdn&quot;&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 &lt;message-id&gt;34jk324j&lt;/message-id&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 &lt;datetime&gt;2008-04-04T12:16:49-05:00&lt;/datetime=
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0&lt;recipient-uri&gt;<a href=3D"mailto:im%3Abob@example=
.com">im:bob@example.com</a>&lt;/recipient-uri&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 &lt;original-recipient-uri<br>
&gt;<br>
&gt;&gt; <a href=3D"mailto:im%3Abob@example.com">im:bob@example.com</a>&lt;=
/original-recipient-uri&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 &lt;delivery-notification&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0&lt;status&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 &lt;delivered/&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0&lt;/status&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 &lt;/delivery-notification&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 &lt;/imdn&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =A0 --imdn-boundary<br>
&gt;<br>
&gt; =A0 Content-type: message/imdn+xml<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =A0 &lt;?xml version=3D&quot;1.0&quot; encoding=3D&quot;UTF-8&quot;?&g=
t;<br>
&gt;<br>
&gt; =A0 &lt;imdn xmlns=3D&quot;urn:ietf:params:xml:ns:imdn&quot;&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 &lt;message-id&gt;34jk324j&lt;/message-id&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 &lt;datetime&gt;2008-04-04T12:16:49-05:00&lt;/datetime=
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0&lt;recipient-uri&gt;<a href=3D"mailto:im%3Abob@example=
.com">im:bob@example.com</a>&lt;/recipient-uri&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 &lt;original-recipient-uri<br>
&gt;<br>
&gt;&gt; <a href=3D"mailto:im%3Abob@example.com">im:bob@example.com</a>&lt;=
/original-recipient-uri&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 &lt;display-notification&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0&lt;status&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 &lt;displayed/&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0&lt;/status&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 &lt;/display-notification&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 &lt;/imdn&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =A0 --imdn-boundary<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Corrected Text<br>
&gt; --------------<br>
&gt; =A0 The aggregated IMDN is constructed using the multipart/mixed MIME<=
br>
&gt;<br>
&gt; =A0 type and including as individual payloads all the IMDNS that were<=
br>
&gt;<br>
&gt; =A0 received as message/imdn+xml.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =A0 Below is an example of aggregated IMDNs.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =A0 From: Bob &lt;<a href=3D"mailto:im%3Abob@example.com">im:bob@examp=
le.com</a>&gt;<br>
&gt;<br>
&gt; =A0 To: Alice &lt;<a href=3D"mailto:im%3Aalice@example.com">im:alice@e=
xample.com</a>&gt;<br>
&gt;<br>
&gt; =A0 NS: imdn &lt;urn:ietf:params:imdn&gt;<br>
&gt;<br>
&gt; =A0 imdn.Message-ID: d834jied93rf<br>
&gt;<br>
&gt; =A0 Content-type: multipart/mixed;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0boundary=3D&quot;imdn-bound=
ary&quot;<br>
&gt;<br>
&gt; =A0 Content-Disposition: notification<br>
&gt;<br>
&gt; =A0 Content-length: ...<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =A0 --imdn-boundary<br>
&gt;<br>
&gt; =A0 Content-type: message/imdn+xml<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =A0 &lt;?xml version=3D&quot;1.0&quot; encoding=3D&quot;UTF-8&quot;?&g=
t;<br>
&gt;<br>
&gt; =A0 &lt;imdn xmlns=3D&quot;urn:ietf:params:xml:ns:imdn&quot;&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 &lt;message-id&gt;34jk324j&lt;/message-id&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 &lt;datetime&gt;2008-04-04T12:16:49-05:00&lt;/datetime=
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0&lt;recipient-uri&gt;<a href=3D"mailto:im%3Abob@example=
.com">im:bob@example.com</a>&lt;/recipient-uri&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 &lt;original-recipient-uri<br>
&gt;<br>
&gt;&gt; <a href=3D"mailto:im%3Abob@example.com">im:bob@example.com</a>&lt;=
/original-recipient-uri&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 &lt;delivery-notification&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0&lt;status&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 &lt;delivered/&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0&lt;/status&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 &lt;/delivery-notification&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 &lt;/imdn&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =A0 --imdn-boundary<br>
&gt;<br>
&gt; =A0 Content-type: message/imdn+xml<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =A0 &lt;?xml version=3D&quot;1.0&quot; encoding=3D&quot;UTF-8&quot;?&g=
t;<br>
&gt;<br>
&gt; =A0 &lt;imdn xmlns=3D&quot;urn:ietf:params:xml:ns:imdn&quot;&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 &lt;message-id&gt;34jk324j&lt;/message-id&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 &lt;datetime&gt;2008-04-04T12:16:49-05:00&lt;/datetime=
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0&lt;recipient-uri&gt;<a href=3D"mailto:im%3Abob@example=
.com">im:bob@example.com</a>&lt;/recipient-uri&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 &lt;original-recipient-uri<br>
&gt;<br>
&gt;&gt; <a href=3D"mailto:im%3Abob@example.com">im:bob@example.com</a>&lt;=
/original-recipient-uri&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 &lt;display-notification&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0&lt;status&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 &lt;displayed/&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0&lt;/status&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 &lt;/display-notification&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 &lt;/imdn&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =A0 --imdn-boundary--<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Notes<br>
&gt; -----<br>
&gt; The last multipart MIME boundary should have a &quot;--&quot; at the e=
nd. In the above example it should be &quot;--imdn-boundary--&quot; instead=
 of &quot;--imdn-boundary&quot;<br>
&gt;<br>
&gt; Instructions:<br>
&gt; -------------<br>
&gt; This errata is currently posted as &quot;Reported&quot;. If necessary,=
 please<br>
&gt; use &quot;Reply All&quot; to discuss whether it should be verified or<=
br>
&gt; rejected. When a decision is reached, the verifying party (IESG)<br>
&gt; can log in to change the status and edit the report, if necessary.<br>
&gt;<br>
&gt; --------------------------------------<br>
&gt; RFC5438 (draft-ietf-simple-imdn-10)<br>
&gt; --------------------------------------<br>
&gt; Title =A0 =A0 =A0 =A0 =A0 =A0 =A0 : Instant Message Disposition Notifi=
cation (IMDN)<br>
&gt; Publication Date =A0 =A0: February 2009<br>
&gt; Author(s) =A0 =A0 =A0 =A0 =A0 : E. Burger, H. Khartabil<br>
&gt; Category =A0 =A0 =A0 =A0 =A0 =A0: PROPOSED STANDARD<br>
&gt; Source =A0 =A0 =A0 =A0 =A0 =A0 =A0: SIP for Instant Messaging and Pres=
ence Leveraging Extensions<br>
&gt; Area =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0: Real-time Applications and Infra=
structure<br>
&gt; Stream =A0 =A0 =A0 =A0 =A0 =A0 =A0: IETF<br>
&gt; Verifying Party =A0 =A0 : IESG<br>
<br>
</div></div></blockquote></div><br></div></div>

--089e013d0db0acc86c04ee879d6b--