Re: [secdir] SecDir Review of draft-ietf-lisp-alt-09
Vince Fuller <vaf@cisco.com> Mon, 28 November 2011 22:51 UTC
Return-Path: <vaf@cisco.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 2966C11E80E7; Mon, 28 Nov 2011 14:51:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level:
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_43=0.6, RCVD_IN_DNSWL_MED=-4]
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 uxlMsEVnXQk4; Mon, 28 Nov 2011 14:51:12 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 68FB611E80D7; Mon, 28 Nov 2011 14:51:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=vaf@cisco.com; l=650; q=dns/txt; s=iport; t=1322520668; x=1323730268; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=BHbrSOzqDsezvqgXhYWwhilxZjQA0SHf2hYUrnZcKjY=; b=QzyB+diZmOidUAMCgx1XoRPr30xsQZqkmo2g6JE45EO4OSZq0WJJgOnb FMNEQEIlbHNPdmAz2dazdB8ulnPF4lcO2hzCaPbkW+KeQuj6arUrHEhV+ IvVj+J0mC6urePSQ6vyN0nGp7dJk9u04tkPvTTqoON5vtp71r8Fkbu1wv I=;
X-IronPort-AV: E=Sophos;i="4.69,587,1315180800"; d="scan'208";a="39514429"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-8.cisco.com with ESMTP; 28 Nov 2011 22:51:08 +0000
Received: from vaf-mac1.cisco.com (vaf-mac1.cisco.com [128.107.165.254]) by rcdn-core2-2.cisco.com (8.14.3/8.14.3) with ESMTP id pASMp7m7015158; Mon, 28 Nov 2011 22:51:08 GMT
Received: by vaf-mac1.cisco.com (Postfix, from userid 113818) id 3E79C1A7BE16; Mon, 28 Nov 2011 14:51:07 -0800 (PST)
Date: Mon, 28 Nov 2011 14:51:07 -0800
From: Vince Fuller <vaf@cisco.com>
To: Catherine Meadows <meadows@itd.nrl.navy.mil>
Message-ID: <20111128225107.GB17970@vaf-mac1.cisco.com>
References: <EDF32EE2-6FB1-4A08-8AF5-3F912EF562D0@itd.nrl.navy.mil>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <EDF32EE2-6FB1-4A08-8AF5-3F912EF562D0@itd.nrl.navy.mil>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Mon, 28 Nov 2011 14:56:37 -0800
Cc: vaf@cisco.com, draft-ietf-lisp-alt.all@tools.ietf.org, iesg@ietf.org, secdir@ietf.org
Subject: Re: [secdir] SecDir Review of draft-ietf-lisp-alt-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: Mon, 28 Nov 2011 22:51:13 -0000
Thank you for the review. > All in all, I think this is a very thorough and well-though-out > discussion of the security considerations. My only suggestion would > be to include a forward reference to paragraph 10.3 in the > discussion of prefix leakage. I can certainly add such a reference as part of the forthcoming -10 draft. Can you be more specific about where you feel that the reference belongs? It looks like the topic of "route leakage" is mentioned on page 5 in the Intoduction section, then in section 6.2 where the suggestion of a separate SAFI for LISP+ALT is made, and, finally, in section 10.1. Thanks, --Vince
- [secdir] SecDir Review of draft-ietf-lisp-alt-09 Catherine Meadows
- Re: [secdir] SecDir Review of draft-ietf-lisp-alt… Vince Fuller
- Re: [secdir] SecDir Review of draft-ietf-lisp-alt… Catherine Meadows
- Re: [secdir] SecDir Review of draft-ietf-lisp-alt… Vince Fuller