New Non-WG Mailing List: masque
IETF Secretariat <ietf-secretariat@ietf.org> Mon, 22 April 2019 14:28 UTC
Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1033F12001B; Mon, 22 Apr 2019 07:28:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: New Non-WG Mailing List: masque
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <155594332902.21194.12701430310750645026.idtracker@ietfa.amsl.com>
Date: Mon, 22 Apr 2019 07:28:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/8ty7zDB2x2Btzev-fXX3ath39nA>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2019 14:28:49 -0000
A new IETF non-working group email list has been created. List address: masque@ietf.org Archive: https://mailarchive.ietf.org/arch/browse/masque/ To subscribe: https://www.ietf.org/mailman/listinfo/masque Purpose: MASQUE (Multiplexed Application Substrate over QUIC Encryption) is a mechanism that allows co-locating and obfuscating networking applications behind an HTTPS web server. The currently prevalent use-case is to allow running a VPN server that is indistinguishable from an HTTPS server to any unauthenticated observer. We do not expect major providers and CDNs to deploy this behind their main TLS certificate, as they are not willing to take the risk of getting blocked (given previous experiences when domain fronting was blocked). An expected use would be for individuals to enable this behind their personal websites via easy-to-configure open-source software. This list belong IETF area: SEC For additional information, please contact the list administrators.
- New Non-WG Mailing List: masque IETF Secretariat