[Simple] [Errata Verified] RFC5438 (3850)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 27 December 2013 17:42 UTC
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
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
- [Simple] [Editorial Errata Reported] RFC5438 (385… RFC Errata System
- Re: [Simple] [Editorial Errata Reported] RFC5438 … Eric Burger
- [Simple] [Errata Verified] RFC5438 (3850) RFC Errata System
- Re: [Simple] [Editorial Errata Reported] RFC5438 … Richard Barnes