Internet DRAFT - draft-service-identification-header-of-san
draft-service-identification-header-of-san
INTAREA L. Ma
Internet-Draft F. Zhou
Intended status: Standards Track H. Li
Expires: 19 February 2023 ZTE Corporation
18 August 2022
Service Identification Header of Service Aware Network
draft-service-identification-header-of-san-00
Abstract
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.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 19 February 2023.
Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Ma, et al. Expires 19 February 2023 [Page 1]
Internet-Draft Service Identification Header of Service August 2022
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Design principles and key elements of SAN identification . . 3
5. Structure of SAN header . . . . . . . . . . . . . . . . . . . 3
6. Security Considerations . . . . . . . . . . . . . . . . . . . 4
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
9. Normative References . . . . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. 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 [I-D.huang-service-aware-network-framework].
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.
2. 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 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
Ma, et al. Expires 19 February 2023 [Page 2]
Internet-Draft Service Identification Header of Service August 2022
3. 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.
4. 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.
5. Structure of SAN header
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|SANID Indicator|S|R| Flags | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SANID(Service ID) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream ID (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Structure of SAN header
Ma, et al. Expires 19 February 2023 [Page 3]
Internet-Draft Service Identification Header of Service August 2022
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.
6. Security Considerations
TBA
7. Acknowledgements
TBA
8. IANA Considerations
TBA
9. Normative References
Ma, et al. Expires 19 February 2023 [Page 4]
Internet-Draft Service Identification Header of Service August 2022
[I-D.huang-service-aware-network-framework]
Huang, D. and B. Tan, "Service Aware Network Framework",
Work in Progress, Internet-Draft, draft-huang-service-
aware-network-framework-00, 24 May 2022,
<https://www.ietf.org/archive/id/draft-huang-service-
aware-network-framework-00.txt>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
Authors' Addresses
Liwei Ma
ZTE Corporation
No.50 Software Avenue
Nanjing
Jiangsu, 210012
China
Email: ma.liwei1@zte.com.cn
Fenlin Zhou
ZTE Corporation
No.50 Software Avenue
Nanjing
Jiangsu, 210012
China
Email: zhou.fenlin@zte.com.cn
Hesong Li
ZTE Corporation
No.6 Huashi Park Rd
Wuhan
Hubei, 430223
China
Email: li.hesong@zte.com.cn
Ma, et al. Expires 19 February 2023 [Page 5]
