Re: [spring] draft-ietf-spring-conflict-resolution - Policy

2016-05-15 Thread Les Ginsberg (ginsberg)
Bruno - After rereading your post, I think I missed part of what you were trying to say. Topology was introduced because it is expected (indeed even REQUIRED) that the same prefix would have a different SID in different topologies. This is why for the purposes of determining "prefix conflict"

Re: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header

2016-05-15 Thread otroan
Tal, > [Apologies if this issue has been discussed before.] > > According to draft-ietf-6man-segment-routing-header, an ‘SR Segment Endpoint > Node’ updates the Destination IP address. > Therefore, it must also update the Layer 4 Checksum, right? > > I wonder if there is an upper bound on the

[spring] L4 Checksum and draft-ietf-6man-segment-routing-header

2016-05-15 Thread Tal Mizrahi
Hi, [Apologies if this issue has been discussed before.] According to draft-ietf-6man-segment-routing-header, an 'SR Segment Endpoint Node' updates the Destination IP address. Therefore, it must also update the Layer 4 Checksum, right? I wonder if there is an upper bound on the size of the