Re: [Simple] [Editorial Errata Reported] RFC5438 (3850)

Eric Burger <eburger@standardstrack.com> Thu, 26 December 2013 13:17 UTC

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

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