From 70ca9fdc0bed18f13c6b761ef69b710bc725844c Mon Sep 17 00:00:00 2001 From: Dave Jones Date: Wed, 6 Mar 2024 09:02:24 +0000 Subject: [PATCH] Get the RFC refs right... --- docs/explain-pi-netboot.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/explain-pi-netboot.rst b/docs/explain-pi-netboot.rst index 3e3251c..b7ff91e 100644 --- a/docs/explain-pi-netboot.rst +++ b/docs/explain-pi-netboot.rst @@ -102,11 +102,11 @@ simple (as the acronym would suggest) and also rather inefficient, being limited to 512-byte blocks, in-order, synchronously (each block must be acknowledged before another can be sent), with no retry mechanism. Various extensions have been proposed to the protocol over the years, including those in :rfc:`2347`, -:rfc:`2348`, and :rfc:`7440`. +:rfc:`2348`, :rfc:`2349`, and :rfc:`7440`. The Pi bootloader implements *some* of these extensions. Specifically, it uses -the "blocksize" extension (:rfc:`2347`) to negotiate a larger size of block to -transfer, and the "tsize" extension (:rfc:`2348`) to attempt to determine the +the "blocksize" extension (:rfc:`2348`) to negotiate a larger size of block to +transfer, and the "tsize" extension (:rfc:`2349`) to attempt to determine the size of a transfer prior to it beginning. However, its use of "tsize" is slightly unusual in that, when it finds the