Routing tables: T-ROa, routing table (in a common agent): AA REi or ASi REi T-ROs, routing table (in a switching element): NA REi Miscellaneous tables: T-CO, connection table: Ci {hostedNWi,CEi} T-CS, control store: inlet->outlet, using CHi, VCi, and Li for inlet/outlet definitions, depending on the type of switch. T-GT, global-title table: GT {REi, destinationAPi} T-L, link table: Li AAli T-LI, layer-interface table: T-PA, platform table: {hostingPA, hostedPA} REMARKS: T-AS, T-CO and T-CS are set on-demand. Remaining tables are managed config- uration tables. Note that combining a T-GT and a T-RE table delivers GT REdef translations. This is the method used in e.g. DNS, since the TCP/UDP layers do not handle routes. T-LI and T-PA are needed only for simulation and model execution. Appendix D: AMLs and AMLp in Short D1 Introduction AMLn is used for modeling the layer structure and the node structure of a net- work system, as described in this book. AMLn can not, however, be used to specify how the modeled system will behave. To that regard we need another language that can be used for specifying interfaces of the AMLn model, and the behavior of its functional elements. This language may be AMLs, 1 where the "s" stands for "ser- vice" (for historical reasons). The only interfaces that cannot be specified by AMLs alone are network inter- faces and their message protocols. In AMLn, network interfaces are structures of message protocols and have no associated behavior, only message protocols have. A message protocol describes the behavior between two OSI layer elements or AMLn agents in terms of the messages they exchange. To that regard we need AMLp. AMLp is a method for specifying message protocols for (primarily) control layers. The "p" stands for "protocol". As has been discussed in this book, the separation of an OSI layer into one or several layer state machines (LSM) and a layer protocol machine (LPM) is a large improvement with respect to protocol specification since it separates two rather independent issues