<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.hares-idr-fsv2-ip-basic" target="https://datatracker.ietf.org/doc/html/draft-hares-idr-fsv2-ip-basic-03">
   <front>
      <title>BGP Flow Specification Version 2 - for Basic IP</title>
      <author initials="S." surname="Hares" fullname="Susan Hares">
         <organization>Hickory Hill Consulting</organization>
      </author>
      <author initials="D. E." surname="Eastlake" fullname="Donald E. Eastlake 3rd">
         <organization>Independent</organization>
      </author>
      <author initials="C." surname="Yadlapalli" fullname="Chaitanya Yadlapalli">
         <organization>ATT</organization>
      </author>
      <author initials="S." surname="Maduschke" fullname="Sven Maduschke">
         <organization>Verizon</organization>
      </author>
      <date month="July" day="22" year="2024" />
      <abstract>
	 <t>   BGP flow specification version 1 (FSv1), defined in RFC 8955, RFC
   8956, and RFC 9117 describes the distribution of traffic filter
   policy (traffic filters and actions) distributed via BGP.  During the
   deployment of BGP FSv1 a number of issues were detected, so version 2
   of the BGP flow specification (FSv2) protocol addresses these
   features.  In order to provide a clear demarcation between FSv1 and
   FSv2, a different NLRI encapsulates FSv2.

   The IDR WG requires two implementation Implementers feedback on FSv2
   was that FSv2 has a correct design, but that breaking FSv2 into a
   progression of documents would aid deployment of the draft.  The IDR
   WG requires two implementation so This document is the first of the
   series of documents indicating the basic FSv2 with user ordering of
   filters added to FSv1 IP Filters and IP actions.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-hares-idr-fsv2-ip-basic-03" />
   
</reference>
