Juniper Networks Inc.

1194 N. Mathilda Ave. Sunnyvale CA US raszuk@juniper.net

Juniper Networks Inc.

1194 N. Mathilda Ave. Sunnyvale CA US roque@juniper.net

Arbor Networks

labovit@arbor.net

This document provides an implementation report for Dissemination of flow specification rules as defined in draft-ietf-idr-flow-spec-01 The editor did not verify the accuracy of the information provided by respondents or by any alternative means. The respondents are experts with the implementations they reported on, and their responses are considered authoritative for the implementations for which their responses represent. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Dissemination of flow specification rules BGP describes an extension to BGP which may be used to propagate information describing flows of data between BGP speakers. Such information may be needed to apply action on selected data flows through and beyond autonoumus systems. Examples of such actions are: dropping, rate limiting, redirecting, monitoring etc ... This document provides an implementation report for Dissemination of flow specification rules as defined in draft-ietf-idr-flow-spec-01 The editor did not verify the accuracy of the information provided by respondents or by any alternative means. The respondents are experts with the implementations they reported on, and their responses are considered authoritative for the implementations for which their responses represent.

Contact and implementation information for person filling out this form: Name: Craig Labovitz, Email: labovit@arbor.net , Vendor: Arbor Networks, Inc. Release: Peakflow SP Name: Pedro Marques, Email: roque@juniper.net, Vendor: Juniper Networks Inc., Release: JUNOS 7.3

Does your implementation supports 0 octet length Next Hop in the MP_REACH_NLRI as defined in Flow-Spec ? Arbor: YES Juniper: YES Does your implementation supports one and two octet of NLRI length field in the MP_REACH_NLRI as defined in Flow-Spec ? Arbor: YES Juniper: YES Does your Flow Specification supports Destination Prefix component (Type 1) as defined in Flow-Spec ? Arbor: YES Juniper: YES Does your Flow Specification supports Source Prefix component (Type 2) as defined in Flow-Spec ? Arbor: YES Juniper: YES Does your Flow Specification supports IP Protocol component (Type 3) as defined in Flow-Spec ? Arbor: YES Juniper: YES Does your Flow Specification supports Port component (Type 4) as defined in Flow-Spec ? Arbor: YES Juniper: YES Does your Flow Specification supports Destination Port component (Type 5) as defined in Flow-Spec ? Arbor: YES Juniper: YES Does your Flow Specification supports Source Port component (Type 6) as defined in Flow-Spec ? Arbor: YES Juniper: YES Does your Flow Specification supports ICMP type component (Type 7) as defined in Flow-Spec ? Arbor: YES Juniper: YES Does your Flow Specification supports ICMP code component (Type 8) as defined in Flow-Spec ? Arbor: YES Juniper: YES Does your Flow Specification supports TCP flags component (Type 9) as defined in Flow-Spec ? Arbor: YES Juniper: YES Does your Flow Specification supports Packet length component (Type 10) as defined in Flow-Spec ? Arbor: YES Juniper: YES Does your Flow Specification supports DSCP component (Type 11) as defined in Flow-Spec ? Arbor: YES Juniper: YES Does your Flow Specification supports Fragment component (Type 12) as defined in Flow-Spec ? Arbor: YES Juniper: YES Does your implementation assures strict type ordering of propagated components as defined in Flow-Spec ? Arbor: YES Juniper: YES Does your implementation supports BGP's Capability Advertisement facility to exchange the Multiprotocol Extension Capability Codeas defined in Flow-Spec ? Arbor: YES Juniper: YES Does your implementation supports dissemination of flow specification rules for IPv4 Unicast as defined in Flow-Spec ? Arbor: YES, but not completely applicable (we are not a router) Juniper: YES Does your implementation supports dissemination of flow specification rules for VPNv4 Unicast as defined in Flow-Spec ? Arbor: YES Juniper: YES

Does your implementation supports ordered traffic filtering rules such that the order of two flow specifications is given by the comparison of NLRI key byte strings as defined by the memcmp() function is the ISO C standard ? Arbor: YES, but not completely applicable Juniper: YES

Does your implementation supports flow routes validation per originator match with corresponding unicast route as defined in Flow-Spec ? Arbor: N/A (we are not a router) Juniper: YES Does your implementation supports flow routes validation to make sure that there are no more specifics flow routes received from a different neighboring AS than the best-match unicast route as defined in Flow-Spec ? Arbor: N/A Juniper: YES

Does your implementation supports traffic-rate extended community filtering action as defined in Flow-Spec ? Arbor: YES Juniper: YES Does your implementation supports traffic-action extended community filtering action as defined in Flow-Spec ? Arbor: YES Juniper: YES Does your implementation supports redirect extended community filtering action as defined in Flow-Spec ? Arbor: NO (but upcoming version will) Juniper: YES

Does your implementation supports a mechanism to log the packet header of filtered traffic as defined in Flow-Spec ? Arbor: N/A Juniper: YES Does your implementation supports a mechanism to count the number of matches for a given Flow Specification rule as defined in Flow-Spec ? Arbor: N/A Juniper: YES

List other implementations that you have tested interoperability of Dissemination of flow specification rules Flow-Spec with: Arbor: Juniper Juniper: Arbor

This document makes no request of IANA. Note to RFC Editor: this section may be removed on publication as an RFC.

Does your implementation supports flow routes rules to match the corresponding unicast routing paths for the relevant prefixes as defined in Flow-Spec ? Arbor: N/A Juniper: YES

The authors would like to thank Yakov Rekhter and Danny McPherson for their comments.