Re: [Diversity] Review of draft-crocker-diversity-conduct-01

S Moonesamy <sm+ietf@elandsys.com> Thu, 19 March 2015 02:13 UTC

Return-Path: <sm@elandsys.com>
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 03C1E1A7D84 for <diversity@ietfa.amsl.com>; Wed, 18 Mar 2015 19:13:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level:
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01] 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 ML8JNuGu0D65 for <diversity@ietfa.amsl.com>; Wed, 18 Mar 2015 19:13:20 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 37CB31A6FF2 for <diversity@ietf.org>; Wed, 18 Mar 2015 19:13:20 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.227.193.53]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id t2J2Cw2X015736 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 Mar 2015 19:13:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1426731194; x=1426817594; bh=aCPl9FSE6vEpZIknswTzEDInP6VKCZkTq51tb0YoAyg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=NL0A2JWbMShwPX9JiuJG0Jt4uZcv1svNIlzobzfH8VOh/G+9E47FTZr05FQdtc6WK Nwj+S7HMWWUnzpUt/fZyf7T2UKF8ThXYt8tvdTQlnNWOE4IHVYne7UHNPRpeq3P6yT 03XtMiN0wKkj1SPSW3wlPOewPPNbOg3rYb2dmadU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1426731194; x=1426817594; i=@elandsys.com; bh=aCPl9FSE6vEpZIknswTzEDInP6VKCZkTq51tb0YoAyg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ogtG0pr8Of7jLDNBM/MXl6HChf4+Lw3Pr9dJFip9yX/nYBMfCZHleN3RedpiZXGwE W6jwJEh5Dfiz/hzUmRNUEmnIekVY6P/PzkN1GU1BqBD++xeR2/ur3I8lZC6NQAK1xv P5IPT5bTr16lueNR7ity8VCX9nxZhnSzzi0S6m2A=
Message-Id: <6.2.5.6.2.20150318182512.114ed198@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 18 Mar 2015 19:12:35 -0700
To: dcrocker@bbiw.net
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <550A1FCC.2010903@dcrocker.net>
References: <6.2.5.6.2.20150318073552.06f93688@elandnews.com> <550A1FCC.2010903@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/diversity/bzWTbBaGIQTy5_VvrEO8JS9iC3k>
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
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 02:13:21 -0000

Hi Dave,
At 18:01 18-03-2015, Dave Crocker wrote:
>The draft is not a specification. It does not offer normative statements
>about policy or practice.  Rather, it is a think-piece, that is, a
>discussion of issues.
>
>What would be the benefits in having it processed through the IETF
>stream?  What would be the risks?
>
>In considering Independent stream, my feeling was (and remains) that a
>document of this sort is a personal offering.  Hence the Independent stream.
>
>If there were some sort of outpouring of interest in having it in the
>IETF stream, that would be fine, but I'm not expecting it, nor do I
>think it significantly affects the document's relevance or utility.

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.  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.

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.

Regards,
S. Moonesamy