]> Service Identification Header of Service Aware Network ZTE Corporation
No.50 Software Avenue Nanjing Jiangsu 210012 China ma.liwei1@zte.com.cn
ZTE Corporation
No.50 Software Avenue Nanjing Jiangsu 210012 China zhou.fenlin@zte.com.cn
ZTE Corporation
No.6 Huashi Park Rd Wuhan Hubei 430223 China li.hesong@zte.com.cn
Beijing Jiaotong University
Beijing China dyang@bjtu.edu.cn
INT INTAREA Service Identification Header of Service Aware Network As the cloud and computing migrates to edges further away from the traditional centered cloud, the services residing at the distributed cloud start to be delivered in such a ubiquitous and dynamic way. That it is challenging to the ongoing routing and interconnecting scheme under which host address is the global networking identification. This draft proposes a service identification which is designed to be treated both as a service routable ID and an interface to the service requirements as well as service-associated cloud resources. Service Aware Network header is illustrated and specified.
Introduction Unlike routing and forwarding scheme which is only involved bearer network, the service delivered from cloud needs delicate coordination among the terminal, bearer network and cloud. In order to improve the end-to-end capability of the network, service aware network framework is proposed . The SAN identification designed in the SAN reference framework, as an interface between clients and services, as well as between services and the network and cloud, solves the challenges that existing identification systems cannot simply integrate services through the endpoints, network and the cloud, and can effectively promote the evolution of service requirements. This proposal introduces an SAN header with a simple semantics service identification as an index in the network layer to enable the network to be highly effectively aware of the requirements of various cloud services. This service identification is designed to purporting to the fundamental and common services for which the service qualities should be guaranteed by both delicate networking and computing resources.
Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.
Terminology
  • SAN: Service Aware Network.
  • SAN ID: Service Aware Network Identification, an identification designed to indicate the fundamental and common service types.
  • SAN header: Encapsulation format of the SAN ID.
Design principles and key elements of SAN identification The SAN identification has global semantics through the terminal, network and cloud, and seamlessly connects and integrates the service, network and cloud system. SAN identification is only applicable to fundamental and common service types. The service identification only covers modular service types which are particularly sensitive to both networking and computing resources. When a service has multiple service instances, there is only one SAN identification used to indicate the general service type. SAN identification is only applicable to service types that have higher than "best effort" and "general computing processing" for computing network resources, that is to provides unified computing network services at layer L3. SAN identification support type aggregation. The aggregate identification structure is beneficial to improve the efficiency of indexing and table query.
Structure of SAN header
Structure of SAN header
SANID Indicator: indicates SAN ID metadata including length type of SAN ID. Flags: 8-bit flags field. The most significant bit is defined in this document. S: indicates the presence of stream ID. R:indicates the presence of the reserved field. the rest will be defined in the future version of this draft. Service ID: fixed length field. Service ID identifies a fundamental and common service ,the recommended SAN ID length is 32 bits, 64 bits, 128 bits or other lengths compatible with the common chip processing scheme. Service ID might consist of Hierarchical type identification (HID) and sub-service identification (Sub-SID). HID could represent the aggregation type of the service identification. Based on the HID, SAN can identify the category of application/service requests initiated by the terminal, and recognize that service sessions belonging to the same category of application/service requests.Sub service identification(Sub-SID), combines with HID to represent a globally unique service semantic identification, and apply to fundamental and common generic service. Stream ID: Fixed length and optional field. The terminal generates a unique Stream ID upon each service request, indicating the specific service stream identified both with the terminal and the service. The life cycle of Stream ID terminates when the associated service request by the specific terminal ends. Reserved: optional and for future extension.
Security Considerations TBA
Acknowledgements TBA
IANA Considerations TBA
Normative References Key words for use in RFCs to Indicate Requirement Levels In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. Service Aware Network Framework ZTE Corporation ZTE Corporation Cloud has been migrating from concentrated center sites to edge nodes with responsive and agile services to the subscribers. This industry-wide trend would be reasonably expected to continue into the future which would enjoy geographically ubiquitous services. Rather than transmitting service data streams to the stable and limited service locations such as centered cloud sites, routing and forwarding network will have to adapt to the emerging scenarios where the service instances would be highly dynamic and distributed, and further more, demand more fine-grained networking policies than the current routing and forwarding scheme unaware of service SLA requirements. This proposal is to demonstrate a framework under which the above-mentioned requirements would be satisfied.