US 7,224,668
`Claim 1
`[1.0] An internetworking
`device comprising: a. a
`plurality of physical
`network interface ports,
`each for providing a
`physical connection point
`to a network for the
`internetworking device, the
`ports being configurable by
`control plane processes;
`
`Cisco
`
`Arista
`
`Cisco devices, at least the Cisco 7500 Series,
`include an internetworking device comprising a
`plurality of physical network interface ports, each
`for providing a physical connection point to a
`network for the internetworking device, the ports
`being configurable by control plane processes.
`
`See, e.g., Control Plane Policing Implementation
`Best Practices available at
`http://www.cisco.com/web/about/security/intellig
`ence/coppwp_gs.html (Ex. 2016) (“IP networks
`provide users with connectivity to networked
`resources such as corporate servers, extranet
`partners, multimedia content, the Internet, and
`any other application envisioned within IP
`networks. While these networks function to carry
`data plane (user-generated) packets, they are also
`created and operated by control plane and
`management plane packets.”).
`
`Cisco devices, at least the Nexus 7000 Series,
`include an internetworking device comprising a
`plurality of physical network interface ports, each
`for providing a physical connection point to a
`network for the internetworking device, the ports
`being configurable by control plane processes.
`See, e.g., Cisco Nexus 7000 Series NX-OS
`Security Configuration Guide, Release 6.x
`(Modified 4/16/14) (Ex. 2017) at p. 646 (“Control
`plane—Handles all routing protocol control
`
`Arista switches, including at least the 7010, 7048,
`7050, 7050X, 7150, 7250X, 7280E, 7300, 7300X,
`and 7500E series models, and/or Arista EOS,
`including at least version 4.14.3F, include an
`internetworking device comprising a plurality of
`physical network interface ports, each for
`providing a physical connection point to a
`network for the internetworking device, the ports
`being configurable by control plane processes.
`
`See, e.g., Arista Configuration Guide v. 4.14.3F -
`Rev. 2 (10/2/14) (Ex. 2024) at p. 45 (“Arista
`Networks features switches with high density,
`non-blocking 100/1000Mb and 10/40/100 Gb
`Ethernet ports that are controlled through an
`extensible modular network operating system.”).
`See, e.g., Arista Configuration Guide v. 4.14.3F -
`Rev. 2 (10/2/14) (Ex. 2024) at p. 622 (“The
`control plane builds and maintains the IP routing
`table”). See, e.g., Arista Configuration Guide v.
`4.14.3F - Rev. 2 (10/2/14) (Ex. 2024) at p. 622
`(“The data plane routes IP packets based on
`information derived by the control plane.”). See,
`e.g., Arista Configuration Guide v. 4.14.3F - Rev.
`2 (10/2/14) (Ex. 2024) at p. 650 (“The control
`plane command places the switch in control-
`plane configuration mode.”). See, e.g., Arista
`7508E Image available at
`http://www.arista.com/assets/images/product/750
`8- specifications.png (Ex. 2025).
`
`- 1 -
`
`Exhibit 2015
`IPR2016-00309
`
`

