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

"Markus Lanthaler" <markus.lanthaler@gmx.net> Mon, 01 July 2013 17:19 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 94D8A21F9A7D for <apps-discuss@ietfa.amsl.com>; Mon, 1 Jul 2013 10:19:53 -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 WMWpCsTYJSCy for <apps-discuss@ietfa.amsl.com>; Mon, 1 Jul 2013 10:19:49 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id DD49A11E81C5 for <apps-discuss@ietf.org>; Mon, 1 Jul 2013 10:19:46 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.29]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0MUiSQ-1UjooH2eOS-00YBCW for <apps-discuss@ietf.org>; Mon, 01 Jul 2013 19:19:45 +0200
Received: (qmail invoked by alias); 01 Jul 2013 17:19:45 -0000
Received: from 178.115.248.36.wireless.dyn.drei.com (EHLO Vostro3500) [178.115.248.36] by mail.gmx.net (mp029) with SMTP; 01 Jul 2013 19:19:45 +0200
X-Authenticated: #419883
X-Provags-ID: V01U2FsdGVkX1/1ktd+hMj17giBgCwiXrIiiQX7D2iXLbhHS3Vg+K M+HCehJKSBt+fU
From: Markus Lanthaler <markus.lanthaler@gmx.net>
To: apps-discuss@ietf.org
References: <20130617205341.15641.96770.idtracker@ietfa.amsl.com> <51BF786B.9060703@stpeter.im>
In-Reply-To: <51BF786B.9060703@stpeter.im>
Date: Mon, 01 Jul 2013 19:19:43 +0200
Message-ID: <016d01ce767f$2ea45990$8bed0cb0$@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: Ac5rnWzRfNP/SGreQsmXVJjAWHLcPQK4Rknw
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 17:19:53 -0000

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.


--
Markus Lanthaler
@markuslanthaler



> -----Original Message-----
> From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
> bounces@ietf.org] On Behalf Of Peter Saint-Andre
> Sent: Monday, June 17, 2013 10:58 PM
> To: apps-discuss@ietf.org
> Subject: Re: [apps-discuss] I-D Action: draft-ietf-appsawg-acct-uri-
> 05.txt
> 
> Based on IESG feedback, added a paragraph about putting a user@host
> address into the localpart of an 'acct' URI (percent-encoding the
> at-sign when doing so).
> 
> On 6/17/13 2:53 PM, internet-drafts@ietf.org wrote:
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >  This draft is a work item of the Applications Area Working Group
> Working Group of the IETF.
> >
> > 	Title           : The 'acct' URI Scheme
> > 	Author(s)       : Peter Saint-Andre
> > 	Filename        : draft-ietf-appsawg-acct-uri-05.txt
> > 	Pages           : 9
> > 	Date            : 2013-06-17
> >
> > Abstract:
> >    This document defines the 'acct' Uniform Resource Identifier (URI)
> >    scheme as a way to identify a user's account at a service
> provider,
> >    irrespective of the particular protocols that can be used to
> interact
> >    with the account.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-appsawg-acct-uri
> >
> > There's also a htmlized version available at:
> > http://tools.ietf.org/html/draft-ietf-appsawg-acct-uri-05
> >
> > A diff from the previous version is available at:
> > http://www.ietf.org/rfcdiff?url2=draft-ietf-appsawg-acct-uri-05
> >
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > apps-discuss mailing list
> > apps-discuss@ietf.org
> > https://www.ietf.org/mailman/listinfo/apps-discuss
> >
> 
> 
> --
> Peter Saint-Andre
> https://stpeter.im/
> 
> 
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss