@@ Page 9 @@
     endpoints sending application data and acknowledgements,
     respectively.  Since CCIDs apply at the level of half-connections,
     we abbreviate HC-Sender to "sender" and HC-Receiver to "receiver" in
-    this document.  See DCCP for more discussion.
+    this document.  See [DCCP] for more discussion.
 
     For simplicity, we say that senders send DCCP-Data packets and
     receivers send DCCP-Ack packets.  Both of these categories are meant
@@ Page 34 @@
 
 
     CCID 3 also introduces three sets of numbers whose values should be
-    allocated by IANA.  We refer to allocation policies, such as
-    Standards Action, outlined in RFC 2434, and most registries reserve
-    some values for experimental and testing use [RFC 3692].
+    allocated by IANA, namely CCID 3-specific Reset Codes, option types,
+    and feature numbers.  These ranges will prevent any future
+    CCID 3-specific allocations from polluting DCCP's corresponding
+    global namespaces; see [DCCP] (Section 10.3).  However, we note that
+    this document makes no particular allocations from the Reset Code
+    range, except for experimental and testing use [RFC 3692].  We refer
+    to the Standards Action policy outlined in RFC 2434.
 
 12.1.  Reset Codes
 
@@ Page 34 @@
     defining the Reset Code.  Reset Codes 184-190 and 248-254 are
     permanently reserved for experimental and testing use.  The
     remaining Reset Codes -- 128-183, 191-247, and 255 -- are currently
-    reserved, and should be allocated with the IETF Consensus policy,
-    which requires RFC publication (not necessarily standards-track).
+    reserved, and should be allocated with the Standards Action policy,
+    which requires IESG review and approval and standards-track IETF RFC
+    publication.
 
 12.2.  Option Types
 
@@ Page 34 @@
     allocates option types 192-194, and option types 184-190 and 248-254
     are permanently reserved for experimental and testing use.  The
     remaining option types -- 128-183, 191, 195-247, and 255 -- are
-    currently reserved, and should be allocated with the IETF Consensus
-    policy, which requires RFC publication (not necessarily standards-
-    track).
+    currently reserved, and should be allocated with the Standards
+    Action policy, which requires IESG review and approval and
+    standards-track IETF RFC publication.
 
 12.3.  Feature Numbers
 
@@ Page 34 @@
     numbers 184-190 and 248-254 are permanently reserved for
     experimental and testing use.  The remaining feature numbers --
     128-183, 191, 193-247, and 255 -- are currently reserved, and should
-    be allocated with the IETF Consensus policy, which requires RFC
-    publication (not necessarily standards-track).
+    be allocated with the Standards Action policy, which requires IESG
+    review and approval and standards-track IETF RFC publication.