Re: [Idr] WG adoption for draft-haas-flowspec-capability-bits - 3/30 to 4/13

Christoph Loibl <c@tix.at> Tue, 06 April 2021 11:09 UTC

Return-Path: <c@tix.at>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC4AD3A1C2B for <idr@ietfa.amsl.com>; Tue, 6 Apr 2021 04:09:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=tix.at
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 S2kDQwFnRIwF for <idr@ietfa.amsl.com>; Tue, 6 Apr 2021 04:09:23 -0700 (PDT)
Received: from mail.fbsd.host (mail.fbsd.host [IPv6:2001:858:58::22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B32153A1C28 for <idr@ietf.org>; Tue, 6 Apr 2021 04:09:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tix.at; s=rev1; h=References:To:Cc:In-Reply-To:Date:Subject:Mime-Version:Content-Type :Message-Id:From:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=bqAd7buvJCoPJzb+JSqW1FiPjO9TpU+RurJ7c9TQsIY=; b=CfbFepZ9q4+sB0hUSU7gbYXWJa Sn3XKReaVJtbbC3ozSdWisa+gUGGfSTMG66R3i2SMP11yEXzsm2yI47P8jg4AzoqPQuPXWARlszJn UXrF0CX6rDkmzBvgD+1VSMk0d0POCyUR6iuE8ZSzNWCpxfqUxEJQCHKfhZBlh9MB5u49j00TAmWpu SPMMqZ1eGxjd/54yNqnJaQmnNfziybrtpnLAT8xt5hIhuj9HzCOlF3DzGkMepcWLZ/8yAkenYaJ6p VZMTYqX4rin1zqfCLxJoIR5RPV2C7AHuMr0vF0aCLfFDrVAMVhKOF125jc1zTSaFpHQr5BObGxlJY /6V9H31w==;
Received: from 213-225-15-174.nat.highway.a1.net ([213.225.15.174] helo=[192.168.43.10]) by mail.fbsd.host with esmtpsa (TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.94) (envelope-from <c@tix.at>) id 1lTja0-000HgZ-Os; Tue, 06 Apr 2021 13:09:09 +0200
From: Christoph Loibl <c@tix.at>
Message-Id: <60F5E1BC-F767-4BC4-BE77-7CCF92191AC8@tix.at>
Content-Type: multipart/alternative; boundary="Apple-Mail=_66DC4993-93AF-4537-B19C-B928C49F54E5"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Tue, 6 Apr 2021 13:09:07 +0200
In-Reply-To: <000001d72569$3eace130$bc06a390$@ndzh.com>
Cc: idr@ietf.org
To: Susan Hares <shares@ndzh.com>
References: <000001d72569$3eace130$bc06a390$@ndzh.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
X-Scanned-By: ClamAV primary on mail.fbsd.host (78.142.178.22); Tue, 06 Apr 2021 13:09:08 +0200
X-SA-Exim-Connect-IP: 213.225.15.174
X-SA-Exim-Mail-From: c@tix.at
X-SA-Exim-Scanned: No (on mail.fbsd.host); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/WF-q2ApULWiaXA27Udt-7hGDqys>
Subject: Re: [Idr] WG adoption for draft-haas-flowspec-capability-bits - 3/30 to 4/13
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Apr 2021 11:09:29 -0000

Hi,

1) yes

2) It may solve the incremental deployment problem that we observe with FS1 and may allow FS extensions to be implemented without waiting for a FS2.

However it will not solve all the problems of FS1 and will most probably delay any work on FS2.

3) yes

I support adoption.

Cheers Christoph  

-- 
Christoph Loibl
c@tix.at | CL8-RIPE | PGP-Key-ID: 0x4B2C0055 | http://www.nextlayer.at



> On 30.03.2021, at 15:33, Susan Hares <shares@ndzh.com> wrote:
> 
> This is a Working Group adoption call for
> https://tools.ietf.org/html/draft-haas-flowspec-capability-bits
> 
> The draft suggests a mechanism to address our incremental deployment issues
> for BGP Flowspec.
> 
> As you discuss this mechanism, there are 3 questions to consider:
> 
> 1) Is this document clear about the proposal? 
> 
> 2) Do you think we should do this with Flow Specification v2?
> Or should we do this instead of Flow Specification v2? 
> 
> 3) Will this help operational networks? 
> 
> Cheerily, Susan Hares 
> 
> 
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr