Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 7
- Abstract
- This document specifies a procedure that deals with a particular issue that may arise when a Service Provider (SP) provides "BGP/MPLS IP VPN" service to a customer and the customer uses OSPFv2 to advertise its routes to the SP. In this situation, a Customer Edge (CE) Router and a Provider Edge (PE) Router are OSPF peers, and customer routes are sent via OSPFv2 from the CE to the PE. The customer routes are converted into BGP routes, and BGP carries them across the backbone to other PE routers. The routes are then converted back to OSPF routes sent via OSPF to other CE routers. As a result of this conversion, some of the information needed to prevent loops may be lost. A procedure is needed to ensure that once a route is sent from a PE to a CE, the route will be ignored by any PE that receives it back from a CE. This document specifies the necessary procedure, using one of the options bits in the LSA (Link State Advertisements) to indicate that an LSA has already been forwarded by a PE and should be ignored by any other PEs that see it. [STANDARDS-TRACK]
- Publication Date
- 2006-06-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC4576- Link
- https://doi.org/10.17487/RFC4576
- Author(s)
- Eric C. RosenPeter PsenakPadma Pillay-Esnault
- Keyword(s)
- Service Provider, Provider Edge, OSPF
Latest version of IETF RFC 4576
Document Versions — IETF RFC 4576
-
▶ IETF RFC 4576 (2006-06-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- RFC328 — OSPFv2 EXTERNAL
- IETF RFC 4364 [Active*]
- IETF RFC 4577 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4576.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 4576, Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs). Available at https://doi.org/10.17487/RFC4576
Snippet:
IETF RFC 4576, Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs). Available at https://doi.org/10.17487/RFC4576
HTML (ISO 690 compliant)
Preview:
IETF RFC 4576, Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs). Available at https://doi.org/10.17487/RFC4576
Snippet:
<span class="citation"><cite>IETF RFC 4576</cite>, Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs). Available at <a href="https://doi.org/10.17487/RFC4576" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4576</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4576, Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs)
doi: 10.17487/RFC4576
url: https://doi.org/10.17487/RFC4576
doi: 10.17487/RFC4576
url: https://doi.org/10.17487/RFC4576
Snippet:
<li> <cite id="bib-rfc4576">IETF RFC 4576</cite>, Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs) <span class="doi">10.17487/RFC4576</span> </li>
Referenced By
- IETF RFC 4577 [Active*]
- IETF RFC 5340 [Active*]
- IETF RFC 6565 [Active*]