Consideration for IP-Based TVR (Time-Variant Routing)
draft-wang-tvr-ip-consideration-00

tvr                                                              J. Wang
Internet-Draft                                              China Mobile
Intended status: Informational                              4 March 2024
Expires: 5 September 2024

         Consideration for IP-Based TVR (Time-Variant Routing)
                   draft-wang-tvr-ip-consideration-00

Abstract

   Satellite network are one of the TVR's use case.  This document makes
   some considerations on using IP for the satellite network.

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 5 September 2024.

Copyright Notice

   Copyright (c) 2024 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.
   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.

Wang                    Expires 5 September 2024                [Page 1]
Internet-Draft              ip-consideration                  March 2024

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Consideration . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Support Dynamic Routing . . . . . . . . . . . . . . . . .   3
     3.2.  Support Quality of Service (QoS) Guarantee  . . . . . . .   3
     3.3.  Support Heterogeneous Network Interconnectioncation . . .   4
   4.  Conclusion  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   7.  Informative References  . . . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   There were three use cases had been defined in the TVR's use case
   document [I-D.ietf-tvr-use-cases].  The first is resource
   preservation; one example of a network where nodes must perform
   resource preservation is an energy-harvesting, wireless sensor
   network.  The second is operating efficiency; one example of a
   network where nodes might seek to optimize operating cost is a set of
   nodes operating over cellular connections that charge both On-Peak
   and Off-Peak data rates.  The third is dynamic reachability; some
   examples of this use case are mobile satellites, predictable moving
   vessels and so on.

   Satellite network and terrestrial network use different physical and
   link layer protocols, making it difficult to achieve convergence at
   the bottom layer.  This problem can be solved at the network layer.
   On the one hand, TCP/IP is a simple and open protocol, which can help
   break the boundaries between heterogeneous networks to realize global
   interconnection.  On the other hand, the business is basically based
   on IP, and the development of IP-based space network can help realize
   the business integration and collaboration between heaven and earth
   and the integration and sharing of network resources, thus reducing
   the cost of network construction and operation and maintenance, and
   not only realizing the integration of heaven and earth in a more
   efficient way, but also better meeting the needs of personal
   communication and information access, and improving the user
   experience.  The development of IP-based space network can not only
   realize the integration of air and sky more efficiently, but also
   better satisfy the needs of personal communication and information
   acquisition, and improve the user experience and satisfaction.

   Although the TCP/IP protocol architecture is very mature for
   terrestrial networks, there are still many challenges in applying it
   to the heterogeneous satellite network with time-variant

Wang                    Expires 5 September 2024                [Page 2]
Internet-Draft              ip-consideration                  March 2024

   characteristics.  The current terrestrial network is homogeneous and
   topologically fixed by default, while the satellite network, which
   has time-variant characteristics, is a heterogeneous and dynamic
   network.

   This document makes some considerations on using IP for the satellite
   network.

2.  Conventions

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

   Considering requirements for on using IP for the satellite network.

3.1.  Support Dynamic Routing

   Networking using IP provides superior flexibility, enhanced
   scalability, and support for dynamic routing and mobile access, among
   other things.  However, the topology of satellite networks containing
   time-varying characteristics changes frequently, and traditional
   static routing techniques cannot meet the demand.  Therefore, dynamic
   routing, such as OSPF, is needed to adapt to the dynamic changes in
   network topology.  Therefore,

   o MUST provide a discovery and resolving methodology for the dynamic
   routing.

3.2.  Support Quality of Service (QoS) Guarantee

   Satellite network may need to support multiple service types, such as
   voice, video, data, etc., which have different requirements for QoS.
   Therefore, it is necessary to design effective QoS guarantee
   mechanisms, such as differential service (DiffServ), integrated
   service (IntServ), etc., to meet the needs of different services..
   Therefore,

   o MUST support Quality of Service (QoS) guarantee for the needs of
   different services.

Wang                    Expires 5 September 2024                [Page 3]
Internet-Draft              ip-consideration                  March 2024

3.3.  Support Heterogeneous Network Interconnectioncation

   Since a satellite network may be composed of several different
   heterogeneous networks, it is necessary to address the need for
   multiple heterogeneous network connections.  Therefore,

   o MUST Support heterogeneous network interconnectioncation.

4.  Conclusion

   This document This document makes some considerations on using IP for
   the satellite network, which is one of TVR's use cases.

5.  Security Considerations

   TBD.

6.  IANA Considerations

   TBD.

7.  Informative References

   [I-D.ietf-tvr-use-cases]
              Birrane, E. J., Kuhn, N., Qu, Y., Taylor, R., and L.
              Zhang, "TVR (Time-Variant Routing) Use Cases", Work in
              Progress, Internet-Draft, draft-ietf-tvr-use-cases-09, 29
              February 2024, <https://datatracker.ietf.org/doc/html/
              draft-ietf-tvr-use-cases-09>.

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

Author's Address

   Jing Wang
   China Mobile
   No.32 XuanWuMen West Street
   Beijing
   100053
   China
   Email: wangjingjc@chinamobile.com

Wang                    Expires 5 September 2024                [Page 4]