Comments on draft-ietf-ospf-2547-dnbit-00.txt
Acee Lindem <acee@REDBACK.COM> Tue, 16 September 2003 21:23 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 RAA13294 for <ospf-archive@LISTS.IETF.ORG>; Tue, 16 Sep 2003 17:23:24 -0400 (EDT)
Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <3.00B99B84@cherry.ease.lsoft.com>; Tue, 16 Sep 2003 17:23:29 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 55088057 for OSPF@PEACH.EASE.LSOFT.COM; Tue, 16 Sep 2003 17:23:27 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Tue, 16 Sep 2003 17:23:27 -0400
Received: from redback.com (login004.redback.com [155.53.12.57]) by prattle.redback.com (Postfix) with ESMTP id 33872628DC0; Tue, 16 Sep 2003 14:22:24 -0700 (PDT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID: <3F677FAF.8080803@redback.com>
Date: Tue, 16 Sep 2003 17:25:03 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Comments on draft-ietf-ospf-2547-dnbit-00.txt
Comments: To: Eric Rosen <erosen@cisco.com>
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit
Eric, Here are my comments: Section 2 Introduction The terminology is somewhat confusing. Normally, we "export" or "redistribute" routes rather than "convert" them. In this case routes are being installed from backbone BGP into the VPN route table. When they are redistributed (or exported) into the OSPF in the VPN they are advertised as summary and AS external LSAs. Similarly, routes that OSPF installs into the VPN route table will be redistributed and advertised across the VPN backbone. Section 3 Replace all instances of "decision process" with "routing computation". The text in parenthesis (The reader will note...) should be explained better or removed. The OSPF-VPN draft dictates that a PE router has to be part of area 0. If it is part of area 0, the summaries in area 0 are used for the route computation and hence feedback is prevented if the PE-CE connection is not in area 0. With the generalized use of the DN bit, the PE area 0 restriction could be relaxed a bit to say that the PE router must advertise itself as an ABR (via its router bits in its router LSA) and the CE routers must not have any area 0 connections when the PE router connection isn't an area 0 connection. However, I'm not sure there is a requirement since no has complained heretofore. Section 4 Please add a diagram of the OSPF options bits with the DN bit included. -- Acee
- Comments on draft-ietf-ospf-2547-dnbit-00.txt Acee Lindem