[IPsec] Possible new charter text to cover iptfs.

Christian Hopps <chopps@chopps.org> Wed, 07 August 2019 10:38 UTC

Return-Path: <chopps@chopps.org>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id AFF50120148; Wed, 7 Aug 2019 03:38:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id icG2jk5Dmz3q; Wed, 7 Aug 2019 03:38:25 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org []) by ietfa.amsl.com (Postfix) with ESMTP id 10D9112002F; Wed, 7 Aug 2019 03:38:25 -0700 (PDT)
Received: from stubbs.home (172-222-100-236.dhcp.chtrptr.net []) (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 74FDC601E9; Wed, 7 Aug 2019 06:38:24 -0400 (EDT)
From: Christian Hopps <chopps@chopps.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_5ABB3CA9-E66C-4F68-9DDA-4C9B80FCC47E"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Message-Id: <DD6E8B10-06CB-4CA2-9B0D-2CE13B494BB2@chopps.org>
Date: Wed, 7 Aug 2019 06:38:23 -0400
Cc: Christian Hopps <chopps@chopps.org>, ipsecme-chairs@ietf.org
To: "ipsec@ietf.org WG" <ipsec@ietf.org>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/QRSIVPWVlTjgForEocTmFT_M1n8>
Subject: [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, 07 Aug 2019 10:38:27 -0000

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.