Re: [89attendees] Oyster card balance

Alexander Harrowell <a.harrowell@gmail.com> Tue, 11 March 2014 16:42 UTC

Return-Path: <a.harrowell@gmail.com>
X-Original-To: 89attendees@ietfa.amsl.com
Delivered-To: 89attendees@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C9981A0473 for <89attendees@ietfa.amsl.com>; Tue, 11 Mar 2014 09:42:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LJRLVp_KUL9f for <89attendees@ietfa.amsl.com>; Tue, 11 Mar 2014 09:41:59 -0700 (PDT)
Received: from mail-qa0-x230.google.com (mail-qa0-x230.google.com [IPv6:2607:f8b0:400d:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 122EE1A0457 for <89attendees@ietf.org>; Tue, 11 Mar 2014 09:41:58 -0700 (PDT)
Received: by mail-qa0-f48.google.com with SMTP id m5so8692959qaj.35 for <89attendees@ietf.org>; Tue, 11 Mar 2014 09:41:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=4nw3kmlJfLa3R8TueZe0wYVZsBA9SqpBQi8bZ4VFGPQ=; b=Gi0wTkiXXeYR4TGGn9qsiHzjqsB9BDECy1otNEzq3f2el+7k38zQGCWQokELg6qTZ8 RFy1j71W7EVCXKZw2DWTySDxqblAMpKkl7id73OSqGg00A/XJcLIVXLXWw5kWadueLom RpHJr6WUIsZyHAKJQOBP5frOilwo2UEC4XFejh4HMYouyfoVu4OA2WWeXu1S2XK5ULmL K0/I5m1UhRZNWpUP7aBd7jkfQJAPyxH49U9vdxlqlyDOcsTGTllxuwi0UfO0PHDrFMDZ PkLaGCGhaIHq8kpD429KZHY/PHyqBsIhuTcTo2Ru6kH8Zwmom9r5NxzrD+W3q7mFY6qa mfpw==
MIME-Version: 1.0
X-Received: by 10.224.136.195 with SMTP id s3mr3507436qat.95.1394556113181; Tue, 11 Mar 2014 09:41:53 -0700 (PDT)
Received: by 10.96.101.67 with HTTP; Tue, 11 Mar 2014 09:41:53 -0700 (PDT)
In-Reply-To: <2C30003C-5BFD-4BC4-B426-D32AF70D19B5@fugue.com>
References: <AE6329C4-4FBF-467C-8CDC-1069153607AA@juniper.net> <531EBBEE.2070105@restena.lu> <CA+qGm=_g6pWc6h2rWmAfw_7oCSE5VW0hvcO=SopvuGhy0JQSjA@mail.gmail.com> <531EE043.1080205@restena.lu> <1394538516.30828.39.camel@localhost> <2C30003C-5BFD-4BC4-B426-D32AF70D19B5@fugue.com>
Date: Tue, 11 Mar 2014 16:41:53 +0000
Message-ID: <CA+qGm=8i47qjdeondA9_yEHt1bVfeQSUxsqszkC9COuW1zm4dw@mail.gmail.com>
From: Alexander Harrowell <a.harrowell@gmail.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/89attendees/4T7GpDbKfg2wtU88pmgEyRxvmww
Cc: Stefan Winter <stefan.winter@restena.lu>, Derek Atkins <DAtkins@mocana.com>, "89attendees@ietf.org" <89attendees@ietf.org>
Subject: Re: [89attendees] Oyster card balance
X-BeenThere: 89attendees@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list of IETF 89 attendees that have opted in to the list." <89attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/89attendees>, <mailto:89attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/89attendees/>
List-Post: <mailto:89attendees@ietf.org>
List-Help: <mailto:89attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/89attendees>, <mailto:89attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Mar 2014 16:42:00 -0000

The answer is both; it's like a banking system, doing
increments/decrements, with an overdraft buffer and a resolution
mechanism.

On Tue, Mar 11, 2014 at 1:17 PM, Ted Lemon <mellon@fugue.com> wrote:
> The Oyster card system knows what transactions have occurred on the oyster card, and can tell you the balance without the card being present.   So I think the balance is stored in the database, not the card, although it may be that the card is used as a backup in case of network partition.   I suspect tampering would be quickly detected (it's certainly easy to detect in principle the way the system is set up) and hence not advisable for those of us who wish to be able to continue attending IETF in person.
>
>
> _______________________________________________
> 89attendees mailing list
> 89attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/89attendees