%% You should probably cite draft-ietf-idr-bgp-attribute-announcement-03 instead of this revision. @techreport{ietf-idr-bgp-attribute-announcement-01, number = {draft-ietf-idr-bgp-attribute-announcement-01}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-attribute-announcement/01/}, author = {Keyur Patel and Jim Uttaro and Bruno Decraene and Wim Henderickx and Jeffrey Haas}, title = {{Constrain Attribute announcement within BGP}}, pagetotal = 9, year = 2017, month = may, day = 19, abstract = {{[}RFC4271{]} defines four different categories of BGP Path attributes. The different Path attribute categories can be identified by the attribute flag values. These flags help identify if an attribute is optional or well-known, Transitive or non-Transitive, Partial, or of an Extended length type. BGP attribute announcement depends on whether an attribute is a well-known or optional, and whether an attribute is a transitive or non-transitive. BGP implementations MUST recognize all well-known attributes. The well-known attributes are always Transitive. It is not required for BGP implementations to recognise all the Optional attributes. The Optional attributes could be Transitive or Non-Transitive. BGP implementations MUST store and forward any Unknown Optional Transitive attributes and ignore and drop any Unknown Optional Non-Transitive attributes. Currently, there is no way to confine the scope of Path attributes within a given Autonomous System (AS) or a given BGP member-AS in Confederation. This draft defines attribute extensions that help confine the scope of Optional attributes within a given AS or a given BGP member-AS in Confederation}, }