$Id: test_form_fa.html,v 1.8 1998/12/09 20:09:28 kmustone Exp $

The following integration test report of the Foreign Agent consists of test cases that are created based on the defined functionality in the functional definition and the technical definition.

Test result codes:
S = Successful
I = Improvements required
F = Failed
N = Not implemented (yet)

Date {date}
Tester {tester}
Modules {modules and versions}
ID	Test case	Result	Comments
FA01	The Foreign Agent starts successfully and gets the configuration information that it needs
FA02	On receipt of an Agent Solicitation message the Foreign Agent replies to the sender with an Agent Advertisement message
FA03	On receipt of a Registration Request the Foreign Agent checks whether it has a pending mobility binding for the Home Agent specified in the request
FA04	If a Registration Request is received while there is no binding for the Mobile Node, an unconfirmed binding is created and the request is forwarded to the next upper Foreign Agent
FA05	If a Registration Request is received while there is a pending binding for the Mobile node, the message is verified with the Session Key
FA06	On a receipt of a Registration Request with an invalid MAC, the request is forwarded to the next higher Mobility Agent
FA07	On a receipt of an invalid Registration Request (Excluding case when only the MAC is invalid), the request is silently discarded
FA08	On a receipt of a valid Registration Request, the binding is updated and a Registration Reply is sent to the care-of address of the request
FA09	If there is a pending binding for the Mobile Node but there is no MAC included in the Registration Request, the Foreign Agent forwards the request to the next higher Mobility Agent.
FA10	On receipt of a Registration Reply the Foreign Agent confirms the corresponding unconfirmed binding, the tunnel is configured and the Registration Reply message is forwarded to the care-of address found in the binding
FA11	When the lifetime timer for a mobility binding expires, the Foreign Agent will purge the associated binding
FA12	When the Foreign Agent receives a Registration Request from a Mobile Node for which the Foreign Agent already has a binding to a different care-of-address than the one in the request, the Foreign Agent modifies the binding and sends the tunnel lifetime to the new care-of-address
FA13	When the Foreign Agent has an unconfirmed binding and the associated Mobile Node sends data to the Correspondent Node, the data is really delivered towards the Home Agent
FA14	When the Foreign Agent has an unconfirmed binding and the associated Mobile Node receives data from the Correspondent Node, the data is really delivered to the Mobile Node
FA15	When the Foreign Agent receives a Registration Request from a Mobile Node for which the Foreign Agent already has a binding to a different care-of-address than the one in the request, the Foreign Agent sends a Registration Reply with a lifetime value of 0 to the lower Foreign Agent of the old binding direction
FA16	Badly formatted messages must not be able to crash the Foreign Agent
FA17	If the Foreign Agent detects errors in the config file, it reports them according to the specification
FA18	When the Foreign Agent has received a Registration Request from the Mobile Node but the binding is still unconfirmed, even if the data packets cannot reach the destination, no ICMP Host Unreachable messages should be sent
FA19	The Foreign Agent logs the events that are defined to be logged in the functional definition
General comments {Comments}