[secdir] Review of draft-ietf-opsec-routing-protocols-crypto-issues-04

Nicolas Williams <Nicolas.Williams@oracle.com> Thu, 20 May 2010 17:24 UTC

Return-Path: <Nicolas.Williams@oracle.com>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id A04D93A6965 for <secdir@core3.amsl.com>; Thu, 20 May 2010 10:24:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.421
X-Spam-Status: No, score=-5.421 tagged_above=-999 required=5 tests=[AWL=1.177, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id IZY6sqAAHGj2 for <secdir@core3.amsl.com>; Thu, 20 May 2010 10:24:55 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com []) by core3.amsl.com (Postfix) with ESMTP id B268A3A699A for <secdir@ietf.org>; Thu, 20 May 2010 10:23:47 -0700 (PDT)
Received: from rcsinet13.oracle.com (rcsinet13.oracle.com []) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4KHNM8g031942 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 20 May 2010 17:23:23 GMT
Received: from acsmt353.oracle.com (acsmt353.oracle.com []) by rcsinet13.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4KDhE1X013077; Thu, 20 May 2010 17:23:20 GMT
Received: from abhmt002.oracle.com by acsmt354.oracle.com with ESMTP id 254758111274376197; Thu, 20 May 2010 10:23:17 -0700
Received: from oracle.com (/ by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 20 May 2010 10:23:15 -0700
Date: Thu, 20 May 2010 12:23:11 -0500
From: Nicolas Williams <Nicolas.Williams@oracle.com>
To: secdir@ietf.org
Message-ID: <20100520172310.GQ9605@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.20 (2010-03-02)
X-Auth-Type: Internal IP
X-Source-IP: rcsinet13.oracle.com []
X-CT-RefId: str=0001.0A090202.4BF5700E.0123:SCFMA4539811,ss=1,fgs=0
Cc: jjaeggli@checkpoint.com, manav.bhatia@alcatel-lucent.com, vishwas@ipinfusion.com, shares@nexthop.com
Subject: [secdir] Review of draft-ietf-opsec-routing-protocols-crypto-issues-04
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 20 May 2010 17:24:56 -0000

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

This document aims to be an Informational RFC describing security
problems with various routing protocols.

Aside from various spelling and other nits that the RFC-Editor can
easily handle, I have no issues with this document and it is ready for