RE: draft-ietf-l3vpn-ospf-2547-04 L3VPN/OSPF WG Last Call
"Yegenoglu, Ferit" <ferit.yegenoglu@lmco.com> Fri, 09 September 2005 20:24 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EDpQf-00026b-32; Fri, 09 Sep 2005 16:24:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EDpQd-00026A-Jf for l3vpn@megatron.ietf.org; Fri, 09 Sep 2005 16:24:55 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07913 for <l3vpn@ietf.org>; Fri, 9 Sep 2005 16:24:53 -0400 (EDT)
Received: from mailgw3a.lmco.com ([192.35.35.7]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EDpUD-0000Sb-Kc for l3vpn@ietf.org; Fri, 09 Sep 2005 16:28:42 -0400
Received: from emss09g01.ems.lmco.com (relay6.ems.lmco.com [166.17.13.59]) by mailgw3a.lmco.com (8.12.10/8.12.10) with ESMTP id j89KOeUW007667 for <l3vpn@ietf.org>; Fri, 9 Sep 2005 16:24:40 -0400 (EDT)
Received: from CONVERSION-DAEMON.lmco.com by lmco.com (PMDF V6.1-1X6 #30875) id <0IMK00301GP4GF@lmco.com> for l3vpn@ietf.org; Fri, 09 Sep 2005 16:24:40 -0400 (EDT)
Received: from EMSS09I00.us.lmco.com ([158.183.26.31]) by lmco.com (PMDF V6.1-1X6 #30875) with ESMTP id <0IMK004AGGP4RW@lmco.com> for l3vpn@ietf.org; Fri, 09 Sep 2005 16:24:40 -0400 (EDT)
Received: from EMSS04M14.us.lmco.com ([162.16.20.50]) by EMSS09I00.us.lmco.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 09 Sep 2005 16:24:40 -0400
Date: Fri, 09 Sep 2005 16:24:40 -0400
From: "Yegenoglu, Ferit" <ferit.yegenoglu@lmco.com>
To: l3vpn@ietf.org
Message-id: <448B84DF3CA2F24E8D3D01A247249AFB0826362D@emss04m14.us.lmco.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.0.6603.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Thread-Topic: draft-ietf-l3vpn-ospf-2547-04 L3VPN/OSPF WG Last Call
thread-index: AcWwg8t2BYcRXqvnRy26NftTuVWuFAE95EXw
content-class: urn:content-classes:message
X-OriginalArrivalTime: 09 Sep 2005 20:24:40.0615 (UTC) FILETIME=[81ADCB70:01C5B57C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Content-Transfer-Encoding: 7bit
Subject: RE: draft-ietf-l3vpn-ospf-2547-04 L3VPN/OSPF WG Last Call
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org
Hi, With respect to sham link advertisement on page 8 the draft says "...PE1 may flood to CE1 a type 1 LSA advertising a link to PE2, and PE2 may flood to CE2 a type 1 LSA advertising a link to PE1." Then, on Section 4.2.8.4, it says sham link endpoint address routes must not be redistributed into OSPF. Can draft's authors please clarify? Thanks, Ferit -----Original Message----- From: l3vpn-bounces@ietf.org [mailto:l3vpn-bounces@ietf.org] On Behalf Of Rick Wilder Sent: Saturday, September 03, 2005 8:33 AM To: l3vpn@ietf.org Subject: draft-ietf-l3vpn-ospf-2547-04 L3VPN/OSPF WG Last Call Please see the announcement below regarding the last call on draft-ietf-l3vpn-ospf-2547-04. Due to a delay in posting this to this list, the last call will conclude on September 17. Rick This begins working group last call on draft-ietf-l3vpn-ospf-2547-04. This last call is limited to the changes that Eric has made to the document (which are outlined in Eric's email below). The last call will end in two weeks (September 14th). Please send any comments to the l3vpn (l3vpn@ietf.org) and OSPF WG mailing lists. The document is an l3vpn WG document but it reflects OSPF operation/interaction with BGP/MPLS in a PE/CE environment. Thanks, Acee At 11:45 AM 8/29/2005 -0400, Eric Rosen wrote: > As a result of AD review, significant changes have been made > to the > specification draft-ietf-l3vpn-ospf-2547. These changes can be seen > in the > latest version, draft -04. It is believed that the draft now > corresponds to > the implementations. > > The following issues were addressed as a result of the AD review. > > The spec was written so as to allow a single VRF to correspond to > multiple > OSPF domains. However, it did not make clear just which > parameters and > procedures are relative to a domain, and which are relative to a > VRF. This > has now been cleared up. However, doing so required extensive > textual > changes. > > There are cases where BGP decides to put a route into the VRF > for a > particular address prefix, and OSPF also decides to put a route into > the VRF > for that same address prefix. Of course, only one of these can > actually be > used for forwarding. The original spec did not make it adequately > clear > just how a choice between two such routes would be made. This > has been > clarified. In some cases, the results will be different than they > would > have been if the VPN were really a pure OSPF network. These > differences are > now explained and their potential consequences pointed out. > > The procedures for forwarding data traffic on a sham link > have been > clarified. The procedures for sending OSPF control traffic on a > sham link > have been clarified. The role of the optional "sham link endpoint > address" > has been clarified. > > The procedures for translating BGP-distributed VPN-IPv4 routes > into OSPF > routes have been clarified. > > A discussion of NSSA routes has been added. Alex says it is not > detailed > enough; any feedback in this area would be welcome. > > Due to the large number of changes, Alex has asked for a new last > call, and > I expect the WG chairs to formally issue the last call shortly.
- draft-ietf-l3vpn-ospf-2547-04 L3VPN/OSPF WG Last … Acee Lindem
- draft-ietf-l3vpn-ospf-2547-04 L3VPN/OSPF WG Last … Rick Wilder
- RE: draft-ietf-l3vpn-ospf-2547-04 L3VPN/OSPF WG L… Yegenoglu, Ferit
- Re: draft-ietf-l3vpn-ospf-2547-04 L3VPN/OSPF WG L… Eric Rosen
- RE: draft-ietf-l3vpn-ospf-2547-04 L3VPN/OSPF WG L… Yegenoglu, Ferit
- Re: draft-ietf-l3vpn-ospf-2547-04 L3VPN/OSPF WG L… Eric Rosen