Hi,
I would highly appreciate a clarification regarding the definition of End.DX2
behavior provided in Section 4.9 of RFC
8986<https://datatracker.ietf.org/doc/html/rfc8986#section-4.9>.
I am copying this definition for your convenience:
The End.DX2 SID MUST be the last segment in an SR Policy, and it is associated
with one outgoing interface I.
When N receives a packet destined to S and S is a local End.DX2 SID, N does the
following:
S01. When an SRH is processed {
S02. If (Segments Left != 0) {
S03. Send an ICMP Parameter Problem to the Source Address
with Code 0 (Erroneous header field encountered)
and Pointer set to the Segments Left field,
interrupt packet processing, and discard the packet.
S04. }
S05. Proceed to process the next header in the packet
S06. }
When processing the Upper-Layer header of a packet matching a FIB entry locally
instantiated as an End.DX2 SID, N does the following:
S01. If (Upper-Layer header type == 143(Ethernet) ) {
S02. Remove the outer IPv6 header with all its extension headers
S03. Forward the Ethernet frame to the OIF I
S04. } Else {
S05. Process as per Section 4.1.1
S06. }
The above definition does not say what happens if the outgoing interface I with
which ann SID with this behavior is associated fails. Specifically, whether it
is possible to reroute the received Ethernet frame - e,g., by encapsulating it
in SRv6 using a Service SID advertised by another PE and forwarding it
accordingly.
I have already asked this question in a slightly different form in my email
dated
11-Jun-20206<https://mailarchive.ietf.org/arch/msg/spring/tdhbTdYaEsCjlbF5IlLlDoWgsuY/>
and then reformulated this question in my email dated
14-Sep-2026<https://mailarchive.ietf.org/arch/msg/spring/rSJQpkPNRV6JxVKtNiTLVv5OB2o/>.
I will highly appreciated an answer from the authors of RFC 8986.
Regards, and lots of thanks in advance,
Sasha
Disclaimer
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 -- [email protected]
To unsubscribe send an email to [email protected]
