Internet-Draft Additional addresses for QUIC March 2024
Piraux & Bonaventure Expires 5 September 2024 [Page]
Workgroup:
QUIC
Internet-Draft:
draft-piraux-quic-additional-addresses-02
Published:
Intended Status:
Experimental
Expires:
Authors:
M. Piraux
UCLouvain & WEL RI
O. Bonaventure
UCLouvain & WEL RI

Additional addresses for QUIC

Abstract

This document specifies a QUIC frame enabling a QUIC server to advertise additional addresses that can be used for a QUIC connection.

About This Document

This note is to be removed before publishing as an RFC.

The latest revision of this draft can be found at https://mpiraux.github.io/draft-piraux-quic-additional-addresses/draft-piraux-quic-additional-addresses.html. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-piraux-quic-additional-addresses/.

Discussion of this document takes place on the QUIC Working Group mailing list (mailto:quic@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/quic/. Subscribe at https://www.ietf.org/mailman/listinfo/quic/.

Source for this draft and an issue tracker can be found at https://github.com/mpiraux/draft-piraux-quic-additional-addresses.

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.

1. Introduction

The QUIC protocol specifies several techniques for network path migration. The client can migrate from one of its local addresses to another at any time after the handshake using connection migration. The server can transfer a connection to one of its other addresses shortly after the handshake by using the preferred_address transport parameter. However, it cannot advertise additional addresses that a client may use.

This limitation impacts several scenarios. For instance, a multihomed server that has access to several subnets cannot advertise all its addresses. In entreprise deployments where provider-assigned IPv6 Addresses are used to solve the multihoming problem [RFC8678], announcing several server addresses enables applications using QUIC to recover from provider failures. Also, a dual-stack server cannot advertise its other address so that a client losing the address family used to establish the connection can migrate to the other address family.

This document proposes a QUIC frame and a QUIC transport parameter enabling a QUIC server to advertise additional addresses that can be used for a QUIC connection.

2. Conventions and Definitions

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

The ADDITIONAL_ADDRESSES frame proposed in this document enables a QUIC server to securely advertise additional addresses. The Additional Addresses transport parameter enables a QUIC client to indicate support for this frame.

These addresses can be used by the client to migrate to a new server address at any time after the handshake. When [MULTIPATH-QUIC] is used over a QUIC connection, the client can use these addresses to establish additional network paths.

When sending packets to a new server address, the client validates the address using Path Validation as described in Section 8.2 of [QUIC-TRANSPORT]. When Preferred Adress and Additional Addresses are used together, the client SHOULD NOT migrate to an additional address before acting on the preferred address indicated by the server.

3.1. Example of use

Figure 1 illustrates an example of use for Additional Addresses in a QUIC deployment featuring a load balancer and a multihomed server making use of the Preferred Address mechanism.

First, the client sends its Initial packet to the load balancer, which forwards it to the first server IP. The client indicates support for this extension by using the dedicated transport parameter. The server answers to the QUIC connection opening and indicates its first IP as a preferred address and its second one as an additional address using the dedicated frame. When the handshake completes, the client validates the preferred address and migrates to it. Later during the connection, the client can validate the path towards the second server IP and can migrate to it.

Client       Load-balancer @ IP lb        Server @ IP a   Server @ IP b
|                      |                      |               |
|       Initial[0]: CRYPTO(CH(Add.Addr))      |               |
|--------------------->|--------------------->|               |
                             ....
|      Handshake[0]: CRYPTO(EE(Pr.Addr=a),..) |               |
|<---------------------|<---------------------|               |
|         1-RTT[0]: ADDITIONAL_ADDRESSES([b]) |               |
|<---------------------|<---------------------|               |
                             ....
|       Handshake[0]: CRYPTO(Fin)             |               |
|--------------------->|--------------------->|               |
|    /* Migration to Preferred Address a */   |               |
|-------------------------------------------->|               |
                             ....
|                      |                      |
|                      |                      .               |
| 1-RTT[X]: PATH_CHALLENGE  /* Migration to Add. Address b */ |
|------------------------------------------------------------>|
|                                   1-RTT[Y]: PATH_RESPONSE   |
|<------------------------------------------------------------|
|                                                             |
Figure 1: A server reached through a load-balancer uses Add. Addresses

4. Additional Addresses Transport Parameter

The following transport parameter is defined:

additional_addresses (TBD - experiments use 0x925addaXX):

Indicates the support of the ADDITIONAL_ADDRESSES frame as defined in the -XX draft version of this document. This transport parameter has a zero-length value. It MUST NOT be sent by a server.

5. ADDITIONAL_ADDRESSES Frames

The server uses an ADDITIONAL_ADDRESSES frame (type=TBD - experiments use 0x925addaXX) to advertise the additional addresses that a client can use to reach it. This frame MUST NOT be sent by a client and can only appear in 1-RTT packets.

Additional Addresses {
  Type (i) = TBD,
  Sequence Number (i),
  Additional Addresses Count (i),
  Additional Address (..) ...,
}
Figure 2: ADDITIONAL_ADDRESSES Frame Format
Sequence Number:

A variable-length integer indicating the sequence of the frame. The number is monotonically increasing within a QUIC connection and is chosen by the sender. It helps the receiver to order ADDITIONAL_ADDRESSES frames by recency. A receiver SHOULD ignore frames with a Sequence Number lower or equal to the highest Sequence Number received.

Additional Addresses Count:

A variable-length integer indicating the number of additional addresses in the frame.

Additional Address {
  Address Version (8),
  IP Address (..),
  IP Port (16),
}
Figure 3: Additional Address Format
Address Version:

An 8-bit value identifying the Internet address version of this address. The value 4 indicates IPv4 while 6 indicates IPv6.

IP Address:

The address value. Its size depends on its version. IPv4 addresses are 32-bit long while IPv6 addresses are 128-bit long.

IP Port:

A 16-bit value representing the port to use with this IP Address.

The ADDITIONAL_ADDRESSES frame is ack-eliciting. When a packet containing an ADDITIONAL_ADDRESSES frame is lost and its content is still relevant, the sender MAY retransmit the frame as is. Otherwise, sending a new frame with a new Sequence number is preferred.

The server can update the client on its additional addresses at any time by sending an ADDITIONAL_ADDRESSES frame. When a client is using one of these additional addresses and receives an ADDITIONAL_ADDRESSES frame not containing this address, it SHOULD stop using it in favor of another address.

6. Security Considerations

This document specifies a mechanism allowing servers to influence the IP addresses towards which clients send QUIC packets. In this case, a malicious server could cause a client to send packets to a victim. A countermeasure similar to Section 21.5.3 of [QUIC-TRANSPORT] is to limit the packets that are sent to a non-validated additional addresses.

Given that a server can provide additional addresses at any point in time, a malicious server could overload a client and direct it against many addresses. To alleviate this, a client can choose to limit the number of addresses it keeps track of and the frequency at which it considers them.

A client MUST NOT send non-probing frames to an additional address prior to validating that address. The generic measures described in Section 21.5.6 of [QUIC-TRANSPORT] also remain applicable for further mitigation.

7. IANA Considerations

This document defines a new transport parameter for indicating support for additional addresses. The draft defines provisional identifiers for experiments. IANA will allocate the final identifiers.

The following entry in Table 1 should be added to the "QUIC Transport Parameters" registry under the "QUIC" heading.

Table 1: Addition to QUIC Transport Parameters Entries
Value Parameter Name. Specification
TBD (experiments use 0x925addaXX) additional_addresses Section 4

The last byte of the experimental transport parameter ID is used by implementations to indicate the version of this document they support. For instance, the value 0x925adda01 indicates the support of the -01 version of this document.

The following entry in Table 1 should be added to the "QUIC Frame Types" registry under the "QUIC" heading.

Table 2: Addition to QUIC Frame Types Entries
Value Frame Type Name Specification
TBD (experiments use 0x925addaXX) ADDITIONAL_ADDRESSES Section 4

The last byte of the experimental frame type is used by implementations to indicate the version of this document they support. For instance, the value 0x925adda01 indicates the support of the -01 version of this document.

8. References

8.1. Normative References

[QUIC-TRANSPORT]
Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based Multiplexed and Secure Transport", RFC 9000, DOI 10.17487/RFC9000, , <https://www.rfc-editor.org/rfc/rfc9000>.
[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/rfc/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/rfc/rfc8174>.

8.2. Informative References

[MULTIPATH-QUIC]
Liu, Y., Ma, Y., De Coninck, Q., Bonaventure, O., Huitema, C., and M. Kühlewind, "Multipath Extension for QUIC", Work in Progress, Internet-Draft, draft-ietf-quic-multipath-06, , <https://datatracker.ietf.org/doc/html/draft-ietf-quic-multipath-06>.
[RFC8678]
Baker, F., Bowers, C., and J. Linkova, "Enterprise Multihoming using Provider-Assigned IPv6 Addresses without Network Prefix Translation: Requirements and Solutions", RFC 8678, DOI 10.17487/RFC8678, , <https://www.rfc-editor.org/rfc/rfc8678>.

Acknowledgments

We thank Quentin De Coninck and François Michel for their feedback and comments on the first version of this document.

We thank Marcel Kempf, Moritz Buhl, Louis Navarre and François Michel for joining the interop during the IETF 118 Hackathon.

Authors' Addresses

Maxime Piraux
UCLouvain & WEL RI
Olivier Bonaventure
UCLouvain & WEL RI