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

"zhaofeng@caict.ac.cn" <zhaofeng@caict.ac.cn> Thu, 28 May 2020 04:06 UTC

Return-Path: <zhaofeng@caict.ac.cn>
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 688263A0BB2 for <ipv6@ietfa.amsl.com>; Wed, 27 May 2020 21:06:01 -0700 (PDT)
X-Quarantine-ID: <DBDR4E48-Fj5>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 09 hex): References: ...438-68F7-412B-8CC2-9E456F15A3CD@gmail.com>,
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 DBDR4E48-Fj5 for <ipv6@ietfa.amsl.com>; Wed, 27 May 2020 21:05:58 -0700 (PDT)
Received: from caict.ac.cn (mail.caict.ac.cn [106.38.3.229]) by ietfa.amsl.com (Postfix) with ESMTP id 881833A0BB6 for <ipv6@ietf.org>; Wed, 27 May 2020 21:05:56 -0700 (PDT)
Received: from LAPTOP-NAK0KB4A (unknown [10.2.98.49]) by app1 (Coremail) with SMTP id H0IICgCn3pSiOM9ec74MAA--.19220S2; Thu, 28 May 2020 12:05:54 +0800 (CST)
Date: Thu, 28 May 2020 12:05:54 +0800
From: "zhaofeng@caict.ac.cn" <zhaofeng@caict.ac.cn>
To: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
Subject: RE: Adoption Call for "The IPv6 Compact Routing Header (CRH)"
References: <4224A438-68F7-412B-8CC2-9E456F15A3CD@gmail.com>,
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.10.151[cn]
Mime-Version: 1.0
Message-ID: <2020052812055437347113@caict.ac.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart758202031031_=----"
X-CM-TRANSID: H0IICgCn3pSiOM9ec74MAA--.19220S2
X-Coremail-Antispam: 1UD129KBjDUn29KB7ZKAUJUUUUU529EdanIXcx71UUUUU7v73 VFW2AGmfu7bjvjm3AaLaJ3UjIYCTnIWjp_UUUOr7k0a2IF6F4UM7kC6x804xWl14x267AK xVWUJVW8JwAFc2x0x2IEx4CE42xK8VAvwI8IcIk0rVWrJVCq3wAFIxvE14AKwVWUJVWUGw A2ocxC64kIII0Yj41l84x0c7CEw4AK67xGY2AK021l84ACjcxK6xIIjxv20xvE14v26F1j 6w1UM28EF7xvwVC0I7IYx2IY6xkF7I0E14v26r4UJVWxJr1l84ACjcxK6I8E87Iv67AKxV W0oVCq3wA2z4x0Y4vEx4A2jsIEc7CjxVAFwI0_GcCE3s1le2I262IYc4CY6c8Ij28IcVAa Y2xG8wAqx4xG67k08I80eVWUJVW8JwAqx4xG6c804VAFz4xC04v7Mc02F40Ew4AK048IF2 xKxVWUJVW8JwAqx4xG6xAIxVCFxsxG0wAv7VC0I7IYx2IY67AKxVWUJVWUGwAv7VC2z280 aVAFwI0_Jr0_Gr1lOx8S6xCaFVCjc4AY6r1j6r4UM4x0Y48IcxkI7VAKI48JM4xvF2IEb7 IF0Fy264kE64k0F24l42xK82IYc2Ij64vIr41l4I8I3I0E4IkC6x0Yz7v_Jr0_Gr1lx2Iq xVAqx4xG67AKxVWUGVWUWwC20s026x8GjcxK67AKxVWUGVWUWwC2zVAF1VAY17CE14v26r 1Y6r17MIIYrxkI7VAKI48JMIIF0xvE2Ix0cI8IcVAFwI0_Jr0_JF4lIxAIcVC0I7IYx2IY 6xkF7I0E14v26r1j6r4UMIIF0xvE42xK8VAvwI8IcIk0rVWrJr0_WFyUJwCI42IY6I8E87 Iv67AKxVWUJVW8JwCI42IY6I8E87Iv6xkF7I0E14v26r1j6r4UMVCEFcxC0VAYjxAxZFUv cSsGvfC2KfnxnUUI43ZEXa7IU8zpBDUUUUU==
X-CM-SenderInfo: p2kd0wxhqjquhdlf3hldfou0/
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/1ACujSD44ewBD8vZSEWChxDbMKA>
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 04:06:02 -0000

Hi 6man,
 
I do not support the adoption.
CRH is not compatible with SRv6 and SRH.CRH has many associated control plane and data plane drafts. However, it is unclear on how these various pieces of work fit together. The working group need the proper understanding on the overall architecture before adoption this draft.
 
In my option,SRv6 compression should be done based on SRv6. Regarding SRv6 compression, I prefer G-SRv6 instead of CRH.
 
Therefore, right now is not a good timing to adopt CRH or even any other solution.
 
Best regards,

Zhao Feng

China Academy of Information and Communication Technology