3.2.1 Abstract Data Model

This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this model as long as their external behavior is consistent with that described in this document.

URI: The URI on which the IP-HTTPS server will accept incoming IP-HTTPS connections.

State: Specifies the current state of the IP-HTTPS server. The possible states are as follows:

Stopped: This is the initial state. IP-HTTPS operations are not possible until the IP-HTTPS server is started.

Listen: In this state, the IP-HTTPS server enables its HTTP stack to listen on the configured URI waiting for IP-HTTPS clients to connect. When the IP-HTTPS server is in the Listen state, it is usable for sending and receiving IPv6 traffic. In the Listen state, the IP-HTTPS server uses Neighbor Discovery [RFC4861] to maintain the link to which the IP-HTTPS clients connect.

Disabled: IP-HTTPS operations are not possible in this state. The IP-HTTPS server transitions to this state based on user actions or administrative policy.

Authentication Mode: Specifies whether the server needs to authenticate the incoming IP-HTTPS client connections. This parameter SHOULD<2> be configurable by an administrator. The possible states are as follows:

Certificates: In this state, the IP-HTTPS server is required to authenticate IP-HTTPS clients. This state MUST be supported.

None: In this state, the IP-HTTPS server does not authenticate IP-HTTPS clients. This state SHOULD<3> be supported.

Client Table: For each IP-HTTPS client connected, the server maintains the following state:

HTTP Connection: The HTTP connection over which the client has connected.

Further details about state processing, handling error conditions, and state transitions are specified in subsequent sections.

Show: