IETF Logo Mail Archive

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

"Paul E. Jones" <paulej@packetizer.com> Tue, 02 July 2013 19:00 UTC

Return-Path: <paulej@packetizer.com>
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 5BFF311E80DF for <apps-discuss@ietfa.amsl.com>; Tue, 2 Jul 2013 12:00:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 zS3e+mqJ6r28 for <apps-discuss@ietfa.amsl.com>; Tue, 2 Jul 2013 12:00:52 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 8C9F121F9A26 for <apps-discuss@ietf.org>; Tue, 2 Jul 2013 12:00:29 -0700 (PDT)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r62J0LZ7000542 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 2 Jul 2013 15:00:21 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1372791621; bh=wpRGE4BmSg/QpuR1hdXafAdbYTDE2RgoQNoFpY4+mFM=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=hax30t43XKzw2tR1FYNa3RKuVICjDRzbxaxCmI3lZEGnih3D350pcwY2RZlI0b/jr TinPcFidMz3bp7GM9CaJSWT7mzXMvrujzr+MX0OxYigvjU8A1faPCrnetAqY+h+vg9 1Zbd/MSUH2gxcW8r8lDpDlNm5bk1o3F80FSBaKBI=
From: "Paul E. Jones" <paulej@packetizer.com>
To: 'Barry Leiba' <barryleiba@computer.org>
References: <20130617205341.15641.96770.idtracker@ietfa.amsl.com> <51BF786B.9060703@stpeter.im> <51D1C423.5000804@stpeter.im> <044d01ce76c4$4f133710$ed39a530$@packetizer.com> <05aa01ce7741$48378220$d8a68660$@packetizer.com> <CAC4RtVBfmPin-Uw9V6Ykkp+1S2FAtkamjzkWSgNeoAUNnw0xLw@mail.gmail.com>
In-Reply-To: <CAC4RtVBfmPin-Uw9V6Ykkp+1S2FAtkamjzkWSgNeoAUNnw0xLw@mail.gmail.com>
Date: Tue, 02 Jul 2013 15:00:53 -0400
Message-ID: <064801ce7756$7a33f000$6e9bd000$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJV0E+HeqM9oFCI0wWnOEzauIjbLQFZvmQ1AoRagrMB4aI7qwIasMd+AiziNPGX8smaoA==
Content-Language: en-us
Cc: apps-discuss@ietf.org
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 19:00:59 -0000

Barry,
 
> A smart email client might be taught to turn that into
> "acct:ferd@example.com?date=20070410" and send off a webfinger (or
> web-foot, or whatever) query, and then only do the message submission
> if it got the go-ahead from that.  But in that case, the date-related
> query belongs as part of the web-foot protocol, not as part of the
> URI.

That kind of data element could be returned via WebFinger as a "property".  For example:

  "properties" :
  {
    "http://packetizer.com/ns/name" : "Paul E. Jones",
    "http://packetizer.com/ns/name#zh-CN" : "保罗‧琼斯"
    "http://packetizer.com/ns/activated" : "2000-02-17T03:00:00Z"
  }

It would be a matter of defining the property identifier (which is a URI) and the format of the date/time string.
 
> If you just want to use the URI as a convenient place to store the
> validity date, I don't buy that.

I don't either.  Humans have to enter these identifiers.  Dates in an identifier just make it more difficult for the human user.

Paul

v2.23.0 | Report a Bug | By Email