Brian,
The customer's workaround was to erase entire AS_PATH via
redistribution. I am not saying that use of this knob is safe.
I am saying that it exists in shipping implementations and simply asking
what SIDR behaviour should be when such policy is present.
That's all.
Best,
R.
Arbitrary AS substitution allows loop creation, even if your own AS is
required.
All that is needed, is multiple instances of replace-as in the loop.
Suppose A replaces B C D with A E F.
Suppose B replaces G A with B C D.
A received B C D, sends A E F to G.
G sends G A E F to B.
B sends B C D E F to A.
We have a loop, which eventually results in path overflow with E F E F E
F etc. at the end of it.
On Wed, Mar 28, 2012 at 4:07 PM, Robert Raszuk <[email protected]
<mailto:[email protected]>> wrote:
the 'replace-as' seems like
loop-creation, joy.
Nope. No loops at least in one implementation ... the implementation
mandates that you insert your own AS - that is not optional.
Rgs,
R.
_________________________________________________
sidr mailing list
[email protected] <mailto:[email protected]>
https://www.ietf.org/mailman/__listinfo/sidr
<https://www.ietf.org/mailman/listinfo/sidr>
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr
