doc: clarify handling of duplicate xDS resource names (#12756)

Risk Level: Low Testing: N/A Docs Changes: Included in PR Release Notes: N/A Signed-off-by: Mark D. Roth <roth@google.com> Mirrored from https://github.com/envoyproxy/envoy @ c7323f25ee8395736b5b6d37a4521b29eeb84a0f
4 years ago · 47a7eb527c
parent b215ae4c0e
commit 47a7eb527c
1 changed files with 6 additions and 0 deletions
--- a/xds_protocol.rst
+++ b/xds_protocol.rst
@ -449,6 +449,12 @@ no mechanism for providing incremental updates of repeated fields within a named
 Most notably, there is currently no mechanism for incrementally updating individual
 endpoints within an EDS response.

+Duplicate Resource Names
+^^^^^^^^^^^^^^^^^^^^^^^^
+
+It is an error for a server to send a single response that contains the same resource name
+twice. Clients should NACK responses that contain multiple instances of the same resource name.
+
 Deleting Resources
 ^^^^^^^^^^^^^^^^^^