[IPsec] Update and WGLC request [Re: I-D Action: draft-ietf-ipsecme-iptfs-02.txt]

Christian Hopps <chopps@chopps.org> Mon, 12 October 2020 15:58 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 C4D123A1591; Mon, 12 Oct 2020 08:58:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 Oht7MvKd26Le; Mon, 12 Oct 2020 08:58:40 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 6D3CF3A0E6D; Mon, 12 Oct 2020 08:58:40 -0700 (PDT)
Received: from stubbs.int.chopps.org (047-050-069-038.biz.spectrum.com [47.50.69.38]) (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 EB2D76020F; Mon, 12 Oct 2020 15:58:39 +0000 (UTC)
From: Christian Hopps <chopps@chopps.org>
Message-Id: <27659521-C1B0-4F0E-A6CC-C6F4B8938FFE@chopps.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_49D479BA-5A52-4EA7-8198-98CB3B01D060"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Mon, 12 Oct 2020 11:58:38 -0400
In-Reply-To: <160148315262.3746.2680691950315422865@ietfa.amsl.com>
Cc: Christian Hopps <chopps@chopps.org>, ipsecme-chairs@ietf.org
To: ipsec@ietf.org
References: <160148315262.3746.2680691950315422865@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/LZp4PnLvQKSAI5MIBNhEIabVvaM>
Subject: [IPsec] Update and WGLC request [Re: I-D Action: draft-ietf-ipsecme-iptfs-02.txt]
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, 12 Oct 2020 15:58:42 -0000

Hi ipsecme and chairs,

This is a small update to the IPTFS draft which incorporates the last 2 changes that had been requested over the last year or so.

1. As requested last year, it dispenses with the late-enabled functionality, replacing it with a SHOULD clause supporting receiving IPTFS encapsulated ESP payloads w/o extra configuration.

2. It highlights that one must send payloads that carry inner packet fragments using consecutive ESP sequence numbered packets (with a caveat for all pad payload insertion).

We feel the document is quite stable at this point and would thus like to ask for moving to WG Last Call.

Thanks,
Chris.

> On Sep 30, 2020, at 12:25 PM, internet-drafts@ietf.org wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the IP Security Maintenance and Extensions WG of the IETF.
> 
>        Title           : IP Traffic Flow Security
>        Author          : Christian Hopps
> 	Filename        : draft-ietf-ipsecme-iptfs-02.txt
> 	Pages           : 26
> 	Date            : 2020-09-30
> 
> Abstract:
>   This document describes a mechanism to enhance IPsec traffic flow
>   security by adding traffic flow confidentiality to encrypted IP
>   encapsulated traffic.  Traffic flow confidentiality is provided by
>   obscuring the size and frequency of IP traffic using a fixed-sized,
>   constant-send-rate IPsec tunnel.  The solution allows for congestion
>   control as well.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-ipsecme-iptfs/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-ipsecme-iptfs-02
> https://datatracker.ietf.org/doc/html/draft-ietf-ipsecme-iptfs-02
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-ipsecme-iptfs-02
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> 
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec
>