Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt

Peter Saint-Andre <stpeter@stpeter.im> Wed, 07 November 2007 23:47 UTC

Return-path: <ietf-message-headers-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpucW-0004Er-UD; Wed, 07 Nov 2007 18:47:40 -0500
Received: from ietf-message-headers by megatron.ietf.org with local (Exim 4.43) id 1IpucV-00048J-GJ for ietf-message-headers-confirm+ok@megatron.ietf.org; Wed, 07 Nov 2007 18:47:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpucV-00046u-5Z for ietf-message-headers@lists.ietf.org; Wed, 07 Nov 2007 18:47:39 -0500
Received: from dizzyd.com ([207.210.219.225]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IpucS-0007b6-I6 for ietf-message-headers@lists.ietf.org; Wed, 07 Nov 2007 18:47:39 -0500
Received: from roundabout.local (dencfw1.jabber.com [207.182.164.5]) (Authenticated sender: stpeter) by dizzyd.com (Postfix) with ESMTP id BF04640081; Wed, 7 Nov 2007 16:47:35 -0700 (MST)
Message-ID: <47324EF1.4000505@stpeter.im>
Date: Wed, 07 Nov 2007 16:49:05 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt
References: <47308BA7.3080204@stpeter.im> <fgq9pj$ksq$1@ger.gmane.org> <4730C881.4040101@stpeter.im> <6.2.5.6.2.20071106124213.03069a38@resistor.net> <47318BC3.7050009@stpeter.im> <6.2.5.6.2.20071107081447.03037770@resistor.net>
In-Reply-To: <6.2.5.6.2.20071107081447.03037770@resistor.net>
X-Enigmail-Version: 0.95.5
OpenPGP: id=7BBD0573; url=http://www.saint-andre.com/me/stpeter.asc
Jabber-ID: stpeter@jabber.org
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 140baa79ca42e6b0e2b4504291346186
Cc: ietf-message-headers@lists.ietf.org, ietf@ietf.org
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0251407960=="
Errors-To: ietf-message-headers-bounces@ietf.org

SM wrote:
> At 01:56 07-11-2007, Peter Saint-Andre wrote:

>> I'm not sure what you mean by "feature". According to RFC 2779, IM and
>> presence are separate domains of functionality, which is why there is an
>> im: URI scheme and a pres: URI scheme. I don't foresee other such URIs.
> 
> Quoting the drafts:
> 
>    Because almost all human users of instant messaging systems are users
>    of email systems, it can be helpful for such users to specify their
>    (IM/presence) URIs in the email messages they author.
> 
> Although IM and presence are separate domains of functionality, the
> proposed mail headers for them :-
> 
>   1. provides a standard location for the exchange of such information
> 
>   2. are associated with the author of the message
> 
>   3. uses similar syntax for the URI
> 
>> What are "these schemes"? What is the category under which it is
>> perceived that the im: scheme and the pres: scheme are the same? Again,
>> according to RFC 2779, RFC 3859, and RFC 3860, these are separate and
>> distinct domains of functionality, which just happen to often be
>> implemented and deployed in the same systems or services.
> 
> You are viewing the im: scheme and the pres: scheme from the point of
> view of their RFCs which is different from the functionality offered by
> the mail header.  In a previous email, you mentioned a generic
> solution.  My point is that it is better to have a generic mail header
> to encompass pres:, im: and other schemes that would use URIs in such a
> manner.
> 
> We could have, for example, the following header:
> 
> Contact-ID: pres:juliet@example.com; im:juliet@example.com
> 
> The MUA would process the header to determine whether there is a
> presence URI or IM URI and take appropriate action.

But what is a Contact-ID? Any means by which you could contact me might
be included in that category -- email, telephone, voicemail, fax, post
office box, various IM addresses, IRC channels where I hang out, etc.

And in fact a pres: URI does not provide a means of contact. It provides
a way for you to know about my network availability, but you can't
communicate with me via that URI, so it's not a Contact-ID at all.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/

_______________________________________________
Ietf-message-headers mailing list
Ietf-message-headers@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-message-headers