IETF Logo Mail Archive

Re: Last Call: <draft-housley-implementer-obligations-01.txt> (Expectations of Implementers of IETF Protocols) to Informational RFC

Avri Doria <avri@acm.org> Mon, 12 May 2014 14:53 UTC

Return-Path: <avri@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E53961A0712 for <ietf@ietfa.amsl.com>; Mon, 12 May 2014 07:53:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.465
X-Spam-Level: *
X-Spam-Status: No, score=1.465 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_SOFTFAIL=0.665] autolearn=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 rcgO-q7L-jQG for <ietf@ietfa.amsl.com>; Mon, 12 May 2014 07:53:40 -0700 (PDT)
Received: from atl4mhob19.myregisteredsite.com (atl4mhob19.myregisteredsite.com [209.17.115.112]) by ietfa.amsl.com (Postfix) with ESMTP id D4CE21A01EA for <ietf@ietf.org>; Mon, 12 May 2014 07:53:40 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.209]) by atl4mhob19.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s4CErP1O007100 for <ietf@ietf.org>; Mon, 12 May 2014 10:53:25 -0400
Received: (qmail 6827 invoked by uid 0); 12 May 2014 14:53:25 -0000
X-TCPREMOTEIP: 68.15.42.104
X-Authenticated-UID: avri@ella.com
Received: from unknown (HELO ?127.0.0.1?) (avri@ella.com@68.15.42.104) by 0 with ESMTPA; 12 May 2014 14:53:25 -0000
Message-ID: <5370E05D.5010607@acm.org>
Date: Mon, 12 May 2014 10:53:17 -0400
From: Avri Doria <avri@acm.org>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-housley-implementer-obligations-01.txt> (Expectations of Implementers of IETF Protocols) to Informational RFC
References: <20140509191841.18372.97889.idtracker@ietfa.amsl.com> <06a301cf6c7e$770e51e0$652af5a0$@olddog.co.uk> <536E8CB1.7060802@gmail.com>
In-Reply-To: <536E8CB1.7060802@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 140512-0, 05/12/2014), Outbound message
X-Antivirus-Status: Not-Tested
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/2Nfmt0q3S2AZ7lg2nxxLMnkfDLk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 12 May 2014 14:53:42 -0000

Hi,

I think it is useful, not only for the new protocol designer, but for
those outside of the IETF, who are trying to understand how the IETF
does what it does.

Having said that, I do think that offering a bit more specificity, as
suggested by Adrian and Brain, would be good.

I would like to see it published.


avri

v2.23.0 | Report a Bug | By Email