Table of Contents - APTAStandards.com

CLIENT
Exhibit 4.3-9 OFX Security Schemes
The password is encrypted by both the client
application and the Secure Socket Layer
(SSL)
protocol. The web server removes the SSL encryption and forwards the
encrypted password and the plaintext OFX data. The channel level
security is sufficient
for most transit related messages, provided that
the network architecture is adequately
secure. However, the application level password encryption can allow a higher level of
security when desired.
4.3.8 Timing & Routing
OFX does not provide any timing and routing requirements.
4.3.9 Usability
SSL ENCRYPTION
OFX DATA
OFX DATA
WEB
OFX
SERVER SERVER
Encrypted Encrypted
Password Password
The OFX board maintains
the OFX specification with members from a wide industry
base. Membership to OFX is free and the process required
for joining the organization,
depending on the work group, typically involves an informal request. There are no
royalties for adapting the specification
to transit. Furthermore, OFX does not require
any fees for
making changes and/or additions to the specification
for members.
Typically,
it takes about six months to process and finalize a change, such as adding 10
new data
elements (aggregates). The process
is estimated to take somewhere between
9-12 months to add a new scheme such
as transit fare collection. This process assumes
the design and development work is completed by APTA. This data was obtained
through phone interviews and/or email correspondence.
The information is accurate
as of July 2004. If APTA is interested in
using any parts of the specification, formal
notification and/or negotiations are necessary.
Page 39