Re: [Editorial Errata Reported] RFC5438 (3850)
Richard Barnes <[email protected]> Fri, 27 Dec 2013 12:42:20 -0500
| Newsgroups | gmane.ietf.simple |
|---|---|
| Message-ID | <CAL02cgRCViRekRixeGBEgmE397rQ_gnbNXxbVsiPcGSbzgQWew@mail.gmail.com> |
--===============0409108297136338840== Content-Type: multipart/alternative; boundary=089e013d0db0acc86c04ee879d6b --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 <[email protected]>wrote: > 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)". > > > > -------------------------------------- > > 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 <[email protected]> > > > > 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:[email protected]> > > > > To: Alice <im:[email protected]> > > > > 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:[email protected]</recipient-uri> > > > > <original-recipient-uri > > > >> im:[email protected]</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:[email protected]</recipient-uri> > > > > <original-recipient-uri > > > >> im:[email protected]</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:[email protected]> > > > > To: Alice <im:[email protected]> > > > > 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:[email protected]</recipient-uri> > > > > <original-recipient-uri > > > >> im:[email protected]</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:[email protected]</recipient-uri> > > > > <original-recipient-uri > > > >> im:[email protected]</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"><<a href=3D"mailto:eburger@stand= ardstrack.com" target=3D"_blank">[email protected]</a>></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 <<a href=3D"mailto:rfc-ed= [email protected]">[email protected]</a>> wrote:<br> <br> > The following errata report has been submitted for RFC5438,<br> > "Instant Message Disposition Notification (IMDN)".<br> ><br> > --------------------------------------<br> > You may review the report below and at:<br> > <a href=3D"http://www.rfc-editor.org/errata_search.php?rfc=3D5438&= eid=3D3850" target=3D"_blank">http://www.rfc-editor.org/errata_search.php?r= fc=3D5438&eid=3D3850</a><br> ><br> > --------------------------------------<br> > Type: Editorial<br> > Reported by: Niket Kumar <<a href=3D"mailto:[email protected]">= [email protected]</a>><br> ><br> > Section: 8.3<br> ><br> > Original Text<br> > -------------<br> > =A0 The aggregated IMDN is constructed using the multipart/mixed MIME<= br> ><br> > =A0 type and including as individual payloads all the IMDNS that were<= br> ><br> > =A0 received as message/imdn+xml.<br> ><br> ><br> ><br> > =A0 Below is an example of aggregated IMDNs.<br> ><br> ><br> ><br> > =A0 From: Bob <<a href=3D"mailto:im%[email protected]">im:bob@examp= le.com</a>><br> ><br> > =A0 To: Alice <<a href=3D"mailto:im%[email protected]">im:alice@e= xample.com</a>><br> ><br> > =A0 NS: imdn <urn:ietf:params:imdn><br> ><br> > =A0 imdn.Message-ID: d834jied93rf<br> ><br> > =A0 Content-type: multipart/mixed;<br> ><br> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0boundary=3D"imdn-bound= ary"<br> ><br> > =A0 Content-Disposition: notification<br> ><br> > =A0 Content-length: ...<br> ><br> ><br> ><br> > =A0 --imdn-boundary<br> ><br> > =A0 Content-type: message/imdn+xml<br> ><br> ><br> ><br> > =A0 <?xml version=3D"1.0" encoding=3D"UTF-8"?&g= t;<br> ><br> > =A0 <imdn xmlns=3D"urn:ietf:params:xml:ns:imdn"><br> ><br> > =A0 =A0 =A0 =A0 <message-id>34jk324j</message-id><br> ><br> > =A0 =A0 =A0 =A0 <datetime>2008-04-04T12:16:49-05:00</datetime= ><br> ><br> > =A0 =A0 =A0 =A0<recipient-uri><a href=3D"mailto:im%3Abob@example= .com">im:[email protected]</a></recipient-uri><br> ><br> > =A0 =A0 =A0 =A0 <original-recipient-uri<br> ><br> >> <a href=3D"mailto:im%[email protected]">im:[email protected]</a><= /original-recipient-uri><br> ><br> > =A0 =A0 =A0 =A0 <delivery-notification><br> ><br> > =A0 =A0 =A0 =A0 =A0 =A0<status><br> ><br> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 <delivered/><br> ><br> > =A0 =A0 =A0 =A0 =A0 =A0</status><br> ><br> > =A0 =A0 =A0 =A0 </delivery-notification><br> ><br> > =A0 =A0 =A0 </imdn><br> ><br> ><br> ><br> > =A0 --imdn-boundary<br> ><br> > =A0 Content-type: message/imdn+xml<br> ><br> ><br> ><br> > =A0 <?xml version=3D"1.0" encoding=3D"UTF-8"?&g= t;<br> ><br> > =A0 <imdn xmlns=3D"urn:ietf:params:xml:ns:imdn"><br> ><br> > =A0 =A0 =A0 =A0 <message-id>34jk324j</message-id><br> ><br> > =A0 =A0 =A0 =A0 <datetime>2008-04-04T12:16:49-05:00</datetime= ><br> ><br> > =A0 =A0 =A0 =A0<recipient-uri><a href=3D"mailto:im%3Abob@example= .com">im:[email protected]</a></recipient-uri><br> ><br> > =A0 =A0 =A0 =A0 <original-recipient-uri<br> ><br> >> <a href=3D"mailto:im%[email protected]">im:[email protected]</a><= /original-recipient-uri><br> ><br> > =A0 =A0 =A0 =A0 <display-notification><br> ><br> > =A0 =A0 =A0 =A0 =A0 =A0<status><br> ><br> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 <displayed/><br> ><br> > =A0 =A0 =A0 =A0 =A0 =A0</status><br> ><br> > =A0 =A0 =A0 =A0 </display-notification><br> ><br> > =A0 =A0 =A0 </imdn><br> ><br> ><br> ><br> > =A0 --imdn-boundary<br> ><br> ><br> ><br> > Corrected Text<br> > --------------<br> > =A0 The aggregated IMDN is constructed using the multipart/mixed MIME<= br> ><br> > =A0 type and including as individual payloads all the IMDNS that were<= br> ><br> > =A0 received as message/imdn+xml.<br> ><br> ><br> ><br> > =A0 Below is an example of aggregated IMDNs.<br> ><br> ><br> ><br> > =A0 From: Bob <<a href=3D"mailto:im%[email protected]">im:bob@examp= le.com</a>><br> ><br> > =A0 To: Alice <<a href=3D"mailto:im%[email protected]">im:alice@e= xample.com</a>><br> ><br> > =A0 NS: imdn <urn:ietf:params:imdn><br> ><br> > =A0 imdn.Message-ID: d834jied93rf<br> ><br> > =A0 Content-type: multipart/mixed;<br> ><br> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0boundary=3D"imdn-bound= ary"<br> ><br> > =A0 Content-Disposition: notification<br> ><br> > =A0 Content-length: ...<br> ><br> ><br> ><br> > =A0 --imdn-boundary<br> ><br> > =A0 Content-type: message/imdn+xml<br> ><br> ><br> ><br> > =A0 <?xml version=3D"1.0" encoding=3D"UTF-8"?&g= t;<br> ><br> > =A0 <imdn xmlns=3D"urn:ietf:params:xml:ns:imdn"><br> ><br> > =A0 =A0 =A0 =A0 <message-id>34jk324j</message-id><br> ><br> > =A0 =A0 =A0 =A0 <datetime>2008-04-04T12:16:49-05:00</datetime= ><br> ><br> > =A0 =A0 =A0 =A0<recipient-uri><a href=3D"mailto:im%3Abob@example= .com">im:[email protected]</a></recipient-uri><br> ><br> > =A0 =A0 =A0 =A0 <original-recipient-uri<br> ><br> >> <a href=3D"mailto:im%[email protected]">im:[email protected]</a><= /original-recipient-uri><br> ><br> > =A0 =A0 =A0 =A0 <delivery-notification><br> ><br> > =A0 =A0 =A0 =A0 =A0 =A0<status><br> ><br> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 <delivered/><br> ><br> > =A0 =A0 =A0 =A0 =A0 =A0</status><br> ><br> > =A0 =A0 =A0 =A0 </delivery-notification><br> ><br> > =A0 =A0 =A0 </imdn><br> ><br> ><br> ><br> > =A0 --imdn-boundary<br> ><br> > =A0 Content-type: message/imdn+xml<br> ><br> ><br> ><br> > =A0 <?xml version=3D"1.0" encoding=3D"UTF-8"?&g= t;<br> ><br> > =A0 <imdn xmlns=3D"urn:ietf:params:xml:ns:imdn"><br> ><br> > =A0 =A0 =A0 =A0 <message-id>34jk324j</message-id><br> ><br> > =A0 =A0 =A0 =A0 <datetime>2008-04-04T12:16:49-05:00</datetime= ><br> ><br> > =A0 =A0 =A0 =A0<recipient-uri><a href=3D"mailto:im%3Abob@example= .com">im:[email protected]</a></recipient-uri><br> ><br> > =A0 =A0 =A0 =A0 <original-recipient-uri<br> ><br> >> <a href=3D"mailto:im%[email protected]">im:[email protected]</a><= /original-recipient-uri><br> ><br> > =A0 =A0 =A0 =A0 <display-notification><br> ><br> > =A0 =A0 =A0 =A0 =A0 =A0<status><br> ><br> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 <displayed/><br> ><br> > =A0 =A0 =A0 =A0 =A0 =A0</status><br> ><br> > =A0 =A0 =A0 =A0 </display-notification><br> ><br> > =A0 =A0 =A0 </imdn><br> ><br> ><br> ><br> > =A0 --imdn-boundary--<br> ><br> ><br> ><br> > Notes<br> > -----<br> > The last multipart MIME boundary should have a "--" at the e= nd. In the above example it should be "--imdn-boundary--" instead= of "--imdn-boundary"<br> ><br> > Instructions:<br> > -------------<br> > This errata is currently posted as "Reported". If necessary,= please<br> > use "Reply All" to discuss whether it should be verified or<= br> > rejected. When a decision is reached, the verifying party (IESG)<br> > can log in to change the status and edit the report, if necessary.<br> ><br> > --------------------------------------<br> > RFC5438 (draft-ietf-simple-imdn-10)<br> > --------------------------------------<br> > Title =A0 =A0 =A0 =A0 =A0 =A0 =A0 : Instant Message Disposition Notifi= cation (IMDN)<br> > Publication Date =A0 =A0: February 2009<br> > Author(s) =A0 =A0 =A0 =A0 =A0 : E. Burger, H. Khartabil<br> > Category =A0 =A0 =A0 =A0 =A0 =A0: PROPOSED STANDARD<br> > Source =A0 =A0 =A0 =A0 =A0 =A0 =A0: SIP for Instant Messaging and Pres= ence Leveraging Extensions<br> > Area =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0: Real-time Applications and Infra= structure<br> > Stream =A0 =A0 =A0 =A0 =A0 =A0 =A0: IETF<br> > Verifying Party =A0 =A0 : IESG<br> <br> </div></div></blockquote></div><br></div></div> --089e013d0db0acc86c04ee879d6b-- --===============0409108297136338840== 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 --===============0409108297136338840==--