Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents () in effect on the date of publication of this document. Copyright NoticeĬopyright (c) 2011 IETF Trust and the persons identified as the document authors. This Internet-Draft will expire on April 26, 2012. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. The list of current Internet- Drafts is at. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. It also clarifies the use of the ORIGINATOR_ID and CLUSTER_LIST attributes in this environment. This document explains what behavior is required of a route reflector that also functions as an EBGP speaker. When it does so, just like any other EBGP speaker it must advertise its routes to its IBGP peers. Considerations for Route Reflection and EBGP Internet Engineering Task ForceĬonsiderations for Route Reflection and EBGPĪlthough originally conceived of as a purely IBGP device, in some cases a route reflector may function as an EBGP speaker in addition to its role as envisioned in RFC 4456.
0 Comments
Leave a Reply. |