IETF Logo Mail Archive

Re: Last Call: <draft-levine-herkula-oneclick-04.txt> (Signalling one-click functionality for list email headers) to Proposed Standard

Viktor Dukhovni <ietf-dane@dukhovni.org> Tue, 13 September 2016 16:04 UTC

Return-Path: <ietf-dane@dukhovni.org>
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 64D9712B573 for <ietf@ietfa.amsl.com>; Tue, 13 Sep 2016 09:04:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 wvMbAw4qQsWf for <ietf@ietfa.amsl.com>; Tue, 13 Sep 2016 09:03:57 -0700 (PDT)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2806812B5F5 for <ietf@ietf.org>; Tue, 13 Sep 2016 08:36:17 -0700 (PDT)
Received: by mournblade.imrryr.org (Postfix, from userid 1034) id 1BDF0282F88; Tue, 13 Sep 2016 15:36:16 +0000 (UTC)
Date: Tue, 13 Sep 2016 15:36:16 +0000
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-levine-herkula-oneclick-04.txt> (Signalling one-click functionality for list email headers) to Proposed Standard
Message-ID: <20160913153615.GG4670@mournblade.imrryr.org>
References: <20160913134903.53136.qmail@ary.lan> <92E953F2FB47FC32E3F4A4FC@JcK-HP8200>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <92E953F2FB47FC32E3F4A4FC@JcK-HP8200>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bbLsWREJ9vs2roRa3FoEmz5UbiQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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, 13 Sep 2016 16:04:02 -0000

On Tue, Sep 13, 2016 at 10:54:19AM -0400, John C Klensin wrote:

> Yes, but, again, I think it is more than hints -- I think there
> either needs to be enough information in the spec for safe,
> interoperable, independent implementations to be created or that
> it isn't appropriate for a Proposed Standard.

I agree that the specification needs to provide sufficient guidance
so that implementors don't make various otherwise likely mistakes.

-- 
	Viktor.

v2.23.0 | Report a Bug | By Email