Re: [Srcomp] CSID and VSID analysis in section 3
"Chengli (Cheng Li)" <c.l@huawei.com> Wed, 14 April 2021 01:44 UTC
Return-Path: <c.l@huawei.com>
X-Original-To: srcomp@ietfa.amsl.com
Delivered-To: srcomp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FCC43A11DB for <srcomp@ietfa.amsl.com>; Tue, 13 Apr 2021 18:44:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level:
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 V3wTSB0xoO_z for <srcomp@ietfa.amsl.com>; Tue, 13 Apr 2021 18:44:24 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC7AC3A11D4 for <srcomp@ietf.org>; Tue, 13 Apr 2021 18:44:23 -0700 (PDT)
Received: from fraeml744-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4FKlPx4kCnz680y3 for <srcomp@ietf.org>; Wed, 14 Apr 2021 09:34:29 +0800 (CST)
Received: from dggpemm100002.china.huawei.com (7.185.36.179) by fraeml744-chm.china.huawei.com (10.206.15.225) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Wed, 14 Apr 2021 03:44:19 +0200
Received: from dggpemm500003.china.huawei.com (7.185.36.56) by dggpemm100002.china.huawei.com (7.185.36.179) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Wed, 14 Apr 2021 09:44:17 +0800
Received: from dggpemm500003.china.huawei.com ([7.185.36.56]) by dggpemm500003.china.huawei.com ([7.185.36.56]) with mapi id 15.01.2106.013; Wed, 14 Apr 2021 09:44:17 +0800
From: "Chengli (Cheng Li)" <c.l@huawei.com>
To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, 'srcomp' <srcomp@ietf.org>
Thread-Topic: CSID and VSID analysis in section 3
Thread-Index: AdcwCBnBv3e0cbPwSleu03dSG5R47wAXgiUgABpeBJA=
Date: Wed, 14 Apr 2021 01:44:17 +0000
Message-ID: <a02a7abab3a64c838f2ff3c3242f3a6e@huawei.com>
References: <99f3c40cd00e4662b2ce50ea53d750a8@huawei.com> <BL0PR05MB5316DC3F5B4F05EF862E01BEAE4F9@BL0PR05MB5316.namprd05.prod.outlook.com>
In-Reply-To: <BL0PR05MB5316DC3F5B4F05EF862E01BEAE4F9@BL0PR05MB5316.namprd05.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.243.130]
Content-Type: multipart/alternative; boundary="_000_a02a7abab3a64c838f2ff3c3242f3a6ehuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/srcomp/9TFzbf4lmMXkLYxbjMdmgKUeccg>
Subject: Re: [Srcomp] CSID and VSID analysis in section 3
X-BeenThere: srcomp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <srcomp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/srcomp>, <mailto:srcomp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/srcomp/>
List-Post: <mailto:srcomp@ietf.org>
List-Help: <mailto:srcomp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/srcomp>, <mailto:srcomp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Apr 2021 01:44:29 -0000
Oh, If we allow that, yes. I just forgot that. Cheng From: Srcomp [mailto:srcomp-bounces@ietf.org] On Behalf Of Ron Bonica Sent: Tuesday, April 13, 2021 9:10 PM To: Chengli (Cheng Li) <c.l@huawei.com>; 'srcomp' <srcomp@ietf.org> Subject: Re: [Srcomp] CSID and VSID analysis in section 3 Cheng Li, Why can't the VSID satisfy the requirement in 3.2.2 using a binding SID? Ron Juniper Business Use Only From: Srcomp <srcomp-bounces@ietf.org<mailto:srcomp-bounces@ietf.org>> On Behalf Of Chengli (Cheng Li) Sent: Monday, April 12, 2021 9:57 PM To: 'srcomp' <srcomp@ietf.org<mailto:srcomp@ietf.org>> Subject: [Srcomp] CSID and VSID analysis in section 3 [External Email. Be cautious of content] Hi all, Here is my output of CSID and VSID in section 3. Thanks, Cheng 3.1<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-srcompdt-spring-compression-analysis-00*section-3.1__;Iw!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-RtjgJIT$>. SRv6 Based A solution to compress SRv6 SID Lists SHOULD be based on the SRv6 architecture, control plane and data plane. The compression solution MAY be based on a different data plane and control plane, provided that it derives sufficient benefit. This section records the use of SRv6 standards for compression. +-----------+------+-----+------+-------+ | | CSID | CRH | VSID | UIDSR | +-----------+------+-----+------+-------+ | U.RFC8402<https://urldefense.com/v3/__https:/tools.ietf.org/html/rfc8402__;!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-cguwU_H$> | Y | | Y | | | U.RFC8754<https://urldefense.com/v3/__https:/tools.ietf.org/html/rfc8754__;!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-SneBCkU$> | Y | | Y | | | U.PGM | Y | | Y | | | U.IGP | Y | | Y | | | U.BGP | Y | | Y | | | U.POL | Y | | Y | | | U.BLS | Y | | Y | | | U.SVC | Y | | Y | | | U.ALG | Y | | Y | | | U.OAM | Y | | Y | | +-----------+------+-----+------+-------+ Table 6: SRv6 Based Conclusion: 3.2<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-srcompdt-spring-compression-analysis-00*section-3.2__;Iw!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-dg2KU6r$>. Functional Requirements 3.2.1<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-srcompdt-spring-compression-analysis-00*section-3.2.1__;Iw!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-V0Q7itO$>. SRv6 Functionality A solution to compress an SRv6 SID list MUST support the functionality of SRv6. This requirement ensures no SRv6 functionality is lost. It is particularly important to understand Bonica, et al. Expires August 23, 2021 [Page 6] ________________________________ <https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-srcompdt-spring-compression-analysis-00*page-7__;Iw!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-TkZW9Mg$> Internet-Draft SRCOMP Requirements February 2021 how a proposal, as evaluated in section "SRv6 Based", provides this functionality. Functional requirements and the drafts defining how a proposal provides the functionality are documented in the table below. +------------------------------------------------------+ | Draft reference Abbreviations | +------------------------------------------------------+ | IDNETPGM: [I-D.ietf-spring-srv6-network-programming<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-srcompdt-spring-compression-analysis-00*ref-I-D.ietf-spring-srv6-network-programming__;Iw!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-bfL53wN$>] | | IDSRPOL: [I-D.ietf-spring-segment-routing-policy<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-srcompdt-spring-compression-analysis-00*ref-I-D.ietf-spring-segment-routing-policy__;Iw!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-V8C2SQO$>] | | IDEXT: [I-D.ietf-lsr-isis-srv6-extensions<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-srcompdt-spring-compression-analysis-00*ref-I-D.ietf-lsr-isis-srv6-extensions__;Iw!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-R8P6FgE$>] | | IDBGPSVC: [I-D.ietf-bess-srv6-services<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-srcompdt-spring-compression-analysis-00*ref-I-D.ietf-bess-srv6-services__;Iw!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-UBaw2pG$>] | | IDBGPLS: [I-D.ietf-idr-bgpls-srv6-ext<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-srcompdt-spring-compression-analysis-00*ref-I-D.ietf-idr-bgpls-srv6-ext__;Iw!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-bmncgYX$>] | | IDSVCP: [I-D.ietf-spring-sr-service-programming<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-srcompdt-spring-compression-analysis-00*ref-I-D.ietf-spring-sr-service-programming__;Iw!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-T4rZSYM$>] | | IDOAM: [I-D.ietf-6man-spring-srv6-oam<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-srcompdt-spring-compression-analysis-00*ref-I-D.ietf-6man-spring-srv6-oam__;Iw!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-YMtj90o$>] | | IDFLEXALG: [I-D.ietf-lsr-flex-algo<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-srcompdt-spring-compression-analysis-00*ref-I-D.ietf-lsr-flex-algo__;Iw!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-awS99LG$>] | | IDTILFA: [I-D.ietf-rtgwg-segment-routing-ti-lfa<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-srcompdt-spring-compression-analysis-00*ref-I-D.ietf-rtgwg-segment-routing-ti-lfa__;Iw!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-fqMCfs0$>] | +------------------------------------------------------+ +---------+------+-----+------+-------+ | | CSID | CRH | VSID | UIDSR | +---------+------+-----+------+-------+ | F.SID | Y | | Y | | | F.Scope | Y | | Y | | | F.PFX | Y | | Y | | | F.ADJ | Y | | Y | | | F.BIND | Y | | Y | | | F.PEER | Y | | Y | | | F.SVC | Y | | Y | | | F.ALG | Y | | Y | | | F.TILFA | Y | | Y | | | F.SEC | Y | | Y | | | F.IGP | Y | | Y | | | F.BGP | Y | | Y | | | F.POL | Y | | Y | | | F.BLS | Y | | Y | | | F.SFC | Y | | Y | | | F.PING | Y | | Y | | +---------+------+-----+------+-------+ Table 7: SRv6 Functionality Conclusion: Bonica, et al. Expires August 23, 2021 [Page 7] ________________________________ <https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-srcompdt-spring-compression-analysis-00*page-8__;Iw!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-eSzS321$> Internet-Draft SRCOMP Requirements February 2021 3.2.2<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-srcompdt-spring-compression-analysis-00*section-3.2.2__;Iw!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-cWsEiQC$>. Heterogeneous SID Lists The compression proposal SHOULD support a combination of compressed and non-compressed segments in a single path. As an example, a solution may satisfy this requirement without being SRv6 based by using a binding SID to impose an additional SRv6 header (IPv6 header plus optional SRH) with non-compressed SID. +-------------------------+------+-----+------+-------+ | | CSID | CRH | VSID | UIDSR | +-------------------------+------+-----+------+-------+ | Heterogeneous SID Lists | Y | | N | | +-------------------------+------+-----+------+-------+ Conclusion: 3.2.3<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-srcompdt-spring-compression-analysis-00*section-3.2.3__;Iw!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-ZZcIK8H$>. SID List Length The compression proposal MUST be able to represent SR paths that contain up to 16 segments. +-------------+------+-----+------+-------+ | | CSID | CRH | VSID | UIDSR | +-------------+------+-----+------+-------+ | 16 Segments | Y | | Y | | +-------------+------+-----+------+-------+ Conclusion: 3.2.4<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-srcompdt-spring-compression-analysis-00*section-3.2.4__;Iw!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-cyqMq1c$>. SID Summarization The solution MUST be compatible with segment summarization. In inter sub-domain deployments with summarization: o Any node can reach any other node in another sub-domain via a prefix segment. o Prefixes are summarized for advertisement between domains. Without summarization, border router SIDs must be leaked: o An additional global prefix segment is required for each domain border to be traversed. Bonica, et al. Expires August 23, 2021 [Page 8] ________________________________ <https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-srcompdt-spring-compression-analysis-00*page-9__;Iw!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-ZJaU4sF$> Internet-Draft SRCOMP Requirements February 2021 +-------------------+------+-----+------+-------+ | | CSID | CRH | VSID | UIDSR | +-------------------+------+-----+------+-------+ | SID Summarization | Y | | Y | | +-------------------+------+-----+------+-------+ Conclusion: 3.3<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-srcompdt-spring-compression-analysis-00*section-3.3__;Iw!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-cp6bjRG$>. Operational Requirements 3.3.1<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-srcompdt-spring-compression-analysis-00*section-3.3.1__;Iw!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-fSlFQD9$>. Lossless Compression A path traversed using a compressed SID list MUST always be the same as the path traversed using the uncompressed SID list if no compression was applied. +----------------------+------+-----+------+-------+ | | CSID | CRH | VSID | UIDSR | +----------------------+------+-----+------+-------+ | Lossless Compression | Y | | Y | | +----------------------+------+-----+------+-------+ Conclusion: 3.4<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-srcompdt-spring-compression-analysis-00*section-3.4__;Iw!!NEt6yMaO-gk!UZnqhTYxUuL0rIfenxzxw5p9KXtx2sd3K8FK_oQQxfN_p1SNpDT8JMkE-Wy_jZQ1$>. Scalability Requirements The compression proposal MUST be capable of representing 65000 adjacency segments per node. The compression proposal MUST be capable of representing 1 million prefix segments per SID numbering space. The compression proposal MUST be capable of representing 1 million services per node. +-------------------------------+------+-----+------+-------+ | | CSID | CRH | VSID | UIDSR | +-------------------------------+------+-----+------+-------+ | Adjacency Segment Scale 65000 | | | | | | Prefix Segment Scale 1000000 | Y | | Y | | | Service Scale 1000000 | | | | | +-------------------------------+------+-----+------+-------+ Table 8: Scale Requirements Conclusion:
- [Srcomp] CSID and VSID analysis in section 3 Chengli (Cheng Li)
- Re: [Srcomp] CSID and VSID analysis in section 3 Ron Bonica
- Re: [Srcomp] CSID and VSID analysis in section 3 Chengli (Cheng Li)