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

"Frank Ellermann" <nobody@xyzzy.claranet.de> Tue, 06 November 2007 21:35 UTC

Return-path: <ietf-message-headers-bounces@ietf.org>
Received: from [] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpW5L-0004sK-Pp; Tue, 06 Nov 2007 16:35:47 -0500
Received: from ietf-message-headers by megatron.ietf.org with local (Exim 4.43) id 1IpW5K-0004sA-Jq for ietf-message-headers-confirm+ok@megatron.ietf.org; Tue, 06 Nov 2007 16:35:46 -0500
Received: from [] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpW5K-0004s2-AD for ietf-message-headers@lists.ietf.org; Tue, 06 Nov 2007 16:35:46 -0500
Received: from main.gmane.org ([] helo=ciao.gmane.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IpW5G-0000Pn-2j for ietf-message-headers@lists.ietf.org; Tue, 06 Nov 2007 16:35:46 -0500
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IpW52-0005Lf-HE for ietf-message-headers@lists.ietf.org; Tue, 06 Nov 2007 21:35:28 +0000
Received: from c-134-89-5.hh.dial.de.ignite.net ([]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf-message-headers@lists.ietf.org>; Tue, 06 Nov 2007 21:35:28 +0000
Received: from nobody by c-134-89-5.hh.dial.de.ignite.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf-message-headers@lists.ietf.org>; Tue, 06 Nov 2007 21:35:28 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: ietf-message-headers@lists.ietf.org
From: "Frank Ellermann" <nobody@xyzzy.claranet.de>
Date: Tue, 6 Nov 2007 22:34:57 +0100
Organization: <http://purl.net/xyzzy>
Lines: 68
Message-ID: <fgqmme$491$1@ger.gmane.org>
References: <47308BA7.3080204@stpeter.im> <fgq9pj$ksq$1@ger.gmane.org> <4730C881.4040101@stpeter.im>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: c-134-89-5.hh.dial.de.ignite.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1914
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: ietf@ietf.org
Subject: [Ietf-message-headers] Re: Re:I-DAction:draft-saintandre-header-pres-00.txt
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
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>
Errors-To: ietf-message-headers-bounces@ietf.org

Peter Saint-Andre wrote:

>> 1 - why two drafts instead of one ?
> Because some people consider IM and presence to be fully separable
> features, which is why we have both the pres: and im: URI schemes

Two schemes with a semantics somewhere between about: and file: ...
if I am interested in pres:juliet@example.com, can say Psi help me ?

>> 2 - who wants to publish pres URIs in email headers ?
> Presumably people who want to show presence icons next to the names
> of message authors.

Okay, but Gmail can manage that without a fancy Pres-ID: mail header
field.  I also don't quite believe in this separation "feature".

>> 3 - what about Netnews ?
> Yes, I added that in version -01 this morning (not yet submitted)


>> 4 - what's going on with the nice jabberid draft ?
> That is still to be determined.

You've now demonstrated your good will wrt im: and pres:, after
that exercise please let's continue with the jabberid.  It was
almost perfect, "experimental" status is also okay.

>> 5 - jabberid had an interesting IRI example, the new
>>     drafts claim that juliet@example.com is an URI.
> For good or for ill, the pres: and im: URI schemes reuse the 
> "mailbox" construct from RFC 2822. Or something like that

For ill, they imitate mailto:.  But what I meant in (5) was a
syntactical nit, juliet@example.com is no URI, you forgot the
scheme, as in im:juliet@example.com

> In any case non-US-ASCII characters would need to be handled
> as is traditional in email systems, as far as I can see.

"mailto-ter" (my name for a successor of mailto-bis supporting
EAI) is a _very_ hard case.  And mailto-bis is also a _very_
hard case.  Don't hold your breath.

IFF mailto-bis survives a Last Call, and IFF im/pres follow
suite, and IFF 2822bis reduces its NO-WS-CTL horrors, and IFF
EAI reaches "experimental", then might be a good time to look
at im/pres again.  

>> 6 - I've never seen a pres: URI outside of RFC 3859,
>>     why should I wish to see this in a mail header ?
> Because it is a more generic solution.

Okay, I've to check if Psi has a "be more generic" option :-)

> http://www.iana.org/assignments/im-srv-labels

Some SRV magic, does it work wrt xmpp ?  Apparently there
is no _xmpp.stpeter.im.  "SRV" is still a mystery for me.

>> if I recall discussions with Paul and Martin on the
>> URI list about RFC 2368 (mailto) correctly. 
> I do not recall that discussion.

<http://article.gmane.org/gmane.org.w3c.uri/578>  Sorry,
it was Bruce and Paul, Matin was in other mailto-threads.


Ietf-message-headers mailing list