idnits 2.17.1 draft-katz-yeung-ospf-traffic-10.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3630 5 Title: Traffic Engineering (TE) Extensions to 6 OSPF Version 2 7 Author(s): D. Katz, K. Kompella, D. Yeung 8 Status: Standards Track 9 Date: September 2003 10 Mailbox: dkatz@juniper.net, myeung@procket.com, 11 kireeti@juniper.net 12 Pages: 14 13 Characters: 27717 14 Updates: 2370 16 I-D Tag: draft-katz-yeung-ospf-traffic-10.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3630.txt 20 This document describes extensions to the OSPF protocol version 2 to 21 support intra-area Traffic Engineering (TE), using Opaque Link State 22 Advertisements. 24 This document is a product of the Open Shortest Path First IGP Working 25 Group of the IETF. 27 This is now a Proposed Standard Protocol. 29 This document specifies an Internet standards track protocol for 30 the Internet community, and requests discussion and suggestions 31 for improvements. Please refer to the current edition of the 32 "Internet Official Protocol Standards" (STD 1) for the 33 standardization state and status of this protocol. Distribution 34 of this memo is unlimited. 36 This announcement is sent to the IETF list and the RFC-DIST list. 37 Requests to be added to or deleted from the IETF distribution list 38 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 39 added to or deleted from the RFC-DIST distribution list should 40 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 42 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 43 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 44 help: ways_to_get_rfcs. For example: 46 To: rfc-info@RFC-EDITOR.ORG 47 Subject: getting rfcs 49 help: ways_to_get_rfcs 51 Requests for special distribution should be addressed to either the 52 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 53 specifically noted otherwise on the RFC itself, all RFCs are for 54 unlimited distribution.echo 55 Submissions for Requests for Comments should be sent to 56 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 57 Authors, for further information.