IETF Logo Mail Archive

Re: Request for Authenticated but not Encrypted Traffic

Lucas Pardue <lucaspardue.24.7@gmail.com> Mon, 03 October 2022 17:19 UTC

Return-Path: <lucaspardue.24.7@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55BC0C1522B6 for <quic@ietfa.amsl.com>; Mon, 3 Oct 2022 10:19:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.855
X-Spam-Level:
X-Spam-Status: No, score=-1.855 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 jZzUmsCYCozN for <quic@ietfa.amsl.com>; Mon, 3 Oct 2022 10:19:32 -0700 (PDT)
Received: from mail-oa1-x2c.google.com (mail-oa1-x2c.google.com [IPv6:2001:4860:4864:20::2c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 DEABDC14CF0A for <quic@ietf.org>; Mon, 3 Oct 2022 10:19:32 -0700 (PDT)
Received: by mail-oa1-x2c.google.com with SMTP id 586e51a60fabf-1322fa1cf6fso6452395fac.6 for <quic@ietf.org>; Mon, 03 Oct 2022 10:19:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=9x2zbHFnUvhZZTXXD+wmQbR2qVqLI01qVeVY2HFqOjA=; b=dgsPjPsJ1zHsdwpAjuWQIKpM/4WLHrQce7c48nzrXHix5ll2ULgNu4R6Ew/eXWff/h iVXew7G77MmJAnwKEk9CizJKoiKFy9O2Cbc1mjIlKeBHFrzzoUH8BLJzS/ejkfJpr9hR s0LHDwFXvOVHj/9vUNGKSxtZN2PJa6JEvCMeMJ7IGGmPdaqbWkvm0Hf1sOXnZGMLfyd0 tKlbks2pZTacNlLcvVd1sS3CC6iiBkHVV2334fmeyt6NqJ3m29HBSnaQX4FxtA7GycEh 8yYykx6xBP+Rbgvv1y3CcSyo/HVIB064Ld+oH9KxXnPmPh4fY/oSrxsPyPZKVFDt6drF 4c8g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=9x2zbHFnUvhZZTXXD+wmQbR2qVqLI01qVeVY2HFqOjA=; b=4ChaaIOSsLBW56RFHPxy3U3TzT+pmg1YQdsMQGJ4qoXmfJTJBJJSWS1DGjVxWjAXWn o8x9n2jyQDkfvqlMcfZnw1dsa90K2jZIxPujvJnRaQmvi/LI3aAxjZvIshyklsc862Tz p9coEeqvtdQ42Uw/84ds0shgdp9PpJR07ZV8Mp/KE3KfvlYzdMokDyrm1/yentJY6sVP fAKA9IjocMJG8/oBpnek8DvKUD21Kl658dgzwtDHJSb0V4wMNlkh+Vi8cXg9mebuTuek MGtqy5nH6yseuZmx6bpNAUnokxO4Ilfgj6WNPhEHAXuPrzpW1ZJIbzq2NPj/lLUipEXh y0wQ==
X-Gm-Message-State: ACrzQf2zU6sML7r+xe8sUBnWsoo97PwzUtkpDdAn045NGbpIvfgMBAsT QIknTPYYSJbkyCQRQTg5BBT2d5jV6rW/C2z5F78=
X-Google-Smtp-Source: AMsMyM5hT3r/hRjemflSYEMGOQPQQNpwqRWtmzBnYR1l8hN98XUME28MEcYKYk7mClUgMIbL1LPQiFsNcb6XEwGbyJ0=
X-Received: by 2002:a05:6871:60a:b0:132:4e9f:d5fc with SMTP id w10-20020a056871060a00b001324e9fd5fcmr4189901oan.150.1664817572207; Mon, 03 Oct 2022 10:19:32 -0700 (PDT)
MIME-Version: 1.0
References: <CAMm+Lwgo5i=FD9sMcp+o_N-e5MprDDCDobzjh-FpwGKhiH99iQ@mail.gmail.com> <3C9CC208-E4E1-4F9F-B10A-6ACF485A0CEF@huitema.net> <CAMm+LwhVM+7Db6ZPLuE5A5VLYqocvZWr=hfKcN=HgYhrdLrgTQ@mail.gmail.com> <dbf9c81b-38f5-2767-1a1b-3309077764aa@huitema.net> <CAC8QAcdfiHvir=jbzegVAi1vqYHiucX4w4J=+vOaiDm14sjDOA@mail.gmail.com>
In-Reply-To: <CAC8QAcdfiHvir=jbzegVAi1vqYHiucX4w4J=+vOaiDm14sjDOA@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Mon, 03 Oct 2022 18:19:20 +0100
Message-ID: <CALGR9oa_gGx=kdgFcoG+7MXW4km8vs60_sUW=6on82AfPsnAqw@mail.gmail.com>
Subject: Re: Request for Authenticated but not Encrypted Traffic
To: sarikaya@ieee.org
Cc: Christian Huitema <huitema@huitema.net>, Phillip Hallam-Baker <phill@hallambaker.com>, Matt Joras <matt.joras@gmail.com>, "Randy Armstrong (OPC)" <randy.armstrong@opcfoundation.org>, quic@ietf.org
Content-Type: multipart/alternative; boundary="00000000000001e11405ea248c08"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/3O_9-mrgQ1eb9dhiME7EDCBiHbo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Oct 2022 17:19:37 -0000

Hi Behcet,


On Mon, Oct 3, 2022 at 5:56 PM Behcet Sarikaya <sarikaya2012@gmail.com>
wrote:

> Hi Christian,
>
> I quickly glanced through RFC 9250 which defines DoQ and references ALPN
> in RFC 7301.
> Agree with Philip that DoQ does not define something that is independent
> of HTTP.
>
> Will it come one day, we don't know?
> Behcet
>

DoQ is an application mapping over QUIC. ALPN is an extension to TLS. DoQ
might use a transactional model that maps to bidirectional streams but that
is the full extent of similarities to HTTP; there is no normative
dependency.

RFC 9000 was written carefully to describe the interface that
application-data-bearing streams can provide to applications. This is not
related to HTTP, QUIC is independent of HTTP. Indeed, QUIC on its own means
pretty much nothing. It needs an application mapping protocol. The
recently-published applicability draft, RFC 9308 [1], is specifically
written to aid designers or implementers of such mappings. Randy might find
RFC 9308 informative if wishing to pursue QUIC as a transport substrate for
the OT application layer traffic.

Cheers
Lucas

[1] - https://www.rfc-editor.org/rfc/rfc9308.html

v2.23.0 | Report a Bug | By Email