From e13df406ae127bb0173478334aa1e03fd5072be0 Mon Sep 17 00:00:00 2001
From: nmortari <60630328+nmortari@users.noreply.github.com>
Date: Tue, 3 Sep 2024 16:13:36 -0700
Subject: [PATCH] Added dial-in information

---
 docs/Telemetry/Dial-In/1-index.md | 20 +++++++++++++++++++-
 1 file changed, 19 insertions(+), 1 deletion(-)

diff --git a/docs/Telemetry/Dial-In/1-index.md b/docs/Telemetry/Dial-In/1-index.md
index 3a15b85..b41bb1a 100644
--- a/docs/Telemetry/Dial-In/1-index.md
+++ b/docs/Telemetry/Dial-In/1-index.md
@@ -1,10 +1,28 @@
 # Dial-In Overview
 
 ## About Dial-In Telemetry
-Dial-in telemetry uses model-driven methods to collect telemetry from a Cisco Nexus device. The term "dial-in" means the external collector is "dialing-in" to the Nexus device and telling the switch what to do. This process happens in two steps. The first step is for the external collector to connect to the Nexus device and tell the switch which telemetry data to collect. The second step is for the Nexus device to collect this data and send it to the external collector.
+Dial-in telemetry uses model-driven methods to collect telemetry from a Cisco Nexus device. The term "dial-in" means the external collector is "dialing-in" to the Nexus device and telling the switch what to send. This process happens in two steps. The first step is for the external collector to connect to the Nexus device and tell the switch which telemetry data to collect. The second step is for the Nexus device to send this data to the external collector.
 
 Dial-in telemetry has multiple methods available for the data structure, encoding, and transport.
 
+## Dial-In Telemetry Features
+Supports the following data structure types:
+
+* DME
+* Cisco Native YANG
+* OpenConfig YANG
+
+Supports the following encoding types:
+
+* JSON
+* GPB Compact
+* GPB Key-Value
+
+Supports the following transport types:
+
+* HTTP
+* gRPC
+
 ## About gRPC
 Google Remote Procedure Call (gRPC) is an open source high performance RPC framework released in 2016. gRPC has many RPCs available to control systems. It uses HTTP/2 for transport, protocol buffers for the interface description language, and includes the following features: