Flow Specification v2 work was chartered to fix the ordering problems with FSv1 (IPv4 RFC8955, IPv6 RFC8956, and to allow additions of new filters and actions. Flow Specification v2 (draft-ietf-idr-flowspec-v2-03) is technically correct, but a lot to implement.
Since IDR requires 2 implementations to publish an RFC, the implementers have requested we break the draft into "chunks" that can be
implemented a little at a time. These "chunks" (portions) of technology will be
Below is a description of the "chunks" of technology, and how four parallel design teams (design teams 1-4) will progress work on documents for each chunk.
By Design Team, we mean that the participants will be expected to:
By Open Design Teams, we mean that anyone may join the design team and attend the FSv2 interims. Minutes will be posted from the design team interims so that others can follow along.
By Four Parallel Open Design Teams, we mean that the 4 design teams will operate simulataneously to create documents for the "chunks" of technology from the original FSv2 work.
Our focus is to get "chunks" of FSv2 technology defined so that the following can happen:
Why are we doing this now? The CAR/CT work put FSv2 work on hold so we are trying to catch up.
The IDR draft (draft-ietf-idr-flowspec-v2-03) will be kept as an IDR WG draft that combines approved FSv2 issues. This document will collect approved changes into one place.
Send email to idr-chairs@ietf.org or contact Susan Hares (shares@ndzh.com).
The key addition for this chunk of FSv2 is the user ordering of filters defined by the FSv2.
This initial draft will stay with the FSv IPv4 and IPv6 and current actions in the Flow Specification Extended Community (FS-EC). The focus of this design team is to determine if the technology for user ordering of filters forms a good foundation for FSV2 work.
Design team: Design Team 1 - Basic IP FSv2
Meetings before IETF-120: 4/29 and 6/3 (Time 10-11:30am EDT)
Meets with Design Team 2: 5/6 and 6/10 (Time 10-11:30am EDT)
initial draft: draft-hares-idr-fsv2-IP-Basic
New drafts requested:
a. Drafts that discuss the pros/cons of filter ordering for work
b. Drafts with filters
FSv2 opens the possibility to add new filters for data packets (IP and non-IP). This chunk of work expands the IP filters to the IP packet headers (layers 3-7) and the payload.
Design team: Design Team 2 - More IP Filters for FSv2
Meetings before IETF-120: 5/6 and 6/10 (Time 10-11:30am ET)
initial draft: draft-ietf-hares-fsv2-more-ip-filters
IDR draft included in FSv2: draft-ietf-idr-flowspec-srv6-05
New drafts requested: Any IP packet filters (header + payload)
New IP filters from draft-ietf-idr-flowspec-v2
Filters in FSv2 are: SID filters
Filters came from: draft-ietf-idr-flowspec-srv6-05
Existing Individual drafts in this area
draft-peng-idr-apn-bgp-flowspec-00
draft-cui-idr-content-filter-flowspec-00
draft-lin-idr-cats-flowspec-ts-00
draft-geng-idr-flowspec-saf-00
FSv1 found problems with undefined interactions between actions.
FSv2 (draft-ietf-idr-flowspec-v2-03)
allows for ordered actions using Wide Community. Many implementers desired both Extended-Community Actions with specific default order and
defined interactions. A new Extended-Community will be expanded for this
Other implementers want to be able to specify an order for actions. The user specification of action ordering will not fit in the Extended Community, and so the Wide Community format (type 2, FSv2 actions) will be used.
One key issues with Ordering of Actions is the action taken when an action does not successfully complete. Potential recovery from a failed action are: ignore, continue, halt, roll-back.
Design team: Design Team 3 - More IP Actions for FSv2
Meetings before IETF-120: 5/13 and 6/17 (Time 10-11:30am ET) with Design Team 4
initial draft: draft-ietf-hares-fsv2-more-ip-actions
New drafts requested: Any Drafts specifying actions taken as
a result of IP filters
FSv1 Actions in addition to RFC8895 and RFC8896
New IP filters from draft-ietf-idr-flowspec-v2
generalized redirection for IPv6 (EC-v6)
draft-ietf0-idr-srv6-flowspec-path-redirect-11
Mark Group ID (APN ID) - 4 actions)
Mark APN Group ID (full, partial, inherit, or stitch)
draft-peng-idr-apn-bgp-flowspec-00
CATS marking of CATs in V6 heaer (1 action)
draft-lin-idr-cats-flowspec-ts-00
Process FS based on interface group + data direction (inbound/outbound)
draft-ietf-idr-flowspec-interfaceset-05
Compress traffic basic on Compression ID
draft-shen-idr-flowspec-traffic-compress-action-01
FSv2 ((draft-ietf-idr-flowspec-v2-03) specified Non-IP filters for MPLS, SFC, L2VPN, and tunnels (using nvo3 concepts).
Design team: Design Team 4 - Non-IP Filters and Actions
Meetings before IETF-120: 5/13 and 6/17 (Time 11-12:00) ET) with Design Team 3
appropriate drafts: Drafts proposing any Non-IP filters or Non-IP Actions
initial drafts:
draft-ietf-hares-fsv2-non-IP -
This FSv2 work included MPLS Filters and actions.
draft-ietf-idr-flowspec-l2vpn
This IDR WG draft provides the L2 Filters and Actions.
3.draft-ietf-idr-flowspec-nv03
This IDR draft includes filtering of various headers of
L2 and L3 tunnels.
**individual drafts for this team **:
draft-xiong-idr-detnet-flow-mapping
This draft provides L2 + latency filters and actions.
draft-zzd-flowspec-path-scheduling
Filtering and actions based on packet timing.