IETF Logo Mail Archive

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

Susan Hares <shares@ndzh.com> Tue, 30 March 2021 13:33 UTC

Return-Path: <shares@ndzh.com>
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 5248A3A120E for <idr@ietfa.amsl.com>; Tue, 30 Mar 2021 06:33:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.347
X-Spam-Level: *
X-Spam-Status: No, score=1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 7IZUH4X3qSFH for <idr@ietfa.amsl.com>; Tue, 30 Mar 2021 06:33:34 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9C303A1265 for <idr@ietf.org>; Tue, 30 Mar 2021 06:33:22 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=50.107.124.96;
From: Susan Hares <shares@ndzh.com>
To: idr@ietf.org
Date: Tue, 30 Mar 2021 09:33:08 -0400
Message-ID: <000001d72569$3eace130$bc06a390$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdclaLcVgb/8sLRSRQGh0zHSuDP1LQ==
Content-Language: en-us
X-Antivirus: AVG (VPS 210330-2, 03/30/2021), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/f0AU6rUMI4WgdAFFyS2d9WjXER0>
Subject: [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, 30 Mar 2021 13:33:38 -0000

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

v2.23.0 | Report a Bug | By Email