Re: [sidr] BGPSEC Threat Model ID

Paul Hoffman <paul.hoffman@vpnc.org> Thu, 03 November 2011 16:19 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4036A1F0C8B for <sidr@ietfa.amsl.com>; Thu, 3 Nov 2011 09:19:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.59
X-Spam-Level:
X-Spam-Status: No, score=-102.59 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 cBIm78bfmOMW for <sidr@ietfa.amsl.com>; Thu, 3 Nov 2011 09:19:53 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id C93461F0C7C for <sidr@ietf.org>; Thu, 3 Nov 2011 09:19:53 -0700 (PDT)
Received: from [10.20.30.100] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id pA3GJqNS093267 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <sidr@ietf.org>; Thu, 3 Nov 2011 09:19:53 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1251.1)
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <p06240808cad85ff73d61@[193.0.26.186]>
Date: Thu, 03 Nov 2011 09:19:52 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <080F8FFF-D2C7-4414-B53A-233F88D2009F@vpnc.org>
References: <E96517DD-BAC7-4DD8-B345-562F71788C6A@tcb.net> <p06240807cad42f85eb7d@[193.0.26.186]> <32744.216.168.239.87.1320175657.squirrel@webmail.tcb.net> <p06240801cad6ab773279@[193.0.26.186]> <D9A38669-883D-4090-9F95-BC5C63220950@tcb.net> <p06240801cad800485596@[193.0.26.186]> <EEBF68E0-FAD9-4AF3-B81B-78760D200D9B@tcb.net> <p06240808cad85ff73d61@[193.0.26.186]>
To: sidr wg list <sidr@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [sidr] BGPSEC Threat Model ID
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Nov 2011 16:19:54 -0000

On Nov 3, 2011, at 8:43 AM, Stephen Kent wrote:

>> If you're intended to play the "charter says .." card then we're wasting our time.
> 
> Yes, we are both wasting our time at this stage.


Maybe not. The charter does not say "every other topic cannot even be mentioned": instead, the charter limits the topics that are meant to be fully covered by the protocols.

Personally, I would prefer to see the threat model document say in the introduction "the following topics are considered to be BGP security threats but are not dealt with in this document:" followed by a list that includes route leakage (with a concise definition of what is meant by it in this context). A similar statement in the Security Considerations section would also be useful for the people who tend to skip introductions but still need to know the limitations of the document.

--Paul Hoffman