North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Question on Unrecognized BGP Path Attribute

  • From: Xin Liu
  • Date: Mon Jul 23 15:02:47 2007
  • Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=fO4c8T7kONCh6YHorMZXXo9QhXxvF2asAxFwogvxvxNyxGooRmv/tiVxxMK3WsoOkmi5Kkfv5p2N1k5ml3asaXhskTdH6vk7kWu9lp0ADLzOq9qtAkPyMaJ/PgFlzKXemwnlLEepXzQchola7pgwscQt7SrvZ+ZzZjJm491f19Y=
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=ki09A/CBDhqZwcUhBtcXGNPcUugjAJ8BNIDPP5Wtzhdd8dzy/SgugniHsGNJqCYAXkmUxHVndTmXHwf/yw6GjS2VwOBFVa8emM1nsUUOwtQ7rrJTW8ll8hat+MSQmp4qeubRuepK8jPheg2Ks1v4kW4VsfLQznsLo2PkTu4Z31U=

Hi,

I have a question about unrecognized BGP path attribute. According to
RFC4271, when a BGP router sees an UPDATE with an unrecognized
optional and transitive path attribute, it should retain the
attribute, and if the path is selected, it should propagate the
attribute to its neighbors. My question is, if later the router sees
an update to the path in which only the unrecognized attribute has
changed, should it immediately propagate the change to its neighbors?
My guess is a yes, but I'm not sure because it's not explicitly
written down in the RFC.

Another question is, in such a case, what will the current routers
from different vendors do? Anyone has any experience on this?

Best
Regards,

Xin Liu