Document Action: Alternative OSPF ABR Implementations to Informational

The IESG <iesg-secretary@ietf.org> Wed, 12 February 2003 02:39 UTC

Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25767 for <ospf-archive@LISTS.IETF.ORG>; Tue, 11 Feb 2003 21:39:01 -0500 (EST)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <12.008DE5A4@cherry.ease.lsoft.com>; Tue, 11 Feb 2003 21:42:41 -0500
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 625454 for OSPF@DISCUSS.MICROSOFT.COM; Tue, 11 Feb 2003 21:42:41 -0500
Received: from 132.151.1.176 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Tue, 11 Feb 2003 21:32:40 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25286; Tue, 11 Feb 2003 21:28:53 -0500 (EST)
Message-ID: <200302120228.VAA25286@ietf.org>
Date: Tue, 11 Feb 2003 21:28:53 -0500
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Comments: RFC822 error: <W> Incorrect or incomplete address field found and ignored.
From: The IESG <iesg-secretary@ietf.org>
Subject: Document Action: Alternative OSPF ABR Implementations to Informational
Comments: cc: RFC Editor <rfc-editor@isi.edu>, Internet Architecture Board <iab@iab.org>
To: OSPF@DISCUSS.MICROSOFT.COM
Precedence: list

The IESG has approved the Internet-Draft 'Alternative OSPF ABR
Implementations' <draft-ietf-ospf-abr-alt-05.txt> as an Informational
RFC.  This document is the product of the Open Shortest Path First IGP
Working Group.  The IESG contact persons are Bill Fenner and Alex Zinin.


RFC Editor Note:

 Section 1.1 "Introduction", first paragraph

 OLD:
       An OSPF routing domain can be split into several subdomains,
         called areas, which limit the scope of LSA flooding. According
       to [Ref1] a router having attachments to multiple areas is called
       an "area border router" (ABR). The primary function of an ABR is
       to provide its attached areas with Type-3 and Type-4 LSAs (which
       are used for describing routes and ASBRs in other areas) as well
       as to perform actual inter-area routing.

 NEW:
       An OSPF routing domain can be split into several subdomains,
       called areas, which limit the scope of LSA flooding. According
       to [Ref1] a router having attachments to multiple areas is called
       an "area border router" (ABR). The primary function of an ABR is
       to provide its attached areas with Type-3 and Type-4 LSAs, which
       are used for describing routes and AS boundary routers (ASBRs) in
       other areas, as well as to perform actual inter-area routing.