IETF Logo Mail Archive

Re: [Ohttp] Discovery (no)

Eric Rescorla <ekr@rtfm.com> Mon, 26 July 2021 19:38 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: ohttp@ietfa.amsl.com
Delivered-To: ohttp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FE3C3A09AC for <ohttp@ietfa.amsl.com>; Mon, 26 Jul 2021 12:38:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g7ljIW22SIkX for <ohttp@ietfa.amsl.com>; Mon, 26 Jul 2021 12:38:06 -0700 (PDT)
Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A9473A0A26 for <ohttp@ietf.org>; Mon, 26 Jul 2021 12:38:01 -0700 (PDT)
Received: by mail-io1-xd2e.google.com with SMTP id h1so13306092iol.9 for <ohttp@ietf.org>; Mon, 26 Jul 2021 12:38:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=CVsHKJq3yO7gcRSoUoC9IGJ5n3el25qakvmHJv2l+hI=; b=lbqMciNpPjg+tp/yLo1Ke+oYbGjhi7eQ1Ocz/yR75sN/xJLCxSf53dEaeMIwyC/1so /L7JioFsIgAUXKxC+dwgQKiLW+fT2c61OtdlV/obkaneClZ7SZyCmnqHEgigDmuhbiJ2 YY3mJ0pQXIA37LLpDmIbz0USP+R0BKu/UVAH79kTkaMs36L1zR+holhNh4VRq+j2uShd 4gtuOdxc5feOBtqQxOvgbqjExO6/RH//84/BuJM97NxR7tnTGIoApgydv+83UdAHC80s C/5iK4KgbQ8g3Lqnt7sxWvtQaDsjobAEZ1hb+7z6MvOSh8jxT78Xls0EEYn0KozS1w6J ILjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=CVsHKJq3yO7gcRSoUoC9IGJ5n3el25qakvmHJv2l+hI=; b=S05c6tozOCFHE2/7WMJpP2NQMm+0RdduwezyxxuTJJqrAngOKd+l15Jkvyu32xRjj7 zHwh+m7Ifq5sS0tVgWEBYrWbs0NSyyFW1gYtWJEUWVD7XtgY58Pk/zscVnwZkkmVmutO Fi6pCNUoOKur/7aRd3aCgcIehPtL0PuK++XBE3sz00rhDlqx1XRVXRt3RFWQS7s6xJIR j08u0shGzx6fXudiv8KCC0U04DOAE8tlo/ebBCOvEbGk9aMkvBf6yS8vihenetc8ZtE0 ZPKOpkjcuBMEHFyRzkDqAzIQ4Ezx5hrBIC0Zap0ebHnAdAUXAJ3ElnvrGg4k/sMl2Ms4 2D6Q==
X-Gm-Message-State: AOAM531CcVtWVvMXTgHG7AqaXeR4k/1suJkWJS/GKe2K0KGxXkVRdaCf SjIKEbNNoExCa0070z/8MDDlD9ocYq+ni+VuAaDC3cumhA2SKA==
X-Google-Smtp-Source: ABdhPJy2CAYqrwwJZsRmBYjvrSt44lLBRVOa2G8PDhk9d9uMU8IH2zAPnqrasiBt+hiyXuKDXXKLn1xmJUzRnH0K0bc=
X-Received: by 2002:a05:6638:338f:: with SMTP id h15mr17920410jav.135.1627328279558; Mon, 26 Jul 2021 12:37:59 -0700 (PDT)
MIME-Version: 1.0
References: <CAEm8Q12LUx42gYODFVBpLUd0UbwfAvfScDC5Wnm+jsmaB6osQQ@mail.gmail.com> <3cb3ea05-57d8-4db2-9bdb-78cf8d8cf4c5@www.fastmail.com> <CAEm8Q12MegnasLOOEcCVLkZ_gW9E2JXx9hoWF1hFm+4dcwfXyw@mail.gmail.com> <CABcZeBMMh6rOymV9QB7sgCB33PD91im94nNR1h2gBo7fmEriRQ@mail.gmail.com> <CAEm8Q10PnoCEzUZb4mh7XBkz4T4ZeVoeyR_jx7u2VdG9SpUYLg@mail.gmail.com>
In-Reply-To: <CAEm8Q10PnoCEzUZb4mh7XBkz4T4ZeVoeyR_jx7u2VdG9SpUYLg@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 26 Jul 2021 12:37:23 -0700
Message-ID: <CABcZeBN_NZHXTBfRc9tGKArx71_xXogVHC0Any+0Vs9C626iYQ@mail.gmail.com>
To: Thomas Mangin <thomas.mangin@exa.net.uk>
Cc: Christopher Wood <caw@heapingbits.net>, ohttp@ietf.org
Content-Type: multipart/alternative; boundary="00000000000009553205c80be4ac"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ohttp/hIvfjj-e8eadOlY1vgdYThkHnjc>
Subject: Re: [Ohttp] Discovery (no)
X-BeenThere: ohttp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Oblivious HTTP <ohttp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ohttp>, <mailto:ohttp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ohttp/>
List-Post: <mailto:ohttp@ietf.org>
List-Help: <mailto:ohttp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ohttp>, <mailto:ohttp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2021 19:38:12 -0000

On Mon, Jul 26, 2021 at 12:34 PM Thomas Mangin <thomas.mangin@exa.net.uk>
wrote:

> On Mon, Jul 26, 2021 at 10:02 AM Thomas Mangin <thomas.mangin@exa.net.uk>
>> wrote:
>>
>>> Good point, please excuse my bad wording, there can no be
>>> interoperability, as there is no way for someone to implement a working
>>> end-to-end connection based on the RFC and check it against another
>>> implementation. It is enough to implement the defined components but not a
>>> full solution.
>>>
>>
>> I don't believe that this is correct.
>>
>> The basic insight here is that in most of the cases of interest there is
>> *already* a relationship between the client and the origin server and that
>> relationship is already worked out of band in some way. So that piece does
>> not need interop.
>>
>
> Thank you Eric,
>
> I feel we will have to agree to disagree: if developers can not create two
> interoperable implementations from a draft/RFC alone, this is not a
> complete document.
>

They *can* create an interoperable implementation. The entities that
interoperate are (a) the client/origin-server and (b) the proxy. It's just
that the client/origin server are in two pieces. But that's no more a
problem than that in order to do QUIC you need a QUIC stack and a UDP stack
but there's not really a standardized interface that goes between them.

-Ekr

v2.23.0 | Report a Bug | By Email