
From nobody Sat Nov 28 08:24:47 2015
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: curdle@ietfa.amsl.com
Delivered-To: curdle@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 429F91B304B for <curdle@ietfa.amsl.com>; Sat, 28 Nov 2015 08:24:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.886
X-Spam-Level: 
X-Spam-Status: No, score=-4.886 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001] 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 OplZWvsF1tvo for <curdle@ietfa.amsl.com>; Sat, 28 Nov 2015 08:24:44 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69FDB1B3048 for <curdle@ietf.org>; Sat, 28 Nov 2015 08:24:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 7883BBE3E for <curdle@ietf.org>; Sat, 28 Nov 2015 16:24:39 +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 RBBl9qMiL0ji for <curdle@ietf.org>; Sat, 28 Nov 2015 16:24:38 +0000 (GMT)
Received: from [10.87.48.91] (unknown [86.46.27.82]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 90F3CBE39 for <curdle@ietf.org>; Sat, 28 Nov 2015 16:24:37 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1448727878; bh=VeU1v3HoP7+ZUCyk/s+Sb9tkWuxbia/3ZU4QqYJfTCc=; h=To:From:Subject:Date:From; b=3Jz2QppTPnY3HTPmcOd8aB609ILxM5AtkQNZLgF4C248etZbGHldjHiHdKdr8GX/J TJW5VD06GACnxCa4aeh1R57lExD9orjzLUymYA3anYuY5JjN7PP6pY5yVfIeZXuDGI sGgST6ZNd3jw/tASoYPrTOR3UEEjPxzl/5m2k3yg=
To: curdle@ietf.org
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <5659D545.2060909@cs.tcd.ie>
Date: Sat, 28 Nov 2015 16:24:37 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/curdle/YuNq6-lLAdCbQiY-b_F95kCt4xU>
Subject: [Curdle] draft charter
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Nov 2015 16:24:46 -0000

Hiya,

Probably no harm to have a link to the draft charter [1] as
#1 in the archive:-)

S.

[1] https://datatracker.ietf.org/doc/charter-ietf-curdle/


From nobody Sat Nov 28 08:25:17 2015
Return-Path: <joelja@bogus.com>
X-Original-To: curdle@ietf.org
Delivered-To: curdle@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DACA1B2DB6; Fri, 27 Nov 2015 16:40:26 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Joel Jaeggli" <joelja@bogus.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151128004026.32154.34180.idtracker@ietfa.amsl.com>
Date: Fri, 27 Nov 2015 16:40:26 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/curdle/yfe_BnRoo5SURNnfjX2taChQe0Q>
X-Mailman-Approved-At: Sat, 28 Nov 2015 08:25:16 -0800
Cc: curdle@ietf.org, curdle-chairs@ietf.org
Subject: [Curdle] Joel Jaeggli's No Objection on charter-ietf-curdle-00-02: (with COMMENT)
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Nov 2015 00:40:26 -0000

Joel Jaeggli has entered the following ballot position for
charter-ietf-curdle-00-02: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-curdle/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

seems like:

The relevant IETF protocols are primarily those protocols that are
standardized
through the IETF and that do not have an active working group, or where
the
working group decides to not take on the work. To be concrete, the
protocols in
scope are Secure Shell (SSH), DNSSEC, PKIX, CMS, XML Digital Signatures
and
potentially Kerberos and JSON.

can be simplified to

The protocols in scope are Secure Shell (SSH), DNSSEC, PKIX, CMS, XML
Digital Signatures and
potentially Kerberos and JSON.

also

As  the CURDLE working group will be handling changes to protocols and
registries some of which include what are now considered outdated 
algorithm
options, the working group can also choose to propose deprecation of
such
algorithms.

The CURDLE working group will be handling changes to protocols and
registries some of which include what are now considered outdated 
algorithm
options, and may propose deprecation of such algorithms.


