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

"Ran Pang(联通集团联通网络技术研究 院本部)" <> Thu, 28 May 2020 07:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 073033A0B97 for <>; Thu, 28 May 2020 00:39:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id GplwIIzR6M5F for <>; Thu, 28 May 2020 00:39:02 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 16A2F3A0B93 for <>; Thu, 28 May 2020 00:39:00 -0700 (PDT)
X-AuditID: 0a000f36-3b3ff7000000040e-b8-5ecf6a92e97d
Received: from M10-HQ-MLCEN06.cnc.intra (Unknown_Domain []) by (Symantec Messaging Gateway) with SMTP id 99.BE.01038.29A6FCE5; Thu, 28 May 2020 15:38:58 +0800 (HKT)
Received: from M10-HQ-ML08.hq.cnc.intra ( by M10-HQ-MLCEN06.cnc.intra ( with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 28 May 2020 15:38:57 +0800
Received: from M10-HQ-ML02.hq.cnc.intra ( by M10-HQ-ML08.hq.cnc.intra ( with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 28 May 2020 15:38:49 +0800
Received: from M10-HQ-ML02.hq.cnc.intra ([fe80::71a2:51ba:f284:c52b]) by M10-HQ-ML02.hq.cnc.intra ([fe80::71a2:51ba:f284:c52b%20]) with mapi id 15.00.1497.006; Thu, 28 May 2020 15:38:49 +0800
From: =?utf-8?B?UmFuIFBhbmco6IGU6YCa6ZuG5Zui6IGU6YCa572R57uc5oqA5pyv56CU56m2?= =?utf-8?B?6Zmi5pys6YOoKQ==?= <>
To: Bob Hinden <>, IPv6 List <>
Subject: Re: Adoption Call for "The IPv6 Compact Routing Header (CRH)"
Thread-Topic: Adoption Call for "The IPv6 Compact Routing Header (CRH)"
Thread-Index: AQHWNLhRNc0GPo2V/EePgbdH23EGBA==
Date: Thu, 28 May 2020 07:38:49 +0000
Message-ID: <defcf5c6292345e7a333d600c4f47561@M10-HQ-ML02.hq.cnc.intra>
References: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_defcf5c6292345e7a333d600c4f47561M10HQML02hqcncintra_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrGIsWRmVeSWpSXmKPExsXC9fOKiu6krPNxBr83slpsfb+PzeLl2fdM DkweO2fdZfdYsuQnUwBTFJdNSmpOZllqkb5dAlfGwbdHWQsOBFfcX3KDsYFxRmAXIyeHhICJ RHfHR+YuRi4OIYHzjBLLl2xgg3B2MEqs336AFc5Zu/EblHMYyJlwAayMTaCNUWLnx2VMIMNE BBwkjs7rZwOxhQXcJNpPPGCFiLtLHL35hQ3C1pOYtusvmM0ioCpxadNMMJsXqGbGxNlgtpCA jcSRg3vZQWxGAVmJaY/ug81nFhCXmDttFivE4QISS/acZ4awRSVePv4HFTeQ2Lp0HwuErSCx vOceI0RvtkTvin2sELsEJU7OfMICsUtZovn4dNYJjGKzkKyYhaRlFpKWWYwcQHFNifW79CFK FCWmdD9kh7A1JFrnzGVHFl/AyL6KUTLY193C2MJA199ELzkjMy+xNC8zOT9XLzlvEyMoKhn4 zXYwfrn1Qe8QIxMH4yFGCQ5mJRFep7On44R4UxIrq1KL8uOLSnNSiw8xSnOwKInzcqquihMS SE8sSc1OTS1ILYLJMnFwSjUwzXJ1Fpud5FgrEPf1wPOzfl9u13ZNiZVzzbHMSpboq6uqaHMT c1yYsCi0xWxXncUht3M1zK85uheo9CVK58eEmsavXVh1furea3p11Zs8Y2IW9RzMLCtX09z0 cHkV0xKdRjONmO/6a9axrnnFenzy88a4/S9Zecx8Lm0z/XHnaZvefkb9uV/l2DLSZrqmTJVJ alMy7zrnn+v3seFw24zNG+8rS5tP1Ij/eMqX8/D1Sp07RVcmhtSyRRxLq1I+8UHMdrXmRv8P FhVGtX2lLdXx3ZfemWQJfi0+Ny1VfoHeY1uB5MkKly49CDmnvbb7x+WL2RHfenX1F9lsmbCk LWeP29HAFT/PqQn3evClLVdiKc5INNRiLipOBACMjWDSOQMAAA==
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: Thu, 28 May 2020 07:39:05 -0000

Hi WG,

It seems like CRH is not compatible with SRv6 and SRH. We need to discuss how CRH cooperates with uSID, G-SRv6 or other SRv6 header compression solutions before adoption, or whether CRH will cause difficulties in the deployment of G-SRv6 and other solutions. At present, we tend to choose solutions compatible with SRH.


From: Bob Hinden<>
Date: 2020-05-16 06:13
To: IPv6 List<>
CC: Bob Hinden<>
Subject: Adoption Call for "The IPv6 Compact Routing Header (CRH)"
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.

Bob and Ole

如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our.