Re: [APPS-REVIEW] Review request: draft-saintandre-jabberid-05.txt

Dave Cridland <dave@cridland.net> Fri, 24 August 2007 08:20 UTC

Return-path: <apps-review-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IOUPQ-000243-Qk; Fri, 24 Aug 2007 04:20:48 -0400
Received: from apps-review by megatron.ietf.org with local (Exim 4.43) id 1IOUPP-00023x-RJ for apps-review-confirm+ok@megatron.ietf.org; Fri, 24 Aug 2007 04:20:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IOUPM-00023o-32 for apps-review@ietf.org; Fri, 24 Aug 2007 04:20:44 -0400
Received: from [2001:838:378:0:2a0:d2ff:fe1b:110f] (helo=turner.dave.cridland.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IOUPL-0001vB-D8 for apps-review@ietf.org; Fri, 24 Aug 2007 04:20:44 -0400
Received: from peirce.dave.cridland.net ([217.155.137.61]) by turner.dave.cridland.net (submission) via TCP with ESMTPA id <Rs6UyQAQZgNx@turner.dave.cridland.net>; Fri, 24 Aug 2007 09:20:25 +0100
Subject: Re: [APPS-REVIEW] Review request: draft-saintandre-jabberid-05.txt
References: <83DD181D-232B-4899-84E6-0511F3053D0A@osafoundation.org> <29508.1187911522.450213@peirce.dave.cridland.net> <1187916766.3689.19.camel@scott.skrb.org>
In-Reply-To: <1187916766.3689.19.camel@scott.skrb.org>
MIME-Version: 1.0
Message-Id: <29508.1187943624.576748@peirce.dave.cridland.net>
Date: Fri, 24 Aug 2007 09:20:24 +0100
From: Dave Cridland <dave@cridland.net>
To: Scott Lawrence <scott@skrb.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: Applications Review List <apps-review@ietf.org>
X-BeenThere: apps-review@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Applications Review List <apps-review.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/apps-review>, <mailto:apps-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/apps-review>
List-Post: <mailto:apps-review@ietf.org>
List-Help: <mailto:apps-review-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/apps-review>, <mailto:apps-review-request@ietf.org?subject=subscribe>
Errors-To: apps-review-bounces@ietf.org

On Fri Aug 24 01:52:46 2007, Scott Lawrence wrote:
> There are any number of possible 'other identifiers' that might be
> included in email (or HTTP or SIP) headers to identify the sender.  
> I
> suspect that identifiers for use in different protocols will all be
> URIs, which implies that they contain a scheme that identifies the
> protocol.  If there is a need for an email header that identifies an
> 'other identifier', then it seems to me that it would be better to 
> make
> it just that and let the scheme define the protocol.  Specify it 
> such
> that it can have multiple values:
> 
>  From-Alt-Uri: sip:scott@example.com, xmpp:scott@jabber.example.com
> 
> This seems more flexible and cleaner than defining a new header for 
> each
> possible identifier type just so that the scheme can be implied for 
> the
> type.

Absolutely - without this discussion, I can't really back Proposed 
Standard. However, Jabber-Id is a deployed mechanism, so it needs 
publication as-is. Therefore I'd say Informational.

FWIW, another point occured to me - which From address does this 
information pertain to? (Technically, a message may have multiple 
 From addresses. Perhaps this specification, and any From-Alt-Uri 
specification, should stipulate it's the Sender, not the From.)

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@jabber.org
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade


_______________________________________________
APPS-REVIEW mailing list
APPS-REVIEW@ietf.org
https://www1.ietf.org/mailman/listinfo/apps-review