Rename PATH_STANDBY to PATH_BACKUP

fixes issue #283

draft-ietf-quic-multipath.md

@@ -200,7 +200,7 @@ to a packet number space.
 
 The same Path ID is used in both directions to
 address a path in the new multipath control frames,
-such as PATH_ABANDON {{path-abandon-frame}}, PATH_STANDBY {{path-standby-frame}}},
+such as PATH_ABANDON {{path-abandon-frame}}, PATh_BACKUP {{path-standby-frame}}},
 PATH_AVAILABLE {{path-available-frame}} as well as MP_ACK {{mp-ack-frame}}.
 Further, connection IDs are issued per Path ID.
 That means each connection ID is associated with exactly one path identifier
@@ -355,7 +355,7 @@ This proposal adds four multipath control frames for path management:
 
 - PATH_ABANDON frame for the receiver side to abandon the path
 (see {{path-abandon-frame}}),
-- PATH_STANDBY and PATH_AVAILABLE frames to express a preference
+- PATh_BACKUP and PATH_AVAILABLE frames to express a preference
 in path usage (see {{path-standby-frame}} and {{path-available-frame}}), and
 - MAX_PATH_ID frame for increasing the limit of active paths.
 
@@ -438,7 +438,7 @@ found in {{Section 8.1.3 of QUIC-TRANSPORT}}.
 
 ## Path Status Management
 
-An endpoint uses the PATH_STANDBY and PATH_AVAILABLE frames to inform the peer that it should
+An endpoint uses the PATh_BACKUP and PATH_AVAILABLE frames to inform the peer that it should
 send packets with the preference expressed by these frames.
 Note that an endpoint might not follow the peer’s advertisements,
 but these frames are still a clear signal of the peer's preference of path usage.
@@ -450,7 +450,7 @@ indicated as "standby" by the peer or non-usage of some locally available paths.
 PATH_AVAILABLE indicates that a path is "available", i.e., it suggests to
 the peer to use its own logic to split traffic among available paths.
 
-PATH_STANDBY marks a path as "standby", i.e., it suggests that no traffic
+PATh_BACKUP marks a path as "standby", i.e., it suggests that no traffic
 should be sent on that path if another path is available.
 If all active paths are marked as "standby", no guidance is provided about
 which path should be used.
@@ -473,7 +473,7 @@ Endpoints use the Path ID
 in these frames to identify which path state is going to be
 changed. Note that both frames can be sent via a different path
 and therefore might arrive in different orders.
-The PATH_AVAILABLE and PATH_STANDBY frames share a common sequence number space
+The PATH_AVAILABLE and PATh_BACKUP frames share a common sequence number space
 to detect and ignore outdated information.
 
 ## Path Close {#path-close}
@@ -1097,22 +1097,22 @@ After sending the PATH_ABANDON frame,
 the endpoint MUST NOT send frames that use the Path ID anymore,
 even on other network paths.
 
-## PATH_STANDBY frame {#path-standby-frame}
+## PATh_BACKUP frame {#path-standby-frame}
 
-PATH_STANDBY Frames are used by endpoints to inform the peer
+PATh_BACKUP Frames are used by endpoints to inform the peer
 about its preference to not use the indicated path for sending.
-PATH_STANDBY frames are formatted as shown in {{fig-path-standby-format}}.
+PATh_BACKUP frames are formatted as shown in {{fig-path-standby-format}}.
 
 ~~~
