I think I see the current plan as a it challenging to depend upon... If the RLP bit is dependent upon ops folks getting the right config-bit set for each customer we would want that to be as much automated as possible so there would be the least chance for 'forgot to set the bit' or 'set bit incorrectly'.
I'm worried that I can't tell reliably what the bit was 2 as-hops away, did they mean 'customer' ? or was that a mistake? Did someone change it mid-path to me? Did the implementation of their vendor gear change/set the wrong attribute value? There seem to be a bunch of uncertainties with this, in my mind. I guess that with bgpsec signing this attribute at least 'joe really meant that jim was his customer', and you can't change the value on a bgpsec path. If we want that, I think having the attribute where it can get changed (not-bgpsec secured paths) is a real problem, or opens up some pretty large problems... _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
