[Doc] Update paper: Add author, Kubernetes note (#1493)

Signed-off-by: Sanjeev Rampal <sr.2357@gmail.com>

Author: srampal

paper/main.tex

@@ -77,7 +77,7 @@
 Xunzhuo Liu, Huamin Chen, Samzong Lu, Yossi Ovadia, Guohong Wen, Hao Wu, \\
 Zhengda Tan, Jintao Zhang, Senan Zedan, Yehudit Kerido, Liav Weiss,
 Haichen Zhang, Bishen Yu, Asaad Balum, Noa Limoy,
-Abdallah Samara, Baofa Fan, Brent Salisbury, Ryan Cook, Zhijie Wang,
+Abdallah Samara, Baofa Fan, Sanjeev Rampal, Brent Salisbury, Ryan Cook, Zhijie Wang,
 Qiping Pan, Rehan Khan, Avishek Goswami, Houston H.\ Zhang, Shuyi Wang,
 Ziang Tang, Fang Han, Zohaib Hassan, Jianqiao Zheng, Avinash Changrani%
 }%

paper/sections/deployment.tex

@@ -13,11 +13,11 @@ \subsection{Deployment Modes}
 
 \noindent\textbf{Kubernetes: Standalone mode.}
 Envoy runs as a sidecar container alongside the router in the same pod.
-The ExtProc filter connects via localhost gRPC.
+The ExtProc filter connects via localhost gRPC. In this mode, the Envoy instance is private to the semantic router and separate from cluster level Envoy gateways. Routes are internally configured and injected by the semantic router into Envoy.
 Deployed via Helm charts with configurable replicas, resource limits, cache backends, and autoscaling.
 
 \noindent\textbf{Kubernetes: Gateway mode.}
-The router runs as an independent service behind an existing Istio or Envoy Gateway deployment, referenced via the gateway's ExtProc configuration.
+The router runs as an independent service behind an existing Istio or Envoy Gateway deployment, referenced via the gateway's ExtProc configuration. In this mode, there is no private Envoy within the semantic router pod. The cluster's Envoy based gateway is used, via Istio or other controller. Routes are explicitly configured at the cluster gateway level via APIs such as Kubernetes Gateway API.
 This mode shares the gateway infrastructure across multiple services.
 
 \subsection{Kubernetes Operator}