Post by Roland PerryPost by BobPost by BobPost by BobPost by Roland PerryPost by BobPost by TweedThis https://eta.st/2023/01/31/rail-tickets.html makes for an interesting
read.
“But what data is inside the barcode of a mobile ticket, and
how do they
work? Could people who aren’t ticket inspectors get the data
out of them?
It turns out that the answer is a bit more interesting than I initially
expected!” and lots more…
It was a very interesting talk. In summary: ITSO is a
complete mess and it's probably never going to be possible to
use a single ITSO card across a number of transport
authorities. But Oyster, despite being designed some years
earlier, looks good by comparison.
Followed the link to the video [1] of the talk about ITSO.
Highlights some major flaws in the ITSO concept, in particular
the ability to validate whether a ticket a card claims to
contain is actually a real ticket as opposed to false data
fraudulently laoded on the ticket can only be done with an
active internet connection.
That suggests the data isn't signed at all, which would be a bit
of a problem. But aren't all gate supposed to be online anyway
(to support the feature of loading a pre-purchased ticket as you
touch the barrier).
The data is signed but the keys to validate the signature need to
be stored securely, so can not be conveyed locally on portable
reading machines.
Really? Can't we sign with a private key and verify with a public key?
The system was designed to be usable as a stored-value card for PAYG
journeys (as is commonly used for things like buses or other local
public transport). If you could write to the card and sign it with a
public key, you could just write to the card that you have 500 quid
of credit on it any time you pleased.
Signing with a public key doesn't validate the ticket. The gripper or
barrier verifies that the stored-value is signed with one of the private
keys held only by authorised ticket sellers, not just any old key.
That doesn't allow for PAYG stored value, which was a key feature
intended for ITSO. The desire was for a system where the passenger can
do like you do with Oyster and tap the card in (and where necessary
out), and the value stored on the card is debited for the trip made.
That requires both read (to check the ballance is sufficient) and
write (to record the journey and adjust the ballance) operations.
Not just a "desire", it's been delivered (in pockets across the country,
anyway).
Setting aside the technical specifics for a moment, I think it's worth
considering what problems need to be solved, what problems ITSO does
solve, and whether ITSO is a good solution.
When ITSO started, there was a basic concept to provide the following
things:
1 smart card for all public transport.
The ability to load all bus, rail tram etc ticket types onto the card
The ability to do the same kinds of ticket checks and inspections for
revenue protection as are done on paper tickets
The ability to support stored value PAYG type tickets to be rolled out
as operators adopt that method of ticketing.
Taking ITSO as it currently exists:
1 smart card for all public transport. That's a fail. There are no
operators who accept all other operators cards, and there are many that
support none issued by anyone but themselves.
Ability to laod all bus, rail, tram etc ticket types. That's a fail. AP
rail tickets are not compatible.
Revenue protection. That's a fail. Validating a ticket requires an
internet connection, not available in all places.
Ability to support PAYG as it gets rolled out. Yes, it seems to have
this one working.
1 out of 4 objectives met. One of the fails is an organisational rather
than technical fail, so it would be possible to meet that if the right
people were pushed into doing so.
Objectives 2 and 3 are already better served by QR code technology, that
can be issued on ticket stock, printed at home or stored on a phone,
because that does not have the limitations that ITSO has. Many places
have adopted CCC payments alongside or instead of dedicated smartcard
PAYG solutions, with the benefit that 1 card covers all operators,
something ITSO spectacularly fails at.
So, the questions I would ask is, after nearly 15 years of development,
is it not reasonable to say that ITSO has failed to achieve its
objectives, and second, would we be better served letting ITSO as it
currently exists die and put our efforts into finding a means of
non-cardboard ticketting that actually meets our needs.
Robin