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

S Moonesamy <sm+ietf@elandsys.com> Thu, 19 March 2015 09:47 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 3BAD91A1BAE for <diversity@ietfa.amsl.com>; Thu, 19 Mar 2015 02:47:37 -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 uFQ7BE6L1Qb7 for <diversity@ietfa.amsl.com>; Thu, 19 Mar 2015 02:47:36 -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 236CB1A00C0 for <diversity@ietf.org>; Thu, 19 Mar 2015 02:47:35 -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 t2J9lCXr008934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 19 Mar 2015 02:47:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1426758448; x=1426844848; bh=X4ryKycWkx3V9mBlqNqjrMt4YOhuDNWI2hJxwo4Fe4I=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=yc87BI9n/t0ZmAEP/LDidXANl/Z52/ARZqj4S03ZOc26Yv0sDTBhc3J9UY1kQbNsp 45atyHn5j4cBT5yBWl/wUUd07Qdl3ihfHN2jJNWdUff+L89Tzeg4tD88B36gNIQt8P UW814kxe7rhwmLeRqF+rqHWxCFfia4iieGf6X9Lg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1426758448; x=1426844848; i=@elandsys.com; bh=X4ryKycWkx3V9mBlqNqjrMt4YOhuDNWI2hJxwo4Fe4I=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=KX44G5CARNqSYNsKlaqb/GBHHLS8qTjgG5+jfUZx9Q+ykL52N4+GBFANzG7VcuWyK p5S1oJ6QdIPtN+DgpwqxdKUwcvcmf/8wX/ri/72r5lCZTns3KbMFurPo1EjiY0JlsN fg75lMBaNrZBpp8sXINC9l26pcvegTCHu+rsv6YM=
Message-Id: <6.2.5.6.2.20150319015131.0ddbf930@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 19 Mar 2015 02:22:01 -0700
To: dcrocker@bbiw.net, S Moonesamy <sm+ietf@elandsys.com>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <550A532B.3030201@dcrocker.net>
References: <6.2.5.6.2.20150318073552.06f93688@elandnews.com> <550A1FCC.2010903@dcrocker.net> <6.2.5.6.2.20150318182512.114ed198@elandnews.com> <550A532B.3030201@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/diversity/qdKkEFNEQUNbePHNOOekck4SC2c>
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 09:47:37 -0000

Hi Dave,
At 21:40 18-03-2015, Dave Crocker wrote:
>You appear to be saying that all documents "about" the IETF have to be
>submitted through the IETF stream.

If I am writing a draft about diversity in the IETF (I wrote one 
previously) I would initially try to get it published within the 
IETF.  If there isn't the outpouring of interest I would look for 
another venue.

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

It is not a RFC stream requirement.  I'll comment more about this below.

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

Ok.

>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 requirement is quite generic.  I cannot assess the level of 
technical quality as the draft is not a technical specification.  As 
for the editorial quality the draft is well-written but it is not 
that crisp.  The draft is at least relevant to a part of the Internet 
community.  I usually refer to RFC 4846 before making a 
recommendation about publication in the Independent Submissions Stream.

I suggest not considering the publication steam as a concern as we 
had this conversation about it.

Regards,
S. Moonesamy