Subject: [karp] Requirement 22 of draft-ietf-karp-threats-reqs-04

From: Brian Weis <[email-masked]>
Date: Fri, 6 Apr 2012 15:58:02 -0700

(Speaking as a WG member.)

A second paragraph was added in this version to Requirement 22. While it's a valiant effort to try to give examples where a circular dependency does and does not exist, both examples are convoluted. Understanding the nuances of the examples, and whether or not in all cases of each example that the bad one is bad and the good one is good, is laborious.  Also it's also not clear to me that the added MUST is necessary. Wouldn't it be sufficient to add this as one reason for the dire warnings already communicated in the previous paragraph? 

I would suggest removing this paragraph completely, and adding something like the following sentence before the last sentence in the previous paragraph: "Relying on external systems may result in a circular dependency between routing and the security mechanisms such that routing cannot be started."

Brian

-- 
Brian Weis
Security Standards and Technology, SRTG, Cisco Systems
Telephone: +1 408 526 4796
Email: [email-masked]