RFC 5575, "Dissemination of Flow Specification Rules", August 2009

Note: This RFC has been obsoleted by RFC 8955

Note: This RFC has been updated by RFC 7674

Errata ID: 3610
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Sergey Antipov
Date Reported: 2013-04-30
Held for Document Update by: Stewart Bryant
Date Held: 2013-09-17

Section 4 says:

   If a given component type within a prefix in unknown, the prefix in
   question cannot be used for traffic filtering purposes by the
   receiver.  Since a flow specification has the semantics of a logical
   AND of all components, if a component is FALSE, by definition it
   cannot be applied.  However, for the purposes of BGP route
   propagation, this prefix should still be transmitted since BGP route
   distribution is independent on NLRI semantics.

It should say:

   If a given component type within a prefix is unknown, the prefix in
   question cannot be used for traffic filtering purposes by the
   receiver.  Since a flow specification has the semantics of a logical
   AND of all components, if a component is FALSE, by definition it
   cannot be applied.  However, for the purposes of BGP route
   propagation, this prefix should still be transmitted since BGP route
   distribution is independent of NLRI semantics.

Notes:

Two minor typos:
- If a given component type within a prefix _in_ unknown
- independent _on_

Report New Errata