1.4 Cloud Native Network Functions added para in the end

Change to

A cloud native network function (CNF) is a cloud native application that implements network functionality. A CNF consists of one or more microservices and has been developed using Cloud Native Principles including immutable infrastructure, declarative APIs, and a “repeatable deployment process”.

An example of a simple CNF is a packet filter that implements a single piece of network functionality as a microservice. A firewall is an example of a CNF which may be composed of more than one microservice (i.e. encryption, decryption, access lists, packet inspection, etc.).

The CNFs themselves, by nature of following cloud native principles, are also composable and can implement and facilitate more complex network functionality if needed.

CNFs and cloud native principles can be used when implementing applications and network infrastructure which needs to meet standards such as 3GPP. For example, an Evolved Packet Core's (EPC) Serving Gateway could be implemented as a CNF and support all 3GPP requirements (eg. S1 protocol stack) allowing integration with other EPC services.

When we intend to define a CNF supporting network functions it is important to understand how much level of decomposition is optimum , For example current VNF's comprise of a set of VM's which has many services . A question will be should we deploy separate container and service for each of them . This idea may look smart but obviously not efficient .

No source file or test is named. Locate the document section titled “1.4 Cloud Native Network Functions,” add the paragraph supplied in the issue at its end, and verify that the rendered documentation contains the new text.

Written by the indexing model from the issue text.