On Wed, Dec 10, 2008 at 4:38 PM, Claudio Jeker <[EMAIL PROTECTED]> wrote: > I looked at the porblem and I'm currently unsure what the best way is to > handle such bad AS4_* attributes. The RFC in all its glory does not > mention how to handle errors. So at the moment I'm in favor of just > dropping/ignoring the bad optional attribute but I need to recheck with > the BGP RFC to see if this is valid. Another solution is to ignore the > full update but I have a bad feeling about that.
Can you ignore just the route with the bad attribute? We don't want to propagate it more.
