Re: [IPsec] Candidate charter text is now in wiki

Paul Wouters <paul@nohats.ca> Fri, 09 February 2018 16:40 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3D07126B72 for <ipsec@ietfa.amsl.com>; Fri, 9 Feb 2018 08:40:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 5HqKc2Ievz3N for <ipsec@ietfa.amsl.com>; Fri, 9 Feb 2018 08:40:10 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B054B1200FC for <ipsec@ietf.org>; Fri, 9 Feb 2018 08:40:10 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3zdLQH4TgvzpP; Fri, 9 Feb 2018 17:40:07 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1518194407; bh=NZjUN1QfEYURsAHgnV9zr+Y66R3B0gYORydzncnTjKY=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=Ff7ygOtJWy7YHfrFMs9fme05lyxSll4DCsLtMYgNA16CRvxveP+fh2geZrjv3bEcI NoFIlbSx8DJ5NhESkWIi8Y0kv9mTX8HNCElMG9rM1hkTgmJHYHr/OJVv/rRh9zxJY+ crtBNGmXl1f2Ki4lrOC1PGAs8tuxJWt3cqgszTfE=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id 5sbkRionQd8S; Fri, 9 Feb 2018 17:40:06 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri, 9 Feb 2018 17:40:04 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id B528C30B3EC; Fri, 9 Feb 2018 11:40:03 -0500 (EST)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca B528C30B3EC
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id A75B4402333D; Fri, 9 Feb 2018 11:40:03 -0500 (EST)
Date: Fri, 09 Feb 2018 11:40:03 -0500
From: Paul Wouters <paul@nohats.ca>
To: Tero Kivinen <kivinen@iki.fi>
cc: mohamed.boucadair@orange.com, "ipsec@ietf.org" <ipsec@ietf.org>
In-Reply-To: <23162.53065.405334.393026@fireball.acr.fi>
Message-ID: <alpine.LRH.2.21.1802091138320.14532@bofh.nohats.ca>
References: <23054.29098.665202.402605@fireball.acr.fi> <787AE7BB302AE849A7480A190F8B93300A07C37A@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <23161.62855.158031.367282@fireball.acr.fi> <787AE7BB302AE849A7480A190F8B93300A0CC90D@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <23162.53065.405334.393026@fireball.acr.fi>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/_CsdnEynf6sxuQrEuRMlJvyfRK0>
Subject: Re: [IPsec] Candidate charter text is now in wiki
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Feb 2018 16:40:13 -0000

On Wed, 7 Feb 2018, Tero Kivinen wrote:

> It depends. If we do not take the item as official working group
> chartered item, there are still few different options. You can either
> get it processed as AD sponsored draft, or you can go individual
> submission track.

It is a little strange we don't have an ops group for ipsec. The IPsecME
group really functions as such. Maybe something covering ops could be
added to the charter to cover these kind of items. Because I do think
everyone would prefer this type of work to happen in a WG and not as
individual/AD sponsored work.

Paul