Re: [spring] My question at the mike about draft-dong-spring-srv6-inter-layer-programming

Hi Sasha,

Your point is very valid and I assumed that the optical path is IP enabled
but there is no routing protocol running over it. There may be a mix up
between the terms L3 adjacency and IGP adjacency.

RFC8986 Section 4.2 End.X works for L3 adjacency (with or without routing
protocol running over the link) as well as L2 bundle members of an L3 LAG
interface. In all cases, the neighbor resolution and handling for IP
packets is expected.

Thanks,
Ketan

On Tue, Nov 8, 2022 at 3:57 PM Alexander Vainshtein <
Alexander.Vainshtein@rbbn.com> wrote:

> Hi,
>
> I would like to repeat the question I have asked at the mike during the
> SPRING WG session today about
> draft-dong-spring-srv6-inter-layer-programming
> <https://datatracker.ietf.org/doc/html/draft-dong-spring-srv6-inter-layer-programming-04>
> :
>
>
>
> How would the node that has allocated an End.XU SID for a specific
> underlay link (i.e., non-IP) identify the Layer 2 encapsulation that has to
> be pushed on the packet with the End.XU SID exposed?
>
>
>
> The reference to End.X behavior in Section 4.2 of RFC 8986
> <https://datatracker.ietf.org/doc/html/rfc8986#section-4.2> looks
> incorrect to me since End.X explicitly speaks about a L3 X-connect and
> usual Layer 2 helpers ARP and/or ND) would be applicable.
>
> But this is not the case for a path for a non-IP path IMHO.
>
>
>
> I may have missed the details of the response by the presenter, but my gut
> feeling is that my question has not been answered.
>
>
>
> Regards, and thanks n advance for the feedback,
>
> Sasha
>
>
>
> 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
>