Re: #227: Encoding advice for new headers and parameters

"Poul-Henning Kamp" <phk@phk.freebsd.dk> Wed, 28 September 2016 05:47 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 C1C561288B8 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 27 Sep 2016 22:47:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.237
X-Spam-Level:
X-Spam-Status: No, score=-9.237 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 TqogqBErDG2p for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 27 Sep 2016 22:47:40 -0700 (PDT)
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 A646312B025 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 27 Sep 2016 22:47:40 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1bp7ed-0007bR-AU for ietf-http-wg-dist@listhub.w3.org; Wed, 28 Sep 2016 05:43:39 +0000
Resent-Date: Wed, 28 Sep 2016 05:43:39 +0000
Resent-Message-Id: <E1bp7ed-0007bR-AU@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <phk@phk.freebsd.dk>) id 1bp7eN-0007UR-CX for ietf-http-wg@listhub.w3.org; Wed, 28 Sep 2016 05:43:23 +0000
Received: from phk.freebsd.dk ([130.225.244.222]) by lisa.w3.org with esmtp (Exim 4.80) (envelope-from <phk@phk.freebsd.dk>) id 1bp7eL-0005LN-Km for ietf-http-wg@w3.org; Wed, 28 Sep 2016 05:43:22 +0000
Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 130C6273B0; Wed, 28 Sep 2016 05:42:57 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id u8S5gtad080115; Wed, 28 Sep 2016 05:42:56 GMT (envelope-from phk@phk.freebsd.dk)
To: Mark Nottingham <mnot@mnot.net>
cc: HTTP Working Group <ietf-http-wg@w3.org>
In-reply-to: <0168B53E-A4CB-41BA-B371-7499837A327E@mnot.net>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
References: <0168B53E-A4CB-41BA-B371-7499837A327E@mnot.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <80113.1475041375.1@critter.freebsd.dk>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 28 Sep 2016 05:42:55 +0000
Message-ID: <80114.1475041375@critter.freebsd.dk>
Received-SPF: none client-ip=130.225.244.222; envelope-from=phk@phk.freebsd.dk; helo=phk.freebsd.dk
X-W3C-Hub-Spam-Status: No, score=-5.9
X-W3C-Hub-Spam-Report: AWL=-0.897, BAYES_40=-0.001, RP_MATCHES_RCVD=-2.999, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: lisa.w3.org 1bp7eL-0005LN-Km 8ed068ab46aeb39ea6fa52bd64aa16de
X-Original-To: ietf-http-wg@w3.org
Subject: Re: #227: Encoding advice for new headers and parameters
Archived-At: <http://www.w3.org/mid/80114.1475041375@critter.freebsd.dk>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32423
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>

--------
In message <0168B53E-A4CB-41BA-B371-7499837A327E@mnot.net>et>, Mark Nottingham writes:

><https://github.com/httpwg/http-extensions/issues/227>
>
>After some discussion in Berlin and Stockholm, as well as experience 
>with dealing with i18n in parameters for the Link header (see 
><https://github.com/mnot/I-D/issues/180>), I think we should give more 
>definite advice about when RFC5987(bis) encoding should and should not 
>be used.

I have an almost done ID for the "common structure" idea I floated after
Stockholm.  That could be a more general solution to this problem.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.