Re: [spring] Mail regarding draft-ietf-spring-conflict-resolution

2017-05-04 Thread Shraddha Hegde
Les, The issues we are discussing here are specific to Segment Routing and SPRING is the right WG to address this. The problem here is not about standardizing what is the default PHP behavior, it is about the scenarios when this default behavior assumption need to be applied. The problem doesn

Re: [spring] Genart last call review of draft-ietf-spring-ipv6-use-cases-10

2017-05-04 Thread Alvaro Retana (aretana)
On 5/2/17, 12:57 PM, "Stewart Bryant" wrote: Stewart: Hi! How are you? Thanks for the detailed review! > A significant part of the justification seems to evolve around the > inability of MPLS to function in an IPv6 only network. It seems to me that this statement summarizes many of the conce

Re: [spring] Mail regarding draft-ietf-spring-conflict-resolution

2017-05-04 Thread Les Ginsberg (ginsberg)
Shraddha - First, there is no SID conflict here. There is therefore nothing for the conflict resolution draft to discuss. Let's look at your scenario more detail. To do so let's use the following simple topology: --A / G-B \ C Using

Re: [spring] RtgDir review: draft-ietf-spring-resiliency-use-cases-08

2017-05-04 Thread Stefano Previdi (sprevidi)
Hi Stephane, Lou, sorry, I missed that comment (in fact I did get it but forgot to address it). I will add the necessary text and will submit a new version asap. s. > On May 4, 2017, at 9:50 AM, stephane.litkow...@orange.com wrote: > > Hi Stefano, > > Speaking as doc Shepherd, I do not see i

Re: [spring] RtgDir review: draft-ietf-spring-resiliency-use-cases-08

2017-05-04 Thread stephane.litkowski
Hi Stefano, Speaking as doc Shepherd, I do not see in the V09, how you are addressing Lou's point about 1:1 and 1+1 protection in the Section 2. I think it make sense to add a simple explicit statement that SPRING should support both approach. It is partially addressed by " The two paths may be