doc: update BOLT quotes (to include same-transmission-order rule).

We implement this, but now we have an appropriate quote!

Signed-off-by: Rusty Russell <[email protected]>

Author: rustyrussell

Makefile

@@ -24,7 +24,7 @@ CCANDIR := ccan
 
 # Where we keep the BOLT RFCs
 BOLTDIR := ../lightning-rfc/
-BOLTVERSION := dcf6b0f359c230ef140e336011890c96eea576fa
+BOLTVERSION := 920e51986d654b78d1ec2afc18152c9986f52a9d
 
 -include config.vars
 

channeld/channeld.c

@@ -2409,6 +2409,10 @@ static void peer_reconnect(struct peer *peer,
 	 *    number of the last `revoke_and_ack` the receiving node sent, AND
 	 *    the receiving node hasn't already received a `closing_signed`:
 	 *    - MUST re-send the `revoke_and_ack`.
+	 *    - if it has previously sent a `commitment_signed` that needs to be
+	 *      retransmitted:
+	 *      - MUST retransmit `revoke_and_ack` and `commitment_signed` in the
+	 *        same relative order as initially transmitted.
 	 *  - otherwise:
 	 *    - if `next_revocation_number` is not equal to 1 greater
 	 *      than the commitment number of the last `revoke_and_ack` the
@@ -2504,8 +2508,12 @@ static void peer_reconnect(struct peer *peer,
 					      ? NULL
 					      : &remote_current_per_commitment_point);
 
-	/* We have to re-send in the same order we sent originally:
-	 * revoke_and_ack (usually) alters our next commitment. */
+	/* BOLT #2:
+ 	 * - if it has previously sent a `commitment_signed` that needs to be
+	 *   retransmitted:
+	 *   - MUST retransmit `revoke_and_ack` and `commitment_signed` in the
+	 *     same relative order as initially transmitted.
+	 */
 	if (retransmit_revoke_and_ack && !peer->last_was_revoke)
 		resend_revoke(peer);