Hi  PIM & MSR6 :

I feel the last-calling document in SPRING may be useful to understand MSR6 and 
related work.

This Spring document[1] defines an SRv6 SID End.Replicate to perform a 
multipoint transport behavior statefully.
The MSR6 document[2] defines an SRv6 SID End.RGB to perform a multipoint 
transport behavior statelessly.

This Spring document [1] uses an SRv6 SID and IPv6 extension header.
The MSR6 document [2] uses an SRv6 SID and IPv6 extension header.

This document [1] clearly stated that “...to establish P2MP trees in SR domain”.
The document [3], as the preceding research of MSR6,  stated that, “… the 
BIERv6 domain is the same as SRv6 domain”.

This document [1] clearly demonstrates how the idea of “using a unicast 
forwarding plane to perform multipoint transport” is adopted.
This argument [4] about MSR6 is that “using a unicast forwarding plane to 
perform multipoint transport” is bad/failed idea (please correct me if I 
understand it wrong).

This Spring document[1] has reached its lastcall in the wide IETF community.
The MSR6 document [2], and the preceding research[3], has been blocked  since 
2019(may be earlier than the End.Replicate), and the claim about it had been 
variable over time:

l  Firstly, the claim was that, SRv6 is a new thing and unmature and some 
terriable hijack.

l  And then, the claim was that, it does not comply with BIER architecture.

l  And then, the claim was that, the BIER wg don’t need it or work on it.

l  And then, the claim was that, the MSR6 makes no difference than BIER.

l  And sometimes, the claim was that, using unicast forwarding plane is 
bad/failed (loop).
(Due to the so long timeline of these discussions, I do not have the link on 
each of above claim, but if it is interested, I can try to find them)

Thanks,
Jingrong

[1] 
https://datatracker.ietf.org/doc/draft-ietf-spring-sr-replication-segment/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-spring-sr-replication-segment%2F&data=05%7C01%7Cjames.n.guichard%40futurewei.com%7C754580bd81ff45ecdb9108dad152afe7%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638052450380683369%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Jf7bnxwWGDztXPD1FvW%2Bi%2BVAb3qnqOBUGudZK4KiGEY%3D&reserved=0>
[2] https://datatracker.ietf.org/doc/draft-lx-msr6-rgb-segment/
[3] https://datatracker.ietf.org/doc/html/draft-xie-bier-ipv6-encapsulation-10
[4] https://mailarchive.ietf.org/arch/msg/msr6/eMUWpjSbo3THJLEXe_t1Pt5PTyc/


本邮件及其附件可能含有华为公司的保密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件!
This e-mail and its attachments may contain confidential information from 
HUAWEI, which is intended only for the person or entity whose address is listed 
above. Any use of the information contained herein in any way (including, but 
not limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is prohibited. If you receive this 
e-mail in error, please notify the sender by phone or email immediately and 
delete it!

From: pim [mailto:pim-boun...@ietf.org] On Behalf Of James Guichard
Sent: Tuesday, November 29, 2022 12:26 AM
To: p...@ietf.org<mailto:p...@ietf.org>
Subject: [pim] Fwd: WGLC for draft-ietf-spring-sr-replication-segment

FYI

Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: James Guichard 
<james.n.guich...@futurewei.com<mailto:james.n.guich...@futurewei.com>>
Sent: Monday, November 28, 2022 10:10 AM
To: SPRING WG <spring@ietf.org<mailto:spring@ietf.org>>
Cc: spring-cha...@ietf.org<mailto:spring-cha...@ietf.org> 
<spring-cha...@ietf.org<mailto:spring-cha...@ietf.org>>
Subject: WGLC for draft-ietf-spring-sr-replication-segment

Dear WG:

This email starts a 2-week Working Group Last Call for 
https://datatracker.ietf.org/doc/draft-ietf-spring-sr-replication-segment/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-spring-sr-replication-segment%2F&data=05%7C01%7Cjames.n.guichard%40futurewei.com%7C754580bd81ff45ecdb9108dad152afe7%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638052450380683369%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Jf7bnxwWGDztXPD1FvW%2Bi%2BVAb3qnqOBUGudZK4KiGEY%3D&reserved=0>

Please read the updated document if you haven’t already and send your comments 
to the SPRING WG list no later than December 12th 2022.

If you are raising a point which you expect will be specifically debated on the 
mailing list, consider using a specific email/thread for this point.

Lastly, if you are an author or contributor please respond to indicate whether 
you know of any undisclosed IPR related to this document.

Thanks!

Jim, Joel & Bruno


_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Reply via email to