Update dash-sonic-hld.md for Inbound, Double Decap, per Issue428

Per DASH Community Call 9/6/2023 convo
sonic-net · Sep 6, 2023 · c8c0826 · c8c0826
1 parent 654b357
commit c8c0826
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/documentation/general/dash-sonic-hld.md b/documentation/general/dash-sonic-hld.md
@@ -1514,4 +1514,4 @@ For the example configuration above, the following is a brief explanation of loo
 		g. Underlay DIP shall be 50.2.2.6 (from mapping), Underlay SIP shall be 55.1.2.3 (from ENI)
 		h. Third Action is Appliance Encap for id 22
 		i. Packet shall be encapsulated with Outer DIP as 100.8.1.2 and SIP as VIP of this originating appliance card with VNI of 101. 
-		j. Inbound flow shall be similar to PL and outer encap shall be of the SLB MUX and not of the NSG appliance.
+		j. Inbound flow shall be similar to PL and outer encap shall be of the SLB MUX and not of the NSG appliance.  (Inbound should create 2 flow entries, 1 IPv4 and 1 IPv6.  How to handle double encap (2 headers) before the flow lookup - could we explain the logic?