idnits 2.17.1 draft-ietf-ospf-stub-adv-02.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 3137 5 Title: OSPF Stub Router Advertisement 6 Author(s): A. Retana, L. Nguyen, R. White, A. Zinin, 7 D. McPherson 8 Status: Informational 9 Date: June 2001 10 Mailbox: aretana@cisco.com, lhnguyen@cisco.com, 11 riw@cisco.com, azinin@cisco.com, 12 danny@ambernetworks.com 13 Pages: 5 14 Characters: 8140 15 Updates/Obsoletes/SeeAlso: None 17 I-D Tag: draft-ietf-ospf-stub-adv-02.txt 19 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3137.txt 21 This memo describes a backward-compatible technique that may be used 22 by OSPF (Open Shortest Path First) implementations to advertise 23 unavailability to forward transit traffic or to lower the preference 24 level for the paths through such a router. In some cases, it is 25 desirable not to route transit traffic via a specific OSPF router. 26 However, OSPF does not specify a standard way to accomplish this. 28 This document is a product of the Open Shortest Path First IGP Working 29 Group of the IETF. 31 This memo provides information for the Internet community. It does 32 not specify an Internet standard of any kind. Distribution of this 33 memo is unlimited. 35 This announcement is sent to the IETF list and the RFC-DIST list. 36 Requests to be added to or deleted from the IETF distribution list 37 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 38 added to or deleted from the RFC-DIST distribution list should 39 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 41 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 42 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 43 help: ways_to_get_rfcs. For example: 45 To: rfc-info@RFC-EDITOR.ORG 46 Subject: getting rfcs 48 help: ways_to_get_rfcs 50 Requests for special distribution should be addressed to either the 51 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 52 specifically noted otherwise on the RFC itself, all RFCs are for 53 unlimited distribution.echo 54 Submissions for Requests for Comments should be sent to 55 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 56 Authors, for further information.