Hi Gyan, >Gyan>I understand the issue with the ASPA path verification, however if the RS >AS added to ASPA then that would influence the forwarding plane is the issue. >How do you insert RS AS for the ASPA path verification but not allow RS to be >part of forwarding plane? I guess you could do a next-hop-unchanged between >the clients connected through the RS.
Is this the confirmation (from RFC7947, Sec. 2.2.1) that you are looking for? "... As the route server does not participate in the actual routing of traffic, the NEXT_HOP attribute MUST be passed unmodified to the route server clients,..." Sriram _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