`
`US 7,224,668
`
`Cisco
`
`Arista
`
`traffic.”).
`
`Cisco devices, at least the Catalyst 6500, include
`an internetworking device comprising a plurality
`of physical network interface ports, each for
`providing a physical connection point to a
`network for the internetworking device, the ports
`being configurable by control plane processes.
`See, e.g., Cisco IOS Software Configuration
`Guide, Release 12.2(33)SXH and Later Releases
`(2007-2012) (Ex. 2018) at p. 53-2 (“The majority
`of traffic managed by the RP is handled by way
`of the control and management planes.”).
`
`See, e.g., Control Plane Policing Implementation
`Best Practices available at
`http://www.cisco.com/web/about/security/intellig
`ence/coppwp_gs.html (Ex. 2016) (“IP networks
`provide users with connectivity to networked
`resources such as corporate servers, extranet
`partners, multimedia content, the Internet, and
`any other application envisioned within IP
`networks. While these networks function to carry
`data plane (user-generated) packets, they are also
`created and operated by control plane and
`management plane packets.”).
`
`[1.1] b. port services,
`for operating on
`packets entering and
`exiting the physical
`network interface
`
`Cisco devices, at least the Cisco 7500 Series,
`include port services, for operating on packets
`entering and exiting the physical network
`interface ports, the port services providing an
`ability to control and monitor packet flows, as
`
`Arista switches, including at least the 7010, 7048,
`7050, 7050X, 7150, 7250X, 7280E, 7300, 7300X,
`and 7500E series models, and/or Arista EOS,
`including at least version 4.14.3F, include port
`services, for operating on packets entering and
`
`- 2 -
`
`

`
`US 7,224,668
`ports, the port
`services providing
`an ability to control
`and monitor packet
`flows, as defined by
`control plane
`configurations;
`
`Cisco
`defined by control plane configurations.
`
`See, e.g., Control Plane Policing Implementation
`Best Practices available at
`http://www.cisco.com/web/about/security/intellig
`ence/coppwp_gs.html (Ex. 2016) (“Interface
`ACL – The interface access control list (iACL) is
`the traditional and most generally available
`approach for managing all packets entering or
`exiting a network device. The iACLs are well
`understood and are generally applicable to data,
`services, control, and management plane packets.
`However, as illustrated in Figure 2, iACLs are
`applied at the interface level to each packet
`ingressing (or egressing) the interface—not just
`control plane packets, for example.”).
`
`Cisco devices, at least the Nexus 7000 Series,
`include port services, for operating on packets
`entering and exiting the physical network
`interface ports, the port services providing an
`ability to control and monitor packet flows, as
`defined by control plane configurations.
`
`See, e.g., Cisco Nexus 7000 Series NX-OS
`Security Configuration Guide, Release 6.x
`(Modified 4/16/14) (Ex. 2017) at p. 455 (“You
`can apply an IPv4 or IPv6 ACL to a Layer 2
`interface, which can be a physical port or a port
`channel. ACLs applied to these interface types
`are considered port ACLs.”).
`
`Arista
`exiting the physical network interface ports, the
`port services providing an ability to control and
`monitor packet flows, as defined by control plane
`configurations.
`
`See, e.g., Arista Configuration Guide v. 4.14.3F -
`Rev. 2 (10/2/14) (Ex. 2024) at p. 622 (“The data
`plane routes IP packets based on information
`derived by the control plane.”). See, e.g., Arista
`Configuration Guide v. 4.14.3F - Rev. 2 (10/2/14)
`(Ex. 2024) at p. 835 (“ACL, Route Map, and
`Prefix List Introduction An access control list
`(ACL) is an ordered set of rules that control the
`inbound flow of packets into Ethernet interfaces,
`port channel interfaces or the switch control
`plane. The switch supports the implementation of
`a wide variety of filtering criteria including IP
`and MAC addresses, TCP/UDP ports with
`include/exclude options without compromising
`its performance or feature set.”). See, e.g., Arista
`Configuration Guide v. 4.14.3F - Rev. 2 (10/2/14)
`(Ex. 2024) at p. 848.
`
`These commands assign test1 ACL to Ethernet 3
`interface, then verifies the assignment.
`
`
`See, e.g., Arista Configuration Guide v. 4.14.3F -
`Rev. 2 (10/2/14) (Ex. 2024) at p. 1027 (“Quality
`
`- 3 -
`
`

`
`Arista
`of Service Conceptual Overview QoS processes
`apply to traffic that flows through Ethernet ports
`and control planes. These processes can modify
`data fields (CoS or DSCP) or assign data streams
`to traffic classes for prioritized handling.
`Transmission queues are configurable for
`individual Ethernet ports to shape traffic based on
`its traffic class. Many switches also support
`traffic policies that apply to data that is filtered by
`access control lists.”).
`
`
`
`US 7,224,668
`
`Cisco
`See, e.g., Cisco Nexus 7000 Series NX-OS
`Quality of Service Configuration Guide (April
`2014) (Ex. 2020) at p. 2-17 (“A QoS policy
`attached to the physical port takes effect when the
`port is not a member of a port channel.”).
`
`Cisco devices, at least the Catalyst 6500, include
`port services, for operating on packets entering
`and exiting the physical network interface ports,
`the port services providing an ability to control
`and monitor packet flows, as defined by control
`plane configurations. See, e.g., Cisco IOS
`Software Configuration Guide, Release
`12.2(33)SXH and Later Releases (2007-2012)
`(Ex. 2018) at p. 51-2 (“Port ACLs perform access
`control on all traffic entering the specified Layer
`2 port.”).
`
`See, e.g., Cisco IOS Quality of Service Solutions
`Configuration Guide, Release 12.2, Quality of
`Service Overview (Ex. 2021) at p. QC-6
`(“Policies can be set that include classification
`based on physical port….”).
`
`See, e.g., Control Plane Policing Implementation
`Best Practices available at
`http://www.cisco.com/web/about/security/intellig
`ence/coppwp_gs.html (Ex. 2016) (“Interface
`ACL – The interface access control list (iACL) is
`the traditional and most generally available
`approach for managing all packets entering or
`exiting a network device. The iACLs are well
`
`- 4 -
`
`

`
`US 7,224,668
`
`[1.2] c. a control
`plane, comprising a
`plurality of
`internetworking
`control plane
`processes, the
`control plane
`processes for
`providing high-level
`control and
`configuration of the
`ports and the port
`services;
`
`Arista
`
`Arista switches, including at least the 7010, 7048,
`7050, 7050X, 7150, 7250X, 7280E, 7300, 7300X,
`and 7500E series models, and/or Arista EOS,
`including at least version 4.14.3F, include a
`control plane, comprising a plurality of
`internetworking control plane processes, the
`control plane processes for providing high-level
`control and configuration of the ports and the port
`services.
`
`See, e.g., Arista Configuration Guide v. 4.14.3F -
`Rev. 2 (10/2/14) (Ex. 2024) at p. 622 (“The
`control plane builds and maintains the IP routing
`table”). See, e.g., Arista White Paper, Arista 7500
`Switch Architecture (March 2014) (Ex. 2026) at
`p. 2 (“Supervisor modules on Arista 7500 Series
`switches are used for control-plane and
`management-plane functions only….”).
`
`Cisco
`understood and are generally applicable to data,
`services, control, and management plane packets.
`However, as illustrated in Figure 2, iACLs are
`applied at the interface level to each packet
`ingressing (or egressing) the interface—not just
`control plane packets, for example.).
`
`Cisco devices, at least the Cisco 7500 Series,
`include a control plane, comprising a plurality of
`internetworking control plane processes, the
`control plane processes for providing high-level
`control and configuration of the ports and the port
`services.
`
`See, e.g., Control Plane Policing Implementation
`Best Practices available at
`http://www.cisco.com/web/about/security/intellig
`ence/coppwp_gs.html (Ex. 2016) (“IP networks
`provide users with connectivity to networked
`resources such as corporate servers, extranet
`partners, multimedia content, the Internet, and
`any other application envisioned within IP
`networks. While these networks function to carry
`data plane (user-generated) packets, they are also
`created and operated by control plane and
`management plane packets.”).
`
`Cisco devices, at least the Nexus 7000 Series,
`include a control plane, comprising a plurality of
`internetworking control plane processes, the
`control plane processes for providing high-level
`control and configuration of the ports and the port
`
`- 5 -
`
`

`
`Arista
`
`US 7,224,668
`
`Cisco
`services. See, e.g., Cisco Nexus 7000 Series NX-
`OS Security Configuration Guide, Release 6.x
`(Modified 4/16/14) (Ex. 2017) at p. 646 (“Control
`plane—Handles all routing protocol control
`traffic.”).
`
`Cisco devices, at least the Catalyst 6500, include
`a control plane, comprising a plurality of
`internetworking control plane processes, the
`control plane processes for providing high-level
`control and configuration of the ports and the port
`services. See, e.g., Cisco IOS Software
`Configuration Guide, Release 12.2(33)SXH and
`Later Releases (2007-2012) (Ex. 2018) at p. 53-2
`(“The majority of traffic managed by the RP is
`handled by way of the control and management
`planes.”).
`
`See, e.g., Control Plane Policing Implementation
`Best Practices available at
`http://www.cisco.com/web/about/security/intellig
`ence/coppwp_gs.html (Ex. 2016) (“IP networks
`provide users with connectivity to networked
`resources such as corporate servers, extranet
`partners, multimedia content, the Internet, and
`any other application envisioned within IP
`networks. While these networks function to carry
`data plane (user-generated) packets, they are also
`created and operated by control plane and
`management plane packets.”).
`
`[1.3] d. wherein: i. a control Cisco devices, at least the Cisco 7500 Series,
`
`Arista switches, including at least the 7010, 7048,
`
`- 6 -
`
`

`
`US 7,224,668
`plane port entity provides
`access to the collection of
`control plane processes, so
`that a set of control plane
`port services can be applied
`thereto; and
`
`Cisco
`include a control plane port entity that provides
`access to the collection of control plane
`processes, so that a set of control plane port
`services can be applied thereto.
`
`See, e.g., Control Plane Policing Implementation
`Best Practices available at
`http://www.cisco.com/web/about/security/intellig
`ence/coppwp_gs.html (Ex. 2016) (“Control Plane
`Policing — CoPP is the Cisco IOS-wide route
`processor protection mechanism.…CoPP is
`deployed once to the punt path of the router.…,
`CoPP applies to all packets that punt to the route
`processor for handling…. CoPP protects the route
`processor on network devices by treating route
`processor resources as a separate entity with its
`own ingress interface (and in some
`implementations, egress also). Because of this
`behavior, a CoPP policy can be developed and
`applied only to those packets within the control
`plane.”).
`
`See, e.g., Deploying Control Plane Policing (Ex.
`2022) at p. 2-3 (“CPP leverages MQC to define
`traffic classification criteria and to specify
`configurable policy actions for the classified
`traffic. Traffic of interest must first be identified
`via class-maps, which are used to define packets
`for a particular traffic class. Once classified,
`enforceable policy actions for the identified
`traffic are created with policy-maps. The control-
`plane global command allows the CP service
`
`Arista
`7050, 7050X, 7150, 7250X, 7280E, 7300, 7300X,
`and 7500E series models, and/or Arista EOS,
`including at least version 4.14.3F, include a
`control plane port entity that provides access to
`the collection of control plane processes, so that a
`set of control plane port services can be applied
`thereto.
`
`See, e.g., Arista Configuration Guide v. 4.14.3F -
`Rev. 2 (10/2/14) (Ex. 2024) at p. 1134 (“Control
`Plane Policies The switch defines one control
`plane policy map named copp-system-policy. The
`copp-systempolicy policy map is always applied
`to the control plane and cannot be removed from
`the switch. Other control plane policy maps
`cannot be added. Copp-system-policy consists of
`preconfigured classes, each containing a static
`class map and traffic resolution commands.
`
`Preconfigured classes cannot be removed from
`copp-system-policy.… Copp-system-policy can
`be modified through the following steps: Add
`classes consisting of an eponymous dynamic
`class map and traffic resolution commands.
`Dynamic class maps are user created, can be
`edited or deleted, filter traffic with a single IPv4
`ACL, and are listed in running-config. • Change
`traffic resolution commands for a preconfigured
`class.”).
`
`See, e.g., Arista Configuration Guide v. 4.14.3F -
`Rev. 2 (10/2/14) (Ex. 2024) at p. 1137 (“Example
`
`- 7 -
`
`

`
`US 7,224,668
`
`Cisco
`policies to be attached to control plane itself....
`Table 1. Cisco Hardware and Cisco IOS Software
`Support.... Cisco 7500 Series.... Release
`12.2(18)S”).
`
`Arista
`• These commands configure a bandwidth range
`of 2000 to 4000 packets per seconds (pps) for
`traffic filtered by the copp-system-lacp class
`map:
`
`
`See, e.g., Arista White Paper, Arista 7500 Switch
`Architecture (March 2014) (Ex. 2026) at p. 10
`(“The packet forwarding pipeline always remains
`in the hardware data-plane. There are no features
`that can be enabled that cause the packet
`forwarding to drop out of the silicon (hardware)
`data-plane forwarding path. In cases where
`software assistance is required (e.g. traffic
`destined within a L3 subnet but for which the
`switch has not yet seen the end device provide an
`ARP and doesn’t have the L3-to-L2 glue entry),
`hardware rate limiters and Control-plane Policing
`are employed to protect the control-plane from
`potential denial of service attacks.”).
`
`See, e.g., Arista Configuration Guide v. 4.14.3F -
`Rev. 2 (10/2/14) (Ex. 2024) at p. 839 (“ACL Rule
`Tracking Hardware rate limiting is applied to
`packets written to the CPU, avoiding potential
`DoS attacks.”).
`
`Cisco devices, at least the Nexus 7000 Series,
`include a control plane port entity that provides
`access to the collection of control plane
`processes, so that a set of control plane port
`services can be applied thereto. See, e.g.,CoPP on
`Nexus 7000 Series Switches (9/4/14) (Ex. 2023)
`at p. 2 (“CoPP is a hardware-based feature that
`protects the Supervisor from DoS attacks. It
`controls the rate at which packets are allowed to
`reach the Supervisor. The CoPP feature is
`modeled like an input QoS policy attached to the
`special interface called the control-plane.
`However, CoPP is a security feature and not part
`of QoS. In order to protect the Supervisor, the
`CoPP separates data plane packets from the
`control plane packets (Exception Logic).”).
`
`Cisco devices, at least the Catalyst 6500, include
`a control plane port entity that provides access to
`the collection of control plane processes, so that a
`set of control plane port services can be applied
`thereto. See, e.g., Control Plane Policing
`Implementation Best Practices available at
`http://www.cisco.com/web/about/security/intellig
`ence/coppwp_gs.html (Ex. 2016) (“Control Plane
`Policing — CoPP is the Cisco IOS-wide route
`processor protection mechanism.…CoPP is
`
`- 8 -
`
`

`
`Arista
`
`US 7,224,668
`
`Cisco
`deployed once to the punt path of the router.…
`CoPP applies to all packets that punt to the route
`processor for handling…. CoPP protects the route
`processor on network devices by treating route
`processor resources as a separate entity with its
`own ingress interface (and in some
`implementations, egress also). Because of this
`behavior, a CoPP policy can be developed and
`applied only to those packets within the control
`plane.”).
`
`See, e.g., Cisco IOS Software Configuration
`Guide, Release 12.2(33)SXH and Later Releases
`(2007-2012) (Ex. 2018) at p. 53-3 (“CoPP uses
`MQC to define traffic classification criteria and
`to specify the configurable policy actions for the
`classified traffic. You must first identify the
`traffic to be classified by defining a class map.
`The class map defines packets for a particular
`traffic class. After you have classified the traffic,
`you can create policy maps to enforce policy
`actions for the identified traffic. The control-
`plane global configuration command allows the
`CoPP service policies to be directly attached to
`the control plane.”).
`
`[1.4] ii. the control plane
`port services operate on
`packets received from
`specific, predetermined
`physical ports and destined
`to the collection of control
`
`Cisco devices, at least the Cisco 7500 Series,
`operate so that the control plane port services
`operate on packets received from specific,
`predetermined physical ports and destined to the
`collection of control plane processes in a way that
`is independent of the physical port interfaces and
`
`Arista switches, including at least the 7010, 7048,
`7050, 7050X, 7150, 7250X, 7280E, 7300, 7300X,
`and 7500E series models, and/or Arista EOS,
`including at least version 4.14.3F, operate so that
`the control plane port services operate on packets
`received from specific, predetermined physical
`
`- 9 -
`
`

`
`US 7,224,668
`plane processes in a way
`that is independent of the
`physical port interfaces and
`services applied thereto.
`
`Arista
`ports and destined to the collection of control
`plane processes in a way that is independent of
`the physical port interfaces and services applied
`thereto.
`
`
`
`See, e.g., Arista White Paper, Arista 7500 Switch
`Architecture (March 2014) (Ex. 2026) at p. 10
`(“The packet forwarding pipeline always remains
`in the hardware data-plane. There are no features
`that can be enabled that cause the packet
`forwarding to drop out of the silicon (hardware)
`data-plane forwarding path. In cases where
`software assistance is required (e.g. traffic
`destined within a L3 subnet but for which the
`switch has not yet seen the end device provide an
`ARP and doesn’t have the L3-to-L2 glue entry),
`hardware rate limiters and Control-plane Policing
`are employed to protect the control-plane from
`potential denial of service attacks.”).
`
`See, e.g., Gary A. Donahue, Arista Warrior
`(2013) (Ex. 2027) at p. 187 (“[F]iltering access to
`the control plane is not interface specific.”).
`
`Cisco
`services applied thereto.
`
`See, e.g., Control Plane Policing Implementation
`Best Practices available at
`http://www.cisco.com/web/about/security/intellig
`ence/coppwp_gs.html (Ex. 2016) (“CoPP protects
`the route processor on network devices by
`treating route processor resources as a separate
`entity with its own ingress interface (and in some
`implementations, egress also)”).
`
`See, e.g., Deploying Control Plane Policing (Ex.
`2022) at p. 2-3 (“CPP leverages MQC to define
`traffic classification criteria and to specify
`configurable policy actions for the classified
`traffic. Traffic of interest must first be identified
`via class-maps, which are used to define packets
`for a particular traffic class. Once classified,
`enforceable policy actions for the identified
`traffic are created with policy-maps. The control-
`plane global command allows the CP service
`policies to be attached to control plane itself...
`Table 1. Cisco Hardware and Cisco IOS Software
`Support.... Cisco 7500 Series.... Release
`12.2(18)S”).
`
`See, e.g., Deploying Control Plane Policing (Ex.
`2022) at p. 5 (“As CPP policies are applied to the
`control plane interface, only traffic destined for
`the Route Processor will be affected by the CPP
`policy.”).
`
`- 10 -
`
`

`
`US 7,224,668
`
`Cisco
`
`Arista
`
`
`
`Cisco devices, at least the Nexus 7000 Series,
`operate so that the control plane port services
`operate on packets received from specific,
`predetermined physical ports and destined to the
`collection of control plane processes in a way that
`is independent of the physical port interfaces and
`services applied thereto.
`
`See, e.g.,CoPP on Nexus 7000 Series Switches
`(9/4/14) (Ex. 2023) at p. 2 (“CoPP is a hardware-
`based feature that protects the Supervisor from
`DoS attacks. It controls the rate at which packets
`are allowed to reach the Supervisor. The CoPP
`feature is modeled like an input QoS policy
`attached to the special interface called the
`control-plane. However, CoPP is a security
`feature and not part of QoS. In order to protect
`the Supervisor, the CoPP separates data plane
`packets from the control plane packets
`(Exception Logic).”).
`
`Cisco devices, at least the Catalyst 6500, operate
`so that the control plane port services operate on
`packets received from specific, predetermined
`physical ports and destined to the collection of
`control plane processes in a way that is
`independent of the physical port interfaces and
`services applied thereto.
`
`See, e.g., Control Plane Policing Implementation
`
`- 11 -
`
`

`
`Arista
`
`US 7,224,668
`
`Cisco
`Best Practices available at
`http://www.cisco.com/web/about/security/intellig
`ence/coppwp_gs.html (Ex. 2016) (“CoPP protects
`the route processor on network devices by
`treating route processor resources as a separate
`entity with its own ingress interface (and in some
`implementations, egress also).”).
`
`See, e.g., Cisco IOS Software Configuration
`Guide, Release 12.2(33)SXH and Later Releases
`(2007-2012) (Ex. 2018) at p. 53-3 (“CoPP uses
`MQC to define traffic classification criteria and
`to specify the configurable policy actions for the
`classified traffic. You must first identify the
`traffic to be classified by defining a class map.
`The class map defines packets for a particular
`traffic class. After you have classified the traffic,
`you can create policy maps to enforce policy
`actions for the identified traffic. The control-
`plane global configuration command allows the
`CoPP service policies to be directly attached to
`the control plane.”).
`
`See supra provided for element [1.0].
`
`See supra provided for element [1.0].
`
`Claim 19
`[19.0] A method for
`processing packets in an
`internetworking device
`comprising the steps of:
`
`a. configuring a plurality of
`physical network interface
`ports, each port for
`
`- 12 -
`
`

`
`Cisco
`
`Arista
`
`See supra provided for element [1.1].
`
`See supra provided for element [1.1].
`
`See supra provided for element [1.2].
`
`See supra provided for element [1.2].
`
`See supra provided for element [1.3].
`
`See supra provided for element [1.3].
`
`US 7,224,668
`providing a physical
`connection point into a
`network, and the ports
`being configurable by
`control plane processes;
`
`[19.1] b. executing port
`services on packets entering
`and exiting the physical
`network interface ports, the
`port services for controlling
`and monitoring packet
`flows as defined by control
`plane configurations;
`
`[19.2] c. executing a
`plurality of control plane
`processes, the control plane
`processes providing high
`level control and
`configuration of the ports
`and port services, and
`additionally comprising the
`steps of:
`
`[19.3] i. accessing the
`collection of control plane
`processes as a control plane
`port entity, so that a set of
`control plane port services
`are applied thereto as a set;
`
`- 13 -
`
`

`
`Cisco
`
`Arista
`
`See supra provided for element [1.4].
`
`See supra provided for element [1.4].
`
`See supra provided for element [1.0].
`
`See supra provided for element [1.0].
`
`US 7,224,668
`
`and
`
`[19.4] ii. operating on
`packets received from
`specific, predetermined
`physical ports and destined
`to the collection of control
`plane processes in a way
`that is independent of the
`individual physical port
`interface configuration and
`port services applied
`thereto.
`
`Claim 55
`[55.0] A computer readable
`storage medium containing
`instructions readable by a
`computer to configure the
`computer to perform a
`method for processing
`packets in an
`internetworking device
`comprising:
`
`a. configuring a plurality of
`physical network interface
`ports, each port for
`providing a physical
`connection point into a
`network, and the ports
`being configurable by
`
`- 14 -
`
`

`
`US 7,224,668
`control plane processes;
`
`[55.1] b. executing port
`services on packets entering
`and exiting the physical
`network interface ports, the
`port services for controlling
`and monitoring packet
`flows as defined by control
`plane configurations;
`
`[55.2] c. executing a
`plurality of control plane
`processes, the control plane
`processes providing high
`level control and
`configuration of the ports
`and port services, and
`additionally comprising the
`steps of:
`
`[55.3] i. accessing the
`collection of control plane
`processes as a control plane
`port entity, so that a set of
`control plane port services
`are applied thereto as a set;
`and
`
`[55.4] ii. operating on
`packets received from
`specific, predetermined
`
`Cisco
`
`Arista
`
`See supra provided for element [1.1].
`
`See supra provided for element [1.1].
`
`See supra provided for element [1.2].
`
`See supra provided for element [1.2].
`
`See supra provided for element [1.3].
`
`See supra provided for element [1.3].
`
`See supra provided for element [1.4].
`
`See supra provided for element [1.4].
`
`- 15 -
`
`

`
`Cisco
`
`Arista
`
`US 7,224,668
`physical ports and destined
`to the collection of control
`plane processes in a way
`that is independent of the
`individual physical port
`interface configuration and
`port services applied
`thereto.
`
`
`
`- 16 -