idnits 2.17.1 draft-ietf-ospf-nssa-update-11.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 3101 5 Title: The OSPF Not-So-Stubby Area (NSSA) Option 6 Author(s): P. Murphy 7 Status: Standards Track 8 Date: January 2003 9 Mailbox: pmurphy@noc.usgs.net 10 Pages: 33 11 Characters: 76243 12 Obsoletes: 1587 14 I-D Tag: draft-ietf-ospf-nssa-update-11.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3101.txt 18 This memo documents an optional type of Open Shortest Path First 19 (OSPF) area that is somewhat humorously referred to as a 20 "not-so-stubby" area (or NSSA). NSSAs are similar to the existing 21 OSPF stub area configuration option but have the additional capability 22 of importing AS external routes in a limited fashion. 24 The OSPF NSSA Option was originally defined in RFC 1587. The 25 functional differences between this memo and RFC 1587 are explained 26 in Appendix F. All differences, while expanding capability, are 27 backward-compatible in nature. Implementations of this memo and of 28 RFC 1587 will interoperate. 30 This document is a product of the Open Shortest Path First IGP Working 31 Group of the IETF. 33 This is now a Proposed Standard Protocol. 35 This document specifies an Internet standards track protocol for 36 the Internet community, and requests discussion and suggestions 37 for improvements. Please refer to the current edition of the 38 "Internet Official Protocol Standards" (STD 1) for the 39 standardization state and status of this protocol. Distribution 40 of this memo is unlimited. 42 This announcement is sent to the IETF list and the RFC-DIST list. 43 Requests to be added to or deleted from the IETF distribution list 44 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 45 added to or deleted from the RFC-DIST distribution list should 46 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 48 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 49 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 50 help: ways_to_get_rfcs. For example: 52 To: rfc-info@RFC-EDITOR.ORG 53 Subject: getting rfcs 55 help: ways_to_get_rfcs 57 Requests for special distribution should be addressed to either the 58 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 59 specifically noted otherwise on the RFC itself, all RFCs are for 60 unlimited distribution.echo 61 Submissions for Requests for Comments should be sent to 62 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 63 Authors, for further information.