JRA1/SA3 Schema Comparison
From GEANT2-JRA1 Wiki
A comparison has been performed between the JRA1 database schema and the SA3 schema. This pages lists commonalities and differences to have a basis for future discussions.
| JRA1 | SA3 | merge proposal |
| routers, switches, measurement points in schema | only routers | include additional information in SA3 schema |
| focused on layer 3 interfaces | differentiation of interfaces into three layers: physical, layer 2 (including technology dependent fields for ATM and frame relay, just one table for all technologies), and layer 3 | extend JRA1 schema for layer 1 and 2 |
| additional table for history information, linked to ID | "date_in", "date_upd" fields in "phy_ifce","l2_ifce","l3_ifce" | additional history table allows for increased flexibility |
| multipoint links representation (point-to-point as special case) | source-dest backbone links | discussion in JRA1 showed need for multipoint links |
| additional tables in JRA1: metrics, measurement data, map configurations, administrative information (authentication, access rights) | interface up/down on layer 2 level, is administrative or operational?; why propogation delay in backbone links (how measured)? Same of routing_cost, pip_percentage | open whether this information is of interest for SA3 |
| table for autonomous systems, how applied?, routing table | needed for JRA1? how to keep up-to-date? |
- With an additional history table the management of revisions can be managed outside of each element. Some issues are still open. Example: There have been two 1 Gigabit/s links from one location to another which have been replaced by a 10 Gb/s link. How to store this information?
- IPv4 or/and IPv6 in the tables?
- why "tag" field in SA3 l2_if_ce?
