Update description for forwarding-viable

release/models/interfaces/openconfig-if-sdn-ext.yang

@@ -47,11 +47,34 @@ module openconfig-if-sdn-ext {
         This is used by an external programming entity to disable an interface
         (usually part of an aggregate) for the purposes of forwarding
         traffic. This allows a logical aggregate to continue to be
-        used with partial capacity, for example.  Note that setting
-        `forwarding-viable = false` is not equivalent to
-        administratively disabling the interface -- in particular, the
-        interface is expected to participate in L2 protocols such as
-        LLDP or LACP even if it blocked from forwarding traffic.";
+        used with partial capacity. Setting `forwarding-viable = false` is not 
+        equivalent to administratively disabling the interface.
+        Some rules to follow when a port/bundle is set for 
+        Forwarding-viable=False:
+          1. Given that L2 protocols like LACP should be allowed to be 
+          transmitted and received on such ports, a device mustn't consider 
+          such ports in the calculation for minimum number of links required 
+          for an aggregate bundle when such a configuration exists on the box.
+          Hence, the device mustn't disable the bundle because the minimum
+          number of member links requirement is not met for the bundle.
+
+          2. L2 protocols like LLDP, LACP must be allowed for transmit and 
+          receive on such ports/bundles, IS-IS PDUs should be handled as per the 
+          requirements for L3 packets below.
+
+          3. L3 packets, control-plane as well as data-plane must be received
+          but not transmitted on such ports/bundles. Since the port is receiving 
+          L3 packets, inflight data-plane traffic will continue to be delivered to its 
+          destination post FIB lookup. Also, received control-plane traffic should be 
+          handled normally. Given that the router is not allowed to transmit L3 control-plane 
+          packets on such a port with its FV set to false, if this is a singleton 
+          port, OR if all member interfaces in a bundle are ever set to be FV=False, 
+          expectations are that the remote end of the connection will have its L3 protocol's 
+          dead-interval OR hold-down timer expired taking down the adjacency/peering on 
+          that connection.
+
+          4. An implementation should follow rule#3 even when the subject
+          port/bundle is the last resort of communication for the device.";
     }
   }