RINA Tutorial at ETSI ISG NGP#3

Editor's Notes

1. (Good stuff ;-) You might also include the 4 characteristics of the new paradigm to really establish that this was a different world.) I put this here rather than at the end so you would see it! ;-) After visiting Boston soon after the ARPANET began, Louis Pouzin then at IRIA set out to assemble a team to build a network, called CYCLADES specifically for doing research on networks. Pouzin’s team had a couple of advantages: they could learn from BBN’s experience and were greatly assisted by them. Also, they were looking at the whole problem: the hosts and the network. Michel Elie and Hubert Zimmermann recognized that there were layers both in the hosts and the network. But more importantly, they were not simply a stack of black boxes in a system, but were a cooperative collection of processes in different systems. And most importantly, the layers had different scope. Packets could only be relayed within a layer so far before having to be relayed by the layer above. Not all systems were involved in all layers. Pouzin had previously worked on Multics the pre-cursor to Unix, where he invented the shell. IRIA (Institute Research de Informatique et Automatique) became INRIA (Nationale was added) in 1979. By 1972, CYCLADES had arrived at the concept of the layers for a network, which had increasing scope: Layer 1: The Physical Layer was the physical media. . . the wire. Layer 2: The Data Link Layer (at this early stage was a point-to-point HDLC-like protocol) ensured that datagrams were not corrupted in transit. Layer 3: The Network Layer relayed datagrams through the network, but would be subject to loss due to congestion and the rare memory error during relaying. Layer 4: The Transport Layer provides end-to-end error control and recovers from loss due to congestion. Layer 5: The Application Layer, the rationale for the network.
2. Note that we don’t distinguish the processes that instantiate the layer in a system from *applications.* They are all just processes. IPC Processes consist of sub-tasks, threads, etc. perhaps even some is an FPGA. The scope of applications names is greater than any layer. Connection-id is formed by concatenating CEP-ids. Port-ids are never exchanged in protocol. Addresses are never visible the user of the layer.
3. It will cause less confusion if you put SDU protection below RMT, especially the middle one where it looks like you are sending it without doing it. It is in the text, but I think people look at figures first. Your decision.
4. RIB daemon also ensures that the information maintains the required level of freshness (synchronization), e.g. routing update as well as load information.
5. You might want some back up slides for multiple layers. That part is going to be hard for them to grasp. Especially since they seem to have a hard time even grasping how multihoming works.
6. Each layer can provide flows of different QoS, with its internal policies (like scheduling, flow control or transmission control) designed to support the advertised QoS level. With this design current LTE protocols are just policies for the common layer machinery, specifically (refer to Figure 7):   The MAC protocol becomes scheduling and medium access control policies for the multi-access radio DIF. The RLC protocol becomes delimiting and retransmission control policies for the multi-access radio DIF. PDCP becomes SDU protection policies for the mobile network top-level DIF (applied only between UEs and eNodeBs). GTP-U is not needed, it is just a connection-id that is already part of the common layer machinery. EPS bearers are flows provided by the mobile network top-level DIF. Radio bearers are flows provided by the multi-access radio DIF.   Since in this design the mobile network top layer is a complete layer, it can perform functions such as differential (per QoS-class) congestion control, dynamic/static QoS-aware routing or SDU protection between eNodeBs and S-GWs and SGW-s and P-GWs.
7. Serving area: This is an area served by one or more serving gateways S-GW, through which the mobile can move without a change of serving gateway. Tracking area: The MME pool areas and the S-GW service areas are both made from smaller, non-overlapping units known as tracking areas (TAs). They are similar to the location and routing areas from UMTS and GSM and will be used to track the locations of mobiles that are on standby mode
8. No need for tunnels nor to keep mappings between tunnels!
9. Note that forgetting an old address is just part of normal operation of the routing protocols. I know they can’t do it now, but point out that multihoming the radio will greatly reduce dropped calls and simplify the handoff procedure. Destination eNodeB selects new address for UE, which still keeps old address. Destination** eNodeB tells new address to source eNodeB. EFCP instances in UE start using new address in outgoing EFCP PDUs. P-GWs with EFCP flows with the UE start seeing the new UE address in incoming PDUs. EFCP instances start using the new address for outgoing EFCP PDUs (old address is no longer present in EFCP PDUs). When timers expire source eNodeB removes forwarding table entry and UE forgets old address.
10. Note that forgetting an old address is just part of normal operation of the routing protocols. I know they can’t do it now, but point out that multihoming the radio will greatly reduce dropped calls and simplify the handoff procedure.