IETF Logo Mail Archive

Re: [IPsec] Possible new charter text to cover iptfs.

Benjamin Kaduk <kaduk@mit.edu> Wed, 23 October 2019 18:21 UTC

Return-Path: <kaduk@mit.edu>
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 2FD79120CB1; Wed, 23 Oct 2019 11:21:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 Abu3d3zNA6au; Wed, 23 Oct 2019 11:21:19 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 CBAB2120D10; Wed, 23 Oct 2019 11:21:16 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x9NILBYb030230 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 23 Oct 2019 14:21:13 -0400
Date: Wed, 23 Oct 2019 11:21:11 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Christian Hopps <chopps@chopps.org>
Cc: "ipsec@ietf.org WG" <ipsec@ietf.org>, ipsecme-chairs@ietf.org, Paul Wouters <paul@nohats.ca>, mcr@sandelman.ca
Message-ID: <20191023182111.GY69013@kduck.mit.edu>
References: <DD6E8B10-06CB-4CA2-9B0D-2CE13B494BB2@chopps.org> <90A18DDA-F20B-4B0C-8FB6-EF5969F7B121@nohats.ca> <2DD52B3F-B503-42FC-B8BF-26DBEAEE04A7@chopps.org> <20191019010019.GU43312@kduck.mit.edu> <905631BC-A6F3-4364-BF25-50B0945A88AE@chopps.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <905631BC-A6F3-4364-BF25-50B0945A88AE@chopps.org>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/JhJLLhDj4Ft2Ayc4ONl2Ob-CE5U>
Subject: Re: [IPsec] Possible new charter text to cover iptfs.
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 23 Oct 2019 18:21:22 -0000

Hi Chris,

On Mon, Oct 21, 2019 at 05:45:27PM -0400, Christian Hopps wrote:
> Hi Ben,
> 
> To perhaps speed this up a little bit, could we maybe run the process in parallel then? We had very positive feedback at the last meeting for adopting draft-hopps-ipsecme-iptfs-01 draft as a WG item, but since new work in ipsecme needs specific charter changes as well, and that seems to take a while, this adoption call has been delayed almost a full meeting cycle at this point.
> 
> IOW, could we do an adoption call contingent on the charter change, and then when the charter change happens we can at the same time adopt the draft as a WG item, thus avoiding more process delay?

Yes, it should be possible to run a contigent adoption call in parallel
with rechartering discussions.

-Ben

v2.23.0 | Report a Bug | By Email