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

Xing Li <xing@cernet.edu.cn> Fri, 22 May 2020 02:08 UTC

Return-Path: <xing@cernet.edu.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 945D93A0DB5 for <ipv6@ietfa.amsl.com>; Thu, 21 May 2020 19:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 wLSyL5Su7Owc for <ipv6@ietfa.amsl.com>; Thu, 21 May 2020 19:08:48 -0700 (PDT)
Received: from zg8tmty1ljiyny4xntqumjca.icoremail.net (zg8tmty1ljiyny4xntqumjca.icoremail.net [165.227.154.27]) by ietfa.amsl.com (Postfix) with SMTP id 1F11B3A0D6A for <ipv6@ietf.org>; Thu, 21 May 2020 19:08:47 -0700 (PDT)
Received: from [192.168.1.102] (unknown [202.112.61.202]) by app-1 (Coremail) with SMTP id DwQGZQD3_2cmNMdeLOoDAg--.12231S2; Fri, 22 May 2020 10:08:39 +0800 (CST)
Message-ID: <5EC73427.2040603@cernet.edu.cn>
Date: Fri, 22 May 2020 10:08:39 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: "Zafar Ali (zali)" <zali@cisco.com>
CC: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>, Xing Li <xing@cernet.edu.cn>
Subject: Re: Adoption Call for "The IPv6 Compact Routing Header (CRH)"
References: <19D30186-B180-4F65-BF00-7AD07CEF3925@gmail.com> <5EBF511D.7080306@cernet.edu.cn> <E5EF8FA7-6A17-4A77-96DC-0BB04DA502D4@cisco.com>
In-Reply-To: <E5EF8FA7-6A17-4A77-96DC-0BB04DA502D4@cisco.com>
Content-Type: multipart/alternative; boundary="------------030005070704050701080903"
X-CM-TRANSID: DwQGZQD3_2cmNMdeLOoDAg--.12231S2
X-Coremail-Antispam: 1UD129KBjvJXoWxXw13GF1DCrWDCw1DWry8Xwb_yoWrGry5pF W3Gr17trWkAF18Jr1kJr10qF15JrykJ3y7Jr1Dtr18Jr15CF10qr1jqr10qa4UArW8Jr4j qr1Utr1UZw1UArJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUQj14x267AKxVW8JVW5JwAFc2x0x2IEx4CE42xK8VAvwI8IcIk0 rVWrJVCq3wAFIxvE14AKwVWUJVWUGwA2ocxC64kIII0Yj41l84x0c7CEw4AK67xGY2AK02 1l84ACjcxK6xIIjxv20xvE14v26r1j6r1xM28EF7xvwVC0I7IYx2IY6xkF7I0E14v26r4j 6F4UM28EF7xvwVC2z280aVAFwI0_Cr0_Gr1UM28EF7xvwVC2z280aVCY1x0267AKxVW8Jr 0_Cr1UM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrVAYj202j2C_Xr0_Wr1l5I8CrVAK z4kIr2xC04v26r1j6r4UMc02F40E42I26xC2a48xMc02F40ExcI2r2IE04Ijxs4lYx0E2I x0cI8IcVAFwI0_Jr0_Jr4lYx0Ex4A2jsIE14v26r1j6r4UMcvjeVCFs4IE7xkEbVWUJVW8 JwACjcxG0xvEwIxGrwACjI8F5VA0II8E6IAqYI8I648v4I1l7480Y4vEI4kI2Ix0rVAqx4 xJMxkF7I0Ew4C26cxK6c8Ij28IcwCY02Avz4vE14v_Gr1l42xK82IYc2Ij64vIr41l4I8I 3I0E4IkC6x0Yz7v_Jr0_Gr1lx2IqxVAqx4xG67AKxVWUGVWUWwC20s026x8GjcxK67AKxV WUGVWUWwC2zVAF1VAY17CE14v26r1q6r43MIIYrxkI7VAKI48JMIIF0xvE2Ix0cI8IcVAF wI0_Jr0_JF4lIxAIcVC0I7IYx2IY6xkF7I0E14v26r1j6r4UMIIF0xvE42xK8VAvwI8IcI k0rVWrZr1j6s0DMIIF0xvEx4A2jsIE14v26r4j6F4UMIIF0xvEx4A2jsIEc7CjxVAFwI0_ Gr0_Gr1UYxBIdaVFxhVjvjDU0xZFpf9x0JUTwZcUUUUU=
X-CM-SenderInfo: p0lqwqxfhu0vvwohv3gofq/
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/krWwKCXyOObC6P8mGTbmMxgOSyo>
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: Fri, 22 May 2020 02:08:52 -0000

Hi, Zafar,

Zafar Ali (zali) 写道:
>
> Hi Xing,
>
>  
>
> Is there any documentation you could share, e.g., on the trial of "CRH 
> can co-exist with SRv6 in the backbone"?
>
Currently there are only internal documents. If people are interested, 
we may submit an ID in v6ops  ^_^.

I can share some information here.

CERNET2 is an IPv6-only backbone,  the routing for internal 
infrastructure is via IS-IS and the customer  and external routes are 
via BGP. The CERNET2  backbone has four vendors.


We have done 3 type of testing.


(1) SRv6 enabled points are using Linux open source  (static routing).
(2) SRv6 enabled points are using one vendor's equipment (static routing).
(3) CRH enabled points are using another vendor's implementation (IS-IS).

The SRv6 and SRH testing  pathes are  cross different vendors and 
running  concurrently,

We are in the process to conduct more testings.

Regards,

xing

>  
>
> Thanks
>
>  
>
> Regards … Zafar
>
>  
>
> *From: *ipv6 <ipv6-bounces@ietf.org> on behalf of Xing Li 
> <xing@cernet.edu.cn>
> *Date: *Friday, May 15, 2020 at 10:48 PM
> *To: *Bob Hinden <bob.hinden@gmail.com>
> *Cc: *IPv6 List <ipv6@ietf.org>
> *Subject: *Re: Adoption Call for "The IPv6 Compact Routing Header (CRH)"
>
>  
>
> 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.
>
>  
>
> Regards,
>
>  
>
> xing
>
> CERNET Center
>
>  
>
>  
>
> 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
>
>      
>
>       https://tools.ietf.org/html/draft-bonica-6man-comp-rtg-hdr
>
>      
>
>     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
>
>     ipv6@ietf.org <mailto:ipv6@ietf.org>
>
>     Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>
>     --------------------------------------------------------------------
>
>      
>
>  
>
>  
>
> --------------------------------------------------------------------
>
> IETF IPv6 working group mailing list
>
> ipv6@ietf.org <mailto:ipv6@ietf.org>
>
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>
> --------------------------------------------------------------------
>
>  
>