[IPsec] Barry Leiba's No Objection on charter-ietf-ipsecme-12-00: (with COMMENT)

Barry Leiba via Datatracker <noreply@ietf.org> Mon, 16 December 2019 07:48 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: ipsec@ietf.org
Delivered-To: ipsec@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D8BC0120025; Sun, 15 Dec 2019 23:48:22 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Barry Leiba via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: ipsecme-chairs@tools.ietf.org, ipsecme-chairs@ietf.org, ipsec@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.113.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Barry Leiba <barryleiba@computer.org>
Message-ID: <157648250284.11650.7617421500571091763.idtracker@ietfa.amsl.com>
Date: Sun, 15 Dec 2019 23:48:22 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/jWGTmtLnX7xPT-_hCWTvdp7UZK4>
Subject: [IPsec] Barry Leiba's No Objection on charter-ietf-ipsecme-12-00: (with COMMENT)
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.29
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, 16 Dec 2019 07:48:23 -0000

Barry Leiba has entered the following ballot position for
charter-ietf-ipsecme-12-00: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-ipsecme/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Some wordsmithing on the two new paragraphs, mostly correcting grammar errors and awkward wording:

NEW
RFC8229, published in 2017, specifies how to encapsulate
IKEv2 and ESP traffic in TCP.  Implementation experience has
revealed that not all situations are covered in RFC8229, and that may
lead to interoperability problems or to suboptimal performance. The WG
will provide a document to give implementors more guidance about how to use
reliable stream transport in IKEv2 and clarify some issues that have been
discovered. A possible starting point is draft-smyslov-ipsecme-tcp-guidelines.

The demand for Traffic Flow Confidentiality has been increasing in the user
community, but the current method defined in RFC4303 (adding null
padding to each ESP payload) is very inefficient in its use of network
resources. The working group will develop an alternative TFC solution that
uses network resources more efficiently.
END