IETF Logo Mail Archive

Re: [Curdle] Alissa Cooper's No Objection on charter-ietf-curdle-00-02: (with COMMENT)

Alissa Cooper <alissa@cooperw.in> Wed, 02 December 2015 13:46 UTC

Return-Path: <alissa@cooperw.in>
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 586CE1A8BC4 for <curdle@ietfa.amsl.com>; Wed, 2 Dec 2015 05:46:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable
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 xtAoc5T0ZsPd for <curdle@ietfa.amsl.com>; Wed, 2 Dec 2015 05:46:26 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 108A21A8BC5 for <curdle@ietf.org>; Wed, 2 Dec 2015 05:46:24 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 6C020203F5 for <curdle@ietf.org>; Wed, 2 Dec 2015 08:46:23 -0500 (EST)
Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 02 Dec 2015 08:46:23 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=J44CVhhRtwG4Uz7Rd6dB3l3RnJw=; b=cLePzk kbdF6kd48vSPKYuirHOQAxVK/GEavgQZ0YdjtohaOcFOD+Qn54KZPeFdoNhKN9CQ 9EYShtxfJGFoxfYYd1ZpDrj25FSCzoIIEDFGiyWGw11NfX41UvmcFIR03BwCms44 dGguujEC1Q+Q70c14XEZZ0B6WZ0OlryY8aZcA=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=J44CVhhRtwG4Uz7 Rd6dB3l3RnJw=; b=i4zrAgibXyMEQ1wDowYSpkzyeUIFdxH5tEQsoF7Dhw6TQ/o unyX6hxm1/o6kUlTl1UUtaNS/impGi3TkD5n94SuCT2QtzQ8V9USGL+NmUmkd09x 63pS5EqG5hTpj2+JA1/RvkO7LYIbnryw8MChVFTEK91tQthn7AqZH1sGzmWE=
X-Sasl-enc: J8WXCQal9LxTmIzgX+WGoUFmEPhyr01XM8t0BtS3Ku62 1449063983
Received: from [192.168.1.203] (c-24-6-61-198.hsd1.ca.comcast.net [24.6.61.198]) by mail.messagingengine.com (Postfix) with ESMTPA id A675EC016C4; Wed, 2 Dec 2015 08:46:22 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <565E304D.6050308@cs.tcd.ie>
Date: Wed, 02 Dec 2015 05:46:25 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <E8E4A74D-83CB-4FDC-9842-45D95BF2B5A7@cooperw.in>
References: <20151130235242.13834.89824.idtracker@ietfa.amsl.com> <565D5B60.8080208@cs.tcd.ie> <8B5B85E0-4172-4BEE-B312-8238397997C6@cooperw.in> <565E304D.6050308@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/curdle/UsDZaLVUYoEu9mTOr4KLqpYpj1c>
Cc: curdle@ietf.org, curdle-chairs@ietf.org, IESG <iesg@ietf.org>
Subject: Re: [Curdle] Alissa Cooper's No Objection on charter-ietf-curdle-00-02: (with COMMENT)
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: Wed, 02 Dec 2015 13:46:27 -0000

> On Dec 1, 2015, at 3:42 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
>>>> 
>>>> 
> I don't get what it means for Kerberos and JSON to be "potentially" in
>>>> scope. It seems to me that they are in scope. If the WG chooses
>>>> not to pursue the work related to them that's ok, but they're
>>>> still in the scope of the charter.
>>> 
>>> "potentially" here just means that if the kitten (for Kerberos) or 
>>> jose (for JSON) WGs preferred to do the work, then that work would 
>>> not be done in curdle. There's a paragraph about that in the
>>> charter,
>> 
>> I understand, but the main point of writing a charter is to say what
>> is out of scope and in scope, not to guarantee that everything in
>> scope will definitely be worked on. If the sentence said “To be
>> concrete, the protocols the WG intends to work on are …” that would
>> be more accurate I think.
> 
> That'd be fine I reckon. Is [1] the right change?

Yes, thanks.
Alissa

> Ta,
> S.
> 
> [1]
> https://www.ietf.org/rfcdiff?url1=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-curdle%2Fwithmilestones-00-02.txt&url2=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-curdle%2Fwithmilestones-00-03.txt
> 
>> 
>> Alissa
>> 
>>> 
>>> Cheers, S.
>>> 
>>> 
>>>> 
>>>> 
>>>> _______________________________________________ Curdle mailing
>>>> list Curdle@ietf.org 
>>>> https://www.ietf.org/mailman/listinfo/curdle
>>>> 
>> 
>>

v2.23.0 | Report a Bug | By Email