over the route. REdef (Route-endpoint definition): Defines how a route (and its channels if multichannel route) must be referred in communication with a hosting network over a layer interface. In general, a hosted network can be hosted in more than one hosting network, which is why an NWi might also be part of an REdef. REdef Node of nw3 AddrPar In general: REi-REdef, where Node of nw2 Node of nw1 REdef::-{hostingNWi OPT, AddrPar OPT} In this case: REdef::=CHOICE {NW1,NW2}, where NW1::={{nw1},NA,API) NW2::={{nw2},CHi} SRi (Substructure-relation identifier): Defines which network levels the relation connects. n2.1.1 n2.1.2 n3.1.1 n3.1.2 n <network level>. <network identifier> <node identifier> REMARKS: ASi, CEi, and Ci are on-demand parameters. Remaining parameters are perma- nent or semi-permanent, which means they are set by configuration management. Lli and PA are used only in model execution. C2 Tables AMLn tables are based on 15 basic parameters: AAli, ALi, APi, As, ASi, CEi, CHi, Ci, GT, Li, Lli, NA, PA, NWi, REi. Eleven configuration management tables are defined: T-AL, T-AP, T-LI, T-PA, T-RE, T-NWg, T-NWd, T-ROa, T-ROs, T-GT, T-L. In addition, there are three dynamic tables for on-demand structures: T-AS, T-CS, T-CO. Tables in common agents: T-AL, actor-layer table: T-AS, association table: ASi AAi Tables for connectivity layers. On each logical network level: T-AP, access-point table (a table in a hosting node): APi hostedNWi T-RE, route-endpoint table (a table in a hosted node): REdef, where REdef::=(hostingNWi OPT, AddrPar OPT}, where AddrPar::={NA, APi, CHOICE{CEi CHi}} --all optional Tables in connectivity layers that translate between network levels: (these are tables that relate horizontally-partitioned logical networks to each other) T-NWg, layer interface translation table (a table in a hosting node): NWi (hosted network, level i) -> REi (hosting network, level i+1) T-NWd, layer interface translation table (a table in a hosted node): NWi (hosting network, level i) REi (hosting network, level i+1) 