Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt
Peter Saint-Andre <stpeter@stpeter.im> Tue, 06 November 2007 20:01 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-0001DB-2R; Tue, 06 Nov 2007 15:01:56 -0500
Received: from ietf-message-headers by megatron.ietf.org with local (Exim 4.43) id 1IpUcT-0001Cu-Hc for ietf-message-headers-confirm+ok@megatron.ietf.org; Tue, 06 Nov 2007 15:01:53 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpUcT-0001Bc-5I for ietf-message-headers@lists.ietf.org; Tue, 06 Nov 2007 15:01:53 -0500
Received: from dizzyd.com ([207.210.219.225]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IpUcP-00062C-3j for ietf-message-headers@lists.ietf.org; Tue, 06 Nov 2007 15:01:53 -0500
Received: from wrk225.corp.jabber.com (dencfw1.jabber.com [207.182.164.5]) (Authenticated sender: stpeter) by dizzyd.com (Postfix) with ESMTP id 57E3E40081; Tue, 6 Nov 2007 13:01:48 -0700 (MST)
Message-ID: <4730C881.4040101@stpeter.im>
Date: Tue, 06 Nov 2007 13:03:13 -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.6) Gecko/20070728 Thunderbird/2.0.0.6 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
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>
In-Reply-To: <fgq9pj$ksq$1@ger.gmane.org>
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: 1.5 (+)
X-Scan-Signature: 17bdfcaea25d1444baef0e24abc38874
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="===============1129557405=="
Errors-To: ietf-message-headers-bounces@ietf.org
Frank Ellermann wrote: > Peter Saint-Andre wrote on the message-headers list: > >> FYI > > Thanks. Frankly, I hate these drafts. Great! Honest feedback is appreciated and agreement is overrated. :) > 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 (as defined in RFCs 3859 and 3860 respectively). See also RFC 2779. > 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. > 3 - what about Netnews ? Yes, I added that in version -01 this morning (not yet submitted): http://svn.xmpp.org:18080/browse/XMPP/trunk/internet-drafts/draft-saintandre-header-pres-01.xml?r1=1337&r2=1339 > 4 - what's going on with the nice jabberid draft ? That is still to be determined. > 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 -- I asked about it once on the SIMPLE WG list but never received a reply, so the exact meaning is unclear to me: http://www1.ietf.org/mail-archive/web/simple/current/msg07163.html In any case non-US-ASCII characters would need to be handled as is traditional in email systems, as far as I can see. > 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. > 7 - the jabberid was obviously about xmpp:, what are > im: and pres: about ? Any instant messaging and presence technology, as registered with the IANA: http://www.iana.org/assignments/im-srv-labels http://www.iana.org/assignments/pres-srv-labels Oddly, the only registered technology is XMPP. But other technologies could be registered (and I presume that the lack of a SIP registration is merely an oversight). > 8 - RFC 3859 still uses RFC 2396 syntax on top of a > RFC 2822 <mailbox>. That's known to be wrong if > I recall discussions with Paul and Martin on the > URI list about RFC 2368 (mailto) correctly. I do not recall that discussion. But, as mentioned, I do admit to being confused about the exact syntax of the pres: and im: URI schemes. > 9 - Likewise RFC 3860. I hope you're not trying to > move vCards piecemeal into mail header fields. By no means. I am trying to address feedback received during the Last Call on draft-saintandre-jabberid. Part of that feedback raised the issue of working on a more generic solution that is not tied to a specific instant messaging and presence technology (in this case, XMPP). These I-Ds are my good-faith attempt at fulfilling my promise to work on a more generic solution. > Frank > > Cc: general list, after all jabberid was Last Called. Fair enough, I retain the cc. 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
- [Ietf-message-headers] [Fwd: I-D Action:draft-sai… Peter Saint-Andre
- [Ietf-message-headers] Re: I-DAction:draft-sainta… Frank Ellermann
- Re: [Ietf-message-headers] Re: I-DAction:draft-sa… Peter Saint-Andre
- [Ietf-message-headers] Re: Re:I-DAction:draft-sai… Frank Ellermann
- Re: [Ietf-message-headers] Re: Re:I-DAction:draft… Peter Saint-Andre
- Re: [Ietf-message-headers] Re: I-DAction:draft-sa… Peter Saint-Andre
- Re: [Ietf-message-headers] Re: I-DAction:draft-sa… Peter Saint-Andre
- Re: [Ietf-message-headers] Re: I-DAction:draft-sa… SM
- Re: [Ietf-message-headers] Re: I-DAction:draft-sa… Peter Saint-Andre
- [Ietf-message-headers] Re: I-DAction:draft-sainta… Frank Ellermann
- Re: [Ietf-message-headers] Re: I-DAction:draft-sa… SM
- Re: [Ietf-message-headers] Re: I-DAction:draft-sa… Sam Hartman
- Re: [Ietf-message-headers] Re: I-DAction:draft-sa… Alexey Melnikov
- Re: [Ietf-message-headers] Re: I-DAction:draft-sa… Peter Saint-Andre
- Re: [Ietf-message-headers] Re: I-DAction:draft-sa… Cullen Jennings
- Re: [Ietf-message-headers] Re: I-DAction:draft-sa… Cullen Jennings
- [Ietf-message-headers] draft-saintandre-header-pr… Bruce Lilly
- [Ietf-message-headers] Re: draft-saintandre-heade… Peter Saint-Andre
- Re: [Ietf-message-headers] Re: draft-saintandre-h… Bruce Lilly
- Re: [Ietf-message-headers] Re: draft-saintandre-h… Peter Saint-Andre
- [Ietf-message-headers] Re: draft-saintandre-heade… Frank Ellermann
- Re: [Ietf-message-headers] Re: draft-saintandre-h… Peter Saint-Andre
- [Ietf-message-headers] Re: draft-saintandre-heade… Frank Ellermann