CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 09:53:41 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=oFKdX1wjKIWMjKglZw90jPCqpqT7dL99x7OCS9O_DXU-1760176421-1.0.1.1-9KmjrhepIW6ln42QKvNEpEvXWCLwMXPNRLdTXP56xwDFxP0zkDkw8XSORjSUjAvbRKUu43epE8yHAOa4b3mqflNPmp9CJBv4o_AO11X5GfE; path=/; expires=Sat, 11-Oct-25 10:23:41 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cd78c1de0daf3d-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 3630 » RFC Editor
Search RFCs
RFC 3630
Traffic Engineering (TE) Extensions to OSPF Version 2, September 2003
- File formats:
- Status:
- PROPOSED STANDARD
- Updates:
- RFC 2370
- Updated by:
- RFC 4203, RFC 5786
- Authors:
- D. Katz
K. Kompella
D. Yeung - Stream:
- IETF
- Source:
- ospf (rtg)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC3630
Discuss this RFC: Send questions or comments to the mailing list lsr@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 3630
Abstract
This document describes extensions to the OSPF protocol version 2 to support intra-area Traffic Engineering (TE), using Opaque Link State Advertisements.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us