[Idr] FSv2 - for IP Basic Interim today at 10:00am to 11:30am EDT (6/3/2024)

[Susan Hares <[e-mail]>]

Greetings:

Today we are holding an IDR interim on Flow Specification version 2 (FSv20

Today's interim focuses on whether the minimal subset for FSv2 in
draft-hares-idr-ip-basic-02.txt
https://datatracker.ietf.org/doc/draft-hares-idr-fsv2-ip-basic/

should be adopted as the minimal subset for FSv2.

This draft is in an adoption call for the minimal subset for the FSv2 work
https://datatracker.ietf.org/doc/draft-ietf-idr-flowspec-v2/

It is the chair's intent to select this minimal subset.
Join us if you like to catch up on the FSv2.

Below I've summarized why we are looking at a minimal subset that can be expanded upon.

Sue

--------

Flow specification version 2 has the challenge inherited from Flow Specification (v1)

There are two conflicting sets of requirements.

The first requirement is to provide a simple update to FSv1 that provides the following:

  1.  User Ordering  of filters,
  2.  deterministic action ordering,
  3.  deterministic actions upon a failure of a flow specification action,
  4.  FSv1 filters, and
  5.  FSv1 actions

The second requirement is to provide a Flow Specification that can become a platform for new applications.

New applications have appeared from IETF groups advanced DDOS,  SFC, detnet, CATs, and TEAS.

These applications require

  1.  User Ordering of filters,
  2.  User Ordering of Actions + Deterministic Action filters,
  3.  New IP Filters,
  4.  New IP Actions with some actions having more complexity than Extended Community,
  5.  Non-IP Actions (L2, SFC, grouping by interface, grouping, and identification per network slice).

The IDR chairs hope that a methodology of agreeing upon a simple base and with additions can allow both simple and complex FSv2.