Internet-Draft Intent-Based Networking July 2023
Yang & Wang Expires 10 January 2024 [Page]
Workgroup:
Internet Research Task Force
Internet-Draft:
draft-yang-nmrg-data-transfer-intent-01
Published:
Intended Status:
Informational
Expires:
Authors:
H. Yang
China Mobile
J. Wang
Centec

Data transmission intent over WAN - one of IBN use cases

Abstract

With the advent of the digital era, there are more and more scenarios such as data off-site AI training, data off-site cloud, and the demand for big data transmission in the WAN is increasing. WAN data transmission involves throughput, delay, packet loss, security and other performance indicators, as well as cost investment. Users have been exploring how to achieve the best performance of data transmission at the lowest cost. This paper implements high quality WAN data transmission based on IBNS.

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 10 January 2024.

Table of Contents

1. Introduction

An increasing number of scenarios require WAN to transmit massive data, such as:

1) Some applications of data production, training, reasoning deployed in a different position, need cloud, edge, huge amounts of data transmission among multiple data centers;

2) Collaborative computing between multiple data centers:

3) Data backup between multiple data centers;

4) loud users huge amounts of data;

The optimal transmission strategy is calculated based on the performance requirements of user data transmission and the upper cost input, and then translated into the specific configuration of the device to realize high-quality WAN data transmission based on the intentional network.

2. Conventions Used in This Document

2.1. Terminology

NTP Network Time Protocol

PTP Precision Time Protocol

DTN Digital Twin Network

2.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.

3. Wan data transmission intent

As defined in [RFC9315]: "Intent is a declaration of operational goals that a network is supposed to meet and outcomes that the network is supposed to deliver, without specifying how to achieve or how to implement them. Those goals and outcomes are defined in a manner that is purely declarative - they specify what to accomplish, not how to achieve it."

Users have different performance requirements for data transmission, such as throughput, delay, packet loss rate, and security level, based on the data type and cost upper limit. These requirements are not optimal at the same time, or all requirements to be optimal will lead to very high costs, causing users to be unable to afford. When a user enters the data transmission intention in the IBNS, the user provides specific performance requirements and cost ceilings. The system calculates the configuration policy based on the counter requirements, cost upper limit, and network status. Then, you can translate the configurations of specific devices (including network devices, firewalls, and storage servers) based on the configuration policies.

Data transmission configuration policies include the selection and parameter configuration of WAN congestion control, packet loss recovery, data encryption, packet loss retransmission, and other technical solutions.

Data transmission cost is mainly dedicated line rental cost, which is related to bandwidth, service time, distance and other parameters.

4. Intent lifecycle

According to the intent lifecycle in [RFC9315],after a user enters data transmission requirements, the IBNS processes the user's intent to meet the requirements.

(1) Input data transmission intention, clarify performance requirements, upper limit of cost input, etc.

(2) The system detects the current network performance in real time,and configuration strategy obtained through comprehensive calculation.

(3) Translate the configuration strategy into specific device configuration. Equipment includes network equipment and IT equipment.

(4) Detect the performance indicators of data transmission in real time and predict the cost of completing data transmission.

(5) Real-time calculation of whether the configuration strategy needs to be adjusted according to the detected network performance, data transmission performance and cost input.Update device configuration while changing configuration policy.

(6) Real-time analysis of cost input and data transmission performance indicators, and feedback to users.

User Space : Translation / IBS : Network Ops : Space : Space (1) : (2) : (3) +----------+ : +----------+ +-----------+ : +-----------+ Fulfill |recognize/+---> |translate/+--^+ learn/ +--^+ configure/| |generate | | | | plan/ | | pro^ision | |intent +^--+ | refine | | render | : | | +----^-----+ : +----------+ +-----^-----+ : +------+----+ | : | : | .............|................................|................|..... | : +--------+ : ^ | : |>alidate| : +-----+----+ | : |----^---+ <----+ monitor/ | Assure +---+---+ : +---------+ +---------+ : | obser^e/ | |report | <---+ |abstract +^---+ analyze | <----+ | +-------+ : +---------+ |aggregate| : +----------+ : +---------+ : (6) (5) (4)
Figure 1: Figure 1: Intent lifecycle

5. Conclusion

This is a usecase of IBNS, which uses IBNS to realize wide-area data transmission. After the user enters the performance parameters and the upper limit of the cost input, IBNS will automatically select the optimal configuration strategy, and can achieve high-quality data transmission services without manual participation.

6. Security Considerations

The security guarantee in data transmission is very important, especially in the transmission of customer privacy data over the WAN (Wide Area Network), which requires high-level data security encryption technology. Different levels of security encryption technology have different functional requirements for the data sending devices, network devices, and data receiving devices, and also have an impact on transmission efficiency. For users with different levels of data security needs, it is necessary to choose appropriate levels of data encryption measures and implement appropriate network configurations, which can be automated through the IBNS. According to the intent lifecycle process, IBNS can automatically perform operations such as intent parsing, configuration, detection, and optimization of user data security levels.

7. IANA Considerations

TBD.

8. References

8.1. Normative References

[RFC6020]
Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, DOI 10.17487/RFC6020, , <https://www.rfc-editor.org/info/rfc6020>.
[RFC6241]
Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, , <https://www.rfc-editor.org/info/rfc6241>.
[RFC8040]
Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Protocol", RFC 8040, DOI 10.17487/RFC8040, , <https://www.rfc-editor.org/info/rfc8040>.
[RFC8329]
Lopez, D., Lopez, E., Dunbar, L., Strassner, J., and R. Kumar, "Framework for Interface to Network Security Functions", RFC 8329, DOI 10.17487/RFC8329, , <https://www.rfc-editor.org/info/rfc8329>.
[RFC9315]
Clemm, A., Ciavaglia, L., Granville, L. Z., and J. Tantsura, "Intent-Based Networking - Concepts and Definitions", RFC 9315, DOI 10.17487/RFC9315, , <https://www.rfc-editor.org/info/rfc9315>.

8.2. Normative References

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <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, , <https://www.rfc-editor.org/info/rfc8174>.

Authors' Addresses

Hongwei Yang
China Mobile
Beijing
100053
China
Junjie Wang
Centec
Suzhou
215000
China