From: Justin Pettit Date: Sat, 24 May 2008 20:54:22 +0000 (-0700) Subject: Make capitalization consistent. X-Git-Url: http://git.onelab.eu/?a=commitdiff_plain;h=048d68dcd53e1762bcb57560f2d0668b6edc725d;p=sliver-openvswitch.git Make capitalization consistent. --- diff --git a/INSTALL b/INSTALL index 5aa65e899..7f493514f 100644 --- a/INSTALL +++ b/INSTALL @@ -137,7 +137,7 @@ The instructions above set up OpenFlow for operation over a plaintext TCP connection. Production use of OpenFlow should use SSL[*] to ensure confidentiality and authenticity of traffic among switches and controllers. The source must be configured with --enable-ssl=yes to -build with ssl support. +build with SSL support. To use SSL with OpenFlow, you must set up a public-key infrastructure (PKI) including a pair of certificate authorities (CAs), one for @@ -381,7 +381,7 @@ following instructions to set up remote switches: 1. Start the datapath and attach it to two or more physical ports as described in the previous section. -2. Run the controller in passive tcp mode on the host which will act as +2. Run the controller in passive TCP mode on the host which will act as the controller. In the example below, the controller will bind to port 975 (the default) awaiting connections from secure channels. diff --git a/README b/README index dd8ef5155..75c01300f 100644 --- a/README +++ b/README @@ -8,7 +8,7 @@ researchers to run experiments in live networks. OpenFlow is based on a simple Ethernet flow switch that exposes a standardized interface for adding and removing flow entries. -An OpenFlow Switch consists of three parts: (1) A "flow table" in +An OpenFlow switch consists of three parts: (1) A "flow table" in which each flow entry is associated with an action telling the switch how to process the flow, (2) a "secure channel" connecting the switch to a remote process (a controller), allowing commands and packets to @@ -16,7 +16,7 @@ be sent between the controller and the switch, and (3) an OpenFlow protocol implementation, providing an open and standard way for a controller to talk to the switch. -An OpenFlow Switch can thus serve as a simple datapath element that +An OpenFlow switch can thus serve as a simple datapath element that forwards packets between ports according to flow actions defined by the controller using OpenFlow commands. Example actions are: @@ -24,7 +24,7 @@ the controller using OpenFlow commands. Example actions are: - Drop this flow's packets - Encapsulate and forward this flow's packets to the controller. -The OpenFlow Switch is defined in detail in the OpenFlow Switch +The OpenFlow switch is defined in detail in the OpenFlow switch Specification [2]. What's here?