Re: draft-thomson-httpbis-catch-00
Martin Thomson <martin.thomson@gmail.com> Tue, 16 December 2014 22:00 UTC
Return-Path: <ietf-http-wg-request@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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7ECDF1A885D for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 16 Dec 2014 14:00:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.012
X-Spam-Level:
X-Spam-Status: No, score=-7.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 2-Ezo_ODqCLf for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 16 Dec 2014 14:00:10 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF9291A8851 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 16 Dec 2014 14:00:10 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1Y108T-0005Oc-0g for ietf-http-wg-dist@listhub.w3.org; Tue, 16 Dec 2014 21:58:29 +0000
Resent-Date: Tue, 16 Dec 2014 21:58:29 +0000
Resent-Message-Id: <E1Y108T-0005Oc-0g@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.80) (envelope-from <martin.thomson@gmail.com>) id 1Y108K-0005Nr-U1 for ietf-http-wg@listhub.w3.org; Tue, 16 Dec 2014 21:58:20 +0000
Received: from mail-ob0-f174.google.com ([209.85.214.174]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <martin.thomson@gmail.com>) id 1Y108K-0005pS-2w for ietf-http-wg@w3.org; Tue, 16 Dec 2014 21:58:20 +0000
Received: by mail-ob0-f174.google.com with SMTP id nt9so895773obb.5 for <ietf-http-wg@w3.org>; Tue, 16 Dec 2014 13:57:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=pH3CgbNJvDHsXE00FSAd/gaRofxbG/Qiv3EglLEAO38=; b=VNtZ88ezbN6uRRgo0gqByaRTLkXwoEmtCYNJrYth4z7ZWeATBYSybRiaEc+yS6gIfn CnyRBUKyKzfSbiHUpFvSiAhFm4UCslRTWAc6ph2yVn+OQcEoA14FjIvxqVFa2pd8K1mj hFVDEQKIdF5vUYCpYxSGUol7q0jNKzT6S/uM1c+g960LDK+qtNdbpCuP726Yi41G5sd2 YR7HwI5N3pwOD933OY3PVN7yME/v4aylGp1CSPFYCb2M3jlFcfKIdihBiH5/93Kz5EJu m7h2nso5+07jDzn98zG7yeYVJ+VUU57ZT0Fcjxj3P+TIwBTuptKwX8zPWloZMoeb/8UV KCHA==
MIME-Version: 1.0
X-Received: by 10.202.212.82 with SMTP id l79mr22620956oig.12.1418767074183; Tue, 16 Dec 2014 13:57:54 -0800 (PST)
Received: by 10.202.49.203 with HTTP; Tue, 16 Dec 2014 13:57:54 -0800 (PST)
In-Reply-To: <D0B5FF71.8CDF1%kwatsen@juniper.net>
References: <D0B4672E.8CA88%kwatsen@juniper.net> <CABkgnnWimAhar8QJUwHgVk5kbuiKjNAfVfK1TYwf-VUzrSLsYg@mail.gmail.com> <D0B5FF71.8CDF1%kwatsen@juniper.net>
Date: Tue, 16 Dec 2014 13:57:54 -0800
Message-ID: <CABkgnnX=0v8XFxpM=nV7Axop7x=gOXO655pAxJ_744E+wM24gA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Kent Watsen <kwatsen@juniper.net>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Received-SPF: pass client-ip=209.85.214.174; envelope-from=martin.thomson@gmail.com; helo=mail-ob0-f174.google.com
X-W3C-Hub-Spam-Status: No, score=-4.5
X-W3C-Hub-Spam-Report: AWL=-1.787, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001
X-W3C-Scan-Sig: maggie.w3.org 1Y108K-0005pS-2w 665e2c54801132ed5599c0dc35fa1dac
X-Original-To: ietf-http-wg@w3.org
Subject: Re: draft-thomson-httpbis-catch-00
Archived-At: <http://www.w3.org/mid/CABkgnnX=0v8XFxpM=nV7Axop7x=gOXO655pAxJ_744E+wM24gA@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/28280
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: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
On 16 December 2014 at 13:31, Kent Watsen <kwatsen@juniper.net> wrote: > First off, the RESTCONF draft desperately needs this to be an RFC - any > chance of that happening soon? Feel free to make that statement here: ietf-http-wg@w3.org They are currently paying more attention to other things. If you want to lend a hand, I'm sure that we can move it faster. (open issues: https://github.com/martinthomson/drafts/labels/http-cant) > Secondly, if not using the "Authorization" request header field, how is it > that the client-certificate is passed into the app biz logic on the HTTP > server? It looks like Apache and NGINX have proprietary mechanisms to > pass the client-cert via the environment and/or headers. Should this > draft define something standard, for interop rasons, or is this considered > an internal app issue? It varies, a lot. And I haven't seen any indication that vendors of those containers want to standardize on an API. So I don't expect this to change.
- Re: draft-thomson-httpbis-catch-00 Martin Thomson