| Standards for Technology in Automotive Retail |
| Home - News Feed

11.3. Internet Connectivity Implementation Patterns
Prev | Chapter 11. Internet Connectivity | Next

## 11.3. Internet Connectivity Implementation Patterns

This section describes the Internet connectivity solutions. The Addressable Hub provides a super set of functionality that supports both the Addressable Endpoint and the Non-Addressable Endpoint. Ideally, all partners would be able to support the Addressable Hub, but due to cost and footprint requirements this is not possible, thus, two alternative solutions are provided, the Addressable and Non-Addressable Endpoints. This section describes the details of each solution.

### 11.3.1. Addressable Hub

This type of Internet connectivity provides a service level required by an OEM or large messaging concentration point for aggregating multiple messaging connections. The following details describe the minimum Internet connection expectations of the Addressable Hub:

- High speed connection to the Internet with access speeds of 1MB or greater.

- Fully connected “always on” endpoint with 24X7 accesses with 99.9% reliability with high availability backup facilities.

- Ability to scale to handle increasing messaging loads.

- Optionally support VPN solutions to communicate with other Addressable Hubs.

- Internet addressable endpoint with a statically defined name that is addressable through the public DNS over the Internet.

- Support for core Internet messaging standards including TCP/IP, HTTP/S (or SMTP/S for ebMS) and SOAP.

- Ability to support a guaranteed once-and-only-once/exactly-once reliable messaging solution

- Ability to support security specifications ranging from none to solutions with full non-repudiation

- Ability to initiate messages both synchronously and asynchronously.

- Ability to receive messages both synchronously and asynchronously.

### 11.3.2. Addressable Endpoint

This type of Internet connectivity provides a service level required by a large dealer or fully functional business-to-business endpoint. The following details describe the minimum Internet connection expectations of the Addressable Endpoint:

- High speed connection to the Internet with access speeds of 128K or greater depending on business needs.

- Internet addressable endpoint with a statically defined name that is addressable through the public DNS over the Internet.

- Fully connected “always on” endpoint with 24X7 accesses with 99% reliability and offline backup capabilities.

- Support for core Internet messaging standards including TCP/IP, HTTP/S (or SMTP/S for ebMS) and SOAP.

- Ability to support a once-and-only-once/exactly-once reliable messaging solution

- Ability to support security specifications ranging from none to solutions with full non-repudiation

- Ability to initiate messages both synchronously and asynchronously

- Ability to also receive messages both synchronously and asynchronously

### 11.3.3. Non-Addressable Endpoint

This type of Internet connectivity provides a service level required for a minimal cost and smallest footprint solution while still providing a reliable, secure messaging endpoint. This endpoint differs in two key areas, it does not require a static public DNS name and it allows for disconnected Internet access. The following details describe the minimum Internet connection expectations of the Non-Addressable Endpoint:

- Dial-up connection to the Internet with access speeds of 28K or greater depending on business needs.

- Disconnected endpoint that is intermittently connected to the Internet

- Support for core Internet messaging standards including TCP/IP, HTTP/S (or SMTP/S for ebMS) and SOAP.

- Ability to support security specifications ranging from none to solutions with full non-repudiation and audit

- Ability to initiate messages both synchronously and asynchronously

- Ability to support a once-and-only-once/exactly-once reliable messaging solution

Prev | Up | Next
11.2. Requirements | Home | 11.4. Discussions