-  PATH_STANDBY Frame {
+  PATh_BACKUP Frame {
     Type (i) = TBD-03 (experiments use 0x15228c07)
     Path Identifier (i),
     Path Status Sequence Number (i),
   }
 ~~~
-{: #fig-path-standby-format title="PATH_STANDBY Frame Format"}
+{: #fig-path-standby-format title="PATh_BACKUP Frame Format"}
 
-PATH_STANDBY Frames contain the following fields:
+PATh_BACKUP Frames contain the following fields:
 
 Path Identifier:
 : The Path ID the status update corresponds to.
@@ -1121,26 +1121,26 @@ Path Identifier:
 
 Path Status Sequence Number:
 : A variable-length integer specifying the sequence number assigned for
-  this PATH_STANDBY frame. The sequence number space is shared with the
+  this PATh_BACKUP frame. The sequence number space is shared with the
   PATH_AVAILABLE frame and the sequence
   number MUST be monotonically increasing generated by the sender of
-  the PATH_STANDBY frame in the same connection. The receiver of
-  the PATH_STANDBY frame needs to use and compare the sequence numbers
+  the PATh_BACKUP frame in the same connection. The receiver of
+  the PATh_BACKUP frame needs to use and compare the sequence numbers
   separately for each Path ID.
 
 Frames may be received out of order. A peer MUST ignore an incoming
-PATH_STANDBY frame if it previously received another PATH_STANDBY frame
+PATh_BACKUP frame if it previously received another PATh_BACKUP frame
 or PATH_AVAILABLE
 for the same Path ID with a
 Path Status sequence number equal to or higher than the Path Status
 sequence number of the incoming frame.
 
-PATH_STANDBY frames are ack-eliciting. If a packet containing a
-PATH_STANDBY frame is considered lost, the peer SHOULD resend the frame
+PATh_BACKUP frames are ack-eliciting. If a packet containing a
+PATh_BACKUP frame is considered lost, the peer SHOULD resend the frame
 only if it contains the last status sent for that path -- as indicated
 by the sequence number.
 
-A PATH_STANDBY frame MAY be bundled with a MP_NEW_CONNECTION_ID frame or
+A PATh_BACKUP frame MAY be bundled with a MP_NEW_CONNECTION_ID frame or
 a PATH_RESPONSE frame in order to indicate the preferred path usage
 before or during path initiation.
 
@@ -1168,15 +1168,15 @@ Path Identifier:
 Path Status Sequence Number:
 : A variable-length integer specifying
   the sequence number assigned for this PATH_AVAILABLE frame.
-  The sequence number space is shared with the PATH_STANDBY frame and the sequence
+  The sequence number space is shared with the PATh_BACKUP frame and the sequence
   number MUST be monotonically increasing generated by the sender of
   the PATH_AVAILABLE frame in the same connection. The receiver of
   the PATH_AVAILABLE frame needs to use and compare the sequence numbers
   separately for each Path ID.
 
 Frames may be received out of order. A peer MUST ignore an incoming
 PATH_AVAILABLE frame if it previously received another PATH_AVAILABLE frame
-or PATH_STANDBY frame for the same Path ID with a
+or PATh_BACKUP frame for the same Path ID with a
 Path Status sequence number equal to or higher than the Path Status
 sequence number of the incoming frame.
 
@@ -1355,7 +1355,7 @@ Value                                              | Frame Name          | Speci
 ---------------------------------------------------|---------------------|-----------------
 TBD-00 - TBD-01 (experiments use 0x15228c00-0x15228c01) | MP_ACK              | {{mp-ack-frame}}
 TBD-02 (experiments use 0x15228c05)                  | PATH_ABANDON        | {{path-abandon-frame}}
-TBD-03 (experiments use 0x15228c07)                  | PATH_STANDBY        | {{path-standby-frame}}
+TBD-03 (experiments use 0x15228c07)                  | PATh_BACKUP        | {{path-standby-frame}}
 TBD-04 (experiments use 0x15228c08)                  | PATH_AVAILABLE      | {{path-available-frame}}
 TBD-05 (experiments use 0x15228c09)                  | MP_NEW_CONNECTION_ID   | {{mp-new-conn-id-frame}}
 TBD-06 (experiments use 0x15228c0a)                  | MP_RETIRE_CONNECTION_ID| {{mp-retire-conn-id-frame}}