Re: [IPv6] FW: New Version Notification for draft-ls-6man-ipcomp-exclude-transport-layer-00.txt

Nick Hilliard <nick@foobar.org> Mon, 24 October 2022 08:28 UTC

Return-Path: <nick@foobar.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 389C8C14F6EC for <ipv6@ietfa.amsl.com>; Mon, 24 Oct 2022 01:28:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level:
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dRIRpCPHH_5D for <ipv6@ietfa.amsl.com>; Mon, 24 Oct 2022 01:28:10 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9229BC1522B7 for <ipv6@ietf.org>; Mon, 24 Oct 2022 01:28:09 -0700 (PDT)
Received: from crumpet.local (unknown [89.101.70.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.netability.ie (Postfix) with ESMTPSA id 7AF839CDB0; Mon, 24 Oct 2022 09:28:06 +0100 (IST)
To: "Shihang(Vincent)" <shihang9=40huawei.com@dmarc.ietf.org>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
References: <166623196798.53565.15728669594489380137@ietfa.amsl.com> <14cee747bfbb464686a840996116a6c7@huawei.com>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <e207dff1-b960-5f09-ccf4-e0ea38c87ef3@foobar.org>
Date: Mon, 24 Oct 2022 09:28:04 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:52.0) Gecko/20100101 PostboxApp/7.0.58
MIME-Version: 1.0
In-Reply-To: <14cee747bfbb464686a840996116a6c7@huawei.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/cSL4IPPPlyYNkT8SNos16Wj66EA>
Subject: Re: [IPv6] FW: New Version Notification for draft-ls-6man-ipcomp-exclude-transport-layer-00.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Oct 2022 08:28:16 -0000

Shihang(Vincent) wrote on 24/10/2022 04:51:
> Hi 6MAN,
> I submitted a new draft about extensions to IPComp which compresses IP payload excluding transport layer and handles the out-of-order processing of compressed and un-compressed IP packet.
> 
> Looking forward to your review and comments.

couple of things on this draft:

- it's not clear that there is a need for a transport layer compression 
mechanism.  Application layer compression has been around for a long 
time and works well.

- as you identified in the draft, the mechanism proposed in this case 
will cause breakage:

>    [...]  Therefore, the
>    transport layer information such as source port and destination port
>    is compressed. [...]   If IPComp compressed those
>    transport layer information, the nodes along the packet's delivery
>    path can not obtain the source port and destination port.  Therefore
>    the IPComp is not compatible with the network functions requiring the
>    transport layer information which makes it harder to deploy.

Examples of things which require transport layer information: ECMP/LAG, 
filtering, control plane protection, etc.  If this information cannot be 
inspected, then this creates a serious regression for normal network 
function.

- in some cases, the output of a compression algorithm will be longer 
than the input. There is no indication in the draft how this would be 
handled.

Nick