9/23/2011 5.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 6.0 Major Updated and revised the technical content. 3/30/2012 6.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 7.0 Updated and revised the technical content. 10/25/2012 7.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 7.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 8.0 Major Updated and revised the technical content. 11/14/2013 8.0 None No changes to the meaning, language,
Protocol Details The IP-HTTPS Protocol encapsulates IPv6 packets over an HTTPS connection. This is achieved by creating a tunneled interface, which provides a symmetric link, with multicast and neighbor discovery capabilities, including unreachable neighbor detection and duplicate address detection per . Like other point-to-point links, for instance PPP , IP-HTTPS uses a static network-layer to link-layer address mapping. There are two main components to IP-HTTPS: IP-HTTPS clients that are connecting to resources inside a private network (such as an enterprise network) and IP-HTTPS servers that facilitate the connection, as illustrated in the diagram below. Figure : IP-HTTPS clients connected to an IP-HTTPS server IP-HTTPS Client Details The following figure the state machine when a client establishes the outgoing IP-HTTPS tunnel. Figure : client state diagram 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. IP-HTTPS clients must be configured with this address in order to use it. State: Specifies the current state of the IP-HTTPS client. The possible states are: Enabled: In this the IP-HTTPS client waits for the pre-conditions specified in Section to happen. These preconditions transition the IP-HTTPS client to the LinkDown state. LinkDown: In this state, the IP-HTTPS client reads the configuration and tries to establish an HTTPS connection to the server. Once the HTTPS connection is established, the client transitions to the Established state. Established: In this state the IP-HTTPS client establishes a bidirectional HTTP stream. It achieves this by sending an HTTP request message to the server and waiting for a HTTP response. Upon receiving a successful HTTP response, it transitions to the LinkUp state. LinkUp: In this state the IP-HTTPS link is up and usable for sending and receiving IPv6 traffic. Disabled: A higher-layer trigger (such as a user action to disable IP-HTTPS) transitions the IP-HTTPS client to the disabled state. IP-HTTPS operations are not possible in this state. Further details about state processing, handling error conditions, and state transitions are specified below.
Index A Abstract data 13 16 8 C 9 27 Client 13 15 15 15 15 14 16 message processing 15 15 16 15 15 16 12 sequencing rules 15 15 16 15 15 16 14 unauthorized connecting to server certificate not valid example ( 21, 21) 22 D Data model - abstract 13 16 E Examples 24 20 20 unauthorized client connecting to server certificate not valid ( 21, 21) 22 23 F 9 G 6 H Higher-layer triggered events 15 15 15 15 17 17 17 17 I 25 25 7 Initialization 14 17 17 17 6 L Local events 16 server 19 19 19 M 24 Message processing client 15 15
16 15 15 server 17 17 18 17 Messages 11 10 N 6 O Other local events 16 18 7 P 20 25 8 8 26 Protocol Details 12 R 6 7 6 7 S Security 25 25 Sequencing rules client 15 15 16 15 15 server 17 17 18 17 Server 16 17 17 17 17 17 17 17 local events 19 19 19 message processing 17 17 18 17 18 sequencing 17 17 18 17 18 17 23 9 11 T Timer events 16 18 Timers 14 17 27 10 Triggered events client 15 15 15 server 17 17 17 Triggered events - higher-layer 15 17 V 9 9