From 7d4404c0e323199236c48e3215812d4eec58df0b Mon Sep 17 00:00:00 2001
From: Amin Ben Romdhane <amin.benromdhane@iopsys.eu>
Date: Mon, 16 Jun 2025 13:49:24 +0200
Subject: [PATCH] bridgemngr: Added vendor extension description

---
 bridgemngr/files/datamodel_description.json | 43 +++++++++++++++++++++
 1 file changed, 43 insertions(+)
 create mode 100644 bridgemngr/files/datamodel_description.json

diff --git a/bridgemngr/files/datamodel_description.json b/bridgemngr/files/datamodel_description.json
new file mode 100644
index 000000000..5b1e932c4
--- /dev/null
+++ b/bridgemngr/files/datamodel_description.json
@@ -0,0 +1,43 @@
+{
+	"Device.": {
+		"type": "object",
+		"protocols": [
+			"cwmp",
+			"usp"
+		],
+		"description": "The top-level object for a Device.",
+		"access": false,
+		"array": false,
+		"Device.Bridging.": {
+			"type": "object",
+			"protocols": [
+				"cwmp",
+				"usp"
+			],
+			"description": "Layer 2 bridging configuration. Specifies bridges between different layer 2 interfaces. Bridges can be defined to include layer 2 filter criteria to selectively bridge traffic between interfaces. This object can be used to configure both 802.1D <<bibref|802.1D-2004>> and 802.1Q <<bibref|802.1Q-2011>> bridges. Not all 802.1D and 802.1Q features are modeled, and some additional features not present in either 802.1D or 802.1Q are modeled. 802.1Q <<bibref|802.1Q-2011>> bridges incorporate 802.1Q <<bibref|802.1Q-2005>> customer and 802.1ad <<bibref|802.1ad-2005>> provider bridges.",
+			"access": false,
+			"array": false,
+			"Device.Bridging.Bridge.{i}.": {
+				"type": "object",
+				"protocols": [
+					"cwmp",
+					"usp"
+				],
+				"description": "Bridge table.",
+				"access": true,
+				"array": true,
+				"{BBF_VENDOR_PREFIX}VLANFiltering": {
+					"type": "boolean",
+					"read": true,
+					"write": true,
+					"protocols": [
+						"cwmp",
+						"usp"
+					],
+					"datatype": "boolean",
+					"description": "Enable or disable VLAN Filtering on this bridge."
+				}
+			}
+		}
+	}
+}