Re: [apps-discuss] I-D Action: draft-ietf-appsawg-acct-uri-05.txt
"Markus Lanthaler" <markus.lanthaler@gmx.net> Mon, 01 July 2013 18:14 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 365A311E814E for <apps-discuss@ietfa.amsl.com>; Mon, 1 Jul 2013 11:14:01 -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=[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 yJaXuU5aS+sN for <apps-discuss@ietfa.amsl.com>; Mon, 1 Jul 2013 11:13:55 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id 1D31421F9A7D for <apps-discuss@ietf.org>; Mon, 1 Jul 2013 11:13:33 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.2]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MHJbp-1UyRZr3jdb-00E86u for <apps-discuss@ietf.org>; Mon, 01 Jul 2013 20:13:28 +0200
Received: (qmail invoked by alias); 01 Jul 2013 18:13:28 -0000
Received: from 178.115.248.36.wireless.dyn.drei.com (EHLO Vostro3500) [178.115.248.36] by mail.gmx.net (mp002) with SMTP; 01 Jul 2013 20:13:28 +0200
X-Authenticated: #419883
X-Provags-ID: V01U2FsdGVkX1/4KSx5R5P4nRKmnRKCuGxACd38SqM6DZvFGp1RJ4 zqthTH9ZZMcqXB
From: Markus Lanthaler <markus.lanthaler@gmx.net>
To: 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>
In-Reply-To: <51D1C423.5000804@stpeter.im>
Date: Mon, 01 Jul 2013 20:13:25 +0200
Message-ID: <017801ce7686$afc9db60$0f5d9220$@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: Ac52hR434SValfatRwSiANlfRdjjPgAASh2w
Content-Language: de
X-Y-GMX-Trusted: 0
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: Mon, 01 Jul 2013 18:14:01 -0000
On Monday, July 01, 2013 8:02 PM, Peter Saint-Andre wrote: > On 7/1/13 11:19 AM, Markus Lanthaler wrote: > > I'm wondering whether it would make sense to add a feature allowing > > associate a date to an account. This would address problems arising > from > > account recycling (think Yahoo). Maybe something like > > > > acct:bob@example.com?date=20130701 > > > > I think at the very least this should be covered in the security > > considerations. > > IMHO we're beyond the point of adding new features to the 'acct' URI > scheme (it has completed Working Group Last Call, IETF Last Call, and > IESG review -- currently I'm working to address one issue about i18n > that arose during IESG review, so that the document can be approved for > publication). Sorry for bringing it up so late in the process. > However, a date could be included in an API or protocol that enables > applications to use 'acct' URIs. Is there a reason why this would need > to be included in the URI itself? Sure.. but I think the date should actually be a (perhaps optional) part of the identifier, i.e., the acct URI. That would also make it easier to exchange it between various applications and protocols. -- Markus Lanthaler @markuslanthaler
- [apps-discuss] I-D Action: draft-ietf-appsawg-acc… internet-drafts
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Peter Saint-Andre
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Markus Lanthaler
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Peter Saint-Andre
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Markus Lanthaler
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Peter Saint-Andre
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… DataPacRat
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Paul E. Jones
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Markus Lanthaler
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Markus Lanthaler
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Paul E. Jones
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Barry Leiba
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Markus Lanthaler
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Paul E. Jones
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Bob Wyman
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… DataPacRat
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Bob Wyman
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Graham Klyne
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Larry Masinter
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Murray S. Kucherawy