From 7cfaea2ee5e73a5a0a669da3b8c949000245cb83 Mon Sep 17 00:00:00 2001 From: VENKATESH KUMAR Date: Wed, 22 Apr 2020 17:31:32 -0400 Subject: dcae r6 doc updates cont. Change-Id: I2303d59ad9491c555adb70de57eb14ab1fa7233c Signed-off-by: VENKATESH KUMAR Issue-ID: DCAEGEN2-1891 Signed-off-by: VENKATESH KUMAR --- docs/sections/apis/ves-hv/index.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) (limited to 'docs/sections/apis/ves-hv') diff --git a/docs/sections/apis/ves-hv/index.rst b/docs/sections/apis/ves-hv/index.rst index df91681c..c3ccfa0c 100644 --- a/docs/sections/apis/ves-hv/index.rst +++ b/docs/sections/apis/ves-hv/index.rst @@ -5,7 +5,6 @@ HV-VES (High Volume VES) ======================== -:Date: 2018-10-05 .. contents:: :depth: 4 @@ -25,9 +24,11 @@ TCP Endpoint ============ HV-VES is exposed as NodePort service on Kubernetes cluster on port 30222/tcp. -It uses plain, insecure TCP connection without socket data encryption. In Dublin release, -there is an experimental option to enable SSL/TLS (see :ref:`ssl_tls_authorization`). -Without TLS client authentication/authorization is not possible. +By default, as of the Frankfurt release, all TCP communications are secured using +SSL/TLS. Plain, insecure TCP connections without socket data encryption can be enabled if needed. + (see ref:`ssl_tls_authorization`). + +Without TLS, client authentication/authorization is not possible. Connections are stream-based (as opposed to request-based) and long-running. Communication is wrapped with thin Wire Transfer Protocol, which mainly provides delimitation. -- cgit 1.2.3-korg