Consider what a simple TRACEROUTE over the SR path would reveal. If you wanted to get really fancy, consider traceroute with RFC 5837 extensions.
Ron Juniper Business Use Only From: Zafar Ali (zali) <z...@cisco.com> Sent: Friday, September 6, 2019 2:13 AM To: Ron Bonica <rbon...@juniper.net>; Rob Shakir <ro...@google.com>; SPRING WG List <spring@ietf.org>; 6...@ietf.org Cc: Zafar Ali (zali) <z...@cisco.com> Subject: Re: [spring] Beyond SRv6. Hi Ron, <snip> > For example, there is no need for an SRv6+ OAM document. It's just IPv6 and > IPv6 OAM just works. Really? How can you perform all OAM functions on a system that is based on a "label mapping table" using standard IPv6 OAM? If service provider has an issue with a (remote) mapping table, how would the provider debug it using the standard IPv6 OAM? Recall, IPv6 never had such "label mapping table" and hence never had to worry about debugging issues with the "label mapping table"
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring