diff --git a/keps/sig-network/4410-k8s-network-interface/README.md b/keps/sig-network/4410-k8s-network-interface/README.md
index 6c72140eb92..80bb6dfebc2 100644
--- a/keps/sig-network/4410-k8s-network-interface/README.md
+++ b/keps/sig-network/4410-k8s-network-interface/README.md
@@ -50,8 +50,9 @@ and accommodate advanced functionalities and potential areas for expansion.
 9. Provide the ability to identify the IP address family without parsing the value (such as a field)
 10. Provide as much backwards-compatibility with CNI as is feasible
 11. Guarantee the network is setup and in a healthy state before containers are started (ephemeral, init, regular)
-12. Provide support for Kata and other virtualized runtimes
-13. Provide a reference implementation
+12. If feasible, provide API awareness of Pod network namespaces (e.g. interface names)
+13. Provide support for Kata and other virtualized runtimes
+14. Provide a reference implementation
 
 ### Non-Goals
 
@@ -76,6 +77,13 @@ As a cluster operator, I need the ability to determine what networks are availab
 
 As a Kubernetes developer, I need the ability to have extension points for pod network setup, teardown and update so that I can support future Kubernetes networking features with either reducing the changes to core kubernetes or eliminating them
 
+#### Story 4
+
+As a tool which manages eBPF programs on a Kubernetes cluster (bpfman,
+inspektorgadget), I would like to be able to see the network interfaces of a
+`Pod` via the Kubernetes API so that I can attach TC/XDP network programs to
+those interfaces based on knowing the Pod name.
+
 ### Notes/Constraints/Caveats
 
 Changes to the pod specification will require hard evidence.