Re: [Ietf-message-headers] For review: Content-Base (update for http)

Mykyta Yevstifeyev <evnikita2@gmail.com> Thu, 08 September 2011 14:15 UTC

Return-Path: <evnikita2@gmail.com>
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 785E421F8B9F for <ietf-message-headers@ietfa.amsl.com>; Thu, 8 Sep 2011 07:15:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.477
X-Spam-Level:
X-Spam-Status: No, score=-3.477 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vYuClJ-Sr0IB for <ietf-message-headers@ietfa.amsl.com>; Thu, 8 Sep 2011 07:14:59 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9D6BA21F8B9A for <ietf-message-headers@ietf.org>; Thu, 8 Sep 2011 07:14:59 -0700 (PDT)
Received: by bkaq10 with SMTP id q10so755352bka.31 for <ietf-message-headers@ietf.org>; Thu, 08 Sep 2011 07:16:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=5h8YV0WXOhpoK1B1OR4jBvSkm4LVQebYnIVmo8d7dYc=; b=tjdGtIPisqpkTFKAkIo+1SPeEYcgHAqauMFyu0ttuatJXJYQ+RchIb9jfEhL3lAI3D cQsKQiA5OFJuffwu4eg5lqOj0j1bLmQ8GkTUlhA5pOXjUA9CMSX5pPVAtBabkUamrVmo QyNvqFpNFrVRvhRgRDes1oPQ+1KxtnK8T5qCY=
Received: by 10.204.133.130 with SMTP id f2mr637113bkt.86.1315491409848; Thu, 08 Sep 2011 07:16:49 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id a3sm743645bkd.11.2011.09.08.07.16.46 (version=SSLv3 cipher=OTHER); Thu, 08 Sep 2011 07:16:47 -0700 (PDT)
Message-ID: <4E68CE6F.4090004@gmail.com>
Date: Thu, 08 Sep 2011 17:17:19 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0.1) Gecko/20110830 Thunderbird/6.0.1
MIME-Version: 1.0
To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
References: <CAHhFybpNtcAxjTvWHSxx2P7iXOSiLr+9xL99bj4aqtS26rK1NQ@mail.gmail.com>
In-Reply-To: <CAHhFybpNtcAxjTvWHSxx2P7iXOSiLr+9xL99bj4aqtS26rK1NQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf-message-headers@ietf.org
Subject: Re: [Ietf-message-headers] For review: Content-Base (update for http)
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 08 Sep 2011 14:15:00 -0000

01.09.2011 23:46, Frank Ellermann wrote:
> On 30 August 2011 10:36, Mykyta Yevstifeyev wrote:
>
>> The same as with MIME header field:
>>> Specification document(s):
>>>     RFC 2068, Section 14.11
>>>     <http://tools.ietf.org/html/rfc2068#section-14.11>
> I've intentionally used the RFCs *obsoleting* Content-Base
> instead of the obsolete RFCs *specifying* Content-Base,
> because the request modifies existing (and wrt the status
> incorrect) registry entries.  The original RFCs can be
> found by their references in RFC 2616 and RFC 2557.  The
> original RFCs are mentioned in the "related information"
> of the templates.
>
> It's apparently possible to have two "specifications" in
> registry entries, so I'll just *add* the original RFC as
> suggested by you (see below for the http Content-Base).

This is fine.  I think the template is ready to be submitted to IANA.

Mykyta

>
> -Frank
> -----------------------------------------------------
> PERMANENT MESSAGE HEADER FIELD REGISTRATION TEMPLATE:
>
> Header field name:
>     Content-Base
>
> Applicable protocol:
>     http
>
> Status:
>     obsoleted
>
> Author/Change controller:
>     IETF
>
> Specification document(s):
>     RFC 2616 section 19.6.3,
>     <URL:http://tools.ietf.org/html/rfc2616#section-19.6.3>
>     RFC 2068, section 14.11,
>     <URL:http://tools.ietf.org/html/rfc2068#section-14.11>
>
> Related information:
>     Content-Base was originally specified in RFC 2068 and
>     later obsoleted in RFC 2616.  The MIME header field
>     Content-Base was also obsoleted (RFC 2557 section 12).
>