Re: [Lsr] LSR Flooding Reduction Drafts - Moving Forward

2018-08-27 Thread tony . li
> so it's party like it's 1999, seems the peer group leader election gets > rediscovered ;-) Interesting old new problems, interesting old new attack > vectors like https://ieeexplore.ieee.org/document/822780/ > No argument there. There are no

Re: [Lsr] LSR Flooding Reduction Drafts - Moving Forward

2018-08-27 Thread Tony Przygienda
On Mon, Aug 27, 2018 at 9:41 AM Huaimo Chen wrote: > Hi Robert, > > > > >Leader election happens automatically and procedures for that are to be > vastly similar to today's DR or DIS election. So with this in mind one may > observe that both OSPF and ISIS are pretty centralized on multiaccess >

Re: [Lsr] LSR Flooding Reduction Drafts - Moving Forward

2018-08-27 Thread Robert Raszuk
> draft-cc-ospf-flooding-reduction-02 allows operators to select distributed mode, centralized one or static one smoothly. Aside from static approach can you summarize in purely technical points advantages your draft proposes over draft-li-dynamic-flooding-05 ? Many thx, R. On Mon, Aug 27,

Re: [Lsr] LSR Flooding Reduction Drafts - Moving Forward

2018-08-27 Thread tony . li
> Today’s DR or DIS election is local to a special interface/network such as a > broadcast interface. Leader election in a network is global. Every node in > the network depends on it (its flooding topology). These two seems different. Hmm…. Ethernet is not ‘special’. Pretty much all that

Re: [Lsr] LSR Flooding Reduction Drafts - Moving Forward

2018-08-27 Thread Huaimo Chen
Hi Robert, >Leader election happens automatically and procedures for that are to be vastly >similar to today's DR or DIS election. So with this in mind one may observe >that both OSPF and ISIS are pretty centralized on multiaccess networks today :) Today’s DR or DIS election is local to a

Re: [Lsr] LSR Flooding Reduction Drafts - Moving Forward

2018-08-27 Thread tony . li
Hi Huaimo, > After flooding reduction is deployed in an operational (ISP) network, will we > be allowed to do experiments on their network? Some may well permit it. Certainly in lab scenarios they may be very willing. It all depends on their motivation to achieve improvements. It should

Re: [Lsr] LSR Flooding Reduction Drafts - Moving Forward

2018-08-27 Thread Robert Raszuk
Hi Huaimo, > Introducing centralized feature into IGP will break IGP's distributed nature That clearly proves that word "centralized" has been significantly overloaded here. To many indeed "centralized" means a controller (like OpenFlow or SDN) and that such device added to a network is to push

Re: [Lsr] LSR Flooding Reduction Drafts - Moving Forward

2018-08-27 Thread Huaimo Chen
>> I think distributed is more practical too. >I would appreciate more detailed insights as to why you (and others) feel this >way. It is not at all obvious to me. IGP is distributed in nature. The distributed computation of flooding topology like distributed SPF will keep IGP still

[Lsr] I-D Action: draft-ietf-ospf-ospfv2-hbit-06.txt

2018-08-27 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Link State Routing WG of the IETF. Title : H-bit Support for OSPFv2 Authors : Keyur Patel Padma Pillay-Esnault

Re: [Lsr] LSR Flooding Reduction Drafts - Moving Forward

2018-08-27 Thread Huaimo Chen
Hi Chris, Peter and Everyone, >-Original Message- >From: Lsr [mailto:lsr-boun...@ietf.org] On Behalf Of Peter Psenak >Sent: Monday, August 27, 2018 8:22 AM >To: Christian Hopps ; Tony Li >Cc: lsr@ietf.org; Jeff Tantsura ; Acee Lindem (acee) >; Tony Przygienda >Subject: Re: [Lsr] LSR

Re: [Lsr] LSR Flooding Reduction Drafts - Moving Forward

2018-08-27 Thread Peter Psenak
Chris and All, On 27/08/18 14:10 , Christian Hopps wrote: On Aug 24, 2018, at 12:29 PM, tony...@tony.li wrote: Being distributed would be very nice. However, that implies that all nodes are going to get to the exact same solution. Which implies that they all must execute the same

Re: [Lsr] LSR Flooding Reduction Drafts - Moving Forward

2018-08-27 Thread Christian Hopps
> On Aug 24, 2018, at 12:29 PM, tony...@tony.li wrote: > > Being distributed would be very nice. However, that implies that all nodes > are going to get to the exact same solution. Which implies that they all must > execute the same algorithm, presumably with the same inputs. > > That’s all