[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Simple] <note> in IMDN



It for the IMDN to carry extra information about the IM. For example,
information on why it was not delivered.

   <?xml version="1.0" encoding="UTF-8"?>
   <imdn xlmns="urn:ietf:params:xml:ns:imdn">
      <message-id>34jk324j</message-id>
      <datetime>2006-04-04T12:16:49-05:00</datetime>
      <recipient-uri>im:bob at example.com <im%3Abob at example.com>
</recipient-uri>
      <original-recipient-uri>
          im:bob at example.com <im%3Abob at exFrom simple-bounces at ietf.org  Tue May 13 16:20:04 2008
Return-Path: <simple-bounces at ietf.org>
X-Original-To: simple-archive at megatron.ietf.org
Delivered-To: ietfarch-simple-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E845F3A67F1;
	Tue, 13 May 2008 16:20:04 -0700 (PDT)
X-Original-To: simple at core3.amsl.com
Delivered-To: simple at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3F8423A67F1
	for <simple at core3.amsl.com>; Tue, 13 May 2008 16:20:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id krYKL1-5uIiM for <simple at core3.amsl.com>;
	Tue, 13 May 2008 16:20:02 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.229])
	by core3.amsl.com (Postfix) with ESMTP id 2CECD3A67AF
	for <simple at ietf.org>; Tue, 13 May 2008 16:20:02 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so2974672rvf.49
	for <simple at ietf.org>; Tue, 13 May 2008 16:17:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	bh=eInDOaPyi4+ns9PBSWcVMZPU4Tv0XwGkUQ/D4cFUQP0=;
	b=IvuvCqikR254xlaNkpdkVA8N2ebXi6hbrXviJ5WIpk1zHMYsUhrUylqvebQHe8PdmYzebggGKQBYG6zkRHYJuYL8QCq73S9SB2QiSy6fAW2qa9b+SsFG42Vi5bH6z2kcQmPEVGVw1qT4jJfCF373XuhSX4lbtIWeZJGmajkc7wY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=gUk5Nd2SWMMUITuuuMrL7z5i8pVeHCY2MN6viH8sd4cqXkmKsmJ94KDiSGt1j7lBBwc6dupYQ9/ywzQnPTZ0tJo+nOiX1pbVaJYlLfmu+MeUdJ+3isFr2XM9ZxO32XeHZzU/EriceYhudVZBf6gNuKVFP98lQDA6eqZTAEc6hPQ=
Received: by 10.114.191.12 with SMTP id o12mr287893waf.224.1210720657718;
	Tue, 13 May 2008 16:17:37 -0700 (PDT)
Received: by 10.114.235.10 with HTTP; Tue, 13 May 2008 16:17:37 -0700 (PDT)
Message-ID: <66cd252f0805131617nc6b20daq939c08faf6af944e at mail.gmail.com>
Date: Wed, 14 May 2008 09:17:37 +1000
From: "Hisham Khartabil" <hisham.khartabil at gmail.com>
To: "Eric Burger" <eburger at standardstrack.com>
In-Reply-To: <B0E6B21A-140F-4F9A-9F28-533BD4085B4D at standardstrack.com>
MIME-Version: 1.0
References: <B0E6B21A-140F-4F9A-9F28-533BD4085B4D at standardstrack.com>
Cc: simple at ietf.org
Subject: Re: [Simple] <note> in IMDN
X-BeenThere: simple at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions
	<simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>,
	<mailto:simple-request at ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/simple>
List-Post: <mailto:simple at ietf.org>
List-Help: <mailto:simple-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>,
	<mailto:simple-request at ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1307531459=="
Sender: simple-bounces at ietf.org
Errors-To: simple-bounces at ietf.org
It for the IMDN to carry extra information about the IM. For example, information on why it was not delivered.
 
   <?xml version="1.0" encoding="UTF-8"?>
   <imdn xlmns="urn:ietf:params:xml:ns:imdn">
      <message-id>34jk324j</message-id>
      <datetime>2006-04-04T12:16:49-05:00</datetime>
      <recipient-uri>im:bob at example.com</recipient-uri>
      <original-recipient-uri>
          im:bob at example.com
      </original-recipient-uri>
      <disposition>
         <delivery/>
      </disposition>
      <status>
         <failed/>
      </status>
      <note lang="en">The IM could not be delivered due to network failure</note>
   </imdn>


 
