Telechat Review of draft-ietf-karp-ops-model-09

Request Review of draft-ietf-karp-ops-model
Requested rev. no specific revision (document currently at 10)
Type Telechat Review
Team Security Area Directorate (secdir)
Deadline 2013-11-19
Requested 2013-10-31
Authors Sam Hartman, Dacheng Zhang
Draft last updated 2013-11-14
Completed reviews Genart Last Call review of -07 by Ben Campbell (diff)
Genart Last Call review of -09 by Ben Campbell (diff)
Secdir Last Call review of -07 by Radia Perlman (diff)
Secdir Telechat review of -09 by Radia Perlman (diff)
Opsdir Telechat review of -09 by Benoît Claise (diff)
Assignment Reviewer Radia Perlman 
State Completed
Review review-ietf-karp-ops-model-09-secdir-telechat-perlman-2013-11-14
Reviewed rev. 09 (document currently at 10)
Review result Has Nits
Review completed: 2013-11-14


I previously reviewed version -07.  This version (-09) is slightly updated.  I'd requested an introduction about what is different for "routing protocol security" rather than, say, an endnode authenticating to an access point.  The authors did add a sentence or so:


 routers need to function in order to

   establish network connectivity.  As a result, centralized services
   cannot typically be used for authentication or other security tasks;
   see Section 4.4.  In addition, routers' roles affect how new routers
   are installed and how problems are handleded;"

There's a couple of typos in the added sentences.  "routers" should be capitalized.  "Handleded" is a typo.

I don't have any objections to the document.


On Tue, Aug 13, 2013 at 10:02 PM, Radia Perlman 


radiaperlman at



I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG.  These comments were written primarily for the benefit of the security area directors.  Document editors and WG chairs should treat these comments just like any other last call comments.

This is a useful document as an informational RFC. The technical content is interesting and useful.

I think the document would be much improved with an introduction about what is different for "routing protocol security" rather than, say, an endnode authenticating to an access point, or nodes forming a peer relationship in an overlay network.  So, for instance, "normal security issues" (i.e., outside the scope of KARP) might assume the network is up, so that it's possible to get CRLs, or be available to be managed, whereas perhaps KARP is targetting cases which depend on less infrastructure.  It would be nice if this document were to have an introduction that talks about things like that.

As for typos...3rd line up from bottom of page 14 has a glitch involving a bunch of spaces and an extra comma after the word "peers".  And I can't parse the last sentence of the 1st paragraph of section 7. "...complexity of and update and risk...."

Speaking of PKI...the document talks about certificates expiring, but not being revoked (CRL, OCSP).