IETF Logo Mail Archive

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

Christian Hopps <chopps@chopps.org> Sun, 13 October 2019 07:10 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 C4E7A1200D6; Sun, 13 Oct 2019 00:10:39 -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 272HoaOcLwHu; Sun, 13 Oct 2019 00:10:38 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id F08F9120025; Sun, 13 Oct 2019 00:10:37 -0700 (PDT)
Received: from stubbs.int.chopps.org (unknown [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 2256F6061F; Sun, 13 Oct 2019 03:10:37 -0400 (EDT)
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: <90A18DDA-F20B-4B0C-8FB6-EF5969F7B121@nohats.ca>
Date: Sun, 13 Oct 2019 03:10:36 -0400
Cc: Christian Hopps <chopps@chopps.org>, ipsecme-chairs@ietf.org, Paul Wouters <paul@nohats.ca>, mcr@sandelman.ca
Content-Transfer-Encoding: quoted-printable
Message-Id: <2DD52B3F-B503-42FC-B8BF-26DBEAEE04A7@chopps.org>
References: <DD6E8B10-06CB-4CA2-9B0D-2CE13B494BB2@chopps.org> <90A18DDA-F20B-4B0C-8FB6-EF5969F7B121@nohats.ca>
To: "ipsec@ietf.org WG" <ipsec@ietf.org>
X-Mailer: Apple Mail (2.3594.4.19)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/aOv1pfEc3rHMz4MmJ42fLH-uwzs>
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: Sun, 13 Oct 2019 07:10:40 -0000

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
>

v2.23.0 | Report a Bug | By Email