Disposition of Miscellaneous Capabilities draft

[Ross Callon <rcallon@juniper.net>]

As some of you might have noticed, the Miscellaneous Capabilities
draft has timed out. My intention is to NOT re-issue this. Instead, I
would like to propose that the parts of this that are actually new be
folded into the Routing Control Plane Security Capabilities document
(draft-zhao-opsec-routing-capabilities-02.txt), and the rest be dropped.

When we thought that there was going to be a complete set of
capabilities drafts, the idea of putting things that didn't fit anywhere
else into a "miscellaneous" draft seemed to make sense. Now that
it is clear that a complete set of capabilities draft is not going to
happen, the idea of a "miscellaneous" draft makes less sense
(particularly since all the parts of this draft that are new will fit into
another draft).

Specifically, looking at the table of contents for the most recent
(-00) version of the miscellaneous capabilities, it contained:

1.  Introduction
2.  IP Stack Capabilities
3.  Performance and Prioritization
     3.1.  Security Features Should Have Minimal Performance Impact
     3.2.  Prioritization of Management Functions
     3.3.  Prioritization of Routing Functions
     3.4.  Resources used by IP Multicast
4.  Security Features Must Not Cause Operational Problems

Section 2, 3.1, and 4 were taken from rfc3871 without any change.
Sections 3.2, 3.3, and 3.4 needed update based on comments
received (particularly from Russ White).

Thus my proposal is to update 3.2, 3.3, and 3.4 and fold these into
the routing control plane draft (I have already done this, and the text
is in draft-zhao-opsec-routing-capabilities-02.txt), and let the rest
fade into history.

Let me know if there is any strong objection to this plan.

Thanks, Ross