HTTP/2 302 date: Mon, 14 Jul 2025 07:08:13 GMT content-type: text/html content-length: 143 location: https://get.ietf.org/implementation-report/report-idr-rfc2796bis.txt cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0 expires: Thu, 01 Jan 1970 00:00:01 GMT vary: Accept-Encoding server: cloudflare cf-ray: 95ef300a5c9875e9-BLR alt-svc: h3=":443"; ma=86400 HTTP/2 200 date: Mon, 14 Jul 2025 07:08:14 GMT content-type: text/plain etag: W/"a97d116a4ee901139ad2115c7914f038" vary: Accept-Encoding server: cloudflare cf-ray: 95ef300a9993a9c3-BLR content-encoding: gzip alt-svc: h3=":443"; ma=86400 Implementation Report Enke Chen Redback Networks Editor BGP Route Reflection - Implementation Report 1. Summary This document provides an implementation report for the BGP Route Reflection [1]. Each response is listed. The editor makes no claim as to the accuracy of the information provided. The following organizations reported having implementations of the BGP Route Reflection: Alcatel, Alcatel Networks, Nexthop Technologies, and Redback Networks. 2. Implementation Forms 2.1. Alcatel Person filling out this form: Brian Winger Does your implementation follow the procedures specified in the Operation Section when advertising an IBGP learned route to an IBGP peer? Yes Does your implementation recognize the two new attributes (ORIGINATOR_ID and CLUSTER_LIST) defined in the document? Yes Does your implementation perform routing information loop detection based on the ORIGINATOR_ID and the CLUSTER_LIST attributes as specified in the document? Yes Does your implementation format the two new attributes (ORIGINATOR_ID and CLUSTER_LIST) as specified in the document when doing route reflection? Yes Does your implementation take the ORIGNATOR_ID and the CLUSTER_LIST attributes into account in route selection as specified in the document? No List other implementations that you have tested for BGP Route Reflection interoperability. Cisco, Juniper 2.2. Alcatel Networks Person filling out this form: Devendra Raut Does your implementation follow the procedures specified in the Operation Section when advertising an IBGP learned route to an IBGP peer? Yes. Does your implementation recognize the two new attributes (ORIGINATOR_ID and CLUSTER_LIST) defined in the document? Yes. Does your implementation perform routing information loop detection based on the ORIGINATOR_ID and the CLUSTER_LIST attributes as specified in the document? Yes. Does your implementation format the two new attributes (ORIGINATOR_ID and CLUSTER_LIST) as specified in the document when doing route reflection? Yes. Does your implementation take the ORIGNATOR_ID and the CLUSTER_LIST attributes into account in route selection as specified in the document? Yes. List other implementations that you have tested for BGP Route Reflection interoperability. Juniper & Cisco. 2.3. NextHop Technologies, Inc. Person filling out this form: Jeffrey Haas Does your implementation follow the procedures specified in the Operation Section when advertising an IBGP learned route to an IBGP peer? Yes Does your implementation recognize the two new attributes (ORIGINATOR_ID and CLUSTER_LIST) defined in the document? Yes Does your implementation perform routing information loop detection based on the ORIGINATOR_ID and the CLUSTER_LIST attributes as specified in the document? Yes Does your implementation format the two new attributes (ORIGINATOR_ID and CLUSTER_LIST) as specified in the document when doing route reflection? Yes Does your implementation take the ORIGNATOR_ID and the CLUSTER_LIST attributes into account in route selection as specified in the document? This can be optionally configured. List other implementations that you have tested for BGP Route Reflection interoperability. Cisco, Juniper 2.4. Redback Networks Person filling out this form: Jenny Yuan (jenny@redback.com) Does your implementation follow the procedures specified in the Operation Section when advertising an IBGP learned route to an IBGP peer? Yes Does your implementation recognize the two new attributes (ORIGINATOR_ID and CLUSTER_LIST) defined in the document? Yes Does your implementation perform routing information loop detection based on the ORIGINATOR_ID and the CLUSTER_LIST attributes as specified in the document? Yes Does your implementation format the two new attributes (ORIGINATOR_ID and CLUSTER_LIST) as specified in the document when doing route reflection? Yes Does your implementation take the ORIGNATOR_ID and the CLUSTER_LIST attributes into account in route selection as specified in the document? Yes List other implementations that you have tested for BGP Route Reflection interoperability. Cisco, Juniper 3. References [1] T. Bates, R. Chandra and E. Chen, "BGP Route Reflection - An Alternative to Full Mesh IBGP", draft-ietf-idr-rfc2796bis-00.txt, March 2004. 4. Author Information Enke Chen Redback Networks, Inc. 300 Holger Way San Jose, CA 95134 Email: enke@redback.com