[AVTCORE] RFC 9443 on Multiplexing Scheme Updates for QUIC

rfc-editor@rfc-editor.org Wed, 12 July 2023 18:09 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26770C14F748; Wed, 12 Jul 2023 11:09:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.855
X-Spam-Level:
X-Spam-Status: No, score=-0.855 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BX972olHc1Mb; Wed, 12 Jul 2023 11:09:13 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D4C5C151060; Wed, 12 Jul 2023 11:09:13 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 5AD3685295; Wed, 12 Jul 2023 11:09:13 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, avt@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230712180913.5AD3685295@rfcpa.amsl.com>
Date: Wed, 12 Jul 2023 11:09:13 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/6q6nqT_92s3xjDQd7TdaeTEB_to>
Subject: [AVTCORE] RFC 9443 on Multiplexing Scheme Updates for QUIC
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2023 18:09:17 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9443

        Title:      Multiplexing Scheme Updates for QUIC 
        Author:     B. Aboba,
                    G. Salgueiro,
                    C. Perkins
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2023
        Mailbox:    bernard.aboba@gmail.com,
                    gsalguei@cisco.com,
                    csp@csperkins.org
        Pages:      8
        Updates:    RFC 5764, RFC 7983

        I-D Tag:    draft-ietf-avtcore-rfc7983bis-09.txt

        URL:        https://www.rfc-editor.org/info/rfc9443

        DOI:        10.17487/RFC9443

RFC 7983 defines a scheme for a Real-time Transport Protocol (RTP)
receiver to demultiplex Datagram Transport Layer Security (DTLS),
Session Traversal Utilities for NAT (STUN), Secure Real-time
Transport Protocol (SRTP) / Secure Real-time Transport Control
Protocol (SRTCP), ZRTP, and Traversal Using Relays around NAT (TURN)
channel packets arriving on a single port.  This document updates RFC
7983 and RFC 5764 to also allow QUIC packets to be multiplexed on a
single receiving socket.

This document is a product of the Audio/Video Transport Core Maintenance Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC