Re: Partial review of draft-ietf-httpbis-rfc5987bis-04

Julian Reschke <julian.reschke@greenbytes.de> Tue, 21 February 2017 19:17 UTC

Return-Path: <julian.reschke@greenbytes.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 984EF129564; Tue, 21 Feb 2017 11:17:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=greenbytes.de header.b=YBHrm1yD; dkim=pass (1024-bit key) header.d=greenbytes.de header.b=YBHrm1yD
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 jSElfwolxsLg; Tue, 21 Feb 2017 11:17:13 -0800 (PST)
Received: from mail.greenbytes.de (mail.greenbytes.de [5.10.171.186]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0724129448; Tue, 21 Feb 2017 11:17:09 -0800 (PST)
Received: by mail.greenbytes.de (Postfix, from userid 117) id 455F015A1125; Tue, 21 Feb 2017 20:17:08 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=greenbytes.de; s=mail; t=1487704628; bh=zV7KCdKAmGKbQjSR4O0dTjmLGvDKNBw92LQcLcFfGgY=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=YBHrm1yDuKI26HjADbV+4cN62RhOgO4VXU3UcvZsXhpwuAOTWKglfxtmcPbapBK+Z sXjtYqtB84FSP/fh8V6IseWAG3z0Wvp6vhhSVZVMHBxaP9C3xx/bOWoZ56dsURChSW pgZLIxis6uI7XwGxSobO5lWCJ1J+BaWPkX2C3OS0=
Received: from [192.168.178.20] (unknown [93.217.71.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mail.greenbytes.de (Postfix) with ESMTPSA id 5460D15A05F8; Tue, 21 Feb 2017 20:17:07 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=greenbytes.de; s=mail; t=1487704628; bh=zV7KCdKAmGKbQjSR4O0dTjmLGvDKNBw92LQcLcFfGgY=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=YBHrm1yDuKI26HjADbV+4cN62RhOgO4VXU3UcvZsXhpwuAOTWKglfxtmcPbapBK+Z sXjtYqtB84FSP/fh8V6IseWAG3z0Wvp6vhhSVZVMHBxaP9C3xx/bOWoZ56dsURChSW pgZLIxis6uI7XwGxSobO5lWCJ1J+BaWPkX2C3OS0=
Subject: Re: Partial review of draft-ietf-httpbis-rfc5987bis-04
To: Jouni Korhonen <jounikor@gmail.com>, ops-dir@ietf.org
References: <148770448855.19178.9845548060581119883.idtracker@ietfa.amsl.com>
From: Julian Reschke <julian.reschke@greenbytes.de>
Message-ID: <b08d4591-437c-f65f-8a51-c4f807261c7e@greenbytes.de>
Date: Tue, 21 Feb 2017 20:17:07 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <148770448855.19178.9845548060581119883.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bMMqAqRKffSfDp6PFovU4Zja2Fs>
Cc: draft-ietf-httpbis-rfc5987bis.all@ietf.org, ietf-http-wg@w3.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 19:17:14 -0000

On 2017-02-21 20:14, Jouni Korhonen wrote:
> ...
> The IDnits complains about non-ascii characters (pound, euro, etc). I
> am not sure whether that will turn out to an "editorial" issue in the
> final RFC text.
> ...

Right. That's because the tool chain doesn't yet support that properly. 
That shouldn't stop us from pushing.

(I'm ok with the spec spending some quality time in the RFC Editor queue 
until they are ready)

Best regards, Julian