On 13/05/2008, Eric Burger <eburger at standardstrack.com> wrote:
Why do we have a <note> field in an IMDN?

It cannot be for correlation, as the sender MUST have a Message-ID.

It cannot be for letting the user what the message is, because we are
talking about IMs here, not e-mails.

It cannot be for displaying status to the IM sender, because the IM
Recipient UA has no idea what the locale of the sender is and will
undoubtably use the wrong language and character set.

It could be used as a spam attack vector, but that would be silly of
us to build in to a protocol.

Does ANYONE object to simply taking out the field?
Does ANYONE want the field to be present?

Please respond to the list ASAP, as this document is WAY overdue.
_______________________________________________
Simple mailing list
Simple at ietf.org
https://www.ietf.org/mailman/listinfo/simple


On 13/05/2008, Eric Burger <eburger at standardstrack.com> wrote:
>
> Why do we have a <note> field in an IMDN?
>
> It cannot be for correlation, as the sender MUST have a Message-ID.
>
> It cannot be for letting the user what the message is, because we are
> talking about IMs here, not e-mails.
>
> It cannot be for displaying status to the IM sender, because the IM
> Recipient UA has no idea what the locale of the sender is and will
> undoubtably use the wrong language and character set.
>
> It could be used as a spam attack vector, but that would be silly of
> us to build in to a protocol.
>
> Does ANYONE object to simply taking out the field?
> Does ANYONE want the field to be present?
>
> Please respond to the list ASAP, as this document is WAY overdue.
> _______________________________________________
> Simple mailing list
> Simple at ietf.org
> https://www.ietf.org/mailman/listinfo/simple
>

------=_Part_9575_23330430.1210720657597
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>It for the IMDN to carry extra information about the IM. For example, information on why it was not delivered.</div>
<div>&nbsp;</div>
<div>&nbsp;&nbsp; &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;<br>&nbsp;&nbsp; &lt;imdn xlmns=&quot;urn:ietf:params:xml:ns:imdn&quot;&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;message-id&gt;34jk324j&lt;/message-id&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;datetime&gt;2006-04-04T12:16:49-05:00&lt;/datetime&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;recipient-uri&gt;<a href="mailto:im%3Abob at example.com">im:bob at example.com</a>&lt;/recipient-uri&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;original-recipient-uri&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href="mailto:im%3Abob at example.com">im:bob at example.com</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/original-recipient-uri&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;disposition&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;delivery/&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/disposition&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;status&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;failed/&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/status&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;note lang=&quot;en&quot;&gt;The IM could not be delivered due to network failure&lt;/note&gt;<br>
&nbsp;&nbsp; &lt;/imdn&gt;<br><br><br>&nbsp;</div>
<div><span class="gmail_quote">On 13/05/2008, <b class="gmail_sendername">Eric Burger</b> &lt;<a href="mailto:eburger at standardstrack.com">eburger at standardstrack.com</a>&gt; wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Why do we have a &lt;note&gt; field in an IMDN?<br><br>It cannot be for correlation, as the sender MUST have a Message-ID.<br>
<br>It cannot be for letting the user what the message is, because we are<br>talking about IMs here, not e-mails.<br><br>It cannot be for displaying status to the IM sender, because the IM<br>Recipient UA has no idea what the locale of the sender is and will<br>
undoubtably use the wrong language and character set.<br><br>It could be used as a spam attack vector, but that would be silly of<br>us to build in to a protocol.<br><br>Does ANYONE object to simply taking out the field?<br>
Does ANYONE want the field to be present?<br><br>Please respond to the list ASAP, as this document is WAY overdue.<br>_______________________________________________<br>Simple mailing list<br><a href="mailto:Simple at ietf.org">Simple at ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/simple";>https://www.ietf.org/mailman/listinfo/simple</a><br></blockquote></div><br>

------=_Part_9575_23330430.1210720657597--
_______________________________________________
Simple mailing list
Simple at ietf.org
https://www.ietf.org/mailman/listinfo/simple