Internet DRAFT - draft-du-ccwg-framework-of-data-express-service
draft-du-ccwg-framework-of-data-express-service
CCWG Z. Du
Internet-Draft China Mobile
Intended status: Informational 17 October 2023
Expires: 19 April 2024
A Framework of Data Express Service
draft-du-ccwg-framework-of-data-express-service-00
Abstract
This document describes a potential framework for Data Express
Service, and related technology requirements.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
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 April 2024.
Copyright Notice
Copyright (c) 2023 IETF Trust and the persons identified as the
document authors. All rights reserved.
Du Expires 19 April 2024 [Page 1]
Internet-Draft Framework of DES October 2023
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.
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 of DES . . . . . . . . . . . . . . . . . . . . . 3
3. Framework of DES and Related Technology . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . 5
7.2. Informative References . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
As rapid development of the AI technologies, we need more powerful
computing capability. In addition, sharing of the data and computing
resource would also be necessary. Under this situation, the network
needs to provide Data Express Service (DES) between different
entities. The target of the service is normally to transfer a large
file or a bundle of files, and the size may be at the GB, TB level,
or even bigger.
Although we can connect to a cloud service anywhere now, sometimes
the file upload experience is not satisfying. Alternatively, we can
post a hard disk to others for this big data transferring. However,
if the job is repeated, it is surely boring and inconvenient. As the
requirements of Data Express Service are growing fast, we need to
provide a more convenient approach.
The mechanisms in Data Express Service should be more automatic and
convenient than the current approaches. Comparing to the approach of
transferring by using the Internet directly, the DES should be
quicker and automatic. Comparing to the manual hard disk express,
the DES should be more extensible and convenient.
In details, the DES scenarios may include inter-cloud backup and
disaster recovery, film and television editing, scientific computing,
cooperation of intelligent computing centers.
Du Expires 19 April 2024 [Page 2]
Internet-Draft Framework of DES October 2023
This document aims to analyse the requirements of DES, and proposes a
potential framework for it.
2. Requirements of DES
The demands of the DES traffic would be slightly different from the
current Internet services.
The first one is that it may be not that real-time. It is only
required to be completed within a time limitation. Some may need to
be completed within hours, and some may need to be completed within
one day or two days.
The traffic amount would be huge normally, and the flow would last
for a while in the network. It would appear as an elephant flow in
the network.
Hence, the traffic characteristic of the DES would be more
predictable than the current Internet service, and we can provide
specific treatment for these traffic. Even, we can schedule the
transport time for them, only if we can finish it on-time. In other
words, we can store the file waiting to be transported.
3. Framework of DES and Related Technology
A framework for DES is proposed in this section as shown in Figure 1.
We recognize two network environments in the framework, i.e., the
access network and the core network.
Traditionally, the client can connecte to the cloud directly.
However, due to the complexed E2E network environment, the E2E
transport speed sometimes is not satisfying.
For the DES, we can split the E2E connection into three parts: from
the client to a Data Harbor, among the Data Harbors, and from the
Data Harbor to the cloud. The Data Harbors can communicate with each
other at a high speed; meanwhile, it can store the files temporarily.
Du Expires 19 April 2024 [Page 3]
Internet-Draft Framework of DES October 2023
+--------+ +----------+ +--------+
| client |+ | | | |+
+--------+|+ Access | Data | Access | Cloud ||+
+--------+| ------| Harbor1 |------- | |||
+--------+ / | | \ +--------+||
/ +----------+ \ +--------+|
Core Core +--------+
/ \ Access
+---------+ +-------------+
| | | |
| Data | | Data |
| Harbor2 | --------------Core Network---------- | Harbor3 |
| | | |
+---------+ +-------------+
Access Network Access Network
+--------+ +--------+
| client |+ | client |+
+--------+|+ +--------+|+
+--------+| +--------+|
+--------+ +--------+
Figure 1: A framework for Data Express Service with Data Harbors
As an example, the procedures of the DES service are as follows:
Step1: a client connects to an available Data Harbor and uploads its
files, if its speed to the target cloud is not satisfying.
Meanwhile, the client should provide the time limitation for the
files.
Step2: the Data Harbors should schedule the transport time for the
files according to its time limitation and the link load between
target Data Harbors.
Step3: after receiving the files, the target Data Harbors should
upload the files to the cloud according to its time limitation and
the link load between the target Data Harbors and the cloud.
If we have many clients that need the DES services, we can built a
high speed link between specific Data Harbors. This is the key
feature that the DES can be more quick than a normal Internet
connection. Under this situation, we also need a high speed
transport protocol to transport files efficiently, or more
specifically, a specific designed congestion control method for the
Data Harbors. The methods mentioned in [I-D.ietf-ccwg-rfc5033bis]
can be considered here. Optionally, to improve the speed between the
Data Harbors, we can also deploy RDMA mechanisms.
Du Expires 19 April 2024 [Page 4]
Internet-Draft Framework of DES October 2023
4. IANA Considerations
TBD.
5. Security Considerations
TBD.
6. Acknowledgements
TBD.
7. References
7.1. Normative References
[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>.
7.2. Informative References
[I-D.ietf-ccwg-rfc5033bis]
Duke, M. and G. Fairhurst, "Specifying New Congestion
Control Algorithms", Work in Progress, Internet-Draft,
draft-ietf-ccwg-rfc5033bis-01, 13 October 2023,
<https://datatracker.ietf.org/doc/html/draft-ietf-ccwg-
rfc5033bis-01>.
Author's Address
Zongpeng Du
China Mobile
No.32 XuanWuMen West Street
Beijing
100053
China
Email: duzongpeng@foxmail.com
Du Expires 19 April 2024 [Page 5]
