RE: Adoption Call for "The IPv6 Compact Routing Header (CRH)"

wangyali <wangyali11@huawei.com> Thu, 28 May 2020 06:47 UTC

Return-Path: <wangyali11@huawei.com>
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 408753A0B48 for <ipv6@ietfa.amsl.com>; Wed, 27 May 2020 23:47:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-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 hjlC4NIinXTQ for <ipv6@ietfa.amsl.com>; Wed, 27 May 2020 23:47:56 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0606C3A0B47 for <ipv6@ietf.org>; Wed, 27 May 2020 23:47:56 -0700 (PDT)
Received: from lhreml724-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 02C98F10395AE541F676; Thu, 28 May 2020 07:47:53 +0100 (IST)
Received: from lhreml724-chm.china.huawei.com (10.201.108.75) by lhreml724-chm.china.huawei.com (10.201.108.75) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Thu, 28 May 2020 07:47:52 +0100
Received: from DGGEML424-HUB.china.huawei.com (10.1.199.41) by lhreml724-chm.china.huawei.com (10.201.108.75) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Thu, 28 May 2020 07:47:52 +0100
Received: from DGGEML524-MBX.china.huawei.com ([169.254.1.54]) by dggeml424-hub.china.huawei.com ([10.1.199.41]) with mapi id 14.03.0487.000; Thu, 28 May 2020 14:47:47 +0800
From: wangyali <wangyali11@huawei.com>
To: "bob.hinden@gmail.com" <bob.hinden@gmail.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: Adoption Call for "The IPv6 Compact Routing Header (CRH)"
Thread-Topic: Adoption Call for "The IPv6 Compact Routing Header (CRH)"
Thread-Index: AdY0u13z33yTyGPlSHGwylndYNNclw==
Date: Thu, 28 May 2020 06:47:47 +0000
Message-ID: <1520992FC97B944A9979C2FC1D7DB0F404E7B4FE@dggeml524-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.203.65]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/dRnFShEzIsJS8U_MsI64VyKPGYo>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 28 May 2020 06:47:57 -0000

Hi 6man,

As far as I know, there are several compression solutions proposed. I think it's better to have a architecture described, to analyses the use cases, and see if several compression solution can coexist. Otherwise, we can compare pros and cons, and choose the best for the industry. IMHO, it's just not the right timing to adopt this work.

Best regards,
Yali