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

Christian Hopps <chopps@chopps.org> Mon, 21 October 2019 21:45 UTC

Return-Path: <chopps@chopps.org>
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 411F312001A; Mon, 21 Oct 2019 14:45:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 PKtV9Bu6yufQ; Mon, 21 Oct 2019 14:45:29 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 4E468120019; Mon, 21 Oct 2019 14:45:29 -0700 (PDT)
Received: from stubbs.int.chopps.org (172-222-100-236.res.spectrum.com [172.222.100.236]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 732FA600E7; Mon, 21 Oct 2019 21:45:28 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3594.4.19\))
From: Christian Hopps <chopps@chopps.org>
In-Reply-To: <20191019010019.GU43312@kduck.mit.edu>
Date: Mon, 21 Oct 2019 17:45:27 -0400
Cc: Christian Hopps <chopps@chopps.org>, "ipsec@ietf.org WG" <ipsec@ietf.org>, ipsecme-chairs@ietf.org, Paul Wouters <paul@nohats.ca>, mcr@sandelman.ca
Content-Transfer-Encoding: quoted-printable
Message-Id: <905631BC-A6F3-4364-BF25-50B0945A88AE@chopps.org>
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>
To: Benjamin Kaduk <kaduk@mit.edu>
X-Mailer: Apple Mail (2.3594.4.19)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/0zcviLsQ2utRrE6Mv_UB-k9HyKA>
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: Mon, 21 Oct 2019 21:45:31 -0000

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?

Thanks,
Chris.

> On Oct 18, 2019, at 9:00 PM, Benjamin Kaduk <kaduk@mit.edu> wrote:
> 
> I think we've got a couple potential recharter topics in flight, so I'd
> like to have the chairs assemble a consolidated version with all the
> updates in it, so that I can start the formal rechartering process.
> 
> -Ben
> 
> On Sun, Oct 13, 2019 at 03:10:36AM -0400, Christian Hopps wrote:
>> Hi ipsecme and charis,
>> 
>> It seems like we've had a good amount of soak time on this. :)
>> 
>> What are the next steps?
>> 
>> Thanks,
>> Chris.
>> 
>>> On Aug 7, 2019, at 7:04 PM, Paul Wouters <paul@nohats.ca> wrote:
>>> 
>>> Seems broad enough - works for me
>>> 
>>> Sent from mobile device
>>> 
>>>> On Aug 7, 2019, at 06:38, Christian Hopps <chopps@chopps.org> wrote:
>>>> 
>>>> Hi ipsecme and chairs,
>>>> 
>>>> As discussed @IETF105 we need to update the charter in order to adopt the IPTFS draft, how does this look for addition to the charter?
>>>> 
>>>> "
>>>> The demand for Traffic Flow Confidentiality has been increasing in the user
>>>> community; however, the current method defined in RFC4303 (i.e., add null
>>>> padding to each ESP payload) is very inefficient in it's use of network
>>>> resources. The working group will develop an alternative TFC solution that
>>>> provides for efficient use of network resources.
>>>> "
>>>> 
>>>> Thanks,
>>>> Chris.
>>>> _______________________________________________
>>>> IPsec mailing list
>>>> IPsec@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ipsec
>>> 
>> 
>> _______________________________________________
>> IPsec mailing list
>> IPsec@ietf.org
>> https://www.ietf.org/mailman/listinfo/ipsec
>