RFC 3630 · PROPOSED STANDARD · 2003
MON · 14 SEP 2026
Traffic Engineering Extensions to OSPF Version 2
Overview
RFC 3630, “Traffic Engineering Extensions to OSPF Version 2”, is a Proposed Standard document published in October 2003 by D. Katz, K. Kompella, D. Yeung. It updates RFC 2370. It has since been updated by RFC 4203, RFC 5786. The canonical text is published by the RFC Editor.
Abstract
This document describes extensions to the OSPF protocol version 2 to support intra-area Traffic Engineering (TE), using Opaque Link State Advertisements.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
Read this RFC
The canonical text of RFC 3630 is hosted at rfc-editor.org. Available in TXT,HTML.
Relationships to other RFCs
Other RFCs from 2003
- RFC 3629 UTF-8, a transformation format of ISO 10646
- RFC 3631 Security Mechanisms for the Internet
- RFC 3628 Policy Requirements for Time-Stamping Authorities
- RFC 3632 VeriSign Registry Registrar Protocol Version 2.0.0
- RFC 3627 Use of /127 Prefix Length Between Routers Considered Harmful
- RFC 3633 IPv6 Prefix Options for Dynamic Host Configuration Protocol version 6
- RFC 3626 Optimized Link State Routing Protocol
- RFC 3634 Key Distribution Center Server Address Sub-option for the Dynamic Host Configuration Protocol CableLabs Client Configuration Option