123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304 |
- /*
- * Copyright 2022-2024 The OpenSSL Project Authors. All Rights Reserved.
- *
- * Licensed under the Apache License 2.0 (the "License"). You may not use
- * this file except in compliance with the License. You can obtain a copy
- * in the file LICENSE in the source distribution or at
- * https://www.openssl.org/source/license.html
- */
- #ifndef OSSL_QUIC_DEMUX_H
- # define OSSL_QUIC_DEMUX_H
- # include <openssl/ssl.h>
- # include "internal/quic_types.h"
- # include "internal/quic_predef.h"
- # include "internal/bio_addr.h"
- # include "internal/time.h"
- # include "internal/list.h"
- # ifndef OPENSSL_NO_QUIC
- /*
- * QUIC Demuxer
- * ============
- *
- * The QUIC connection demuxer is the entity responsible for receiving datagrams
- * from the network via a datagram BIO. It parses the headers of the first
- * packet in the datagram to determine that packet's DCID and hands off
- * processing of the entire datagram to a single callback function which can
- * decide how to handle and route the datagram, for example by looking up
- * a QRX instance and injecting the URXE into that QRX.
- *
- * A QRX will typically be instantiated per QUIC connection and contains the
- * cryptographic resources needed to decrypt QUIC packets for that connection.
- * However, it is up to the callback function to handle routing, for example by
- * consulting a LCIDM instance. Thus the demuxer has no specific knowledge of
- * any QRX and is not coupled to it. All CID knowledge is also externalised into
- * a LCIDM or other CID state tracking object, without the DEMUX being coupled
- * to any particular DCID resolution mechanism.
- *
- * URX Queue
- * ---------
- *
- * Since the demuxer must handle the initial reception of datagrams from the OS,
- * RX queue management for new, unprocessed datagrams is also handled by the
- * demuxer.
- *
- * The demuxer maintains a queue of Unprocessed RX Entries (URXEs), which store
- * unprocessed (i.e., encrypted, unvalidated) data received from the network.
- * The URXE queue is designed to allow multiple datagrams to be received in a
- * single call to BIO_recvmmsg, where supported.
- *
- * One URXE is used per received datagram. Each datagram may contain multiple
- * packets, however, this is not the demuxer's concern. QUIC prohibits different
- * packets in the same datagram from containing different DCIDs; the demuxer
- * only considers the DCID of the first packet in a datagram when deciding how
- * to route a received datagram, and it is the responsibility of the QRX to
- * enforce this rule. Packets other than the first packet in a datagram are not
- * examined by the demuxer, and the demuxer does not perform validation of
- * packet headers other than to the minimum extent necessary to extract the
- * DCID; further parsing and validation of packet headers is the responsibility
- * of the QRX.
- *
- * Rather than defining an opaque interface, the URXE structure internals
- * are exposed. Since the demuxer is only exposed to other parts of the QUIC
- * implementation internals, this poses no problem, and has a number of
- * advantages:
- *
- * - Fields in the URXE can be allocated to support requirements in other
- * components, like the QRX, which would otherwise have to allocate extra
- * memory corresponding to each URXE.
- *
- * - Other components, like the QRX, can keep the URXE in queues of its own
- * when it is not being managed by the demuxer.
- *
- * URX Queue Structure
- * -------------------
- *
- * The URXE queue is maintained as a simple doubly-linked list. URXE entries are
- * moved between different lists in their lifecycle (for example, from a free
- * list to a pending list and vice versa). The buffer into which datagrams are
- * received immediately follows this URXE header structure and is part of the
- * same allocation.
- */
- /* Maximum number of packets we allow to exist in one datagram. */
- #define QUIC_MAX_PKT_PER_URXE (sizeof(uint64_t) * 8)
- struct quic_urxe_st {
- OSSL_LIST_MEMBER(urxe, QUIC_URXE);
- /*
- * The URXE data starts after this structure so we don't need a pointer.
- * data_len stores the current length (i.e., the length of the received
- * datagram) and alloc_len stores the allocation length. The URXE will be
- * reallocated if we need a larger allocation than is available, though this
- * should not be common as we will have a good idea of worst-case MTUs up
- * front.
- */
- size_t data_len, alloc_len;
- /*
- * Bitfields per packet. processed indicates the packet has been processed
- * and must not be processed again, hpr_removed indicates header protection
- * has already been removed. Used by QRX only; not used by the demuxer.
- */
- uint64_t processed, hpr_removed;
- /*
- * This monotonically increases with each datagram received. It is used for
- * diagnostic purposes only.
- */
- uint64_t datagram_id;
- /*
- * Address of peer we received the datagram from, and the local interface
- * address we received it on. If local address support is not enabled, local
- * is zeroed.
- */
- BIO_ADDR peer, local;
- /*
- * Time at which datagram was received (or ossl_time_zero()) if a now
- * function was not provided).
- */
- OSSL_TIME time;
- /*
- * Used by the QRX to mark whether a datagram has been deferred. Used by the
- * QRX only; not used by the demuxer.
- */
- char deferred;
- /*
- * Used by the DEMUX to track if a URXE has been handed out. Used primarily
- * for debugging purposes.
- */
- char demux_state;
- };
- /* Accessors for URXE buffer. */
- static ossl_unused ossl_inline unsigned char *
- ossl_quic_urxe_data(const QUIC_URXE *e)
- {
- return (unsigned char *)&e[1];
- }
- static ossl_unused ossl_inline unsigned char *
- ossl_quic_urxe_data_end(const QUIC_URXE *e)
- {
- return ossl_quic_urxe_data(e) + e->data_len;
- }
- /* List structure tracking a queue of URXEs. */
- DEFINE_LIST_OF(urxe, QUIC_URXE);
- typedef OSSL_LIST(urxe) QUIC_URXE_LIST;
- /*
- * List management helpers. These are used by the demuxer but can also be used
- * by users of the demuxer to manage URXEs.
- */
- void ossl_quic_urxe_remove(QUIC_URXE_LIST *l, QUIC_URXE *e);
- void ossl_quic_urxe_insert_head(QUIC_URXE_LIST *l, QUIC_URXE *e);
- void ossl_quic_urxe_insert_tail(QUIC_URXE_LIST *l, QUIC_URXE *e);
- /*
- * Called when a datagram is received for a given connection ID.
- *
- * e is a URXE containing the datagram payload. It is permissible for the callee
- * to mutate this buffer; once the demuxer calls this callback, it will never
- * read the buffer again.
- *
- * If a DCID was identified for the datagram, dcid is non-NULL; otherwise
- * it is NULL.
- *
- * The callee must arrange for ossl_quic_demux_release_urxe or
- * ossl_quic_demux_reinject_urxe to be called on the URXE at some point in the
- * future (this need not be before the callback returns).
- *
- * At the time the callback is made, the URXE will not be in any queue,
- * therefore the callee can use the prev and next fields as it wishes.
- */
- typedef void (ossl_quic_demux_cb_fn)(QUIC_URXE *e, void *arg,
- const QUIC_CONN_ID *dcid);
- /*
- * Creates a new demuxer. The given BIO is used to receive datagrams from the
- * network using BIO_recvmmsg. short_conn_id_len is the length of destination
- * connection IDs used in RX'd packets; it must have the same value for all
- * connections used on a socket. default_urxe_alloc_len is the buffer size to
- * receive datagrams into; it should be a value large enough to contain any
- * received datagram according to local MTUs, etc.
- *
- * now is an optional function used to determine the time a datagram was
- * received. now_arg is an opaque argument passed to the function. If now is
- * NULL, ossl_time_zero() is used as the datagram reception time.
- */
- QUIC_DEMUX *ossl_quic_demux_new(BIO *net_bio,
- size_t short_conn_id_len,
- OSSL_TIME (*now)(void *arg),
- void *now_arg);
- /*
- * Destroy a demuxer. All URXEs must have been released back to the demuxer
- * before calling this. No-op if demux is NULL.
- */
- void ossl_quic_demux_free(QUIC_DEMUX *demux);
- /*
- * Changes the BIO which the demuxer reads from. This also sets the MTU if the
- * BIO supports querying the MTU.
- */
- void ossl_quic_demux_set_bio(QUIC_DEMUX *demux, BIO *net_bio);
- /*
- * Changes the MTU in bytes we use to receive datagrams.
- */
- int ossl_quic_demux_set_mtu(QUIC_DEMUX *demux, unsigned int mtu);
- /*
- * Set the default packet handler. This is used for incoming packets which don't
- * match a registered DCID. This is only needed for servers. If a default packet
- * handler is not set, a packet which doesn't match a registered DCID is
- * silently dropped. A default packet handler may be unset by passing NULL.
- *
- * The handler is responsible for ensuring that ossl_quic_demux_reinject_urxe or
- * ossl_quic_demux_release_urxe is called on the passed packet at some point in
- * the future, which may or may not be before the handler returns.
- */
- void ossl_quic_demux_set_default_handler(QUIC_DEMUX *demux,
- ossl_quic_demux_cb_fn *cb,
- void *cb_arg);
- /*
- * Releases a URXE back to the demuxer. No reference must be made to the URXE or
- * its buffer after calling this function. The URXE must not be in any queue;
- * that is, its prev and next pointers must be NULL.
- */
- void ossl_quic_demux_release_urxe(QUIC_DEMUX *demux,
- QUIC_URXE *e);
- /*
- * Reinjects a URXE which was issued to a registered DCID callback or the
- * default packet handler callback back into the pending queue. This is useful
- * when a packet has been handled by the default packet handler callback such
- * that a DCID has now been registered and can be dispatched normally by DCID.
- * Once this has been called, the caller must not touch the URXE anymore and
- * must not also call ossl_quic_demux_release_urxe().
- *
- * The URXE is reinjected at the head of the queue, so it will be reprocessed
- * immediately.
- */
- void ossl_quic_demux_reinject_urxe(QUIC_DEMUX *demux,
- QUIC_URXE *e);
- /*
- * Process any unprocessed RX'd datagrams, by calling registered callbacks by
- * connection ID, reading more datagrams from the BIO if necessary.
- *
- * Returns one of the following values:
- *
- * QUIC_DEMUX_PUMP_RES_OK
- * At least one incoming datagram was processed.
- *
- * QUIC_DEMUX_PUMP_RES_TRANSIENT_FAIL
- * No more incoming datagrams are currently available.
- * Call again later.
- *
- * QUIC_DEMUX_PUMP_RES_PERMANENT_FAIL
- * Either the network read BIO has failed in a non-transient fashion, or
- * the QUIC implementation has encountered an internal state, assertion
- * or allocation error. The caller should tear down the connection
- * similarly to in the case of a protocol violation.
- *
- */
- #define QUIC_DEMUX_PUMP_RES_OK 1
- #define QUIC_DEMUX_PUMP_RES_TRANSIENT_FAIL (-1)
- #define QUIC_DEMUX_PUMP_RES_PERMANENT_FAIL (-2)
- int ossl_quic_demux_pump(QUIC_DEMUX *demux);
- /*
- * Artificially inject a packet into the demuxer for testing purposes. The
- * buffer must not exceed the URXE size being used by the demuxer.
- *
- * If peer or local are NULL, their respective fields are zeroed in the injected
- * URXE.
- *
- * Returns 1 on success or 0 on failure.
- */
- int ossl_quic_demux_inject(QUIC_DEMUX *demux,
- const unsigned char *buf,
- size_t buf_len,
- const BIO_ADDR *peer,
- const BIO_ADDR *local);
- /*
- * Returns 1 if there are any pending URXEs.
- */
- int ossl_quic_demux_has_pending(const QUIC_DEMUX *demux);
- # endif
- #endif
|