[Masque] RFC 9484 on Proxying IP in HTTP

rfc-editor@rfc-editor.org Thu, 19 October 2023 20:13 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: masque@ietfa.amsl.com
Delivered-To: masque@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A366FC151548; Thu, 19 Oct 2023 13:13:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.467
X-Spam-Level:
X-Spam-Status: No, score=-4.467 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 1c-eh_KqptmQ; Thu, 19 Oct 2023 13:13: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 66BCEC151535; Thu, 19 Oct 2023 13:13:13 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 523AB195423A; Thu, 19 Oct 2023 13:13: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, masque@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20231019201313.523AB195423A@rfcpa.amsl.com>
Date: Thu, 19 Oct 2023 13:13:13 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/masque/AvRZyOQLEdRBH-r6pMFRfueYtm4>
Subject: [Masque] RFC 9484 on Proxying IP in HTTP
X-BeenThere: masque@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Multiplexed Application Substrate over QUIC Encryption <masque.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/masque>, <mailto:masque-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/masque/>
List-Post: <mailto:masque@ietf.org>
List-Help: <mailto:masque-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/masque>, <mailto:masque-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Oct 2023 20:13:17 -0000

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

        
        RFC 9484

        Title:      Proxying IP in HTTP 
        Author:     T. Pauly, Ed.,
                    D. Schinazi,
                    A. Chernyakhovsky,
                    M. Kühlewind,
                    M. Westerlund
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2023
        Mailbox:    tpauly@apple.com,
                    dschinazi.ietf@gmail.com,
                    achernya@google.com,
                    mirja.kuehlewind@ericsson.com,
                    magnus.westerlund@ericsson.com
        Pages:      37
        Updates:    RFC 9298

        I-D Tag:    draft-ietf-masque-connect-ip-13.txt

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

        DOI:        10.17487/RFC9484

This document describes how to proxy IP packets in HTTP. This
protocol is similar to UDP proxying in HTTP but allows transmitting
arbitrary IP packets. More specifically, this document defines a
protocol that allows an HTTP client to create an IP tunnel through an
HTTP server that acts as an IP proxy. This document updates RFC 9298.

This document is a product of the Multiplexed Application Substrate over QUIC Encryption 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