add patch section

gh-pages/docs/Known-Issues.md

@@ -1,4 +1,4 @@
-# Known Issues
+# Known Issues & Patches
 
 Here is a list of known issues that will updated on a regular basis to captures various lessons-learned relating to the configurations, testing, performance, and deployment of ION:
 
@@ -7,15 +7,15 @@ Here is a list of known issues that will updated on a regular basis to captures
 ### UDP CLA
 
 * When using UDP CLA for data delivery, one should be aware that:
-   * UDP is inherently unreliable. Therefore the delivery of BP bundles may not be guaranteed, even withing a controlled, isolated network environment.
-   * It is best to use iperf and other performance testing tools to properly character UDP performance before using UDP CLA. UDP loss may have high loss rate due to presence of other traffic or insufficient internal buffer.
-   * When UDP CLA is used to deliver bundles larger than 64K, those bundle will be fragmented and reassembled at the destination. It has been observed on some platforms that UDP buffer overflow can cause a large number of 'cyclic' packet drops so that an unexpected large number of bundles are unable to be reassembled at the destination. These bundle fragments (which are themselves bundles) will take up storage and remain until either (a) the remaining fragments arrived or (b) the TTL expired.
+  * UDP is inherently unreliable. Therefore the delivery of BP bundles may not be guaranteed, even withing a controlled, isolated network environment.
+  * It is best to use iperf and other performance testing tools to properly character UDP performance before using UDP CLA. UDP loss may have high loss rate due to presence of other traffic or insufficient internal buffer.
+  * When UDP CLA is used to deliver bundles larger than 64K, those bundle will be fragmented and reassembled at the destination. It has been observed on some platforms that UDP buffer overflow can cause a large number of 'cyclic' packet drops so that an unexpected large number of bundles are unable to be reassembled at the destination. These bundle fragments (which are themselves bundles) will take up storage and remain until either (a) the remaining fragments arrived or (b) the TTL expired.
 
 ### LTP CLA
 
 * When using LTP over the UDP-based communication services (udpcli and udpclo daemons):
-   * The network layer MTU and kernel buffer size should be properly configured
-   * The use "WAN emulator" to add delay and probabilistic loss to data should be careful not to filter out UDP fragments that are needed to reconstruct the LTP segments or significantly delayed them such that the UDP segment reassembly will expire.
+  * The network layer MTU and kernel buffer size should be properly configured
+  * The use "WAN emulator" to add delay and probabilistic loss to data should be careful not to filter out UDP fragments that are needed to reconstruct the LTP segments or significantly delayed them such that the UDP segment reassembly will expire.
 
 ## Bundle Protocol
 
@@ -27,19 +27,19 @@ Here is a list of known issues that will updated on a regular basis to captures
 
 * When developing and testing ION in a docker container with root permission while mounting to ION code residing in a user's directory on the host machine, file ownership may switch from user to `root`. This sometimes leads to build and test errors when one switches back to the host's development and testing environment. Therefore, we recommend that you execute the `make clean` and `git stash` command to remove all build and testing artifacts from ION 's source directory before exiting the container.
 
-## SDR transaction
+## SDR 
 
 ### SDR transaction reversal
 
 When SDR transaction is canceled due to anomaly, ION will attempt automatically try the following:
 
-1. Reverse transaction - if it is configured - to revert modifications to the SDR's heap space which contains both user and protocol data units. This action rolls back a series of operations on the SDR's data of the cancelled the transaction. 
+1. Reverse transaction - if it is configured - to revert modifications to the SDR's heap space which contains both user and protocol data units. This action rolls back a series of operations on the SDR's data of the cancelled the transaction.
 2. Once the SDR's heap space has been restored, the "volatile" state of the protocols must be restored because they might be modified by the transaction as well. This is performed by the `ionrestart` utility.
-3. After the volatiles are reloaded, the 3rd step of restoring ION operation will need to be triggered by the users. During the anomously event that caused the transaction cancellation, some of ION's various daemons may have stopped. They can be restored by simply issuing the start ('s') command through `ionadmin` and `bpadmin`. 
+3. After the volatiles are reloaded, the 3rd step of restoring ION operation will need to be triggered by the users. During the anomously event that caused the transaction cancellation, some of ION's various daemons may have stopped. They can be restored by simply issuing the start ('s') command through `ionadmin` and `bpadmin`.
 
-### 'Init' Process PID 1 ###
+### 'Init' Process PID 1
 
-The reloading of the volatile state and restarting of daemons is necessary to ensure the ION system is in a consistent state before resuming normal operations. 
+The reloading of the volatile state and restarting of daemons is necessary to ensure the ION system is in a consistent state before resuming normal operations.
 
 During the reloading of the volatile state, the bundle protocol schemes, inducts, and outducts are stopped by terminating the associated daemons. The restart process will wait for the daemon's to be terminated before restarting them. When running ION inside a docker container, the `init` process (PID 1) should be properly configured to reap all zombie processes because the restart process cannot proceed if a terminated daemon remains a zombie. Typically to ensure the proper `init` process, one should use the `--init` option for `docker run` command.
 
@@ -57,10 +57,27 @@ at line 216 of ici/utils/ionadmin.c, ionadmin can't initialize ION.
 
 It indicates that ION is unable to clean out previously left behind semaphore files. This typically occurs when the previous ION run was launched by a different user, and ION was not properly shutdown via a shutdown script - instead, the global `ionstop` or `killm` script was used. The semaphore files used by POSIX named semaphore typically only allows the owner to delete it. The work around is to clear these files out. ION-related semaphore files have the name pattern of `sem.ion:GLOBAL:<integer>`. For Ubuntu, it is usually found in the `/dev/shm` directory; for other Linux distribution, the location can be different.
 
-
-## Reporting Issues ##
+## Reporting Issues
 
 * ION related issues can be reported to the public GitHub page for ION-DTN or ion-core.
 * ION's SourceForge page is now deprecated and issued reported there will not be monitored.
 
+## Patches
+
+In this section, we post patches issued between or ahead of major releases to fix bugs.
+
+Each patch is described as follows:
+
+- Issue Date: this is the date when the patch is made available.
+- Issue No.: GitHub issue number, if any, related to the patch.
+- Issue description
+- Link to the patch
+- The baseline version of ION from which the patch is issued.
+- The target version of ION to which the patch will incorporate. 
+
+| Issue Date | Issue # | Issue Description | Patch | From ION ver. | To ION ver. |
+|------------|---------|-------------------|-------|-----|-----|
+| TBD | 33 | bpv7 extension block CRC failure | TBD | 4.1.3 | 4.1.4 |
+
+