IETF Logo Mail Archive

Re: [therightkey] Ramping up

Rob Stradling <rob.stradling@comodo.com> Thu, 20 February 2014 20:42 UTC

Return-Path: <rob.stradling@comodo.com>
X-Original-To: therightkey@ietfa.amsl.com
Delivered-To: therightkey@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD5AA1A02CF for <therightkey@ietfa.amsl.com>; Thu, 20 Feb 2014 12:42:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.11
X-Spam-Level:
X-Spam-Status: No, score=0.11 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_MISMATCH_NET=0.611, SPF_PASS=-0.001] 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 JqLRdUB_skVh for <therightkey@ietfa.amsl.com>; Thu, 20 Feb 2014 12:42:21 -0800 (PST)
Received: from ian.brad.office.comodo.net (eth5.brad-fw.brad.office.ccanet.co.uk [178.255.87.226]) by ietfa.amsl.com (Postfix) with ESMTP id 4D41C1A02F0 for <therightkey@ietf.org>; Thu, 20 Feb 2014 12:42:20 -0800 (PST)
Received: (qmail 1402 invoked by uid 1000); 20 Feb 2014 20:42:15 -0000
Received: from nigel.brad.office.comodo.net (HELO [192.168.0.58]) (192.168.0.58) (smtp-auth username rob, mechanism plain) by ian.brad.office.comodo.net (qpsmtpd/0.40) with (AES128-SHA encrypted) ESMTPSA; Thu, 20 Feb 2014 20:42:15 +0000
Message-ID: <530668A7.8070308@comodo.com>
Date: Thu, 20 Feb 2014 20:42:15 +0000
From: Rob Stradling <rob.stradling@comodo.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>, "trans@ietf.org" <therightkey@ietf.org>
References: <53025C8F.5020803@gmail.com>
In-Reply-To: <53025C8F.5020803@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/therightkey/LglsbwBap-2Kz8R2T3Q-I-M-hIA
Subject: Re: [therightkey] Ramping up
X-BeenThere: therightkey@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <therightkey.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/therightkey>, <mailto:therightkey-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/therightkey/>
List-Post: <mailto:therightkey@ietf.org>
List-Help: <mailto:therightkey-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/therightkey>, <mailto:therightkey-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Feb 2014 20:42:25 -0000

On 17/02/14 19:01, Melinda Shore wrote:
<snip>
> 5) the corollary to 4 is that I do try to get as much done on
>     the mailing list as possible.  One thing that's been useful
>     in some circumstances in the past has been an issue tracker.
>     We do have a working group wiki page with an issue tracker,
>     and I'd like to get a sense of whether the working group in
>     general and the authors more specifically would find it
>     helpful in progressing the document.

Hi Melinda.  Thanks for taking on the WG chair role.  :-)

Given the close relationship between RFC6962(-bis) and the open-source 
CT project, we've so far been logging issues for RFC6962-bis on the 
issue tracker at 
https://code.google.com/p/certificate-transparency/issues/list

I don't suppose it really matters which issue tracker we use.  Using an 
issue tracker will definitely be "helpful in progressing the document" 
though, IMHO.

-- 
Rob Stradling
Senior Research & Development Scientist
COMODO - Creating Trust Online

v2.26.15 | Report a Bug | By Email | System Status