Re: [OSPF] WG Adoption Call for "OSPF Stub Neighbors"

"Acee Lindem (acee)" <> Mon, 01 February 2016 23:21 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id AA5E01B3896 for <>; Mon, 1 Feb 2016 15:21:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 83DWodMXfiVL for <>; Mon, 1 Feb 2016 15:21:39 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0A88D1B3894 for <>; Mon, 1 Feb 2016 15:21:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=3712; q=dns/txt; s=iport; t=1454368898; x=1455578498; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=gUIESyOqcHqMDgV7uH41kYRsim0H3z9ZsfWvMtGjnFM=; b=Cp+ni4OCaYkpWhGN63Jph0oqZFWkT8HNmV9UUaqjQyEPTcqT3EqFO+Bp Mnu1FqIVwiJ7czwEGvS1mpWfCuCB73WNVwlrpBwfOuhXuI8a0uLjgmH0j LdiEGTkFz99PKaZ6/f69ID/nM62Wfd3kQY/ufy8mEbDXqAdkQts8WKwSC I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.22,382,1449532800"; d="scan'208";a="69253123"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Feb 2016 23:21:38 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id u11NLbCI032730 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <>; Mon, 1 Feb 2016 23:21:38 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 1 Feb 2016 18:21:36 -0500
Received: from ([]) by ([]) with mapi id 15.00.1104.009; Mon, 1 Feb 2016 18:21:37 -0500
From: "Acee Lindem (acee)" <>
To: "Anton Smirnov (asmirnov)" <>, OSPF WG List <>
Thread-Topic: [OSPF] WG Adoption Call for "OSPF Stub Neighbors"
Thread-Index: AQHRXGP2IACKhU9aokSCi/p6itPWXp8X1ccA
Date: Mon, 01 Feb 2016 23:21:36 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [OSPF] WG Adoption Call for "OSPF Stub Neighbors"
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 01 Feb 2016 23:21:40 -0000

Thanks Anton - I agree with that this enhancement should support P2MP as
well. Note that the disclosed IPR abstracts the LSA scoping to a stub-site
specific database so P2MP and other use cases, e.g. parallel links to the
same site, can be accommodated.


On 1/31/16, 3:14 PM, "Anton Smirnov (asmirnov)" <> wrote:

>    Hello,
>    Hub-and-Spoke topology is a known topology where OSPF traditionally
>performed poorly and in my opinion work in this area is very important.
>    On the other hand, I have number of concerns regarding usability of
>approach chosen in this draft and I think in its current state the draft
>is not ready for WG adoption.
>    I have big concerns regarding implementation simplicity and solution
>applicability (i.e. hub-and-spoke networks where proposed solution
>doesn't work). But first of all I want to make a comment on the text as
>it is.
>    Some hub-and-spoke topologies are point-to-multipoint networks. 10
>years ago it was a fraction of all hub-and-spoke WAN, nowadays it is a
>majority. Draft doesn't consider multipoint operations (at least it
>doesn't have word 'multipoint' in it). But multipoint has very big
>implications on having multiple spoofed Router LSAs and their filtering
>- since all stub neighbors are on the same interface, one can't use
>per-interface filtering (which is tightly related to per-interface
>flooding). Spoofed Router LSA will have a new type of flooding behavior
>- per-neighbor. This is doable but it is not specified anywhere and is
>not coded by any implementation I am aware of (i.e. existing filtering
>mechanisms are between different interfaces, not between neighbors on
>the same multipoint interface).
>    So the draft needs to define new LSA flooding scope - per-neighbor
>flooding scope, much like interface-scope flooding had to be devised for
>Opaque LSAs.
>    This is not all for implementation complexity not covered in the
>draft but it will be a good start.
>On 01/26/2016 05:39 PM, Acee Lindem (acee) wrote:
>> This draft was has gone through some refinements after being presented
>> Hawaii and in Yokohama there was some support of this protocol
>> Here is a URL for you convenience.
>> Please indicate your support (or concerns) for adopting this as a WG
>> Document. The WG Adoption call will end in 2 weeks.
>> Thanks,
>> Acee
>> _______________________________________________
>> OSPF mailing list