IETF Logo Mail Archive

Re: [apps-discuss] WGLC for draft-ietf-appsawg-mime-default-charset

Alexey Melnikov <alexey.melnikov@isode.com> Fri, 13 April 2012 18:51 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D52A011E80C1 for <apps-discuss@ietfa.amsl.com>; Fri, 13 Apr 2012 11:51:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.396
X-Spam-Level:
X-Spam-Status: No, score=-102.396 tagged_above=-999 required=5 tests=[AWL=0.203, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 DB06Uu44NZNx for <apps-discuss@ietfa.amsl.com>; Fri, 13 Apr 2012 11:51:23 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 3400611E8098 for <apps-discuss@ietf.org>; Fri, 13 Apr 2012 11:51:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1334343081; d=isode.com; s=selector; i=@isode.com; bh=gzDlRaQx2i6aQHbbObaMQ8239WjqFlCmzMQYB8I6fe8=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=iM8LazSliZr1kd5/j+YhMDjOpJV00l6RfFI4NODXg/F7cRH1ac8gg6GrRTqq+J8Hd2zcNy qZbkkLHPAuU6GhCevsGUmvQHSWTOr2hQHxFW1H9gpBXdlpIthc53O4/WNdzlTsqmcTbqxh 63iOPtwqGvxdU22BgwRef/ipBeAnlBs=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPSA id <T4h1qAAg228u@rufus.isode.com>; Fri, 13 Apr 2012 19:51:21 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <4F8875D1.1000502@isode.com>
Date: Fri, 13 Apr 2012 19:52:01 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: Julian Reschke <julian.reschke@gmx.de>
References: <9452079D1A51524AA5749AD23E0039280C9874@exch-mbx901.corp.cloudmark.com> <01OE2UNN2HJ000ZUIL@mauve.mrochek.com> <4F82B5F6.3050806@gmx.de> <01OE3UQGECV600ZUIL@mauve.mrochek.com> <4F843332.7060705@isode.com> <4F8437E7.1070501@gmx.de>
In-Reply-To: <4F8437E7.1070501@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Ned Freed <ned.freed@mrochek.com>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] WGLC for draft-ietf-appsawg-mime-default-charset
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Apr 2012 18:51:23 -0000

On 10/04/2012 14:38, Julian Reschke wrote:
> On 2012-04-10 15:18, Alexey Melnikov wrote:
>> ...
>>> Not sure I see any need for a normative reference though.
>>
>> (I've mentioned my opinion to Julian, but I would like to state it for
>> the record.)
>> I think an update to RFC 2616 should have a reference to
>> draft-ietf-appsawg-mime-default-charset and make it clear that the
>> previous default was removed. An Informative reference to
>> draft-ietf-appsawg-mime-default-charset should be fine.
>
> HTTPbis *does* make it clear that the default (overriding the base 
> spec) was removed.
>
> What's not clear to me is why it would need to reference 
> draft-ietf-appsawg-mime-default-charset.
People who only read/implemented RFC 2616 need to be told that the rules 
changed. Similarly for people who read/implemented RFC 2046. Navigating 
through the maze of RFCs obsoleting each other is difficult for people 
who don't deal with them on a daily basis (and it is non trivial even 
for people who do). A reference to 
draft-ietf-appsawg-mime-default-charset would help with that.

v2.23.0 | Report a Bug | By Email