Re: [Diversity] Review of draft-crocker-diversity-conduct-01
Dave Crocker <dhc@dcrocker.net> Thu, 19 March 2015 04:40 UTC
Return-Path: <dhc@dcrocker.net>
X-Original-To: diversity@ietfa.amsl.com
Delivered-To: diversity@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F56B1A8790 for <diversity@ietfa.amsl.com>; Wed, 18 Mar 2015 21:40:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 cD6n_CRfVey6 for <diversity@ietfa.amsl.com>; Wed, 18 Mar 2015 21:40:43 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE4251A876D for <diversity@ietf.org>; Wed, 18 Mar 2015 21:40:43 -0700 (PDT)
Received: from [192.168.1.87] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id t2J4eGNs009888 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 18 Mar 2015 21:40:19 -0700
Message-ID: <550A532B.3030201@dcrocker.net>
Date: Wed, 18 Mar 2015 21:40:11 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
References: <6.2.5.6.2.20150318073552.06f93688@elandnews.com> <550A1FCC.2010903@dcrocker.net> <6.2.5.6.2.20150318182512.114ed198@elandnews.com>
In-Reply-To: <6.2.5.6.2.20150318182512.114ed198@elandnews.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 18 Mar 2015 21:40:20 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/diversity/Y9p9YHL__AA-5IfRfgjjAsm3ra8>
Cc: Narelle Clark <narelle.clark@pavonis.com.au>, diversity@ietf.org
Subject: Re: [Diversity] Review of draft-crocker-diversity-conduct-01
X-BeenThere: diversity@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: Diversity open mailing list <diversity.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/diversity>, <mailto:diversity-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/diversity/>
List-Post: <mailto:diversity@ietf.org>
List-Help: <mailto:diversity-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/diversity>, <mailto:diversity-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Mar 2015 04:40:45 -0000
On 3/18/2015 7:12 PM, S Moonesamy wrote: > I'll response to the specific point about the Independent Submissions > Stream and follow up on the other parts in a few days. > > Here's how I look at the document in respect to publication in the > stream. The document is about the IETF. The IETF has a stream. The > default place for it to be published would be in that stream. SM, You appear to be saying that all documents "about" the IETF have to be submitted through the IETF stream. I can't tell whether you see your use of 'should' as your personal opinion or as an RFC stream requirement. I am not aware of any requirement that matches what you've said. Quite the contrary. I believe the scope of the Independent stream covers a personal document like this entirely reasonably. So the issue is whether it is somehow better to have it go through the IETF stream. I see two factors to consider. One is whether there is sufficient community interest in the document? The other is whether there is significant benefit in going through an IETF rough consensus approval process? I don't see the answer being yes to either question? Some benefit, perhaps, but not enough to be worth the considerably greater effort. > I also > look at how a documents fits within the Independent Submissions Stream. > It's quite straightforward for a specification as there is some guidance > about that. It is less obvious for this draft as I have to figure out > in which other category to fit it in. Perhaps you should review the requirements for Independent Stream. For example, on: https://www.rfc-editor.org/indsubs.html "The independent submission stream allows RFC publication for some documents that are outside the official IETF/IAB/IRTF process but are relevant to the Internet community and achieve reasonable levels of technical and editorial quality. " That's pretty general and this document certainly falls within that scope, as I read it. > > The benefit of processing through the IETF Stream is that it could be > read as meaning that the IETF is mature enough to handle > self-criticism. The risk is that the draft may not gain consensus. As I said in my previous note, that would be fine if there were more community interest. The draft has been around for quite awhile but has received minimal comment. d/ -- Dave Crocker Brandenburg InternetWorking bbiw.net
- Re: [Diversity] Review of draft-crocker-diversity… Dave Crocker
- Re: [Diversity] Review of draft-crocker-diversity… S Moonesamy
- Re: [Diversity] Review of draft-crocker-diversity… Dave Crocker
- [Diversity] Review of draft-crocker-diversity-con… S Moonesamy
- Re: [Diversity] Review of draft-crocker-diversity… S Moonesamy
- Re: [Diversity] Review of draft-crocker-diversity… S Moonesamy
- Re: [Diversity] Review of draft-crocker-diversity… Dave Crocker
- Re: [Diversity] Review of draft-crocker-diversity… Dave Crocker
- Re: [Diversity] Review of draft-crocker-diversity… S Moonesamy
- Re: [Diversity] Review of draft-crocker-diversity… Dave Crocker