Re: [apps-discuss] I-D Action: draft-ietf-appsawg-acct-uri-05.txt

"Markus Lanthaler" <markus.lanthaler@gmx.net> Tue, 02 July 2013 09:01 UTC

Return-Path: <markus.lanthaler@gmx.net>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0B9C11E8433 for <apps-discuss@ietfa.amsl.com>; Tue, 2 Jul 2013 02:01:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.15
X-Spam-Level:
X-Spam-Status: No, score=-1.15 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dPJR7IAol7bZ for <apps-discuss@ietfa.amsl.com>; Tue, 2 Jul 2013 02:01:26 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id 62DC111E843E for <apps-discuss@ietf.org>; Tue, 2 Jul 2013 02:01:26 -0700 (PDT)
Received: from Vostro3500 ([178.115.248.36]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MN1Gu-1UrjXn3NaS-006eLr; Tue, 02 Jul 2013 11:01:24 +0200
From: Markus Lanthaler <markus.lanthaler@gmx.net>
To: "'Paul E. Jones'" <paulej@packetizer.com>, apps-discuss@ietf.org
References: <20130617205341.15641.96770.idtracker@ietfa.amsl.com> <51BF786B.9060703@stpeter.im> <016d01ce767f$2ea45990$8bed0cb0$@lanthaler@gmx.net> <51D1C423.5000804@stpeter.im> <017801ce7686$afc9db60$0f5d9220$@lanthaler@gmx.net> <044d01ce76c4$4f133710$ed39a530$@packetizer.com>
In-Reply-To: <044d01ce76c4$4f133710$ed39a530$@packetizer.com>
Date: Tue, 02 Jul 2013 11:01:21 +0200
Message-ID: <010901ce7702$ba7283b0$2f578b10$@lanthaler>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQJV0E+HeqM9oFCI0wWnOEzauIjbLQFZvmQ1AgGRSyQChFqCswFTtRQ8mAhImyCAAH+ZEA==
Content-Language: de
X-Provags-ID: V03:K0:B1IbRlgiDcpWIZoXk2PgML+BuC88RAQ44+Wq42CTYtwNxiP7Eys mOGWJ0Br7ioj6kUJ2UyoHmzHC35ltkkfnC3FHL3D4zBU33xpYiojfHon1fXlO3o4sdaEvQ3 FHmmZqsNVOC2i4QiVin4adIzDqD1VD98xAtGX6jiU5Jh4zu0y3BUMESoKQsrUabI+9B7Bk9 2xZAwk+pBdmJb5XmA9hLA==
Subject: Re: [apps-discuss] I-D Action: draft-ietf-appsawg-acct-uri-05.txt
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jul 2013 09:01:32 -0000

On Tuesday, July 02, 2013 3:35 AM, Paul E. Jones wrote:
> Wherever the acct URI is used, I would assume a human initially provided
the
> URI (directly or indirectly via a simple "user@domain" entry).  How would
> the human user know any date associated with an account?

I'm not so sure about that, but in any case, why not simply use the current
date when the user enters the acct URI? That way the system would know once
for all that the user meant the account that was valid at that point in
time.


> I think recycling account identifiers is a "bad thing".  Set aside the
acct
> URI scheme itself for a minute.  Just imagine some prospective employer
> performing a search one day for some Yahoo! user ID and discovering all
> kinds of nasty things posted on the web several years ago by the previous
> owner of that account.  The new owner might lose an opportunity for
> employment.

True, but if a date would have been used there as well it would be possible
to distinguish the two accounts.


> Having a date as a part of any user identifier might help, but it is a
> little difficult for the average person to use.  Could you imagine if all
> account IDs looked like paulej.20130701@packetizer.com?

What about paulej@packetizer.com?date=20130701

Is that still too difficult? The date wouldn't have to be necessary though.
A user can simply type in paulej@packetizer.com and the system adds the
current date automatically.



--
Markus Lanthaler
@markuslanthaler