1. 1 Miscellaneous Capabilities for IP Network Infrastructure IETF 64 Vancouver, BC, Canada November 2005

2. 2 Goal of This Document OPSEC WG Charter outlines various documents to be produced –Framework; Standards Survey; Current Practices; Packet Filtering; Event Logging; In-Band; Out-of-Band; Interface; AAA; Documentation & Assurance; Miscellaneous Miscellaneous Caps includes any text from RFC3871 that doesn’t fit other documents Draft is largely taken from RFC3871, with a bit of additional text

3. 3 Issue: Must / Should / May We are defining Capabilities We are not writing Requirements What is required may vary between environments, and over time Do we want to specify MUST, SHOULD, MAY, and so on? Current compromise: MUST (etc..) is in the context of the capability

4. 4 Context for MUST, SHOULD, … “The use of the terms MUST, SHOULD, and so on are in the context of each capability in the sense that if you conform to any particular capability then you MUST or SHOULD do what is specified for that capability, but there is no requirement that you actually do conform to any particular capability.”

5. 5 Contents of Misc Cap Draft Introduction –Describes what this document includes –Otherwise references other WG documents Route Filtering Capabilities –Taken from RFC3871 IP Stack Capabilities –Taken from RFC3871

6. 6 Contents of Draft, continued Performance and Prioritization –Somewhat extended from what is in 3871 –Nearly all as SHOULD (rather than MUST) Security Features must not cause operational problems –Again taken from RFC3871 –(I have to wonder whether this is almost too obvious)

7. 7 Proposed Disposition of Draft We are not done Comments and updates will be needed I think that it is a reasonable start Propose that it become a working group draft