MASQUE extension for signaling throughput advice
draft-ihlar-scone-masque-mediabitrate-01

Standard Communication with Network Elements                    M. Ihlar
Internet-Draft                                              M. Kühlewind
Intended status: Standards Track                                Ericsson
Expires: 24 April 2025                                   21 October 2024

            MASQUE extension for signaling throughput advice
                draft-ihlar-scone-masque-mediabitrate-01

Abstract

   This document specifies a new Capsule (RFC9297) that can be used with
   CONNECT-UDP (RFC9298), CONNECT-IP (RFC9484), or other future CONNECT
   extensions to signal throughput advice for traffic that is proxied
   through an HTTP server.

About This Document

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

   Status information for this document may be found at
   https://datatracker.ietf.org/doc/draft-ihlar-scone-masque-
   mediabitrate/.

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

   Source for this draft and an issue tracker can be found at
   https://github.com/mirjak/draft-masque-mediabitrate.

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

Ihlar & Kühlewind         Expires 24 April 2025                 [Page 1]
Internet-Draft      MASQUE throughput advice capsule        October 2024

   This Internet-Draft will expire on 24 April 2025.

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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   3
   3.  Indicating Support for Throughput Advice Signaling  . . . . .   3
   4.  THROUGHPUT_ADVICE Capsule Type Format . . . . . . . . . . . .   3
   5.  Applicability . . . . . . . . . . . . . . . . . . . . . . . .   3
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
     7.1.  Capsule types . . . . . . . . . . . . . . . . . . . . . .   4
     7.2.  HTTP headers  . . . . . . . . . . . . . . . . . . . . . .   4
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   This document specifies an HTTP Capsule (RFC9297) that can be used
   with CONNECT-UDP (RFC9298), CONNECT-IP (RFC9484), or other future
   CONNECT extensions to signal throughput advice for traffic proxied
   through an HTTP server.

   The extension can be used with the HTTP CONNECT method when the
   :protocol pseudo-header is equal to "connect-udp" or "connect-ip", as
   well as with future CONNECT protocols that use the Capsule Protocol.

Ihlar & Kühlewind         Expires 24 April 2025                 [Page 2]
Internet-Draft      MASQUE throughput advice capsule        October 2024

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.  Indicating Support for Throughput Advice Signaling

   A client that wishes to receive throughput advice capsules can
   indicate support by sending a request header with the boolean-valued
   Item Structured Field: "Throughput-Advice: ?1".  The HTTP proxy can
   indicate support by sending a response header with the same boolean-
   valued Item Structured Field: "Throughput-Advice: ?1".  See
   Section 3.3.6 of [RFC8941] for information about the boolean format.

   Once support has been established, a proxy MAY send THROUGHPUT_ADVICE
   capsules at any time during the lifetime of the stream that
   originated the request.

4.  THROUGHPUT_ADVICE Capsule Type Format

   The THROUGHPUT_ADVICE Capsule has the following format:

   THROUGHPUT_ADVICE Capsule {
     Type (i) = 0xTBD,
     Length (i)
     Bitrate (i)
     [Average Window (i)]
   }

   The capsule has the following fields:

   Bitrate: The maximum sustainable throughput that the client can
   expect for proxied traffic, expressed in kilobits per second.

   Average Window: Indicates the duration over which the bitrate is
   enforced, expressed in milliseconds.  This field is optional.

5.  Applicability

   If the sole purpose of the communication between a client endpoint
   and a network element is the exchange of throughput advice, it is
   RECOMMENDED to use more lightweight approaches than HTTP proxying,
   such as [SCONE] or [TRAIN].

Ihlar & Kühlewind         Expires 24 April 2025                 [Page 3]
Internet-Draft      MASQUE throughput advice capsule        October 2024

   However, in cases where clients connect to the Internet via MASQUE
   proxies and also want to receive throughput advice from the MASQUE
   proxy, it can be beneficial to communicate directly with the proxy
   using the already established communication channel.

6.  Security Considerations

   TODO Security

7.  IANA Considerations

7.1.  Capsule types

   This document adds following entries to the "HTTP Capsule Types"
   registry:

                +===============+=======+=================+
                | Capsule Type  | Value | Specification   |
                +===============+=======+=================+
                | MEDIA-BITRATE | TBD   | (This document) |
                +---------------+-------+-----------------+

                   Table 1: New Capsule Type to register

7.2.  HTTP headers

   This document adds following entry to the "Hypertext Transfer
   Protocol (HTTP) Field Name Registry":

    +===================+==========+===========+===========+==========+
    | Field Name        | Template | Status    | Reference | Comments |
    +===================+==========+===========+===========+==========+
    | Throughput-Advice |          | permanent | (This     |          |
    |                   |          |           | document) |          |
    +-------------------+----------+-----------+-----------+----------+

                    Table 2: HTTP Field Name to register

8.  References

8.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/rfc/rfc2119>.

Ihlar & Kühlewind         Expires 24 April 2025                 [Page 4]
Internet-Draft      MASQUE throughput advice capsule        October 2024

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

   [RFC8941]  Nottingham, M. and P. Kamp, "Structured Field Values for
              HTTP", RFC 8941, DOI 10.17487/RFC8941, February 2021,
              <https://www.rfc-editor.org/rfc/rfc8941>.

8.2.  Informative References

   [SCONE]    Joras, M. and M. Ihlar, "A new QUIC version for network
              property communication", Work in Progress, Internet-Draft,
              draft-joras-scone-quic-protocol-00, 21 October 2024,
              <https://datatracker.ietf.org/doc/html/draft-joras-scone-
              quic-protocol-00>.

   [TRAIN]    Thomson, M., Huitema, C., and K. Oku, "Transparent Rate
              Adaptation Indications for Networks (TRAIN) Protocol",
              Work in Progress, Internet-Draft, draft-thomson-scone-
              train-protocol-00, 14 October 2024,
              <https://datatracker.ietf.org/doc/html/draft-thomson-
              scone-train-protocol-00>.

Acknowledgments

   TODO acknowledge.

Authors' Addresses

   Marcus Ihlar
   Ericsson
   Email: marcus.ihlar@ericsson.com

   Mirja Kühlewind
   Ericsson
   Email: mirja.kuehlewind@ericsson.com

Ihlar & Kühlewind         Expires 24 April 2025                 [Page 5]