IETF Logo Mail Archive

OSPF sham link

Kalyan Bade <kalyan@JUNIPER.NET> Wed, 28 September 2005 23:34 UTC

Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EKlRh-0000SZ-SK for ospf-archive@megatron.ietf.org; Wed, 28 Sep 2005 19:34:41 -0400
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 TAA21142 for <ospf-archive@LISTS.IETF.ORG>; Wed, 28 Sep 2005 19:34:38 -0400 (EDT)
Received: from vms.dc.lsoft.com (209.119.0.2) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <19.010FE5D9@cherry.ease.lsoft.com>; Wed, 28 Sep 2005 19:34:36 -0400
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.4) with spool id 86738477 for OSPF@PEACH.EASE.LSOFT.COM; Wed, 28 Sep 2005 19:34:33 -0400
Received: from 207.17.137.119 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0m) with TCP; Wed, 28 Sep 2005 19:34:33 -0400
Received: from unknown (HELO alpha.jnpr.net) (172.24.18.126) by borg.juniper.net with ESMTP; 28 Sep 2005 16:34:33 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.97,147,1125903600"; d="scan'208"; a="502542372:sNHT20474228"
Received: from photon.jnpr.net ([172.24.18.198]) by alpha.jnpr.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 28 Sep 2005 16:34:32 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Thread-Topic: OSPF sham link
Thread-Index: AcW6+u6gERZNVEzGQPmtIbYSc/rfdgJiEgow
X-OriginalArrivalTime: 28 Sep 2005 23:34:32.0936 (UTC) FILETIME=[2DE14680:01C5C485]
Message-ID: <062B922B6EC55149B5A267ECE78E5D440A2506F6@photon.jnpr.net>
Date: Wed, 28 Sep 2005 16:34:32 -0700
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Kalyan Bade <kalyan@JUNIPER.NET>
Subject: OSPF sham link
Comments: cc: Yakov Rekhter <yakov@juniper.net>
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
List-Help: <http://peach.ease.lsoft.com/scripts/wa.exe?LIST=OSPF>, <mailto:LISTSERV@PEACH.EASE.LSOFT.COM?body=INFO+OSPF>
List-Unsubscribe: <mailto:OSPF-unsubscribe-request@PEACH.EASE.LSOFT.COM>
List-Subscribe: <mailto:OSPF-subscribe-request@PEACH.EASE.LSOFT.COM>
List-Owner: <mailto:OSPF-request@PEACH.EASE.LSOFT.COM>
List-Archive: <http://peach.ease.lsoft.com/scripts/wa.exe?LIST=OSPF>
Content-Transfer-Encoding: quoted-printable

Folks,

I have a question regarding the distribution of sham link endpoint in
the OSPF domain.

From draft-ietf-l3vpn-ospf-2547-04.txt, section 4.2.7.1 last paragraph,
it is quoted that sham link endpoint address must not be distributed by
OSPF. I would like to know the requirement behind this. Say if the sham
link endpoint is the loopback and some customer wants the loopback in
the OSPF domain, as per the spec we cannot do that now. This is not
desirable. Am I missing something here?

Thanks,
Kalyan.

v2.23.0 | Report a Bug | By Email