Generalized IPv6 Tunnel for QUIC
draft-li-rtgwg-gip6-for-quic-02
| Document | Type | Active Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Zhenbin Li , Shuanglong Chen , Hang Shi | ||
| Last updated | 2024-01-10 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-li-rtgwg-gip6-for-quic-02
rtgwg Z. Li
Internet-Draft S. Chen
Intended status: Standards Track H. Shi
Expires: 14 July 2024 Huawei
11 January 2024
Generalized IPv6 Tunnel for QUIC
draft-li-rtgwg-gip6-for-quic-02
Abstract
This document defines a new encapsulation method for QUIC packet
transmission based on IPv6 extension headers. This method enables
QUIC packet transmission to easily inherit the extended functions of
IPv6.
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 14 July 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.
Li, et al. Expires 14 July 2024 [Page 1]
Internet-Draft GIP6 for QUIC January 2024
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
3. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 3
4. Encapsulation of GIP6 for QUIC . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . 4
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
7.1. Normative References . . . . . . . . . . . . . . . . . . 4
7.2. Informative References . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
[I-D.li-rtgwg-generalized-ipv6-tunnel] proposes the Generalize IPv6
Tunnel to unify the IP tunnels and remove duplicate functions and
support new features. QUIC, as a general-purpose transport layer
network protocol, is gradually being applied on the network side,
such as DNS over QUIC [RFC9250] and QUIC tunnel
[I-D.piraux-quic-tunnel]. QUIC tunnel-based packet transmission also
faces the issue of being extended to support new features.
This document defines encapsulation of QUIC headers into the GIP6
tunnel encapsulation and attempts to solve these issues.
2. Terminology
* APN: Application-aware Networking
* IOAM: In-situ Operations, Administration, and Maintenance
2.1. 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.
Li, et al. Expires 14 July 2024 [Page 2]
Internet-Draft GIP6 for QUIC January 2024
3. Problem Statement
As mentioned in the draft [I-D.li-rtgwg-generalized-ipv6-tunnel],
many new features, such as Alternate Marking
[I-D.ietf-6man-ipv6-alt-mark], IOAM
[I-D.ietf-ippm-ioam-ipv6-options], resource isolation
[I-D.ietf-6man-enhanced-vpn-vtn-id] , and APN
[I-D.li-apn-ipv6-encap], are emerging and the corresponding
encapsulations over the IPv6 are defined. Since there are all kinds
of existing IP tunnels (including UDP-based tunnels), if these new
features need to be supported over these tunnels, it is very
difficult to extend for these tunnels. If QUIC is used as a tunnel
for transmission of data packets in the network, it will also face
the challenge to support these new features.
4. Encapsulation of GIP6 for QUIC
[I-D.li-rtgwg-generalized-ipv6-tunnel] defined the GIP6 tunnel which
uses the IPv6 header and IPv6 extension header to support both
functions of existing IP tunnels and new features. The GIP6 tunnel
unifies the IP tunnels which removes the duplicate functions and
supports new features. This can greatly reduce the repeated effort
to extend the exiting IP tunnels to support the new features.
To support existing QUIC functions, the GIP6 tunnel is extended as
follows:
1. Definition of the QUIC Option: A new option called QUIC Option is
defined to carry the QUIC header information. The QUIC Option
MUST only be encapsulated in the Destination Options Header
(DOH). The format of the QUIC option is shown in Figure 1:
2. The function of the UDP header for ECMP can replaced by the flow
label of the IPv6 header in the GIP6 tunnel. To ensure
compatibility, the value of the flow label calculated for the
purpose of ECMP SHOULD be the same as that of the source port of
the UDP.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Opt Data Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| QUIC Header (Variable Bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: QUIC option header
Li, et al. Expires 14 July 2024 [Page 3]
Internet-Draft GIP6 for QUIC January 2024
where:
* Option Type: 8-bit selector. QUIC option. Value TBD by IANA.
* Opt Data Len: 8-bit unsigned integer. Length of the option, in
octets, excluding the Option Type and Option Length fields.
* Option Data: variable. QUIC Header Information. For the detailed
definition of the QUIC headers, please refer to [RFC8999].
5. Security Considerations
This document does not introduce any new security considerations.
6. IANA Considerations
The Option Type should be assigned in IANA's "Destination Options"
registry.
This draft requests the following IPv6 Option Type assignment from
the Destination Options sub-registry of Internet Protocol Version 6
(IPv6) Parameters (https://www.iana.org/assignments/
ipv6-parameters/).
Hex Value Binary Value Description Reference
act chg rest
----------------------------------------------------------------
TBD 00 0 TBD QUIC [This draft]
7. References
7.1. Normative References
[RFC9250] Huitema, C., Dickinson, S., and A. Mankin, "DNS over
Dedicated QUIC Connections", RFC 9250,
DOI 10.17487/RFC9250, May 2022,
<https://www.rfc-editor.org/rfc/rfc9250>.
[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/rfc/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/rfc/rfc8174>.
Li, et al. Expires 14 July 2024 [Page 4]
Internet-Draft GIP6 for QUIC January 2024
[RFC8999] Thomson, M., "Version-Independent Properties of QUIC",
RFC 8999, DOI 10.17487/RFC8999, May 2021,
<https://www.rfc-editor.org/rfc/rfc8999>.
7.2. Informative References
[I-D.li-rtgwg-generalized-ipv6-tunnel]
Li, Z., Chen, S., Gao, Q., Zhang, S., and Q. Xu,
"Generalized IPv6 Tunnel (GIP6)", Work in Progress,
Internet-Draft, draft-li-rtgwg-generalized-ipv6-tunnel-03,
6 November 2022, <https://datatracker.ietf.org/doc/html/
draft-li-rtgwg-generalized-ipv6-tunnel-03>.
[I-D.piraux-quic-tunnel]
Piraux, M., Bonaventure, O., and A. Masputra, "Tunneling
Internet protocols inside QUIC", Work in Progress,
Internet-Draft, draft-piraux-quic-tunnel-03, 12 August
2020, <https://datatracker.ietf.org/doc/html/draft-piraux-
quic-tunnel-03>.
[I-D.ietf-6man-ipv6-alt-mark]
Fioccola, G., Zhou, T., Cociglio, M., Qin, F., and R.
Pang, "IPv6 Application of the Alternate-Marking Method",
Work in Progress, Internet-Draft, draft-ietf-6man-ipv6-
alt-mark-17, 27 September 2022,
<https://datatracker.ietf.org/doc/html/draft-ietf-6man-
ipv6-alt-mark-17>.
[I-D.ietf-ippm-ioam-ipv6-options]
Bhandari, S. and F. Brockners, "IPv6 Options for In Situ
Operations, Administration, and Maintenance (IOAM)", Work
in Progress, Internet-Draft, draft-ietf-ippm-ioam-ipv6-
options-12, 7 May 2023,
<https://datatracker.ietf.org/doc/html/draft-ietf-ippm-
ioam-ipv6-options-12>.
[I-D.ietf-6man-enhanced-vpn-vtn-id]
Dong, J., Li, Z., Xie, C., Ma, C., and G. S. Mishra,
"Carrying Virtual Transport Network (VTN) Information in
IPv6 Extension Header", Work in Progress, Internet-Draft,
draft-ietf-6man-enhanced-vpn-vtn-id-05, 6 July 2023,
<https://datatracker.ietf.org/doc/html/draft-ietf-6man-
enhanced-vpn-vtn-id-05>.
Li, et al. Expires 14 July 2024 [Page 5]
Internet-Draft GIP6 for QUIC January 2024
[I-D.li-apn-ipv6-encap]
Li, Z., Peng, S., and C. Xie, "Application-aware IPv6
Networking (APN6) Encapsulation", Work in Progress,
Internet-Draft, draft-li-apn-ipv6-encap-07, 10 July 2023,
<https://datatracker.ietf.org/doc/html/draft-li-apn-ipv6-
encap-07>.
Authors' Addresses
Zhenbin Li
Huawei
Beiqing Road
Beijing
China
Email: lizhenbin@huawei.com
Shuanglong Chen
Huawei
Beiqing Road
Beijing
Email: chenshuanglong@huawei.com
Hang Shi
Huawei
Beiqing Road
Beijing
China
Email: shihang9@huawei.com
Li, et al. Expires 14 July 2024 [Page 6]