[secdir] Secdir review of draft-ietf-karp-ops-mode-09
Radia Perlman <radiaperlman@gmail.com> Wed, 13 November 2013 06:35 UTC
Return-Path: <radiaperlman@gmail.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D47521F8FF5; Tue, 12 Nov 2013 22:35:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.489
X-Spam-Level:
X-Spam-Status: No, score=-2.489 tagged_above=-999 required=5 tests=[AWL=0.110, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XBATKwbgTOCq; Tue, 12 Nov 2013 22:35:38 -0800 (PST)
Received: from mail-la0-x231.google.com (mail-la0-x231.google.com [IPv6:2a00:1450:4010:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id B6EFD11E8177; Tue, 12 Nov 2013 22:35:35 -0800 (PST)
Received: by mail-la0-f49.google.com with SMTP id er20so2768050lab.22 for <multiple recipients>; Tue, 12 Nov 2013 22:35:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=/7uEX6SyeUBbTCDGx7z+cigrEJn113azdvEcea00BNA=; b=fTPKz2AR8tAHomLRiHn2vJ9+9rCLwVN3vyh0/sF4fBscdi5/nsHLU5eSDWeObMhj8n D6LHi1dS2D1ILwnpdPV0v6TwzwuNWI30TFTPQ2OX3EfFrGeuPoH7OcZgHY7SqwkdKX/U 2nIYPBilmRSpSsMUI2aWLdBeq7lKyD3vIy7iBuVK4/NWXEfTz59afGpmqmeZ2N8W345H hpVdTRGSeKh4ZLGlc9H8BzbZ7GzNVG9LTZw2ZmPcyThDkZQpOKz1kDNpiib1FNJvtnks FRJyZo+HoqgxgMWbs5s6H2/rh75JFQzqDkUtL3IX2NjCkIi476WWSklT7x2QnbDFot2l F8EA==
MIME-Version: 1.0
X-Received: by 10.112.210.136 with SMTP id mu8mr12884515lbc.25.1384324534677; Tue, 12 Nov 2013 22:35:34 -0800 (PST)
Received: by 10.112.188.197 with HTTP; Tue, 12 Nov 2013 22:35:34 -0800 (PST)
Date: Tue, 12 Nov 2013 22:35:34 -0800
Message-ID: <CAFOuuo57sFRreUcXhooAZXcJG7pv7pw0p4TixYR21TtBw5tdJQ@mail.gmail.com>
From: Radia Perlman <radiaperlman@gmail.com>
To: The IESG <iesg@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>, draft-ietf-karp-ops-model.all@tools.ietf.org
Content-Type: multipart/alternative; boundary="001a11c3c70424b84904eb092c5b"
Subject: [secdir] Secdir review of draft-ietf-karp-ops-mode-09
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Nov 2013 06:35:39 -0000
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. Radia On Tue, Aug 13, 2013 at 10:02 PM, Radia Perlman <radiaperlman@gmail.com>wrote: > 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). > > Radia >
- [secdir] Secdir review of draft-ietf-karp-ops-mod… Radia Perlman