Re: [Lsr] Thoughts on the area proxy and flood reflector drafts.

Christian Hopps <chopps@chopps.org> Wed, 10 June 2020 18:58 UTC

Return-Path: <chopps@chopps.org>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E89633A0F7F for <lsr@ietfa.amsl.com>; Wed, 10 Jun 2020 11:58:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FcoxaLLJSEwl for <lsr@ietfa.amsl.com>; Wed, 10 Jun 2020 11:58:43 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 4BAE23A07D0 for <lsr@ietf.org>; Wed, 10 Jun 2020 11:58:23 -0700 (PDT)
Received: from stubbs.int.chopps.org (047-050-069-038.biz.spectrum.com [47.50.69.38]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id C4E9D60D9D; Wed, 10 Jun 2020 18:58:22 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Christian Hopps <chopps@chopps.org>
In-Reply-To: <CA+wi2hO0qnOCoTuR4TGXc+y7rcffZRcOx04cLbt7Dn4hW_mT+Q@mail.gmail.com>
Date: Wed, 10 Jun 2020 14:58:21 -0400
Cc: Christian Hopps <chopps@chopps.org>, lsr@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <CC54BF06-61AE-4DBA-A81A-D7D3B35EEECB@chopps.org>
References: <790B898F-DB03-499E-BAAE-369504539475@chopps.org> <22086D70-6A19-4EA3-B15B-405FD5271262@chopps.org> <CA+wi2hMGcfqgPBoWLbqhS5vrF_Jy1RtAM7iMan4uYUjEc9X_2Q@mail.gmail.com> <48779A7B-FC92-495E-A2D6-98700E9FB337@chopps.org> <CA+wi2hOPEP=xT34QVV=ZYAg3ou1=gsg1n=5x3ZQXy_p84dt65A@mail.gmail.com> <EFCF321D-1D96-4DC7-931C-75037BCA4DF0@chopps.org> <CA+wi2hNSzKmF1r8c5AbgiMDHYKNfkZfzfoOQERySHsYt_+9d8Q@mail.gmail.com> <60C6D2D1-BC9C-4A43-BFC2-7583A85FBD40@chopps.org> <CA+wi2hO0qnOCoTuR4TGXc+y7rcffZRcOx04cLbt7Dn4hW_mT+Q@mail.gmail.com>
To: Tony Przygienda <tonysietf@gmail.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/aCq7ScgF_r7j7x7y6kOz0_AdXmw>
Subject: Re: [Lsr] Thoughts on the area proxy and flood reflector drafts.
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jun 2020 18:58:45 -0000


> On Jun 10, 2020, at 2:10 PM, Tony Przygienda <tonysietf@gmail.com> wrote:
> 
> 
> 
> On Wed, Jun 10, 2020 at 11:04 AM Christian Hopps <chopps@chopps.org> wrote:
> 
> ....
> 
> 
> > I also suggest to look up why in PNNI we ended up introducing a special "L1 equivalent" computation to the peer group leader to validate that it was actually reachable for correct operation (especially hierarchy negotiations) on peer group egresses which in a sense was like but worse than virtual links operationally IME. I was suggesting then to keep an SVC from PGL to every border for that reason since a partition of a PGL led otherwise to the peer groups looking like the same thing for a while with highly undesirable operational effects (my memory doesn't reach that far really but we had at least discussions then to implement proprietary solution in Fore to have such SVCs for more stable deployments). In more abstract terms, flooding is extremely good to quickly "route around failures" when e'ones state is completely decentralized but is simply not a great mechanism if you have to talk to an entity couple hops away in a stable manner, especially if this entity hold state you need for correct operation when talking to your peers. 
> 
> 
> So we understand L2 tunnels from leaf to FR are "real" tunnels and have nothing to do with virtual links. 
> 
> As to the data plane, nope, you don't end up with any "virtual links" I can recognize unless you choose to call redistribution "virtual links" as well, maybe look @ the presentation again. 

That's exactly it! Excellent. :)

Safely using redistributed reachability to provide transit w/o tunnels is exactly what OSPF virtual links are, so that's why I'm saying

"A solution without tunnels is also possible by judicious scoping of reachability information between the levels."

will reduce to the same thing, if you want it to actually work generically. Perhaps this will become more obvious when that part of the draft is fleshed out.

Thanks,
Chris.

> 
> -- tony 
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr