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

Michael Richardson <mcr@sandelman.ca> Wed, 07 August 2019 16:50 UTC

Return-Path: <mcr@sandelman.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 2013312069F; Wed, 7 Aug 2019 09:50:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 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, URIBL_BLOCKED=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 PgHqq-JqsW-v; Wed, 7 Aug 2019 09:50:43 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03AB512069B; Wed, 7 Aug 2019 09:50:42 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 0E732380BE; Wed, 7 Aug 2019 12:50:05 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id C5E823F; Wed, 7 Aug 2019 12:50:41 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Christian Hopps <chopps@chopps.org>
cc: "ipsec@ietf.org WG" <ipsec@ietf.org>, ipsecme-chairs@ietf.org
In-Reply-To: <DD6E8B10-06CB-4CA2-9B0D-2CE13B494BB2@chopps.org>
References: <DD6E8B10-06CB-4CA2-9B0D-2CE13B494BB2@chopps.org>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6114.1565196641.1@localhost>
Date: Wed, 07 Aug 2019 12:50:41 -0400
Message-ID: <6115.1565196641@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/FJVS-Hn0DPHjkk33FPCNuWX0zbU>
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, 07 Aug 2019 16:50:53 -0000

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?

Works for me.

    > " 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