Supposedly "Segment Routing" is an architecture according to RFC 8402, so
anything that satisfies the architecture can use the term "Segment Routing"..
If SPRING want to play that game, then stop using "IPv6", because a number
of proposals blatantly and purposely don't comply with Internet
Hi Ron,
“limp” is indeed humorous interpretation! I can see why you would not want to
take seriously!
I do confess that I’m not a native English speaker.
I intended it to be pronounced “/limf/” as in the “lymphatic system” due to the
distribution of state to nodes in the system.
Thanks
Zafar,
This is a pretty obvious attempt to create backronymn (
https://en.wikipedia.org/wiki/Backronym ) with negative connotations. So, I am
not taking it seriously.
(For those who are not native speakers of English, the work “limp” carries
negative connotations in English.)
Hi Ron,
I agree with Dan, Jeff and others that the name should NOT create confusion
with an already established technology (SR).
The name should reflect the design and the spirit of your proposal.
To try to help you differentiate your solution, may I propose
“LIMPH: Label Indirection with
Exactly like a binding SID
Ron
Sent from my phone
On Sep 26, 2019, at 10:07 AM, Stewart Bryant
mailto:stewart.bry...@gmail.com>> wrote:
On 25/09/2019 22:25, Ron Bonica wrote:
Daniel,
I’m not sure that I agree. The PSSI doesn’t represent per-path information. It
represents an instruction
On 25/09/2019 22:25, Ron Bonica wrote:
Daniel,
I’m not sure that I agree. The PSSI doesn’t represent per-path
information. It represents an instruction to be executed at a segment
endpoint.
Ron
Like a binding SID?
S
Juniper Business Use Only
*From:*Bernier, Daniel
*Sent:*
The thing that pushes the original SR design into statefulness is
binding SIDs which require state to be pre-positioned in the network.
- Stewart
On 25/09/2019 20:50, Joel M. Halpern wrote:
SR is Stateless in the sense of not having per-path state. It is not
stateless in a general sense,
Ron,
Say I have the following topology (augmenting on Robert's use case) with x
Number of VRFs on PE1 or PE2
PE1 -- P1 -- P2 -- P3 -- PE2
| | |
SE1 SE2 SE3
For a single path program, when a packet sourced in a VPN on PE1 needs to
