Re: [hrpc] first screening of RFC7230 for Human Rights leads

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 04 February 2015 10:07 UTC

Received: from [10.10.12.45] (helo=mx2.greenhost.nl) by mailman.lan with esmtp (Exim 4.72) (envelope-from <stephen.farrell@cs.tcd.ie>) id 1YIwrh-0000oZ-Np for hrpc@article19.io; Wed, 04 Feb 2015 11:07:21 +0100
Received: from mercury.scss.tcd.ie ([134.226.56.6]) by mx2.greenhost.nl with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <stephen.farrell@cs.tcd.ie>) id 1YIwre-00050V-On for hrpc@article19.io; Wed, 04 Feb 2015 11:07:21 +0100
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 4E151BF0D; Wed, 4 Feb 2015 10:07:49 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sLexXEc81oyQ; Wed, 4 Feb 2015 10:07:48 +0000 (GMT)
Received: from [10.87.48.73] (unknown [86.42.17.67]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id E3963BEFB; Wed, 4 Feb 2015 10:07:47 +0000 (GMT)
Message-ID: <54D1EF53.60209@cs.tcd.ie>
Date: Wed, 04 Feb 2015 10:07:15 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, hrpc@article19.io
References: <54D0FCD7.60302@article19.org> <87siem8tv6.fsf@alice.fifthhorseman.net>
In-Reply-To: <87siem8tv6.fsf@alice.fifthhorseman.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Spam-Level: /
X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50, RCVD_IN_DNSWL_NONE, T_RP_MATCHES_RCVD autolearn=disabled version=3.3.2
X-Spam-Score: 0.8
X-Virus-Scanned: by Greenhost Virus Scanner
X-Scan-Signature: 51a43cd7ff6838d9e9bce89dbcde6c26
Subject: Re: [hrpc] first screening of RFC7230 for Human Rights leads
X-BeenThere: hrpc@article19.io
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Human Rights Protocol Consideration Discussion list <hrpc.article19.io>
List-Unsubscribe: <https://lists.ghserv.net/mailman/options/hrpc>, <mailto:hrpc-request@article19.io?subject=unsubscribe>
List-Archive: <http://lists.ghserv.net/pipermail/hrpc>
List-Post: <mailto:hrpc@article19.io>
List-Help: <mailto:hrpc-request@article19.io?subject=help>
List-Subscribe: <https://lists.ghserv.net/mailman/listinfo/hrpc>, <mailto:hrpc-request@article19.io?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2015 10:07:22 -0000

One snippet...

On 03/02/15 23:20, Daniel Kahn Gillmor wrote:
> Unfortunately, not all proposed standards hold this line on content
> neutrality:
> 
>   https://tools.ietf.org/html/draft-nottingham-safe-hint-05
> 
> (of course, the above draft isn't an official RFC yet -- should we be
> comparing drafts-that-didn't make it with drafts that ended up becoming
> RFCs?)

AFAIK that draft is not continuing to publication. The IESG
ballot positions are at [1]. I don't know if the author plans to
bring it back or somewhere else in the same or some other form.

So I'd not concentrate on that, unless you're interested in how
the IETF process has (so far) stopped a bad idea from becoming
an RFC and proposed standard. If you are interested in the latter,
then I'm happy to help explain some of the minutiae, e.g. that
10 yes or no-objections IESG ballots are needed for a proposed
standard. (This was the first time I've ever seen 6 abstain
ballots on a draft in my 4 years on the IESG.)

S.

[1] https://datatracker.ietf.org/doc/draft-nottingham-safe-hint/ballot/