draft-litkowski-spring-non-protected-paths-00
S. Litkowski, Orange
M. Aissaoui, Nokia
IETF 97 Seoul
Problem statement
• Customer are requesting non protected paths
(because protection may be end-to-end)
• Multiple solutions may be used in SPRING
• We need to have a single recommended solution
to ensure deployability
The draft
• It presents the various solutions
• We have some constraints with SPRING-TE: MSD
and loadbalancing !
• It tries to highlight pros/cons
– We are providing a very first overview in -00, it should
be augmented in the next release !
• Final outcome would be a recommended solution
The options that we are analyzing
1. Use only Adj-SID B=0
2. Use a combination of Node-SID and Adj-SID
– Node-SID strict SPF (is it really applicable ?)
– Adding protection flag in the Node SID
– Using two Node SIDs with local policies
3. Use a combination of Adj-SIDs and binding-SIDs
– Binding-SID represents a list of Adj-SID
Next steps
• We need to enhance the analysis:
– More detailled pros/cons
• Feedback from WG is welcome
– Any other option to consider ?
• We have some deployment requirement:
– We need to go fast ! And close this asap to start coding
(when necessary) and then deploy
• We ask for WG adoption