Re: I-D for a YANG data model to configure HTTP clients and servers

Ben Schwartz <bemasc@google.com> Wed, 20 May 2020 01:37 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D63D83A0896 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 19 May 2020 18:37:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level:
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 YPsBUVUYDpnZ for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 19 May 2020 18:37:14 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (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 2D1393A087D for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 19 May 2020 18:37:13 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1jbDcR-00024U-Dy for ietf-http-wg-dist@listhub.w3.org; Wed, 20 May 2020 01:34:03 +0000
Resent-Date: Wed, 20 May 2020 01:34:03 +0000
Resent-Message-Id: <E1jbDcR-00024U-Dy@lyra.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <bemasc@google.com>) id 1jbDcQ-00023i-Be for ietf-http-wg@listhub.w3.org; Wed, 20 May 2020 01:34:02 +0000
Received: from mail-wr1-x42b.google.com ([2a00:1450:4864:20::42b]) by mimas.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <bemasc@google.com>) id 1jbDcO-0001O3-Bk for ietf-http-wg@w3.org; Wed, 20 May 2020 01:34:02 +0000
Received: by mail-wr1-x42b.google.com with SMTP id l11so1472730wru.0 for <ietf-http-wg@w3.org>; Tue, 19 May 2020 18:33:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Vv4dzTRxM6avWcZ+ziBKV3qGwf2/8xSskSpBJXdBgBE=; b=oNa9EvCjSto26hWppKkaCeW0pa2xjlZaaczVtmbrui2CQJcCvq8A+mnwB8iXyK5KvV 1NtgNGQdx3parwzuGBlD6cTUDz/6VTcC0J7Q/Jmvxf1pyIkdoWaEscfJIv7sBnWb0MbZ OFcD5Pi4EwS7jmwSSymyqcJDzx4Z/xEkUdDPaAwdHPIzd+0hsu04d/8bjjPOrG+eqW1K jE4hPfm5mqXNvbWEfkfJMCZ3YKD/HdmicIMFf01dLuJ7RR6fJszzasBr77ugA/mlBBM0 Vf2CREuB6Kn8DNoHxxdBEaHl4KluGjZuQ+myJ8ftnin5m7qZHVBR5IuT2VDW7BzW0w0A SQQA==
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=Vv4dzTRxM6avWcZ+ziBKV3qGwf2/8xSskSpBJXdBgBE=; b=mVpTjC6+ANL8UX21LDRAf2k9fe0J+RbamlhkSmCy/V1xi4Cs+z7S9bpEzItKFLQ0ov kFKM3SWkcUThyQyEYhq2M7CXfgZrPEiOglnRIc8CDkpLYw09jLNWk4zJNQiYvS4VMPUB Ap0VHaO6DhWHsSCYNjUyceB4zFBPuWTh90D6lZajee3AHmwKI9Nw9f/MjuH8+MlXoO5l 18KoxMbhPnKEmqho57HPMEaAWyC8OOV2k0jR6/NkcpaxtzWq6VJjJb2YYn4xgWCcKBAH 5hH4CPRICkCB5B+lhrQnhj13P1Xzn+NgrgnqcKKT+IUZr1QEELjUXJWC68VQBU41YRFZ VvcA==
X-Gm-Message-State: AOAM533YVVxd8zjZ9BFYOxZeHTISt10uFqfaEcmrA8GcDqPdTCzqvlqT vQ357gsXqR9cLx0vCAdTAd69hUJ55emabWIV+nI1QQ==
X-Google-Smtp-Source: ABdhPJyMp2BqrE5knjkZuuPsfIdeB115MCkugupOJH9zWwKS+KdPZmpqvUx5RGt99c4pIN/d1czdYPsx1DrqhlSCfcw=
X-Received: by 2002:adf:814a:: with SMTP id 68mr1650940wrm.177.1589938428525; Tue, 19 May 2020 18:33:48 -0700 (PDT)
MIME-Version: 1.0
References: <01000171e5dd76ed-e0bb6d02-faa5-4672-93ab-74bc96ae9775-000000@email.amazonses.com> <CC4173EC-67BB-4652-885E-4C50564CB05A@mnot.net> <01000171eaff2503-d978e760-f03b-416b-9208-f9a95d1ecadb-000000@email.amazonses.com> <41183D9D-6287-416D-B160-F67E0B40916C@mnot.net> <0100017205194aed-7b540ec1-10ac-4d1e-b66b-682f321c3e99-000000@email.amazonses.com> <20200512034441.GC4623@1wt.eu> <010001720a7abfc7-775d8708-8a88-4d8a-bf8d-cff51a02c1b2-000000@email.amazonses.com> <010001721a5bb104-2c64f226-b46f-40a8-8ca7-2298e3ed3811-000000@email.amazonses.com> <CAHbrMsAh=LsB0wwjW0DK3vc5eAfKJZOE6NEFb2P=UkeV4Y8kxg@mail.gmail.com> <010001722ebcc4ef-2c6b91a9-f736-443d-ab22-1629b8187145-000000@email.amazonses.com>
In-Reply-To: <010001722ebcc4ef-2c6b91a9-f736-443d-ab22-1629b8187145-000000@email.amazonses.com>
From: Ben Schwartz <bemasc@google.com>
Date: Tue, 19 May 2020 21:33:36 -0400
Message-ID: <CAHbrMsBgPLsBGs143bt9irPck7rxLbW9x5NntDK4HT97pcSS2w@mail.gmail.com>
To: Kent Watsen <kent+ietf@watsen.net>
Cc: HTTP Working Group <ietf-http-wg@w3.org>, "netconf-chairs@ietf.org" <netconf-chairs@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="00000000000048bb5105a60a6380"
Received-SPF: pass client-ip=2a00:1450:4864:20::42b; envelope-from=bemasc@google.com; helo=mail-wr1-x42b.google.com
X-W3C-Hub-Spam-Status: No, score=-20.6
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5, W3C_AA=-1, W3C_DB=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1jbDcO-0001O3-Bk 1e528f2adac4292f3567db861690cbdb
X-Original-To: ietf-http-wg@w3.org
Subject: Re: I-D for a YANG data model to configure HTTP clients and servers
Archived-At: <https://www.w3.org/mid/CAHbrMsBgPLsBGs143bt9irPck7rxLbW9x5NntDK4HT97pcSS2w@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37675
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On Tue, May 19, 2020 at 5:00 PM Kent Watsen <kent+ietf@watsen.net> wrote:

