Clarify VES listener accepts all domains

A concern was raised based on the prior
wording that it left it open that there
may be multiple listeners each handling
different domains.  The wording was
updated to remove any ambiguity.

Issue-ID: VNFRQTS-871
Signed-off-by: Lovett, Trevor <trevor.lovett@att.com>
Change-Id: Id06ac6181a9cda086e9ada8a1880703cdd282788

diff --git a/docs/Chapter8/ves7_1spec.rst b/docs/Chapter8/ves7_1spec.rst
index e63628a..2c8b933 100644 (file)
--- a/docs/Chapter8/ves7_1spec.rst
+++ b/docs/Chapter8/ves7_1spec.rst
@@ -362,9 +362,8 @@ an ONAP controller action, or provided manually.
   VES Events. The events shall only be sent to one VES Event Listener at a time.
   Please note: If a FQDN is used, the DNS query would return a single IP
   address.
-* A single VES Event Listener may handle more than one type of VES event
-  (different domains); i.e. same VES Event Listener can receive and process
-  heartbeat, fault, measurement, syslog, etc. events.
+* The active VES Event Listener (either the primary or secondary) will handle
+  all VES events regardless of domain.
 * **VES Credentials**: If the NF is using Basic Authentication, then the NF
   must support the provisioning of security and authentication parameters
   (HTTP username and password) in order to be able to authenticate with the