IETF Logo Mail Archive

Re: [Ietf-message-headers] HTTP Refresh header

Graham Klyne <gk@ninebynine.org> Thu, 10 August 2017 10:41 UTC

Return-Path: <gk@ninebynine.org>
X-Original-To: ietf-message-headers@ietfa.amsl.com
Delivered-To: ietf-message-headers@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 505B1132692 for <ietf-message-headers@ietfa.amsl.com>; Thu, 10 Aug 2017 03:41:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level:
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=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 LkEexbYywRXl for <ietf-message-headers@ietfa.amsl.com>; Thu, 10 Aug 2017 03:41:18 -0700 (PDT)
Received: from relay15.mail.ox.ac.uk (relay15.mail.ox.ac.uk [163.1.2.163]) (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 5DD341288B8 for <ietf-message-headers@ietf.org>; Thu, 10 Aug 2017 03:41:18 -0700 (PDT)
Received: from smtp6.mail.ox.ac.uk ([163.1.2.206]) by relay15.mail.ox.ac.uk with esmtp (Exim 4.89) (envelope-from <gk@ninebynine.org>) id 1dfktw-0004uX-nP; Thu, 10 Aug 2017 11:41:16 +0100
Received: from [213.205.252.147] (helo=sasharissa.local) by smtp6.mail.ox.ac.uk with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <gk@ninebynine.org>) id 1dfktt-0009nP-Ka; Thu, 10 Aug 2017 11:41:15 +0100
Message-ID: <598C3840.60600@ninebynine.org>
Date: Thu, 10 Aug 2017 11:41:04 +0100
From: Graham Klyne <gk@ninebynine.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Anne van Kesteren <annevk@annevk.nl>, Julian Reschke <julian.reschke@gmx.de>
CC: ietf-message-headers@ietf.org
References: <CADnb78jQHnrsjpXYZQCQt1kcaRTxWSJWDyyF74os6FPvshyPZg@mail.gmail.com> <1c5ce02a-9312-34e5-35b8-b5e1ba6089d4@gmx.de> <0C07550D-D9AD-4095-9A58-C027D8B49A17@mnot.net> <b50537c8-cbbc-25bd-c67e-471734384e44@gmx.de> <CADnb78j+0XXjc2G90DJV0h_PmcLnMbQRdOAgzm4e=z7P57iskA@mail.gmail.com>
In-Reply-To: <CADnb78j+0XXjc2G90DJV0h_PmcLnMbQRdOAgzm4e=z7P57iskA@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
X-Oxmail-Spam-Status: score=0.0 tests=none
X-Oxmail-Spam-Level: /
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-message-headers/_iQ-9vsSKMdMJDBanlwOmF8biOc>
Subject: Re: [Ietf-message-headers] HTTP Refresh header
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-message-headers/>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Aug 2017 10:41:21 -0000

On 10/08/2017 09:02, Anne van Kesteren wrote:
> On Wed, Aug 9, 2017 at 8:28 PM, Julian Reschke <julian.reschke@gmx.de> wrote:
>> That is true, but the registration actually should reference something that
>> specifies the HTTP header field.
>
> Could you be more specific?
>

FYI, the requirement for permanent registration per 
https://tools.ietf.org/html/rfc3864#section-2.1 includes "Specification 
required", which is defined as:

[[
Specification Required - Values and their meaning must be
            documented in an RFC or other permanent and readily available
            reference, in sufficient detail so that interoperability
            between independent implementations is possible.
]]
-- https://tools.ietf.org/html/rfc2434#section-2

#g
--

v2.23.0 | Report a Bug | By Email