Dear WG,
I don't support WG adoption.
It is not a new idea for each Virtual Network to have its own SIDs.
e.g. The earlist description of the SID be allocated per flex-algorithm and
related metric
information was in draft-hegdeppsenak-isis-sr-flex-algo-00(2017.7.17) (now is
draft-ietf-isis-sr-flex-algo) .
The earlist description of the SID be allocated per MT was in
draft-filsfils-spring-segment-routing-04(2014.7.3)
(now is RFC8402 ), and draft-peng-lsr-network-slicing-00(2019.2.25) describe the
SID be allocated per AII(alias alice). For slice resources,
https://tools.ietf.org/html/draft-peng-teas-network-slicing-03
induced slice-id(AII) for slice resources management, and can differentiate
them (e.g. L2 link or L3 interface,
section 7 ), and how to compute SR-BE or SR-TE path according to AII combined
with other criteria.
Regards,
Ran
-----Original Message-----From: spring <[email protected]> On Behalf Of
James GuichardSent: Wednesday, July 15, 2020 8:17 PMTo: [email protected]:
[email protected]: [spring] WG Adoption Call for
draft-dong-spring-sr-for-enhanced-vpnDear WG: This email begins a 2 week WG
adoption call for
https://datatracker.ietf.org/doc/draft-dong-spring-sr-for-enhanced-vpn/
<https://datatracker.ietf.org/doc/draft-dong-spring-sr-for-enhanced-vpn/>
ending Wednesday 29th July 2020. Please speak up if you support or oppose
adopting this document into the WG. Please also provide comments/reasons for
that support (or lack thereof). Silence will not be considered consent.
Thanks! Jim, Joel & Bruno
_______________________________________________spring mailing
[email protected]
_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring
