Re: [Srcomp] Analysis Text: Protocol Design
"xiechf@chinatelecom.cn" <xiechf@chinatelecom.cn> Tue, 23 March 2021 07:32 UTC
Return-Path: <xiechf@chinatelecom.cn>
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 511633A20D5 for <srcomp@ietfa.amsl.com>; Tue, 23 Mar 2021 00:32:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[HTML_MESSAGE=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 tjZ4-MFUdwwD for <srcomp@ietfa.amsl.com>; Tue, 23 Mar 2021 00:32:12 -0700 (PDT)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.223]) by ietfa.amsl.com (Postfix) with ESMTP id AA6003A20D2 for <srcomp@ietf.org>; Tue, 23 Mar 2021 00:32:11 -0700 (PDT)
HMM_SOURCE_IP: 172.18.0.48:11269.464678485
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-219.142.69.78?logid-9129f50512b14209ad37bcf321edeadf (unknown [172.18.0.48]) by chinatelecom.cn (HERMES) with SMTP id 7B2A7280094; Tue, 23 Mar 2021 15:32:13 +0800 (CST)
X-189-SAVE-TO-SEND: 66040161@chinatelecom.cn
Received: from ([172.18.0.48]) by App0024 with ESMTP id 9129f50512b14209ad37bcf321edeadf for c.l@huawei.com; Tue Mar 23 15:32:14 2021
X-Transaction-ID: 9129f50512b14209ad37bcf321edeadf
X-filter-score: filter<0>
X-Real-From: xiechf@chinatelecom.cn
X-Receive-IP: 172.18.0.48
X-MEDUSA-Status: 0
Sender: xiechf@chinatelecom.cn
Date: Tue, 23 Mar 2021 15:32:07 +0800
From: "xiechf@chinatelecom.cn" <xiechf@chinatelecom.cn>
To: "Chengli (Cheng Li)" <c.l@huawei.com>, "Darren Dukes (ddukes)" <ddukes=40cisco.com@dmarc.ietf.org>, srcomp <srcomp@ietf.org>
References: <BN6PR11MB4081C35F368C21A7837519C2C8649@BN6PR11MB4081.namprd11.prod.outlook.com>, <202103231514150988219@chinatelecom.cn>, <eb5df88217a743fc85d8588722425c2c@huawei.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.20.273[cn]
Mime-Version: 1.0
Message-ID: <2021032315320707935615@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart048174304324_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/srcomp/XT3snSILJUhOoDzzakOY98LD-H4>
Subject: Re: [Srcomp] Analysis Text: Protocol Design
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: Tue, 23 Mar 2021 07:32:17 -0000
Cheng, Thank you for your feedback, I view this from the perspective of the equipment, the co-exsitance happens within the same equipment ? Best regards Chongfeng xiechf@chinatelecom.cn From: Chengli (Cheng Li) Date: 2021-03-23 15:22 To: xiechf@chinatelecom.cn; Darren Dukes (ddukes); srcomp Subject: Re: [Srcomp] Analysis Text: Protocol Design Hi Chongfeng, This requirement says that the compression mechanism MUST be capable to co-exist with SRv6. It does not limit the gradation of the existing SRv6 device. The solution CAN NOT co-exist with SRv6 is not applicable with this requirement. So far, I think all compression mechanisms can be deployed with SRv6 simultaneously. Hope my answer address your question. Thanks, Cheng From: Srcomp [mailto:srcomp-bounces@ietf.org] On Behalf Of xiechf@chinatelecom.cn Sent: Tuesday, March 23, 2021 3:14 PM To: Darren Dukes (ddukes) <ddukes=40cisco.com@dmarc.ietf.org>; srcomp <srcomp@ietf.org> Subject: Re: [Srcomp] Analysis Text: Protocol Design Hi，folks I don't think this requirement is clear, does it mean "The compression proposal MUST support deployment in existing SRv6 networks without any upgradation or replacement of the existing SRv6-capable equipment" or not? Thanks! Chognfeng xiechf@chinatelecom.cn From: Darren Dukes \(ddukes\) Date: 2021-03-23 10:32 To: srcomp@ietf.org Subject: [Srcomp] Analysis Text: Protocol Design Following up on last week’s actions, attached is the protocol design analysis text 4. Protocol Design Requirements 4.1. SRv6 Base Coexistance The compression proposal MUST support deployment in existing SRv6 networks. +-----------------------+------+-----+------+-------+ | | CSID | CRH | VSID | UIDSR | +-----------------------+------+-----+------+-------+ | SRv6 Base Coexistence | Yes | Yes | Yes | | +-----------------------+------+-----+------+-------+ Conclusion: All proposals can be deployed simultaneously with the SRv6 base solution.
- [Srcomp] Analysis Text: Protocol Design Darren Dukes (ddukes)
- Re: [Srcomp] Analysis Text: Protocol Design xiechf@chinatelecom.cn
- Re: [Srcomp] Analysis Text: Protocol Design Chengli (Cheng Li)
- Re: [Srcomp] Analysis Text: Protocol Design xiechf@chinatelecom.cn
- Re: [Srcomp] Analysis Text: Protocol Design Chengli (Cheng Li)
- Re: [Srcomp] Analysis Text: Protocol Design xiechf@chinatelecom.cn
- Re: [Srcomp] Analysis Text: Protocol Design Chengli (Cheng Li)
- Re: [Srcomp] Analysis Text: Protocol Design xiechf@chinatelecom.cn
- Re: [Srcomp] Analysis Text: Protocol Design Ron Bonica
- Re: [Srcomp] Analysis Text: Protocol Design Ron Bonica