KEP-3008: minor update to future work and alternatives

keps/sig-node/3008-cri-class-based-resources/README.md

@@ -307,7 +307,11 @@ This might be a good place to talk about core concepts and how they relate.
 This is only the first in getting class-based resources supported in
 Kubernetes. Important pieces like resource status, resource disovery and
 permission control are [non-goals](#non-goals) not solved here. However, these
-aspects are briefly discussed in [future work](#future-work).
+aspects are briefly discussed in [future work](#future-work). However, the risk
+in this sort of piecemeal approach is finding devil in the details, resulting
+in inconsistent and/or crippled and/or cumbersome end result. However, there is
+a lot of experience in extending the API and understanding which sort of
+solutions are functional and practical.
 
 ### Risks and Mitigations
 
@@ -491,6 +495,12 @@ the pod qos class in the future.  The runtime could provide a set of OOM
 classes, making it possible for the user to specify a burstable pod with low
 oom priority (low chance of being killed).
 
+### Default class
+
+A mechanism for indicating that the (runtime) default class should be used. The
+default class would/should be a node/runtime specific attribute. How should
+this be specified in the CRI protocol/`cri-api` and Pod spec?
+
 ### Test Plan
 
 <!--
@@ -1071,6 +1081,16 @@ The scope of the KEP could be narrowed down by concentrating on RDT only,
 dropping support for blockio. This would center the focus on RDT only which is
 well understood and specified in the OCI runtime specification.
 
+### Widen the scope
+
+The currently chosen strategy of this KEP is "minimum viable product" with
+incremental future steps of improving and supplementing the functionality. This
+strategy was chosen in order to make the review easier by handling smaller
+digestible (but still coherent and self-contained) chunks at a time.
+
+An alternaive would be to widen the scope of this KEP to include some or all of
+the subjects mentioned in [future work](#future-work) (i.e. resource discovery,
+status/capacity and access control).
 
 ## Infrastructure Needed (Optional)