Original text:
its first cryptographic handshake message, which for TLS is the ClientHello.  Servers might need to parse the entire ClientHello (e.g., to access extensions such as Server Name Identification (SNI) <del> or Application Layer Protocol Negotiation (ALPN)) in order to decide </del>  whether to accept the new incoming QUIC connection.  If the ClientHello spans multiple Initial packets, such servers would need to buffer the first received fragments, which could consume excessive Endpoints use transport parameters to authenticate the negotiation of connection IDs during the handshake; see cid-auth. <del> Application Layer Protocol Negotiation (ALPN; see ALPN) allows </del>  clients to offer multiple application protocols during connection establishment.  The transport parameters that a client includes during the handshake apply to all application protocols that the validation of the server certificate as described above), and sending an HTTP/3 request message targeting the URI to the server over that secured connection.  Unless some other mechanism is used to select <del> HTTP/3, the token "h3" is used in the Application Layer Protocol </del>  Negotiation (ALPN; see RFC7301) extension during the TLS handshake. Connectivity problems (e.g., blocking UDP) can result in QUIC 11.1. This document creates a new registration for the identification of <del> HTTP/3 in the "Application Layer Protocol Negotiation (ALPN) Protocol </del>  IDs" registry established in RFC7301. The "h3" string identifies HTTP/3:

Reviewer comments:
as well as other instances of the term. RFC 7301 does indeed hyphenate (and that's correct, since "application-layer" is being used as a single unit to describe "protocol").
URL says the registry is

Revised text:
its first cryptographic handshake message, which for TLS is the ClientHello.  Servers might need to parse the entire ClientHello (e.g., to access extensions such as Server Name Identification (SNI)  <ins> or Application-Layer Protocol Negotiation (ALPN)) in order to decide </ins> whether to accept the new incoming QUIC connection.  If the ClientHello spans multiple Initial packets, such servers would need to buffer the first received fragments, which could consume excessive Endpoints use transport parameters to authenticate the negotiation of connection IDs during the handshake; see cid-auth.  <ins> Application-Layer Protocol Negotiation (ALPN; see ALPN) allows </ins> clients to offer multiple application protocols during connection establishment.  The transport parameters that a client includes during the handshake apply to all application protocols that the validation of the server certificate as described above), and sending an HTTP/3 request message targeting the URI to the server over that secured connection.  Unless some other mechanism is used to select  <ins> HTTP/3, the token "h3" is used in the Application-Layer Protocol </ins> Negotiation (ALPN; see RFC7301) extension during the TLS handshake. Connectivity problems (e.g., blocking UDP) can result in QUIC 11.1. This document creates a new registration for the identification of  <ins> HTTP/3 in the "Application-Layer Protocol Negotiation (ALPN) Protocol </ins> IDs" registry established in RFC7301. The "h3" string identifies HTTP/3: