Hi all,
I have a technical question on the following aspect of the SR Replication
Segment for Multi-point Service Delivery
draft<https://datatracker.ietf.org/doc/html/draft-ietf-spring-sr-replication-segment-10#name-replication-segment>.
The draft states that:
A Replication segment is identified by the tuple <Replication-ID, Node-ID>,
where:¶<https://datatracker.ietf.org/doc/html/draft-ietf-spring-sr-replication-segment-10#section-2-2>
* Replication-ID: An identifier for a Replication segment that is unique in
context of the Replication
Node.¶<https://datatracker.ietf.org/doc/html/draft-ietf-spring-sr-replication-segment-10#section-2-3-1>
* Node-ID: The address of the Replication Node that the Replication segment
is for. Note that the root of a multi-point service is also a Replication Node.
A Replication segment includes the following
elements:¶<https://datatracker.ietf.org/doc/html/draft-ietf-spring-sr-replication-segment-10#section-2-5>
* Replication SID: The Segment Identifier of a Replication segment. This is
a SR-MPLS label or a SRv6 SID
[RFC8402<https://datatracker.ietf.org/doc/html/draft-ietf-spring-sr-replication-segment-10#RFC8402>].¶<https://datatracker.ietf.org/doc/html/draft-ietf-spring-sr-replication-segment-10#section-2-6-1>
* Downstream Nodes: Set of nodes in Segment Routing domain to which a
packet is replicated by the Replication
segment.¶<https://datatracker.ietf.org/doc/html/draft-ietf-spring-sr-replication-segment-10#section-2-6-2>
* Replication State: See below.
Replication State is a list of replication branches to the Downstream Nodes. In
this document, each branch is abstracted to a <Downstream Node, Downstream
Replication SID> tuple.
My question is:
Can the same "Downstream Replication ID in a given "Downstream Node" be
included/ in the Replication state of multiple Replication segments, especially
of Replication segments identified by different Node IDs?
I have not found any answer to this question in the text of the draft. At the
same time I think that a positive answer to my question would contradict the
definitions in Section 3.1 of the MVPN and EVPN with SR P2MP and Ingress
Replication
draft<https://datatracker.ietf.org/doc/html/draft-ietf-bess-mvpn-evpn-sr-p2mp-06#name-mpls-label>
because these definitions assume that the Replication SID can be used as the
"context label" for resolving the context label space space for looking up the
upstream allocated label advertised in the PTA attribute of the suitable
Mutlicast VPN route (in the case of aggregated P-tunnels).
IMHO and FWIW an explicit and unambiguous answer to my question should be
provided by the authors in order to advance the draft.
Regards, and lots of thanks in advance,
Sasha
Regards,
Sasha
From: spring <spring-boun...@ietf.org> On Behalf Of James Guichard
Sent: Tuesday, October 18, 2022 6:18 PM
To: SPRING WG <spring@ietf.org>
Cc: p...@ietf.org; spring-cha...@ietf.org
Subject: [EXTERNAL] [spring] WGLC for draft-ietf-spring-sr-replication-segment
Dear WG:
This email starts a 3 week Working Group Last Call for
draft-ietf-spring-sr-replication-segment [1].
Please read this document if you haven’t read the most recent version and send
your comments to the SPRING WG list no later than November 6th 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 response to indicate whether
you know of any undisclosed IPR related to this document.
Thanks!
Jim, Joel & Bruno
[1]
https://datatracker.ietf.org/doc/draft-ietf-spring-sr-replication-segment/<https://clicktime.symantec.com/15sLvRMR98Uy4qFgjBRVq?h=BxqfSEE4yhnFTweS-HkSx6apYbqZcVz9G_EXdBH6dp8=&u=https://datatracker.ietf.org/doc/draft-ietf-spring-sr-replication-segment/>
Notice: This e-mail together with any attachments may contain information of
Ribbon Communications Inc. and its Affiliates that is confidential and/or
proprietary for the sole use of the intended recipient. Any review, disclosure,
reliance or distribution by others or forwarding without express permission is
strictly prohibited. If you are not the intended recipient, please notify the
sender immediately and then delete all copies, including any attachments.
Notice: This e-mail together with any attachments may contain information of
Ribbon Communications Inc. and its Affiliates that is confidential and/or
proprietary for the sole use of the intended recipient. Any review, disclosure,
reliance or distribution by others or forwarding without express permission is
strictly prohibited. If you are not the intended recipient, please notify the
sender immediately and then delete all copies, including any attachments.
_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
