diff --git a/configuration/chassis.rst b/configuration/chassis.rst
index 2a8a317..11b433a 100644
--- a/configuration/chassis.rst
+++ b/configuration/chassis.rst
@@ -77,6 +77,15 @@
 A ``singleton port`` uniquely identifies a switch port and it contains the following fields:
 
 * ``id``: An arbitrary ID, unique in the scope of a chassis. **Required**
+
+    .. note::
+        We recommend using the following naming convention for both ONOS network config and Stratum chassis config:
+            - For unchannelized ports, use the **front panel port** number directly.
+            - For channelized ports, use the **front panel port number * 100 + channel id**.
+              For example, we can use port id ``2903`` for port ``29/3`` (port 29 channel 3).
+            - Note that we use **zero-based** channel number for singleton port ``id``
+              but the ``channel`` field described below uses **one-based** channel number.
+
 * ``name``: An optional user friendly name for the port (e.g., ``10/1`` to identify channel
   1 of front-panel port 10). **Required**
 
diff --git a/configuration/network.rst b/configuration/network.rst
index 1ab1766..6f6d0d0 100644
--- a/configuration/network.rst
+++ b/configuration/network.rst
@@ -115,19 +115,9 @@
 Before describing the ONOS netcfg, it is worth nothing how we refer to ports for
 Tofino-based devices. Netcfg uses the format ``device:<name>/<port-number>``.
 
-``<port-number>`` is a special value that is usually different than the number
-shown in the switch front panel. It is the same number used for P4 table
-programming and depends on the specific Tofino ASIC SKU (e.g., dual-pipe vs.
-quad-pipe) and switch vendor/platform. In Stratum this is often referred to as
-the *SDK port ID*, as this is the number used for all Tofino SDK calls. In Intel
-documentation this is referred to as the ``DP_ID``. We plan to remove this
-dependency on such a low level detail in future releases, but for now, to find
-out the mapping between front-panel ports and ``DP_ID`` you have the following
-options:
-
-- Ask your switch vendor
-- Use the command `pm.show` on the BF shell of a running Stratum instance
-  (see :ref:`troubleshooting_guide`)
+``<port-number>`` is a unique, arbitrary value that should be consistent
+with the ``id`` field defined in Stratum chassis config.
+See :ref:`singleton_port` for more details.
 
 Bridging and Unicast Routing
 ----------------------------