From fa5669495f2d6faa292b9771246c986c661c7e93 Mon Sep 17 00:00:00 2001 From: Wonsuk Lee Date: Tue, 5 Sep 2023 19:14:30 +0900 Subject: [PATCH 1/4] Propsed texts for initialization and closure of HTTPS --- spec/VISSv2_Transport.html | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/spec/VISSv2_Transport.html b/spec/VISSv2_Transport.html index 4e02076..1158bda 100644 --- a/spec/VISSv2_Transport.html +++ b/spec/VISSv2_Transport.html @@ -321,12 +321,24 @@

Session Life Time Management

Initialization

-

HTTP long polling?

+

Initialization involves setting up a secure HTTPS session between the client and the server. + This ensures encrypted communication for data transmission. + To initialize a secure session, the client sends a request to the server using the HTTPS protocol. + This is achieved by connecting to the server's designated URL using the 'https://' scheme. + The client can use a web browser, a native application, or a suitable library in the case of programmatically managed sessions.
+ The client connects to the server using the specified hostname, which often includes the "www" prefix. + The communication typically takes place over port 443, the default port for secure HTTPS connections. + The hostname resolution can be done via DNS or configured through local settings. +

Closure

-

HTTP long polling?

+

Closure entails ending the established HTTPS session when the communication is complete or when the client no longer requires the connection. + Either the client or the server can initiate the session closure. The client can signal the end of the session by sending an appropriate request to the server, + indicating the intent to close the connection.
+ Upon session closure, any allocated resources, such as server-side threads or memory, are released, improving overall system efficiency. +

From 6054fe37bfbad9d918d96904a059b30e30ef9d69 Mon Sep 17 00:00:00 2001 From: Wonsuk Lee Date: Tue, 5 Sep 2023 19:54:52 +0900 Subject: [PATCH 2/4] Merge signal discovery read with dynamic metadata read on HTTPS --- spec/VISSv2_Transport.html | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/spec/VISSv2_Transport.html b/spec/VISSv2_Transport.html index 1158bda..b97d081 100644 --- a/spec/VISSv2_Transport.html +++ b/spec/VISSv2_Transport.html @@ -519,12 +519,8 @@

Signal Discovery Read

}

- - -
-

Dynamic Metadata Read

- The dynamic metadata, i. e. any other metadata kept by the vehicle system, + A client may send a signal discovery read request to access dynamic metadata. The dynamic metadata, i. e. any other metadata kept by the vehicle system, is retrieved by the setting the "type" to "dynamic-metadata". The value MUST be set to one of the domain names as specified in the [[viss2-core]], Dynamic Metadata Filter Operation chapter.
From a8011ea5d2a1661e81e2ba04317191d3eb8b94eb Mon Sep 17 00:00:00 2001 From: Wonsuk Lee Date: Wed, 6 Sep 2023 18:51:16 +0900 Subject: [PATCH 3/4] Revised texts to fix the "www" prefix concern --- spec/VISSv2_Transport.html | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/spec/VISSv2_Transport.html b/spec/VISSv2_Transport.html index b97d081..bb41a84 100644 --- a/spec/VISSv2_Transport.html +++ b/spec/VISSv2_Transport.html @@ -326,7 +326,8 @@

Initialization

To initialize a secure session, the client sends a request to the server using the HTTPS protocol. This is achieved by connecting to the server's designated URL using the 'https://' scheme. The client can use a web browser, a native application, or a suitable library in the case of programmatically managed sessions.
- The client connects to the server using the specified hostname, which often includes the "www" prefix. + While the client typically connects to the server using the specified hostname, which often includes the "www" prefix, + it's important to note that this convention may not apply in situations where VISS operates within a local, in-vehicle network or if remote vehicle connections are allowed. The communication typically takes place over port 443, the default port for secure HTTPS connections. The hostname resolution can be done via DNS or configured through local settings.

From 02a76ba8aa397c8b5fa1e6157428999b47a83d8f Mon Sep 17 00:00:00 2001 From: Wonsuk Lee Date: Wed, 27 Sep 2023 18:08:18 +0900 Subject: [PATCH 4/4] Fixed the conflict sentence --- spec/VISSv2_Transport.html | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/spec/VISSv2_Transport.html b/spec/VISSv2_Transport.html index bb41a84..d188635 100644 --- a/spec/VISSv2_Transport.html +++ b/spec/VISSv2_Transport.html @@ -521,8 +521,7 @@

Signal Discovery Read

- A client may send a signal discovery read request to access dynamic metadata. The dynamic metadata, i. e. any other metadata kept by the vehicle system, - is retrieved by the setting the "type" to "dynamic-metadata". + The dynamic metadata, i. e. any other metadata kept by the vehicle system, is retrieved by the setting the "type" to "dynamic-metadata". The value MUST be set to one of the domain names as specified in the [[viss2-core]], Dynamic Metadata Filter Operation chapter.
Example: