Allow RTS calls prior to initial route table load
To better support heartbeat responses it is necessary to
allow RTS messages to be sent prior to the loading of
the initial route table. This change implements this and
has the side effect of also allowing wormhold sends prior
to a route table arrival (which is ok since no routing
is needed for wormhole traffic).
Issue-ID: RIC-589
Signed-off-by: E. Scott Daniels <daniels@research.att.com>
Change-Id: I302bdd0f274a7c5bc95f3f382e3374b21662ab8c
diff --git a/CHANGES_CORE.txt b/CHANGES_CORE.txt
index 8f58711..1acf21c 100644
--- a/CHANGES_CORE.txt
+++ b/CHANGES_CORE.txt
@@ -5,6 +5,12 @@
# API and build change and fix summaries. Doc correctsions
# and/or changes are not mentioned here; see the commit messages.
+2020 July 9; version 4.1.3
+ Allow RTS messages to be sent before the arrival of the initial
+ route table. Calls to RTS (heart beat responses) prior to the
+ initial route table load could cause a crash if a framework
+ blindly assumes that RTS is valid. (RIC-589)
+
2020 June 22; version 4.1.2
Fix typo in RIC Message header file.