Re: [sidr] suggested amendment to draft-ymbk-bgpsec-reqs

Andrei Robachevsky <andrei.robachevsky@gmail.com> Mon, 04 April 2011 10:27 UTC

Return-Path: <andrei.robachevsky@gmail.com>
X-Original-To: sidr@core3.amsl.com
Delivered-To: sidr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D16E13A6961 for <sidr@core3.amsl.com>; Mon, 4 Apr 2011 03:27:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.49
X-Spam-Level:
X-Spam-Status: No, score=-3.49 tagged_above=-999 required=5 tests=[AWL=-0.118, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J7iZlVV1FhzU for <sidr@core3.amsl.com>; Mon, 4 Apr 2011 03:27:14 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 89D9B3A695E for <sidr@ietf.org>; Mon, 4 Apr 2011 03:27:14 -0700 (PDT)
Received: by ewy19 with SMTP id 19so1896392ewy.31 for <sidr@ietf.org>; Mon, 04 Apr 2011 03:28:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=VkSkSDGjKQzdWljKOzfhK9OVmd3e6j12QI0w04MeQg8=; b=cHhIxnwnilX8g9iwQQvAQcrT1NszmWQCr8HW0LMxSObV4ldpSFqxk88m2agNDhbEnl t1YwwE1m8AgKx0mCG+KA/G+6Asfxi7D45MtJCJVhIUTjoPPZY4RY04rLcHrGugviJDWw qK9cor6wie7yiid1f79SXkFay6qtSktaTjdnc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=YRt7It2AOXsfXuQlshH1opGHpPa+T+frw5hp0fVPTQjbcG6+3N5mJBN9SSsDlBOivo umP4YktxRj4Lc+N7C+f6u9w33utE6MXhf16GTU4VAsozQkEPWy1mGONg+F0IgqZ1dT21 rUuSdMjFvkXfts8nkpqIFRDsPkF+i7lJoYCRg=
Received: by 10.213.22.148 with SMTP id n20mr1492292ebb.40.1301912935133; Mon, 04 Apr 2011 03:28:55 -0700 (PDT)
Received: from Andrei-Robachevskys-MacBook-Air.local (d126092.upc-d.chello.nl [213.46.126.92]) by mx.google.com with ESMTPS id q53sm3213015eeh.25.2011.04.04.03.28.52 (version=SSLv3 cipher=OTHER); Mon, 04 Apr 2011 03:28:53 -0700 (PDT)
Message-ID: <4D999D63.4060706@gmail.com>
Date: Mon, 04 Apr 2011 12:28:51 +0200
From: Andrei Robachevsky <andrei.robachevsky@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Sandra Murphy <Sandra.Murphy@sparta.com>
References: <4D95C701.9010308@gmail.com> <Pine.WNT.4.64.1104011619360.8152@SMURPHY-LT.columbia.ads.sparta.com>
In-Reply-To: <Pine.WNT.4.64.1104011619360.8152@SMURPHY-LT.columbia.ads.sparta.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: sidr@ietf.org
Subject: Re: [sidr] suggested amendment to draft-ymbk-bgpsec-reqs
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 04 Apr 2011 10:27:21 -0000

Sandra Murphy wrote on 01-04-11 22:24:
> 
> 
> On Fri, 1 Apr 2011, Andrei Robachevsky wrote:
> 
>> Hi,
>>
>> I propose the inclusion of the following requirement:
>>
>> 3.x A BGPsec design should not decrease the performance characteristics
>> of the BGP, nor have a negative impact on the overall resilience of the
>> routing system.
> 
> Could you say how strictly you would want this requirement interpreted?
> For example, I would say that not even TCP-AO has NO impact on
> performance and resilience.  Do you want the requirement to forbid TCP-AO?
> 
> --Sandy, speaking as wg co-chair
> 

I agree with the comments on the list, it was more a strawman. How about
a more moderate requirement:

3.x A BGPsec design MUST provide analysis of the operational
considerations for deployment with respect to the impact on the
performance characteristics and the overall resilience of the routing
system. 	

This may be already implied in 3.3, but I'd like to make these two
aspects more explicit.

> 
> 
>>
>> Examples that I have in mind is the convergence time or a solution that
>> can make the global routing system more fragile (e.g. an expired
>> signature blacking out a significant part of the Internet). Perhaps that
>> should also be covered in the deployment considerations, since this
>> depends partly on local policy decisions.
>>
>> Andrei
>> _______________________________________________
>> sidr mailing list
>> sidr@ietf.org
>> https://www.ietf.org/mailman/listinfo/sidr
>>


Andrei