IETF Logo Mail Archive

Re: [Ohttp] Discovery (no)

Thomas Mangin <thomas.mangin@exa.net.uk> Mon, 26 July 2021 17:02 UTC

Return-Path: <thomas.mangin@exa.net.uk>
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 E736A3A0D1C for <ohttp@ietfa.amsl.com>; Mon, 26 Jul 2021 10:02:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=exa-net-uk.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 TN2kpPBAlcHG for <ohttp@ietfa.amsl.com>; Mon, 26 Jul 2021 10:02:38 -0700 (PDT)
Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (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 7BF2D3A1D6E for <ohttp@ietf.org>; Mon, 26 Jul 2021 10:02:38 -0700 (PDT)
Received: by mail-lj1-x231.google.com with SMTP id l4so12127080ljq.4 for <ohttp@ietf.org>; Mon, 26 Jul 2021 10:02:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=exa-net-uk.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tVbipPgrYMBGn/KYlp2qbudKeaQ0iyVXBnuTzv5lbD4=; b=N5PQKz9ZqTWhjTSIIpYVLQKUTpEs8uz+OqVMQufXYU2hjXxh1KXy3BrPZp42FzstuR Ed4JgkqZuC1BKzq9RwqFhtPXj8o1ddntx1Kz55meDTDo0M6FJArUia3kH2QeV5Dv5vN3 7z0VaqA9rT9X+q2EOQD+QR6wBDcQjRdcRJihCpU2tf1Hl2cGRvhdXqfhXROg59Rg8Wzo 8ykmAVscJ1++EEaydyu+TWtNt3RZhG/d0F6WD/LTVXBVpLblL/HL65qlTzUXe5S+CqxH 5y7DMSqNnCP9u9WLmIALF0EW/hw1TNR1tTgeMP9oBK+uFRIJ0N1wIi55zlSF2dpi5E6E PFTg==
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=tVbipPgrYMBGn/KYlp2qbudKeaQ0iyVXBnuTzv5lbD4=; b=ikKmtI6up7P3BFJKgJOaaS6+5aOOPVOdTyyuHykDTHfh0J8hPFR5Z46UCxu3OAV8KL 9tGy5wruThbYq6+82oysx0nZkbODm6LZ9b6wJb2b5/miEyT99fp7E3ChCH87EuHchxks 74XxVKngcFh+J8ME0uDYSDiG4xpX1B0+Vp3NJVXCrHkAbq9cIdxnqz1Qw3CCxoRhQYLI BzaqCFN4mDdXm4pPhgLPXVnaFEsF4c64HgEyA5pU5KfFagRWDV/ANyAwZt84plmplnWg GLTV7zQcQBXxXpA0RqfXUItdyl0sNTDHpylvUl5oAscW6R/OnLUVwpDVLFwdP+Vewzsc W/0w==
X-Gm-Message-State: AOAM531E2sWflCNNe8mWFzNmfX7PIqy889IkIV3ieDGezq3XKcHphDZd oHjbTmXiPFYvfPzJU9WNHERyCIbWrkKCeD7R9kqcuG9slpvfUg==
X-Google-Smtp-Source: ABdhPJzrmQcQGC86gUkohuR4DAdfijYoZNNRwuWobzWMZ3QsuA2lFIkZNRLmE0adg6EDN5a/BsqDTZOg3xpgFtL7oFI=
X-Received: by 2002:a2e:a22c:: with SMTP id i12mr12903265ljm.267.1627318955446; Mon, 26 Jul 2021 10:02:35 -0700 (PDT)
MIME-Version: 1.0
References: <CAEm8Q12LUx42gYODFVBpLUd0UbwfAvfScDC5Wnm+jsmaB6osQQ@mail.gmail.com> <3cb3ea05-57d8-4db2-9bdb-78cf8d8cf4c5@www.fastmail.com>
In-Reply-To: <3cb3ea05-57d8-4db2-9bdb-78cf8d8cf4c5@www.fastmail.com>
From: Thomas Mangin <thomas.mangin@exa.net.uk>
Date: Mon, 26 Jul 2021 18:02:24 +0100
Message-ID: <CAEm8Q12MegnasLOOEcCVLkZ_gW9E2JXx9hoWF1hFm+4dcwfXyw@mail.gmail.com>
To: caw@heapingbits.net
Cc: ohttp@ietf.org
Content-Type: multipart/alternative; boundary="00000000000046aa5705c809b856"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ohttp/-whwoAtotz-z-YjMLW26E1VUfIA>
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 17:02:44 -0000

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.

Thomas

On Mon, 26 Jul 2021 at 16:05, Christopher Wood <caw@heapingbits.net> wrote:

> On Mon, Jul 26, 2021, at 7:21 AM, Thomas Mangin wrote:
> > Hello, I just found this mailing list/group and I am curious.
> >
> > Mark makes a good point but it is possible to implement a HTTP proxy
> > using the HTTP specification, and the specification is for a protocol
> > which can work without proxy.
> >
> > I am unclear on what this group intend to standardise if part of the
> > protocol is left undocumented: it will prevent interoperability and may
> > lead to multiple incompatible different key discovery mechanism and
> > therefore non-interroperable implementations.
>
> Can you elaborate on what OHTTP interoperability problems arise if two
> different discovery mechanisms are used?
>
> Best,
> Chris
>
> --
> Ohttp mailing list
> Ohttp@ietf.org
> https://www.ietf.org/mailman/listinfo/ohttp
>

v2.23.0 | Report a Bug | By Email