Supported Open Standards

Junos OS substantially supports the following open standards:

• OpenFlow Switch Specification, Version 1.0.0

  For a detailed list of supported messages and fields, match conditions, wild cards, flow actions, statistics, and features, see OpenFlow v1.0 Compliance Matrix for Devices Running Junos OS.

  The Junos OS implementation of OpenFlow v1.0 differs from the specification in the following ways:

  (The sections of the OpenFlow specification are indicated in the parentheses.)

  • Junos OS supports only the following flow action types (section 5.2.4):

    • OFPAT_OUTPUT—supports OFPP_NORMAL, OFPP_FLOOD, OFPP_ALL, and OFPP_CONTROLLER for normal flow actions, and OFPP_FLOOD and OFPP_ALL for Send Packet flow actions.

    • OFPAT_SET_VLAN_VID—support varies by platform.

    • OFPAT_STRIP_VLAN—support varies by platform

  • Flow priority is supported according to OpenFlow Switch Specification v1.3.0 in which there is no prioritization of exact match entries over wildcard entries.

  • Emergency mode as defined in OpenFlow v1.0 is not supported. If the controller connection is lost and cannot be reestablished, the switch maintains all flow states in the control and data planes.

  The following features are not supported:

  • Encryption through TLS connection (section 4.4)

  • 802.1D Spanning Tree Protocol (sections 4.5 and 5.2.1)

  • OFPP_LOCAL virtual port (section 5.2.1)

  • Physical port features OFPPF_PAUSE and OFPPF_PAUSE_ASYM (section 5.2.1)

  • Queue structures and queue configuration messages (section 5.2.2 and 5.3.4)

  • Flow action types: OFPAT_SET_VLAN_PCP, OFPAT_SET_DL_SRC/DST, OFPAT_SET_NW_SRC/DST/TOS, OFPAT_SET_TP_SRC/DST and OFPAT_ENQUEUE (section 5.2.4)

  • buffer_id for Modify Flow Entry Message, Send Packet Message, and Packet-In Message (sections 5.3.3, 5.3.6, and 5.4.1)

  • Port Modification Message (section 5.3.3)

  • Vendor Statistics (section 5.3.5)

  • Vendor message (section 5.5.4)

• OpenFlow Switch Specification, Version 1.3.1

  For a detailed list of supported messages and fields, port structure flags and numbering, match conditions, flow actions, multipart messages, flow instructions, and group types, see OpenFlow v1.3.1 Compliance Matrix for Devices Running Junos OS.

  The Junos OS implementation of OpenFlow v1.3.1 differs from the specification in the following ways:

  (The sections of the OpenFlow specification are indicated in the parentheses.)

  • Junos OS supports only the following flow action types (section 5.12):

    • OFPAT_SET_VLAN_VID

    • OFPAT_POP_VLAN

    • OFPAT_GROUP

  • Junos OS supports only the following group types (section 5.6.1):

    • OFPGT_ALL

    • OFPGT_INDIRECT

  • Junos OS supports only one flow instruction per flow entry. Further, only the following flow instructions (section A.2.4) are supported:

    • OFPIT_WRITE_ACTIONS

    • OFPIT_APPLY_ACTIONS

  • For OFPT_SET_CONFIG (section A.3.2), Junos OS supports only the OFPC_FRAG_NORMAL configuration flag, and the OFPCML_NO_BUFFER setting for the miss_send_len field.

  • On MX Series routers, Junos OS supports only the following IPv6-related match conditions (A.2.3.7):

    • OFPXMT_OFB_IPV6_SRC

    • OFPXMT_OFB_IPV6_DST

  The following features are not supported:

  • Multiple flow tables (section 5)

  • Table metadata (section 2)

  • Action sets (section 5.10)

  • Meter (section 5.7)

  • MPLS fields (section 5.12.1)

  • MPLS actions (section 5.10 and 5.12)

  • Encryption through TLS connection (section 6.3.3)

  • Per-port queues (section A.2.2)

  • Auxiliary connections (section 6.3.5)

  • Multiple virtual switches (section A.3.1)

  • IPv6-related set-field actions (5.12)