Re: [Editorial Errata Reported] RFC5438 (3850)

Eric Burger <[email protected]> Thu, 26 Dec 2013 08:17:09 -0500
Newsgroups gmane.ietf.simple
Message-ID <[email protected]>
--===============4226180993252943691==
Content-Type: multipart/signed; boundary="Apple-Mail=_D1A0AF29-8835-401C-8A87-C1A739851EC5"; protocol="application/pgp-signature"; micalg=pgp-sha1


--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 =
<[email protected]> 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 <[email protected]>
>=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:[email protected]>
>=20
>   To: Alice <im:[email protected]>
>=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:[email protected]</recipient-uri>
>=20
>         <original-recipient-uri
>=20
>> im:[email protected]</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:[email protected]</recipient-uri>
>=20
>         <original-recipient-uri
>=20
>> im:[email protected]</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:[email protected]>
>=20
>   To: Alice <im:[email protected]>
>=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:[email protected]</recipient-uri>
>=20
>         <original-recipient-uri
>=20
>> im:[email protected]</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:[email protected]</recipient-uri>
>=20
>         <original-recipient-uri
>=20
>> im:[email protected]</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--

--===============4226180993252943691==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Simple mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/simple

--===============4226180993252943691==--