Re: [secdir] review of draft-saucez-lisp-impact-04.txt

Damien Saucez <damien.saucez@inria.fr> Tue, 13 October 2015 06:13 UTC

Return-Path: <damien.saucez@inria.fr>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CE041B3904; Mon, 12 Oct 2015 23:13:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.56
X-Spam-Level:
X-Spam-Status: No, score=-6.56 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F-9uduA4ybCh; Mon, 12 Oct 2015 23:13:12 -0700 (PDT)
Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B89E1B3901; Mon, 12 Oct 2015 23:13:11 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.17,676,1437429600"; d="scan'208";a="182463755"
Received: from ppp-seco21th2-46-193-174-136.wb.wifirst.net (HELO [10.188.169.250]) ([46.193.174.136]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/AES128-SHA; 13 Oct 2015 08:13:09 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Damien Saucez <damien.saucez@inria.fr>
In-Reply-To: <201510130301.t9D31WfT016243@sylvester.rhmr.com>
Date: Tue, 13 Oct 2015 08:13:08 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <5CB43879-FDB2-4C69-9B3C-9830E2E9F8E0@inria.fr>
References: <201510130301.t9D31WfT016243@sylvester.rhmr.com>
To: Hilarie Orman <ho@alum.mit.edu>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/secdir/Rppdm5XbSHe45Br19NNP0jAvzbA>
X-Mailman-Approved-At: Thu, 22 Oct 2015 07:18:03 -0700
Cc: draft-saucez-lisp-impact@tools.ietf.org, iesg@ietf.org, secdir@ietf.org
Subject: Re: [secdir] review of draft-saucez-lisp-impact-04.txt
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 13 Oct 2015 06:13:15 -0000

Dear Hilarie,

Thank you for the review. I would have a question regarding the document you reviewed. Did you review th

draft-sauces-lisp-impact-04

or 

draft-ietf-lisp-impact-04

Thank you,

Damien Saucez 

On 13 Oct 2015, at 05:01, Hilarie Orman <ho@alum.mit.edu> wrote:

> Secdir review of LISP Impact
> draft-saucez-lisp-impact-04.txt
> 
> Do not be alarmed.  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.
> 
> A new way of handling routing information has been defined in IETF
> documents about the Locator/Identifier Separation Protocol (LISP).
> The draft under discussion here elaborates on the possible
> consequences of widespread use of LISP.
> 
> The draft punts on security considerations and refers to previous
> documents describing threats to LISP and how LISP uses cryptography
> for protecting the integrity of its messages.
> 
> It seems to me that if the purported impact of LISP is to "scale the
> Internet", then its impact on security should be a major part of the
> equation.  Will it make routing information more or less vulnerable
> malicious manipulation?  How will it affect the stability of a network
> that is under constant threat of attack?
> 
> I don't feel that the draft can achieve its purpose without addressing
> security.
> 
> Hilarie
> 
> PS. I was very disappointed to realize that this was not a draft
> about my favorite programming language.
>