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

Xing Li <> Sat, 16 May 2020 02:47 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0046C3A08C5 for <>; Fri, 15 May 2020 19:47:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id NE0aXgLVy9Ly for <>; Fri, 15 May 2020 19:47:20 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id C6A8C3A08C0 for <>; Fri, 15 May 2020 19:47:18 -0700 (PDT)
Received: from [] (unknown []) by app-3 (Coremail) with SMTP id EQQGZQAXF8QxVL9eMTGTAg--.61005S2; Sat, 16 May 2020 10:47:14 +0800 (CST)
Message-ID: <>
Date: Sat, 16 May 2020 10:34:05 +0800
From: Xing Li <>
User-Agent: Thunderbird (Windows/20100228)
MIME-Version: 1.0
To: Bob Hinden <>
CC: IPv6 List <>, Xing Li <>
Subject: Re: Adoption Call for "The IPv6 Compact Routing Header (CRH)"
References: <>
In-Reply-To: <>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Coremail-Antispam: 1UD129KBjvJXoW7AF45Gw4kAryxXw13GF17Jrb_yoW8uFWfpF ZxGr13Jrs8tr18GryxJr18WF45AryrJFW7Ar1Utr1Fyr15C3W8Kr1UtrnYqa4UAryrJF4j qr1Utr1DJw10yrJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUvG14x267AKxVWUJVW8JwAFc2x0x2IEx4CE42xK8VAvwI8IcIk0 rVWrJVCq3wAFIxvE14AKwVWUJVWUGwA2ocxC64kIII0Yj41l84x0c7CEw4AK67xGY2AK02 1l84ACjcxK6xIIjxv20xvE14v26r1I6r4UM28EF7xvwVC0I7IYx2IY6xkF7I0E14v26r4j 6F4UM28EF7xvwVC2z280aVAFwI0_Cr0_Gr1UM28EF7xvwVC2z280aVCY1x0267AKxVW8Jr 0_Cr1UM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrVACY4xI64kE6c02F40Ex7xfMcIj 6xIIjxv20xvE14v26r106r15McIj6I8E87Iv67AKxVWUJVW8JwAm72CE4IkC6x0Yz7v_Jr 0_Gr1lF7xvr2IY64vIr41lF7I21c0EjII2zVCS5cI20VAGYxC7MxkF7I0Ew4C26cxK6c8I j28IcwCY02Avz4vE14v_Gr1l42xK82IYc2Ij64vIr41l4I8I3I0E4IkC6x0Yz7v_Jr0_Gr 1lx2IqxVAqx4xG67AKxVWUJVWUGwC20s026x8GjcxK67AKxVWUGVWUWwC2zVAF1VAY17CE 14v26r126r1DMIIYrxkI7VAKI48JMIIF0xvE2Ix0cI8IcVAFwI0_Jr0_JF4lIxAIcVC0I7 IYx2IY6xkF7I0E14v26r1j6r4UMIIF0xvE42xK8VAvwI8IcIk0rVWrJr0_WFyUJwCI42IY 6I8E87Iv67AKxVW8JVWxJwCI42IY6I8E87Iv6xkF7I0E14v26r4j6r4UJbIYCTnIWIevJa 73UjIFyTuYvjfU8FApUUUUU
X-CM-SenderInfo: p0lqwqxfhu0vvwohv3gofq/
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 16 May 2020 02:47:23 -0000

I support WG adoption. CRH.

We have tested the SRv6 and CRH in CERNET2 (which is one of the largest 
IPv6-only backbones in the world). Both techniques work smoothly. 

One of the important fact is that the CRH can operate with current IS-IS 
support of different vendors in the CERNET2 backbone and CRH can 
co-exist with SRv6 in the backbone.

In summary, as an operator, we see the great value of CRH and therefore 
support its WG adoption.



Bob Hinden 写道:
> This message starts a two-week 6MAN call on adopting:
>  Title:          The IPv6 Compact Routing Header (CRH)
>  Authors:        R. Bonica, Y. Kamite, T. Niwa, A. Alston, L. Jalil
>  File Name:      draft-bonica-6man-comp-rtg-hdr-21
>  Document date:  2020-05-14
> as a working group item. Substantive comments regarding adopting this document should be directed to the mailing list.  Editorial suggestions can be sent to the authors.
> Please note that this is an adoption call, it is not a w.g. last call for advancement, adoption means that it will become a w.g. draft.  As the working group document, the w.g. will decide how the document should change going forward.
> This adoption call will end on 29 May 2020.
> The chairs note there has been a lot of discussions on the list about this draft.   After discussing with our area directors, we think it is appropriate to start a working group adoption call.  The authors have been active in resolving issues raised on the list.
> Could those who are willing to work on this document, either as contributors, authors or reviewers please notify the list.   That gives us an indication of the energy level in the working group
> to work on this.
> Regards,
> Bob and Ole
> ------------------------------------------------------------------------
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> Administrative Requests:
> --------------------------------------------------------------------