First pass up to configuration
Change-Id: Ifd82c38aa18d5216c5772a64d9d77046def005fe
diff --git a/architecture.rst b/architecture.rst
index ff078a4..4fa4cb1 100644
--- a/architecture.rst
+++ b/architecture.rst
@@ -84,13 +84,13 @@
Policy Based Routing. But SDN control greatly simplifies the software running on each switch,
and control is moved into SDN applications running in the edge cloud.
-While these traditional switching/routing features are not particularly novel, SD-Fabric’s
+While these traditional switching/routing features are not particularly novel, SD-Fabric's
fundamental embrace of programmable silicon offers advantages that go far beyond traditional
fabrics.
Programmable Data Planes & P4
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-SD-Fabric’s data plane is fully programmable. In marked contrast to traditional fabrics, features
+SD-Fabric's data plane is fully programmable. In marked contrast to traditional fabrics, features
are not prescribed by switch vendors. This is made possible by P4, a high-level programming
language used to define the switch packet processing pipeline, which can be compiled to run at
line-rate on programmable ASICs like Intel Tofino (see https://opennetworking.org/p4/). P4
@@ -115,7 +115,7 @@
With integrated UPF processing, SD-Fabric can implement a 4G/5G local breakout for edge
applications that is multi-terabit and low-latency, without taking away CPU processing power for
containers or VMs. In contrast to UPF solutions based on full or partial smartNIC offload,
-SDFabric’s embedded UPF does not require additional hardware other than the same leaf and spine
+SD-Fabric's embedded UPF does not require additional hardware other than the same leaf and spine
switches used to interconnect servers and base stations. At the same time, SD-Fabric can be
integrated with both CPU-based or smartNIC-based UPFs to improve scale while supporting
differentiated services on a hardware-based fast-path at line rate for mission critical 4G/5G
@@ -138,10 +138,10 @@
- For GTP-U tunnels, it produces reports about the inner flow, thus monitoring the
forwarding behavior and perceived QoS for individual UE flows.
-SD-Fabric’s INT implementation is compliant with the open source INT specification, and it has
-been validated to work with Intel’s DeepInsight performance monitoring solution, which acts as
+SD-Fabric's INT implementation is compliant with the open source INT specification, and it has
+been validated to work with Intel's DeepInsight performance monitoring solution, which acts as
the collector of INT reports generated by switches. Moreover, to avoid overloading the INT
-collector and to minimize the overhead of INT reports in the fabric, SD-Fabric’s data plane uses
+collector and to minimize the overhead of INT reports in the fabric, SD-Fabric's data plane uses
P4 to implement smart filters and triggers that drastically reduce the number of reports
generated, for example, by filtering out duplicates and by triggering report generation only in
case of meaningful anomalies (e.g., spikes in hop latency, path changes, drops, queue congestion,
@@ -150,7 +150,7 @@
Flexible ASIC Resource Allocation
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-The P4 program at the base of SD-Fabric’s software stack defines match-action tables for
+The P4 program at the base of SD-Fabric's software stack defines match-action tables for
common L2/L3 features such as bridging, IPv4/IPv6 routing, MPLS termination, and ACL, as well
as specialized features like UPF, with tables that store GTP-U tunnel information and more. In
contrast to fixed-function ASICs used in traditional fabrics, table sizes are not fixed. The use of
@@ -211,7 +211,7 @@
a critical role in closed loop control by offering a programmatic way to dynamically change the
packet forwarding behavior.
-At a high level, SD-Fabric’s APIs fall into four major categories: configuration, information,
+At a high level, SD-Fabric's APIs fall into four major categories: configuration, information,
control, and OAM.
- Configuration: APIs let users set up SD-Fabric features such as VLAN information for
@@ -251,7 +251,7 @@
and spine switches. Similarly, logs of each component in SD-Fabric are streamed to an EFK stack
(ElasticSearch, Fluentbit, Kibana) for log preservation, filtering and analysis. SD-Fabric offers a
single-pane-of-glass for logging and troubleshooting network state, which can further be
-integrated with operator’s backend systems
+integrated with operator's backend systems
.. image:: images/arch-logging.png
:width: 1000px
@@ -318,7 +318,7 @@
Open Network Operating System (ONOS)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-SD-Fabric uses ONF’s Open Network Operating System (ONOS) as the SDN controller. ONOS is
+SD-Fabric uses ONF's Open Network Operating System (ONOS) as the SDN controller. ONOS is
designed as a distributed system, composed of multiple instances operating in a cluster, with all
instances actively operating on the network while being functionally identical. This unique
capability of ONOS simultaneously affords high availability and horizontal scaling of the control
@@ -339,7 +339,7 @@
API, which allows applications to program switching devices in a pipeline-agnostic
way. By using Flow-Objectives, applications can be written without worrying about low-level
pipeline details of various switching chips. The API is implemented by specific device drivers
-that are aware of the pipelines they serve and can thus convert the application’s API calls to
+that are aware of the pipelines they serve and can thus convert the application's API calls to
device-specific rules. In this way, the application can be written once, and adapted to pipelines
from different ASIC vendors.