@techreport{chandra-bgp4-cap-neg-00, number = {draft-chandra-bgp4-cap-neg-00}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-chandra-bgp4-cap-neg/00/}, author = {John Scudder and Ravi Chandra}, title = {{Capabilities Negotiation with BGP-4}}, pagetotal = 4, year = 1997, month = jul, day = 17, abstract = {Currently BGP-4 {[}BGP-4{]} requires that when a BGP speaker receives an OPEN message with one or more unrecognized Optional Parameters, the speaker must terminate BGP peering. This complicates introduction of new capabilities in BGP. This document defines new Optional Parameter, called Capabilities, that is expected to facilitate introduction of new capabilities in BGP by providing graceful capability negotiation. The proposed parameter is backward compatible - a router that supports the parameter can maintain BGP peering with a router that doesn't support the parameter.}, }