IETF Logo Mail Archive

Re: [Ohttp] John Scudder's No Objection on charter-ietf-ohttp-00-00: (with COMMENT)

Vittorio Bertola <vittorio.bertola@open-xchange.com> Fri, 18 June 2021 08:19 UTC

Return-Path: <vittorio.bertola@open-xchange.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 468213A41E2 for <ohttp@ietfa.amsl.com>; Fri, 18 Jun 2021 01:19:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_DNSWL_BLOCKED=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=open-xchange.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 0eKyyUkQTJDo for <ohttp@ietfa.amsl.com>; Fri, 18 Jun 2021 01:19:42 -0700 (PDT)
Received: from mx4.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5849E3A41E0 for <ohttp@ietf.org>; Fri, 18 Jun 2021 01:19:42 -0700 (PDT)
Received: from imap.open-xchange.com (imap.open-xchange.com [10.20.28.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx4.open-xchange.com (Postfix) with ESMTPSA id 5CE176A0E4; Fri, 18 Jun 2021 10:19:39 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1624004379; bh=A85C+rpDOgLdlYd65/XjQqW7l9SSYgMB2TLMXGsT8fg=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=Y0gh9BZ5/xIY7yyjuK6b/NUbYmyXBYoN+FlNSahAN73Ax824zBbLOaTDsKSlMfiPU zUZVnGx/PeK5U87oQ+vhVYYcoe+KZSUybo+CuJ5Gy/UBfk8ZieqSn/Ao9gKrLd1BXl 8x5Hn0LNtZ1QOuYT31/BsUZ06p+LdIMRqhlT6XKNnJvuotyL5b3k+nnWYocleoAFg0 LrPTtgW64ZmPuWwpVVpAsIZ9w8A1S9tjjklQKNOyZOrqlkcvsBSlEHnJFWLAS1tkMo BBHlDpfncleAoTs0Rs8BtvWS/AEN7rCf7KYufRRkNBrpoVWoUkBV2ahsbxolccf0+h w2HN/0uCXwzmA==
Received: from appsuite-gw2.open-xchange.com ([10.20.28.82]) by imap.open-xchange.com with ESMTPSA id 7s2UFhtXzGBjFAAA3c6Kzw (envelope-from <vittorio.bertola@open-xchange.com>); Fri, 18 Jun 2021 10:19:39 +0200
Date: Fri, 18 Jun 2021 10:19:39 +0200
From: Vittorio Bertola <vittorio.bertola@open-xchange.com>
To: John Scudder <jgs@juniper.net>
Cc: ohttp@ietf.org
Message-ID: <942003890.31616.1624004379293@appsuite-gw2.open-xchange.com>
In-Reply-To: <162393874371.32588.547882093119823322@ietfa.amsl.com>
References: <162393874371.32588.547882093119823322@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.5-Rev14
X-Originating-Client: open-xchange-appsuite
Autocrypt: addr=vittorio.bertola@open-xchange.com; prefer-encrypt=mutual; keydata= mQENBFhFR+UBCACfoywFKBRfzasiiR9/6dwY36eLePXcdScumDMR8qoXvRS55QYDjp5bs+yMq41qWV9 xp/cqryY9jnvHbeF3TsE5yEazpD1dleRbkpElUBpPwXqkrSP8uXO9KkS9KoX6gdml6M4L+F82WpqYC1 uTzOE6HPmhmQ4cGSgoia2jolxAhRpzoYN99/BwpvoZeTSLP5K6yPlMPYkMev/uZlAkMMhelli9IN6yA yxcC0AeHSnOAcNKUr13yXyMlTyi1cdMJ4sk88zIbefxwg3PAtYjkz3wgvP96cNVwAgSt4+j/ZuVaENP pgVuM512m051j9SlspWDHtzrci5pBKKFsibnTelrABEBAAG0NUJlcnRvbGEsIFZpdHRvcmlvIDx2aXR 0b3Jpby5iZXJ0b2xhQG9wZW4teGNoYW5nZS5jb20+iQFABBMBAgAqBAsJCAcGFQoJCAsCBRYCAwEAAp 4BAhsDBYkSzAMABQMAAAAABYJYRUflAAoJEIU2cHmzj8qNaG0H/ROY+suCP86hoN+9RIV66Ej8b3sb8 UgwFJOJMupZfeb9yTIJwE4VQT5lTt146CcJJ5jvxD6FZn1Htw9y4/45pPAF7xLE066jg3OqRvzeWRZ3 IDUfJJIiM5YGk1xWxDqppSwhnKcMOuI72iioWxX0nGQrWxpnWJsjt08IEEwuYucDkul1PHsrLJbTd58 fiMKLVwag+IE1SPHOwkPF6arZQZIfB5ThtOZV+36Jn8Hok9XfeXWBVyPkiWCQYVX39QsIbr0JNR9kQy 4g2ZFexOcTe8Jo12jPRL7V8OqStdDes3cje9lWFLnX05nrfLuE0l0JKWEg8akN+McFXc+oV68h7nu5A Q0EWEVH5QEIAIDKanNBe1uRfk8AjLirflZO291VNkOAeUu+dIhecGnZeQW6htlDinlYOnXhtsY1mK9W PUu+xshDq7lXn2G0LxldYwyJYZaJtDgIKqVqwxfA34Lj27oqPuXwcvGhdCgt0SW/YcalRdAi0/AzUCu 5GSaj2kaGUSnBYYUP4szGJXjaK2psP5toQSCtx2pfSXQ6MaqPK9Zzy+D5xc6VWQRp/iRImodAcPf8fg JJvRyJ8Jla3lKWyvBBzJDg6MOf6Fts78bJSt23X0uPp93g7GgbYkuRMnFI4RGoTVkxjD/HBEJ0CNg22 hoHJondhmKnZVrHEluFuSnW0wBEIYomcPSPB+cAEQEAAYkBMQQYAQIAGwUCWEVH5QIbDAQLCQgHBhUK CQgLAgUJEswDAAAKCRCFNnB5s4/KjdO8B/wNpvWtOpLdotR/Xh4fu08Fd63nnNfbIGIETWsVi0Sbr8i E5duuGaaWIcMmUvgKe/BM0Fpj9X01Zjm90uoPrlVVuQWrf+vFlbalUYVZr51gl5UyUFHk+iAZCAA0WB rsmACKvuV1P7GuiX3UV9b59T9taYJxN3dNFuftrEuvsqHimFtlekUjUwoCekTJdncFusBhwz2OrKhHr WWrEsXkfh0+pURWYAlKlTxvXuI7gAfHEQM+6OnrWvXYtlhd0M1sBPnCjbyG63Qws7Rek9bEWKtH6dA6 dmT2FQT+g1S9Mdf0WkPTQNX0x24dm8IoHuD3KYwX7Svx43Xa17aZnXqUjtj1
Archived-At: <https://mailarchive.ietf.org/arch/msg/ohttp/pWX3_u1Thqq0oW1ubWe_yaFuPzk>
Subject: Re: [Ohttp] John Scudder's No Objection on charter-ietf-ohttp-00-00: (with COMMENT)
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: Fri, 18 Jun 2021 08:19:47 -0000


> Il 17/06/2021 16:05 John Scudder via Datatracker <noreply@ietf.org> ha scritto:
> 
> Regarding Robert’s points, I had naïvely read the charter as being clearly for
> "generic oblivious HTTP mechanism to hide clients from servers”, but after
> looking at §3.1 (“applicability”) of draft-thomson-http-oblivious-01, I see his
> point: it does seem as though the author views OHTTP as being a niche, not a
> general, solution. The intended applicability of the work seems worth, at
> minimum, making more explicit in the charter, and again seems like it supports
> the idea of having a BOF where it can be discussed.

I have a general, possibly naive question. Does a niche applicability statement really exempt us from a discussion on how the new mechanism, once standardized, could be used outside of that niche and how it would then impact the Internet in general?

-- 
Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
vittorio.bertola@open-xchange.com 
Office @ Via Treviso 12, 10144 Torino, Italy

v2.23.0 | Report a Bug | By Email