Re: [spring] draft-ginsberg-spring-conflict-resolution: SRGB INCONSISTENCY

2016-01-11 Thread Les Ginsberg (ginsberg)
Folks – This thread is about SRGB inconsistency. SRGB inconsistency is an INTRA-node issue. There is no SRGB conflict issue between nodes. There will be a separate thread about SID conflict issues – where inter-node conflicts certainly are possible – but that is NOT what we are discussing in

Re: [spring] draft-ginsberg-spring-conflict-resolution: SRGB INCONSISTENCY

2016-01-11 Thread Les Ginsberg (ginsberg)
Wim – Please explain to me how the receivers – who you are proposing to make one of the choices below – know what the node which advertised the overlapping ranges is actually doing when it installs local labels in its forwarding plane? For example, suppose in the example below the receivers

Re: [spring] draft-ginsberg-spring-conflict-resolution

2016-01-11 Thread Stewart Bryant
Actually SIDs should not have the semantics of an IP address. They should have the semantics of an instruction. If you want to make an analogy, that should be with a MPLS label. Where some people think of a label as short hand for an address. If a label could only be an address we could not have

Re: [spring] draft-ginsberg-spring-conflict-resolution

2016-01-11 Thread stephane.litkowski
Fully agree but this is not the choice that has been made at the beginning. Do you want to propose a change ? From: rras...@gmail.com [mailto:rras...@gmail.com] On Behalf Of Robert Raszuk Sent: Friday, January 08, 2016 15:26 To: LITKOWSKI Stephane SCE/OINIS Cc: Stewart Bryant; Les Ginsberg

Re: [spring] draft-ginsberg-spring-conflict-resolution: SRGB INCONSISTENCY

2016-01-11 Thread HENDERICKX, Wim (Wim)
I believe we agree to minimise the network impact when SRGB data is inconsistent. Option 1 is we ignore a advertisements of some nodes. The main issue I see with this is determining who is right/wrong. Implementation is rather easy, but you will impact traffic from certain nodes in some case as