Re: Header Insertion and TI-FA

[Gyan Mishra <[e-mail]>]

On Tue, May 12, 2020 at 12:06 AM Andrew Alston <
[e-mail]> wrote:

> I believe how we get around AH issue from a customer endpoint flow is that
> the customer flow is tunneled, h.encap,  so sits in the payloadend to end
> customer packet remains unaltered so their is no impact to end to end
> customer flows if AH is used by any endpoint customer cuz. As far as the
> outer header H.encap that happens on the SR source or TI-LFA merge point
> the closer domain intra or inter domain SRv6 comes into play and if the
> operator tries to use AH instead of ESP the operator that would be broken.
> The operator would have to aware to not try to use AH and to use ESP
> instead.
>
> [AA] Gyan - my problem here is that as you state - the operator would have
> to be aware - now correct me if I am wrong - but that seems to imply that
> implementation of this could break existing deployments unless the existing
> deployments were modified - and I quote from the spring charter
>
> SPRING WG should avoid modification to existing data planes that would make
> them incompatible with existing deployments.
>

   Gyan> Very Good point.  Mangling of EH insertion or deletion is
modifying the existing IPv6 data plane and a violation of the SR charter.
Agreed. So this would be brown field existing deployments that was let’s
say LDPv6 a v6 only core that was being converted to SRv6 hypothetical real
world example.  So in this case the LDPv6 data plan would have accommodated
AH, however when upgraded to support SRv6 AH would be broken.

>
>
> Andrew
>
>>
> --

Gyan  Mishra

Network Engineering & Technology

Verizon

Silver Spring, MD 20904

Phone: [phone]

Email: [e-mail]