[Idr] Flow Specification Interim Results (June 7th, 2021)

Susan Hares <shares@ndzh.com> Fri, 09 July 2021 15:58 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 5051A3A25D0 for <idr@ietfa.amsl.com>; Fri, 9 Jul 2021 08:58:26 -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, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.398, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id klFy6laRJZB0 for <idr@ietfa.amsl.com>; Fri, 9 Jul 2021 08:58:22 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net []) (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 CB7383A25CD for <idr@ietf.org>; Fri, 9 Jul 2021 08:58:21 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=;
From: "Susan Hares" <shares@ndzh.com>
To: <idr@ietf.org>
Date: Fri, 9 Jul 2021 11:58:08 -0400
Message-ID: <001b01d774db$39e30c80$ada92580$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_001C_01D774B9.B2D2A500"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Add02r5PQOyVrRGuRh+1RxSyVHcNNQ==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/EykIONhjXEktD6P_dGK1CGGKJA4>
Subject: [Idr] Flow Specification Interim Results (June 7th, 2021)
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: Fri, 09 Jul 2021 15:58:26 -0000

The Interim meeting report for the June 7th interim on Flow specification can be found on the IDR wiki at: 




The interim page for this interim is at: 

 <https://datatracker.ietf.org/meeting/interim-2021-idr-01/session/idr> https://datatracker.ietf.org/meeting/interim-2021-idr-01/session/idr


The minutes for the June 7th interim are at: 



Please send any comments on these minutes. 


The meeting discussed the following motivations for flow specification v2:  move to a full TLV format, expand sorting rules for firewall applications, and define clearly flow specification actions interactions. The move to a full TLV format will introduce a new type of error: a well formed but invalid TLV. 


The alternate to flow specification v2 is extending flow specification v1. This has been investigated by two proposals: capability bits (draft-haas-flowspec-capability-bits) and 

Explicit term ordering (draft-haas-idr-flowspec-term-order). 


The result of the interim is that developers and those deploying flow specification desired:

DDos Based work only in Flow specification v1, and all other work in v2. This work includes the following: a new TLV format, all AFI/SAFIs in new TLV, term ordering, new capabilities, and action resolution in Flow Specification.


The gray area after the interim is the existing drafts with redirect functions with deployed protocol. 

The following existing drafts are allowed for v1 only: 

* draft-ietf-idr-redirect-ip-02.txt

* draft-ietf-idr-path-redirect-11.txt

* draft-ietf-idr-flowspec-interfaceset-05.txt 


The following proposed drafts which augment these drafts will be considered for v1: 

* draft-ietf0-idr-srv6-flowspec-path-redirect, 

* draft-dmc-idr-flowspec-tn-aware-mobility. 


However, these authors of these drafts should also publish v2 forms of the draft. 


All other existing IDR flow specification drafts must transition to the v2 specification.  The flow specification v2 flow specification will be fast tracked with interims held to increase the speed.  Authors of v2 flow specification drafts are encourage to attend the interims. 


A full list of IDR flow specification drafts is provided on the wiki.