On Mon, Dec 31, 2012 at 3:24 PM, Jakob Heitz <[email protected]> wrote: > That covers malformed attribute flags.
Except in the MP_REACH_NLRI or MP_UNREACH_NLRI, which is not a foolish exception if the goal is to recover all the NLRI; but if the goal is to avoid session-reset, it is. Like I keep saying, the goal of error-handling should be to make session-reset avoidable. Today it is not. It is creating complex rules which must be supported by both sides of the BGP session to try very hard to keep the network in a good state. This is a good goal in itself, but not to the exclusion of avoiding session-reset. Again, the existing draft also ignores conflicts with RFC4271. So do the updates to RFC4760. You are not allowed to put attributes into the attribute list in any order you want. RFC4271 explicitly requires that attributes be sorted by Attribute Type Code. A Capability negotiation is necessary to change the ordering of attributes. Finally, because the current error-handling concept can't be implemented without such a capability, it's not useful if the other BGP speaker lacks support. That is why IGNORE BAD MESSAGES is needed. It doesn't require support on both sides. -- Jeff S Wheeler <[email protected]> Sr Network Operator / Innovative Network Concepts _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