>
> Hi Ben.
>
> Thanks for CC-ing netconf-chairs, as I’d forgotten to in my follow up...
>
>
> 2. Configuring an HTTP client to connect thru a Proxy
>>
>> I think that only once in my career, perhaps a couple decades ago, I had
>> to configure a client to connect thru a proxy.   With that in mind, I ask
>> this question as someone that really doesn’t know what the state of the art
>> is.
>>
>> My fuzzy-memory is that, connecting thru an HTTP proxy entailed
>> establishing an HTTP connection to a proxy, and that connection is most
>> likely, if not exclusively, on top of TLS (i.e., HTTPS) and mutually
>> authenticated.
>>
>
> What you're describing is usually called a "Secure Web Proxy”.
>
>
> Thanks for clarifying my terminology.
>
>
> It is a popular type of proxy but far from the only one.
>
>
> I don’t understand this comment, especially in context of the next comment…
>
>
> The client always  authenticates the server name (in the usual way with
> TLS), but servers might or might not require clients to authenticate, and
> might do so in many different ways.
>
>
This comment was in reference to a Secure Web Proxy.  When using a SOCKS5
proxy, in contrast, there is typically no use of TLS between client and
proxy (although there will still be end-to-end TLS if the proxied
connection is for HTTPS).


>
> Sounds exactly like what the current configuration model enables:
>
> - client MUST use HTTPS (not HTTP)
> - client MUST auth the secure web proxy's TLS cert
> - client MAY provide TLS-level client certificate
> - client MAY provide one-of-many HTTP client-auth schemes
>
> To be clear, any combination of TLS-level and/or HTTP-level client-auth
> (including none) is allowed.
>
> Sounds right?
>

Yes.


>
>
> That is, in order to configure an HTTP(S) client to connect through a
>> proxy, effectively entails configuring it to establish a second HTTP(S)
>> connection.  That is, a first HTTP(S) connection is *to* the proxy, and a
>> second HTTP(S) connection is *thru* the proxy.   Yes?
>>
>
> Yes, connections through a Secure Web Proxy have end-to-end TLS "inside"
> the client-proxy TLS.
>
>
> Thanks for the confirmation.
>
> Kent
>
>
>