All

Andrew had mentioned an important gap that exists with transport networks
 and migration to SR and TDM CES emulation over packet PSN gap and possible
solutions such as migration to EVPN as well as supporting PW setup in
VPWS-EVPN.

Along those same lines of SR gaps that exist for operators migrating from
MPLS to SR here is another possible gap and wondering if it has been
addressed and possible solutions.

RSVP-TE is used extensively over the Internet using “auto bandwidth” PCALC
for cSPF paths  Path / Reserve messages for bandwidth management using PCE
or other vendor based modeling tools to manage TE tunnels usage.

SR-MPLS or SRv6 data planes using SR-TE policy candidate paths bound via
BSID to forwarding plane does not have a concept of PCALC due to non
existent RSVP State thus no bandwidth management.

How do operators that rely on PCALC auto bandwidth and as well that use
ACTN network slicing able to get the same bandwidth management
functionality with SR policy?

Another question related to inter AS SR-MPLS and SRv6?

With regards to inter-as SR-TE one of the major advantages with SR is that
SR-TE can be used to stitch the underlay LSP path together similar to inter
as option B with segmented LSP stitching.

This allows with the SRGB domain wide labels we can build the underlay LSP
and we don’t need inter-as options and use SR-TE color extended community
signaled by egress PE to signal color mapped to SID list that maps to the
VPN. On the inter-as PE-PE ASBR the BSID is popped and new BSID is pushed
onto the stack by source node using BSID to stitch the path.

This is one of the major advantages of SR as it gets around all the
scalability issue related to inter-as options.

Do we have any operators with production deployments SR-MPLS and SRv6 if
any exist of using SR-TE BSID for inter-as path stitching E2E EPE path
instead of inter-as options.

Kind Regards

Gyan




-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mis...@verizon.com <gyan.s.mis...@verizon.com>*



*M 301 502-1347*
_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Reply via email to