Hi Yubao, Thanks for your email. Please check inline below.
On Thu, Mar 3, 2022 at 8:20 AM <[email protected]> wrote: > > Hi authors, > > > > I reviewed this draft and I don't understand this sentence very > well: "The SRv6 Endpoint behavior of the Service SID thus signaled *is > entirely up to the originator* of the advertisement" > KT> Indeed. The egress PE is the one that picks the SRv6 SID to be signaled with the specific route. > Is it saying that when PE1 receives an Ethernet A-D per ES route whose > SRv6 SID Information Sub-TLV's SRv6 Endpoint Behavior field is set to X > （where X is not 0xFFFF), > > that Ethernet A-D per ES route should be indifferently processed by PE1 > no matter what value will X be set to? > KT> I am not sure of the draft text that you are referring to when drawing up this inference. For SRv6 SID behaviors that use arguments (e.g. Ethernet A-D per ES routes with behavior End.DT2M), it is necessary for the ingress PE to not be indifferent to the behavior since it needs to put the argument part correctly in the SRv6 SID used on the data path. > > Is it necessary for the receiver-side processing of Ethernet A-D per ES > route's Endpoint Behavior field to be clearly described? > KT> Sec 6.3 is where the egress PE processing and use of the ARG received via the Ethernet A-D per ES route with the SRv6 SID received along with Route Type 3 is described. Thanks, Ketan > > Thanks, > > Yubao > > > >
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
