Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

https://samtrafiken.atlassian.net/wiki/x/gYBTBg

MTS1

https://bitbucket.org/samtrafiken/bob-mts-1-mobile-ticket-format/src/master/
In MTS1 you can find specifications regarding:

  • EC (primary) and RSA (fallback) algorithm for issuer and device signature of mobile ticket bundles (MTB). Issuer signature ensures that the requests comes from a trusted participant. Device signatures are used to provide a binding between the mobile ticket and the device (e.g. a mobile phone).

  • The structure of the mobile ticket bundle

  • Schemas of security headers of the mobile ticket bundle

MTS2

https://bitbucket.org/samtrafiken/bob-mts-2-device-key-derivation/src/master/
In MTS2 you can find specifications regarding:

  • How a device key, used for device signatures, can be calculated. Device keys are used to provide a binding between the mobile ticket bundle and the device (e.g. a mobile phone). To read about the keys and algorithms see MTS1

MTS3

https://bitbucket.org/samtrafiken/bob-mts-3-coordinated-ticket-namespace/src/master/
In MTS3 you can find specifications regarding:

  • Coordinated Ticket Name Space, which defines a common set of variables and data structures to be used within the MTB. For example version handling and metadata. To read about MTBs see MTS1.

  • Schemas for version handling, metadata et.c.

MTS4

https://bitbucket.org/samtrafiken/bob-mts-4-coordination-and-key-management/src/master/
In MTS4 you can find specifications regarding:

  • Coordination and key management between participants and the administrative body (Samtrafiken)

  • Participant metadata set, containing current keys and related metadata, is distributed by Samtrafiken to participants and all participants needs to retrieve this list regulary.

  • Mandatory fields of the JSON Web Signature (JWS) protected header

  • Schema for the participant metadata set

MTS5
https://bitbucket.org/samtrafiken/bob-mts-5-proof-of-possession-authorisation-tokens/src/master/
In MTS5 you can find specifications regarding:

  • How to generate and validate a proof-of-possession (of private keys) token. Private keys are used to sign critical parts of requests and responses.

  • How to validated proof-of-possession tokens

  • Specification of Primary and fallback algorithms

  • Hash calculation and how to verify it

MTS6
https://bitbucket.org/samtrafiken/bob-mts-6-tickle/src/master/
In MTS6 you can find specifications regarding:

  • The generic language Tickle how to write and evaluate conditions for the journey

  • The language is use to define time and spatial geographical conditions including macros (complex conditions saved in the client for less data in messages)

MTS7
https://bitbucket.org/samtrafiken/bob-mts-7-travel-card-application/src/master/
In MTS7 you can find specifications regarding:

  • Methods to store a MTB on a chip embedded in a smart card, a wearable or similar

  • Requrements and compliance levels that has to be fulfilled to use this

  • Specific commands to use

  • Complete data structures that is needed

  • Security issues that needs to be considered

MTS8
https://bitbucket.org/samtrafiken/bob-mts-8-date-and-time-formats/src/master/
In MTS8 you can find specifications regarding:

  • Date and time formats used within the mobile ticket specifications and related APIs

  • ISO standards regaring time duration and intervall formats

  • No labels