IETF Logo Mail Archive

RE: draft-ietf-l3vpn-ospf-2547-04 L3VPN/OSPF WG Last Call

"Yegenoglu, Ferit" <ferit.yegenoglu@lmco.com> Mon, 12 September 2005 16:44 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EErQL-0003Fl-Hm; Mon, 12 Sep 2005 12:44:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EErQJ-0003DZ-BQ for l3vpn@megatron.ietf.org; Mon, 12 Sep 2005 12:44:51 -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 MAA01250 for <l3vpn@ietf.org>; Mon, 12 Sep 2005 12:44:41 -0400 (EDT)
Received: from mailgw3a.lmco.com ([192.35.35.7]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EErUN-0001R5-H7 for l3vpn@ietf.org; Mon, 12 Sep 2005 12:49:06 -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 j8CGiXUW020457; Mon, 12 Sep 2005 12:44:33 -0400 (EDT)
Received: from CONVERSION-DAEMON.lmco.com by lmco.com (PMDF V6.1-1X6 #30875) id <0IMP00001QI8OE@lmco.com>; Mon, 12 Sep 2005 12:44:32 -0400 (EDT)
Received: from EMSS09I01.us.lmco.com ([158.183.26.24]) by lmco.com (PMDF V6.1-1X6 #30875) with ESMTP id <0IMP001ZFQI70Z@lmco.com>; Mon, 12 Sep 2005 12:44:32 -0400 (EDT)
Received: from EMSS04M14.us.lmco.com ([162.16.20.50]) by EMSS09I01.us.lmco.com with Microsoft SMTPSVC(5.0.2195.6713); Mon, 12 Sep 2005 12:44:32 -0400
Date: Mon, 12 Sep 2005 12:43:43 -0400
From: "Yegenoglu, Ferit" <ferit.yegenoglu@lmco.com>
To: erosen@cisco.com
Message-id: <448B84DF3CA2F24E8D3D01A247249AFB08263630@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: AcW3qHOb+ubP93E1TTuD2t2uwRxXcQAECpaw
content-class: urn:content-classes:message
X-OriginalArrivalTime: 12 Sep 2005 16:44:32.0492 (UTC) FILETIME=[40436AC0:01C5B7B9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
Cc: l3vpn@ietf.org
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

Thanks. I had not realized that a separate OSPF virtual link (in
addition to sham link) had to be configured, as mentioned at the end of
Section 4.2.7.2. What can go wrong if the sham link endpoint address is
used as the endpoint address of the OSPF virtual link? Also, are there
any guidelines as to how the OSPF virtual link endpoint addresses are
selected?



-----Original Message-----
From: Eric Rosen [mailto:erosen@cisco.com] 
Sent: Monday, September 12, 2005 10:44 AM
To: Yegenoglu, Ferit
Cc: l3vpn@ietf.org
Subject: Re: draft-ietf-l3vpn-ospf-2547-04 L3VPN/OSPF WG Last Call



> 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.

What section  4.2.8.4 means is that  the routes of type  "sham link
endpoint address" are to be treated only as specified in section 4.2.7,
and the rules of 4.2.8 (4.2.8.1, 4.2.8.2) do not apply.

v2.23.0 | Report a Bug | By Email