MODIFICATION HISTORY: -------------------- -------- version 0.1.15 ------------------------------------------------------ ** 2003.03.16: Compliance with Out-of-Core Functionality Slight modifications needed to be made in order to maintain compatibility with changes that were made in SSFNet to support out-of-core memory usage. -------- version 0.1.14 ------------------------------------------------------ ** 2003.02.24: More Documentation Clean-Up -------- version 0.1.13 ------------------------------------------------------ ** 2002.12.18: Bug Fix: LSA Propagation Across AS Boundary There was a bug which could sometimes result in LSA's being propagated into different ASes. -------- version 0.1.12 ------------------------------------------------------ ** 2002.02.19: Documentation Cleaned Up -------- version 0.1.11 ------------------------------------------------------ ** 2001.01.23: Forwarding Table 'Replace' Instead of 'Add' Instead of just adding routes to the forwarding table (which does not replace any old routes with the same destination which were also added by the same protocol), OSPF is careful to replace old routes. Not doing so can leave old, unused routes hanging around. Some validation test output was modified in order to accommodate changes in forwarding table printouts. -------- version 0.1.10 ------------------------------------------------------ ** 2001.01.21: Updated Validation Tests Added "sort" on test outputs in "make valid" (was sorted only for "make all", causing problems on some platforms). -------- version 0.1.9 ------------------------------------------------------- ** 2001.01.20: Updated Routing Protocol Information Exchange A routing protocol may need to know when the local forwarding table (FIB) is modified by another source. For example, if BGP routes are being exported to OSPF, then OSPF needs to know whenever BGP makes a change to the FIB. By implementing the FIBChangeListener interface for sOSPF, OSPF can now listen for such changes. It no longer receives changes directly from BGP, as it did previously via method call. -------- version 0.1.8 ------------------------------------------------------- ** 2002.01.20: Updated Validation Tests Updated the output files for the fwdtable1 and fwdtable2 validation tests to include the new additional data printed out by the forwarding table (administrative distance). -------- version 0.1.7 ------------------------------------------------------- ** 2001.10.30: Renamed 'assert' Methods As of Java 1.4.0, 'assert' is a keyword. The Debug.assert and Debug.gassert methods have been renamed to 'affirm' and 'gaffirm' in response to the change. -------- version 0.1.6 ------------------------------------------------------- ** 2001.06.06: 'sort' Inconsistency Avoided An inconsistency in the Unix 'sort' program was causing certain validation tests to fail. The problem is being resolved (or avoided!) by not only sorting validation test results, but also sorting the files which those test results are matched against. -------- version 0.1.5 ------------------------------------------------------- ** 2001.06.02: revised test DML files DML configuration files of the tests were revised to accomodate the new release of tcpClient|Server (test results are the same). -------- version 0.1.4 ------------------------------------------------------- ** 2000.11.03: Documentation Update File OSPF/package.html was added so that javadoc-generated documentation will contain a description of the package. -------- version 0.1.3 ------------------------------------------------------- ** 2000.10.19: Memory Usage Reduced Part of the implementation which was using up a great deal of memory (a process in the sOSPF.init() method) was replaced with a lightweight Timer object. -------- version 0.1.2 ------------------------------------------------------- ** 2000.10.11: Validation Tests More Portable, Documentation Updated The automated validation tests previously relied on a specific ordering of the output which could vary when run on different JVMs. The output is now sorted in such a way that it is independent of which JVM is being used. -------- version 0.1.1 ------------------------------------------------------- ** 2000.10.10: Validation Tests Automated All validation tests were modified so that they could be run and checked for success automatically, rather than examining the output of the tests manually as was previously done. -------- version 0.1.0 ------------------------------------------------------- ** 2000.09.23: All Point-To-Point Networks Added to Forwarding Table Previously, the forwarding table for an OSPF router would contain entries for each point-to-point network to which it was directly connected, but not for any point-to-point networks to which it was not directly connect. Now such a forwarding table contains an entry for each point-to-point network in the area, whether the local router is directly connected to it or not. The primary reason for this was so that a packet addressed to an interface address on a non-adjacent router would not be dropped. The impetus came from the need for BGP to establish IBGP peers with neighbors to whom it was not physically directly connected. ** 2000.09.22: Support for Loopback Interfaces In general, a great deal of code clean-up and rearrangement was done, and minor (backward-compatible) changes and improvements to functionaliy were added. The only significant addition was for the support of loopback interfaces. (See sections 9.1 and 12.4.1 of RFC 2328.) Note that such loopback interfaces are not the same as the commonly known loopback address (127.0.0.1). -------- version 0.0.18 ------------------------------------------------------ ** 2000.06.15: Enforce Proper OSPF Area Specification in DML Changes in the area_descriptor and sOSPF classes to enforce proper use of the 'ospf_area' DML attribute. Currently only one area is ever used (which will likely change in the future), and an ospf_area attribute must always appear together in the same Net where an AS_status attribute appears. The value of ospf_area must currently always be 0, indicating a backbone router. Validation tests have been updated to accommodate this change. -------- version 0.0.17 ------------------------------------------------------ ** 2000.05.30: Validation Tests Updated; Options Adjusted Only minor changes. No change in the core behavior of OSPF was made. DML files for validation tests which used BGP were updated to accommodate an update in the behavior of BGP (since it now uses Sockets and TCP). The "show_AS" option was added as a temporary replacement for the "show_AS_area" option. The addition was made since there are no area numbers yet available to show. -------- version 0.0.16 ------------------------------------------------------ ** 2000.01.07: External Route Flooding Improved There was an error in the code for flooding link state advertisements within the AS after external route information was received from BGP. The router that learned of the new information sent advertisements to each neighbor using different sequence numbers when in fact it should have been using the same sequence number for each message, leading to an enormous number of redundant messages being sent. The method sOSPF.sendLSAListAllItrf() was modified to correct the problem. -------- version 0.0.15 ------------------------------------------------------ ** 1999.12.14: Tests and Documentation Cleaned Up Tests cleaned up a bit more, Makefiles streamlined and updated, documentation updated. -------- version 0.0.14 ------------------------------------------------------ ** 1999.12.13: Validation Tests Updated Tests updated to use tcpClient (instead of the old soloClient) and the 'pattern' DML attribute. -------- version 0.0.13 and earlier ------------------------------------------ Detailed record not available. See OSPF/doc/index.html.