Mind hover

References https://success.docker.com/article/security-best-practices Description Aspects The micro services running (inside Pod/ Container environment) should be having restricted access to resources and priviledges. RBAC Network Access 3rd Party access to system resources Security aspects available in Kubernetes Pod security policy  

Cloud based microservice frameworks Some of open source platforms available are Swarm (Docker), Kubernetes (google), mesos, The most popular in communities and internet industry seems to be kubernetes and picking steam in telecom front as well for upcoming 5G Service based architecture. The kubernetes has the default container solution based on Rket ? but the most popular combinations are using Docker as container. Kubernetes/ an Cloud orachastrator !! Deployment automation of scaling in (zooming in/ increasing) and out (zooming out, decreasing) Network plugin available such as flannel (popular, support only IPv4), calico (support IPv4, IPv6), weavenet Kubernetes currently does not support dual stack IPv4, IPv6 inter-working etc capabilities till version 1.13 (dec 2018). Another limitation, it does not recognize the multiple interfaces in case enable to POD's for configuring services exposure and external communication till version 1.13 (dec 2018) Will be adding more...

NSSF - Network Slice Selector Function The 5G System architecture (3GPP TS 23.501: 5G SA; Stage 2) consists of the following network functions (NF). - Authentication Server Function (AUSF) - Core Access and Mobility Management Function (AMF) - Data network (DN), e.g. operator services, Internet access or 3rd party services - Structured Data Storage network function (SDSF) - Unstructured Data Storage network function (UDSF) - Network Exposure Function (NEF) - NF Repository Function (NRF) - Network Slice Selection Function (NSSF) ======>>> our focus - Policy Control function (PCF) - Session Management Function (SMF) - Unified Data Management (UDM) - Unified Data Repository (UDR) - User plane Function (UPF) - Application Function (AF) - User Equipment (UE) - (Radio) Access Network ((R)AN)

4G steps towards moving into world of network slicing with different options to utilize the opportunities which cloud/ virtualization market unleashing. Final destination to 5G architecture, where the network slicing is build-in with NSSF introduction in 3GPP. CUPS – Control User Place Separation of 4G network. This attempts to separate the Control and User Place at SGW/ PGW to achieve better control and resource requirements for network deployments. (e)DÉCOR – (enhanced) Dedicated Core Network allocation DÉCOR – R13 (No UE Changes, UE Usage Type parameter in Subscription Data … /// describes UE usage characteristics that enables the selection of a specific Dedicated Core Network (DCN).… MME uses it to map to DCN value. DCN selection at ENodeB Messages where it can be contained ULR (MME-> HSS) / IDR (HSS -> MME) / Reset (HSS -> MME) Authentication Information Answer (AIA – S6A) 29272 – S6A spec - If the MME or SGSN supports the Dedicated Core Netwo...

# Linux Networking - http://jodies.de/ipcalc?host=10.230.208.121&mask1=28&mask2= - To explore IP addressing/ masks IPv6 MTU related http://www.tcpipguide.com/free/t_IPv6DatagramSizeMaximumTransmissionUnitMTUFragment.htm https://tgsidau.wordpress.com/2013/12/16/ipv6-pmtud/ # RFCs UDP - 768 IP      - 791 ICMP - 792 TCP   - 793 SCTP - 3286 DIAMETER - 3588 (old), 6733 (latest) # Diameter RFC's Credit control application - 4006 (old), 8506 (latest) DOIC - 7683 DOIC rate control - 8582 # Telecom/ 3GPP / 4G PCC architecture - TS 23.203 Gx Interface - TS 29.212 Procedures -  GTPv1-U - TS 29.281 GTPv2-C - TS 29.274 NAS   TS 24.301  (for 5G its 501) EUTRAN Architecture - TS 23.401 4G procedures - TS 23.401 S1AP Application Part - TS 36.413 S1 general aspects - TS 36.410 4G Security Arechitecture - 33.401 # 5G Arena ------------ 5g spec list from 3gpp site - https://www.3gpp.org/dynareport/SpecList.htm?release=Rel-16...

Radio has always remained as one of crucial resources to wireless technology. They are always first to go into factory to look upon and improve the existing design/ architecture/ philosophies to give better user experience of the core/ back-haul capabilities. https://www.netmanias.com/en/?m=view&id=techdocs&no=13463 more to come ..

The transport has gone for several churn to cater to different requirements at each occassions. Currently after having experiences with SCTP/ MPTCP, the transport is getting one more re-calibrating as QUIC (google experiment) ...... to be updated in coming days. Main aim remains to be as light as UDP and still provide some reliability as TCP but not all. QUIC is an experimental projects towards same. Though the TCP was consistently used over the years and enhanced to mitigate the security/ reliability/ performance aspects. Its defeating the market progression to cloud. Cloud has made new technical advancements for the framework/ protocol/ environments where things can be deployed faster and analysis & results are much faster and quicker. Then our traditional OS based layering and very hard coupling and similarly tedious releasing it for usages and subsequently rollbacks and rollouts processes. Hence the experiment by google QUIC to decouple some of TCP sort of features from ...