Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux]

2019-02-13 Thread Peter Psenak

Hi Huaimo,

On 13/02/2019 22:50 , Huaimo Chen wrote:

Hi Peter,

My explanations/answers are in line below with prefix [HC].

-Original Message-
From: Peter Psenak [mailto:ppse...@cisco.com]
Sent: Wednesday, February 6, 2019 4:58 AM
To: Huaimo Chen ; Acee Lindem (acee) ; 
Christian Hopps ; lsr@ietf.org
Subject: Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux]

Hi Huaimo,

On 03/02/2019 17:58 , Huaimo Chen wrote:

Hi Acee,



I agree with you on keeping the signaling for two modes. The other
parts for the distributed solution need to be removed.


optimized flooding is not only about algorithm to calculate the flooding 
topology and the way it is distributed/computed. It is also about local 
rules to make sure the flooding remains consistent. These are 
_independent_ of centralized/distributed modes. And it make no sense to 
specify these rules in two drafts.


There are no "other" parts specific for the distributed solution.

[HC] Some behaviors for the distributed solution/mode are described in 
draft-li-dynamic-flooding. For example, there are a few of places from page 27 
to 30, which define the behaviors specific for the distributed solution/mode.


I strongly disagree. The fact that we say in centralized mode area 
leader recomputes and in distributed mode all nodes recompute make no 
difference in behavior.


thanks,
Peter



draft-li-dyanmic-flooding defines:

1. the signalling that is common and used by both modes 2. distribution of the 
flooding-topology, which is specific to centralized mode 3. common behavior of 
the nodes that support the extension, which is independent of the mode of 
operation.

[HC] In addition to these, draft-cc-lsr-flooding-reduction defines more, 
including concrete protections, operations, and algorithms for computing a 
flooding topology.

Best Regards,
Huaimo

thanks,
Peter






Best Regards,

Huaimo

*From:* Acee Lindem (acee) [mailto:a...@cisco.com]
*Sent:* Sunday, February 3, 2019 11:45 AM
*To:* Huaimo Chen ; Christian Hopps
; lsr@ietf.org
*Subject:* Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft
Redux]



Hi Huaimo,



See inline.



*From: *Lsr mailto:lsr-boun...@ietf.org>> on
behalf of Huaimo Chen mailto:huaimo.c...@huawei.com>>
*Date: *Saturday, February 2, 2019 at 12:27 AM
*To: *Christian Hopps mailto:cho...@chopps.org>>,
"lsr@ietf.org " mailto:lsr@ietf.org>>
*Subject: *Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft
Redux]



Hi Everyone,



We proposed the distributed solution first, and Tony proposed the
centralized solution first. Tony added the distributed solution
(except for the algorithms to compute flooding topology) into his
draft. And then we added the centralized solution into our draft. The
latest versions of the two drafts have largely converged at least at
the high level to a solution for solving the same problem.



Our draft has multiple key technical advantages over Tony's draft as
we described in our email to the LSR list, which are summarized below:

1.   It uses a fraction of flooding resource (i.e., it is multiple
times more efficient in flooding topology encoding);

2.   It provides fault tolerance to multiple failures, minimizing
impact on network convergence, thus minimizing traffic lose; and

3.   It is simpler and needs less processing time (i.e., faster and
more efficient) in multiple scenarios.

Based on the technical merits, our draft should be moved forward.
However, Chair proposed to move Tony's draft forward and have us work
on a distributed algorithm as we started with.



I think that the distributed solution in Tony's draft needs to be
removed and they work on the centralized solution. We remove the
centralized solution from our draft and work on the distributed solution.



I'm against "cutting the baby in half" given that the signaling for
the distributed solution is a proper subset of what is required for
the centralized solution. It is undesirable to have different
signaling for the two modes. For the distributed algorithm you are
proposing, do see problems with the signaling?



Thanks,

Acee



Best Regards,

Huaimo



-Original Message-

From: Lsr [mailto:lsr-boun...@ietf.org] On Behalf Of Christian Hopps

Sent: Friday, February 1, 2019 7:26 AM

To: lsr@ietf.org 

Cc: cho...@chopps.org 

Subject: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux]





Summary of where we are at with dynamic flooding reduction:



- We have a well written original work that came first and described
the problems as well as a TLVs to allow for a centralized solution
(draft-li-dyanmic-flooding). We do not need to standardize the
centralized algorithm.



- A small change to this work allowed for distributed algorithms and
for outside work on distributed algorithms to continue in parallel.



- We have another original work that started primarily as a
distributed algorithm

   

Re: [Lsr] 答复: WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.

2019-02-13 Thread Yangang
Support the adoption on these two drafts.

Yangang

-Original Message-
From: Lsr [mailto:lsr-boun...@ietf.org] On Behalf Of Lizhenbin
Sent: Thursday, February 14, 2019 2:21 PM
To: 'Christian Hopps' ; lsr@ietf.org
Cc: lsr-cha...@ietf.org; lsr-...@ietf.org
Subject: Re: [Lsr] 答复: WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + 
IPR poll.

Hi Chris & Acee,
I have explained my concerns the previous mails. In order to avoid unnecessary 
overlap, I supports the adoption of the drafts like follows:
- both drafts are adopted at the same time keeping draft-li-dynamic-flooding 
focus on the centralized solution and draft-cc-lsr-flooding-reduction on the 
distributed solution.
- draft-li-dynamic-flooding can keep on refining the centralized solution 
without mentioning distributed solutions.
- draft-cc-lsr-flooding-reduction can keep on refining the distributed 
solutions. For the signaling which can be shared by the two modes, the draft 
can indicate the distributed solutions reuse the signaling defined in 
draft-li-dynamic-flooding without defining new signaling. 
- both drafts change the draft names to reflect different solutions without 
causing confusion.


Thanks & Regards,
Zhenbin (Robin)



-邮件原件-
发件人: Christian Hopps [mailto:cho...@chopps.org]
发送时间: 2019年2月11日 18:45
收件人: lsr@ietf.org
抄送: lsr-cha...@ietf.org; lsr-...@ietf.org; cho...@chopps.org
主题: [Lsr] WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.


Hi Folks,

We are starting a 2 week adoption call on draft-li-lsr-dynamic-flooding-02.

The aim of this document is to describe the problem space and standardize a way 
to signal dynamic flooding information. It does not standardize any specific 
algorithm for flooding topology creation.

Authors please respond indicating if you are aware of any IPR related to this 
work.

We also have another draft (draft-cc-lsr-flooding-reduction-01) that started as 
a distributed flooding topology algorithm and morphed into that plus competing 
ideas on signaling of flooding topology information. The intent after adoption 
of draft-li-lsr-dynamic-flooding-02 is two-fold. One, the WG can discuss adding 
any signaling ideas from this work to the adopted signaling draft (with proper 
attribution given as appropriate), and two, for the authors of 
draft-cc-lsr-flooding-reduction-01 to publish a new document without the 
signaling portion and instead focus on their flooding topology algorithm. This 
new focused document can be considered in parallel along with the other 
algorithm work that has been proposed.

Flooding topology creation is seen as a hard problem for which we don't expect 
a one-size-fits-all solution. Taking the steps outlined above will help us move 
forward on the solutions.

Thanks,
Chris & Acee.
LSR WG Chairs.

___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr
___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr
___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr


[Lsr] 答复: 答复: WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.

2019-02-13 Thread Dongjie (Jimmy)
+1. 

Support to start the adoption poll on both drafts.

-Jie

> -邮件原件-
> 发件人: Lsr [mailto:lsr-boun...@ietf.org] 代表 Aijun Wang
> 发送时间: 2019年2月14日 10:38
> 收件人: 'Christian Hopps' ; lsr@ietf.org
> 抄送: lsr-cha...@ietf.org; lsr-...@ietf.org
> 主题: [Lsr] 答复: WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR
> poll.
> 
> Hi, Christian:
> 
> Supports for the adoption of two drafts at the same time, in which
> one(draft-li-lsr-dynamic-flooding-02) focuses on the centralized mode and
> the other(draft-cc-lsr-flooding-reduction-01) focuses on the distributed
> mode.
> 
> The centralized mode for is one straightforward way to realize the flooding
> reduction, and I admire Tony Li give his solution first. But from the
> consideration of solution robustness, the distributed mode may be more
> promising.
> My consideration for distributed mode is that it should not cover only the
> algorithm, more contents need to be standardized in future. Huaimo has one
> good start point for distributed mode, and he also gives abundant thoughts
> for the centralized mode that the current version of
> draft-li-lsr-dynamic-flooding-02 has not covered yet.
> 
> Proposal for the name of two drafts may be
> draft-ietf-lsr-flooding-reduction-centralized-mode and
> draft-ietf-lsr-flooding-reduction-distributed-mode.
> 
> 
> Best Regards.
> 
> Aijun Wang
> Network R and Operation Support Department China Telecom Corporation
> Limited Beijing Research Institute,Beijing, China.
> 
> -邮件原件-
> 发件人: Christian Hopps [mailto:cho...@chopps.org]
> 发送时间: 2019年2月11日 18:45
> 收件人: lsr@ietf.org
> 抄送: lsr-cha...@ietf.org; lsr-...@ietf.org; cho...@chopps.org
> 主题: [Lsr] WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.
> 
> 
> Hi Folks,
> 
> We are starting a 2 week adoption call on draft-li-lsr-dynamic-flooding-02.
> 
> The aim of this document is to describe the problem space and standardize a
> way to signal dynamic flooding information. It does not standardize any
> specific algorithm for flooding topology creation.
> 
> Authors please respond indicating if you are aware of any IPR related to
> this work.
> 
> We also have another draft (draft-cc-lsr-flooding-reduction-01) that started
> as a distributed flooding topology algorithm and morphed into that plus
> competing ideas on signaling of flooding topology information. The intent
> after adoption of draft-li-lsr-dynamic-flooding-02 is two-fold. One, the WG
> can discuss adding any signaling ideas from this work to the adopted
> signaling draft (with proper attribution given as appropriate), and two, for
> the authors of draft-cc-lsr-flooding-reduction-01 to publish a new document
> without the signaling portion and instead focus on their flooding topology
> algorithm. This new focused document can be considered in parallel along
> with the other algorithm work that has been proposed.
> 
> Flooding topology creation is seen as a hard problem for which we don't
> expect a one-size-fits-all solution. Taking the steps outlined above will
> help us move forward on the solutions.
> 
> Thanks,
> Chris & Acee.
> LSR WG Chairs.
> 
> ___
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr


Re: [Lsr] 答复: WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.

2019-02-13 Thread Huzhibo
Supports for the adoption of two drafts at the same time, IGP Reduce Flooding 
still have some problem needs to be solved, for example, how to ensure the 
reliability of Flooding in a multi-point failure scenario. The way to solve 
these problems in a distributed and centralized manner may be different. 
Therefore, it is recommended to promote separately and continue to conduct 
research in their respective directions.

Ths

Zhibo

-Original Message-
From: Lsr [mailto:lsr-boun...@ietf.org] On Behalf Of Aijun Wang
Sent: Thursday, February 14, 2019 10:38 AM
To: 'Christian Hopps' ; lsr@ietf.org
Cc: lsr-cha...@ietf.org; lsr-...@ietf.org
Subject: [Lsr] 答复: WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR 
poll.

Hi, Christian:

Supports for the adoption of two drafts at the same time, in which
one(draft-li-lsr-dynamic-flooding-02) focuses on the centralized mode and the 
other(draft-cc-lsr-flooding-reduction-01) focuses on the distributed mode.

The centralized mode for is one straightforward way to realize the flooding 
reduction, and I admire Tony Li give his solution first. But from the 
consideration of solution robustness, the distributed mode may be more 
promising.
My consideration for distributed mode is that it should not cover only the 
algorithm, more contents need to be standardized in future. Huaimo has one good 
start point for distributed mode, and he also gives abundant thoughts for the 
centralized mode that the current version of
draft-li-lsr-dynamic-flooding-02 has not covered yet.

Proposal for the name of two drafts may be 
draft-ietf-lsr-flooding-reduction-centralized-mode and 
draft-ietf-lsr-flooding-reduction-distributed-mode.


Best Regards.

Aijun Wang
Network R and Operation Support Department China Telecom Corporation Limited 
Beijing Research Institute,Beijing, China.

-邮件原件-
发件人: Christian Hopps [mailto:cho...@chopps.org]
发送时间: 2019年2月11日 18:45
收件人: lsr@ietf.org
抄送: lsr-cha...@ietf.org; lsr-...@ietf.org; cho...@chopps.org
主题: [Lsr] WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.


Hi Folks,

We are starting a 2 week adoption call on draft-li-lsr-dynamic-flooding-02.

The aim of this document is to describe the problem space and standardize a
way to signal dynamic flooding information. It does not standardize any
specific algorithm for flooding topology creation.

Authors please respond indicating if you are aware of any IPR related to
this work.

We also have another draft (draft-cc-lsr-flooding-reduction-01) that started
as a distributed flooding topology algorithm and morphed into that plus
competing ideas on signaling of flooding topology information. The intent
after adoption of draft-li-lsr-dynamic-flooding-02 is two-fold. One, the WG
can discuss adding any signaling ideas from this work to the adopted
signaling draft (with proper attribution given as appropriate), and two, for
the authors of draft-cc-lsr-flooding-reduction-01 to publish a new document
without the signaling portion and instead focus on their flooding topology
algorithm. This new focused document can be considered in parallel along
with the other algorithm work that has been proposed.

Flooding topology creation is seen as a hard problem for which we don't
expect a one-size-fits-all solution. Taking the steps outlined above will
help us move forward on the solutions.

Thanks,
Chris & Acee.
LSR WG Chairs.

___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr
___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr


Re: [Lsr] 答复: WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.

2019-02-13 Thread Guyunan (Yunan Gu, IP Technology Research Dept. NW)
Supports for the adoption of two drafts at the same time +1


BR,

Yunan


-Original Message-
From: Lsr [mailto:lsr-boun...@ietf.org] On Behalf Of Aijun Wang
Sent: Thursday, February 14, 2019 10:38 AM
To: 'Christian Hopps' ; lsr@ietf.org
Cc: lsr-cha...@ietf.org; lsr-...@ietf.org
Subject: [Lsr] 答复: WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR 
poll.

Hi, Christian:

Supports for the adoption of two drafts at the same time, in which
one(draft-li-lsr-dynamic-flooding-02) focuses on the centralized mode and the 
other(draft-cc-lsr-flooding-reduction-01) focuses on the distributed mode.

The centralized mode for is one straightforward way to realize the flooding 
reduction, and I admire Tony Li give his solution first. But from the 
consideration of solution robustness, the distributed mode may be more 
promising.
My consideration for distributed mode is that it should not cover only the 
algorithm, more contents need to be standardized in future. Huaimo has one good 
start point for distributed mode, and he also gives abundant thoughts for the 
centralized mode that the current version of
draft-li-lsr-dynamic-flooding-02 has not covered yet.

Proposal for the name of two drafts may be 
draft-ietf-lsr-flooding-reduction-centralized-mode and 
draft-ietf-lsr-flooding-reduction-distributed-mode.


Best Regards.

Aijun Wang
Network R and Operation Support Department China Telecom Corporation Limited 
Beijing Research Institute,Beijing, China.

-邮件原件-
发件人: Christian Hopps [mailto:cho...@chopps.org]
发送时间: 2019年2月11日 18:45
收件人: lsr@ietf.org
抄送: lsr-cha...@ietf.org; lsr-...@ietf.org; cho...@chopps.org
主题: [Lsr] WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.


Hi Folks,

We are starting a 2 week adoption call on draft-li-lsr-dynamic-flooding-02.

The aim of this document is to describe the problem space and standardize a
way to signal dynamic flooding information. It does not standardize any
specific algorithm for flooding topology creation.

Authors please respond indicating if you are aware of any IPR related to
this work.

We also have another draft (draft-cc-lsr-flooding-reduction-01) that started
as a distributed flooding topology algorithm and morphed into that plus
competing ideas on signaling of flooding topology information. The intent
after adoption of draft-li-lsr-dynamic-flooding-02 is two-fold. One, the WG
can discuss adding any signaling ideas from this work to the adopted
signaling draft (with proper attribution given as appropriate), and two, for
the authors of draft-cc-lsr-flooding-reduction-01 to publish a new document
without the signaling portion and instead focus on their flooding topology
algorithm. This new focused document can be considered in parallel along
with the other algorithm work that has been proposed.

Flooding topology creation is seen as a hard problem for which we don't
expect a one-size-fits-all solution. Taking the steps outlined above will
help us move forward on the solutions.

Thanks,
Chris & Acee.
LSR WG Chairs.

___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr
___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr


Re: [Lsr] 答复: WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.

2019-02-13 Thread Lizhenbin
Hi Chris & Acee,
I have explained my concerns the previous mails. In order to avoid unnecessary 
overlap, I supports the adoption of the drafts like follows:
- both drafts are adopted at the same time keeping draft-li-dynamic-flooding 
focus on the centralized solution and draft-cc-lsr-flooding-reduction on the 
distributed solution.
- draft-li-dynamic-flooding can keep on refining the centralized solution 
without mentioning distributed solutions.
- draft-cc-lsr-flooding-reduction can keep on refining the distributed 
solutions. For the signaling which can be shared by the two modes, the draft 
can indicate the distributed solutions reuse the signaling defined in 
draft-li-dynamic-flooding without defining new signaling. 
- both drafts change the draft names to reflect different solutions without 
causing confusion.


Thanks & Regards,
Zhenbin (Robin)



-邮件原件-
发件人: Christian Hopps [mailto:cho...@chopps.org]
发送时间: 2019年2月11日 18:45
收件人: lsr@ietf.org
抄送: lsr-cha...@ietf.org; lsr-...@ietf.org; cho...@chopps.org
主题: [Lsr] WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.


Hi Folks,

We are starting a 2 week adoption call on draft-li-lsr-dynamic-flooding-02.

The aim of this document is to describe the problem space and standardize a
way to signal dynamic flooding information. It does not standardize any
specific algorithm for flooding topology creation.

Authors please respond indicating if you are aware of any IPR related to
this work.

We also have another draft (draft-cc-lsr-flooding-reduction-01) that started
as a distributed flooding topology algorithm and morphed into that plus
competing ideas on signaling of flooding topology information. The intent
after adoption of draft-li-lsr-dynamic-flooding-02 is two-fold. One, the WG
can discuss adding any signaling ideas from this work to the adopted
signaling draft (with proper attribution given as appropriate), and two, for
the authors of draft-cc-lsr-flooding-reduction-01 to publish a new document
without the signaling portion and instead focus on their flooding topology
algorithm. This new focused document can be considered in parallel along
with the other algorithm work that has been proposed.

Flooding topology creation is seen as a hard problem for which we don't
expect a one-size-fits-all solution. Taking the steps outlined above will
help us move forward on the solutions.

Thanks,
Chris & Acee.
LSR WG Chairs.

___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr
___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr


[Lsr] 答复: WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.

2019-02-13 Thread Aijun Wang
Hi, Christian:

Supports for the adoption of two drafts at the same time, in which
one(draft-li-lsr-dynamic-flooding-02) focuses on the centralized mode and
the other(draft-cc-lsr-flooding-reduction-01) focuses on the distributed
mode.

The centralized mode for is one straightforward way to realize the flooding
reduction, and I admire Tony Li give his solution first. But from the
consideration of solution robustness, the distributed mode may be more
promising.
My consideration for distributed mode is that it should not cover only the
algorithm, more contents need to be standardized in future. Huaimo has one
good start point for distributed mode, and he also gives abundant thoughts
for the centralized mode that the current version of
draft-li-lsr-dynamic-flooding-02 has not covered yet.

Proposal for the name of two drafts may be
draft-ietf-lsr-flooding-reduction-centralized-mode and
draft-ietf-lsr-flooding-reduction-distributed-mode.


Best Regards.

Aijun Wang
Network R and Operation Support Department
China Telecom Corporation Limited Beijing Research Institute,Beijing, China.

-邮件原件-
发件人: Christian Hopps [mailto:cho...@chopps.org] 
发送时间: 2019年2月11日 18:45
收件人: lsr@ietf.org
抄送: lsr-cha...@ietf.org; lsr-...@ietf.org; cho...@chopps.org
主题: [Lsr] WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR
poll.


Hi Folks,

We are starting a 2 week adoption call on draft-li-lsr-dynamic-flooding-02.

The aim of this document is to describe the problem space and standardize a
way to signal dynamic flooding information. It does not standardize any
specific algorithm for flooding topology creation.

Authors please respond indicating if you are aware of any IPR related to
this work.

We also have another draft (draft-cc-lsr-flooding-reduction-01) that started
as a distributed flooding topology algorithm and morphed into that plus
competing ideas on signaling of flooding topology information. The intent
after adoption of draft-li-lsr-dynamic-flooding-02 is two-fold. One, the WG
can discuss adding any signaling ideas from this work to the adopted
signaling draft (with proper attribution given as appropriate), and two, for
the authors of draft-cc-lsr-flooding-reduction-01 to publish a new document
without the signaling portion and instead focus on their flooding topology
algorithm. This new focused document can be considered in parallel along
with the other algorithm work that has been proposed.

Flooding topology creation is seen as a hard problem for which we don't
expect a one-size-fits-all solution. Taking the steps outlined above will
help us move forward on the solutions.

Thanks,
Chris & Acee.
LSR WG Chairs.

___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr


Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux]

2019-02-13 Thread Huaimo Chen
Hi Peter,

My explanations/answers are in line below with prefix [HC].

-Original Message-
From: Peter Psenak [mailto:ppse...@cisco.com] 
Sent: Wednesday, February 6, 2019 4:58 AM
To: Huaimo Chen ; Acee Lindem (acee) ; 
Christian Hopps ; lsr@ietf.org
Subject: Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux]

Hi Huaimo,

On 03/02/2019 17:58 , Huaimo Chen wrote:
> Hi Acee,
>
>
>
> I agree with you on keeping the signaling for two modes. The other 
> parts for the distributed solution need to be removed.

There are no "other" parts specific for the distributed solution.

[HC] Some behaviors for the distributed solution/mode are described in 
draft-li-dynamic-flooding. For example, there are a few of places from page 27 
to 30, which define the behaviors specific for the distributed solution/mode.

draft-li-dyanmic-flooding defines:

1. the signalling that is common and used by both modes 2. distribution of the 
flooding-topology, which is specific to centralized mode 3. common behavior of 
the nodes that support the extension, which is independent of the mode of 
operation.

[HC] In addition to these, draft-cc-lsr-flooding-reduction defines more, 
including concrete protections, operations, and algorithms for computing a 
flooding topology.

Best Regards,
Huaimo

thanks,
Peter


>
>
>
> Best Regards,
>
> Huaimo
>
> *From:* Acee Lindem (acee) [mailto:a...@cisco.com]
> *Sent:* Sunday, February 3, 2019 11:45 AM
> *To:* Huaimo Chen ; Christian Hopps 
> ; lsr@ietf.org
> *Subject:* Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft 
> Redux]
>
>
>
> Hi Huaimo,
>
>
>
> See inline.
>
>
>
> *From: *Lsr mailto:lsr-boun...@ietf.org>> on 
> behalf of Huaimo Chen  >
> *Date: *Saturday, February 2, 2019 at 12:27 AM
> *To: *Christian Hopps mailto:cho...@chopps.org>>, 
> "lsr@ietf.org "  >
> *Subject: *Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft 
> Redux]
>
>
>
> Hi Everyone,
>
>
>
> We proposed the distributed solution first, and Tony proposed the 
> centralized solution first. Tony added the distributed solution 
> (except for the algorithms to compute flooding topology) into his 
> draft. And then we added the centralized solution into our draft. The 
> latest versions of the two drafts have largely converged at least at 
> the high level to a solution for solving the same problem.
>
>
>
> Our draft has multiple key technical advantages over Tony's draft as 
> we described in our email to the LSR list, which are summarized below:
>
> 1.   It uses a fraction of flooding resource (i.e., it is multiple
> times more efficient in flooding topology encoding);
>
> 2.   It provides fault tolerance to multiple failures, minimizing
> impact on network convergence, thus minimizing traffic lose; and
>
> 3.   It is simpler and needs less processing time (i.e., faster and
> more efficient) in multiple scenarios.
>
> Based on the technical merits, our draft should be moved forward.
> However, Chair proposed to move Tony's draft forward and have us work 
> on a distributed algorithm as we started with.
>
>
>
> I think that the distributed solution in Tony's draft needs to be 
> removed and they work on the centralized solution. We remove the 
> centralized solution from our draft and work on the distributed solution.
>
>
>
> I'm against "cutting the baby in half" given that the signaling for 
> the distributed solution is a proper subset of what is required for 
> the centralized solution. It is undesirable to have different 
> signaling for the two modes. For the distributed algorithm you are 
> proposing, do see problems with the signaling?
>
>
>
> Thanks,
>
> Acee
>
>
>
> Best Regards,
>
> Huaimo
>
>
>
> -Original Message-
>
> From: Lsr [mailto:lsr-boun...@ietf.org] On Behalf Of Christian Hopps
>
> Sent: Friday, February 1, 2019 7:26 AM
>
> To: lsr@ietf.org 
>
> Cc: cho...@chopps.org 
>
> Subject: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux]
>
>
>
>
>
> Summary of where we are at with dynamic flooding reduction:
>
>
>
> - We have a well written original work that came first and described 
> the problems as well as a TLVs to allow for a centralized solution 
> (draft-li-dyanmic-flooding). We do not need to standardize the 
> centralized algorithm.
>
>
>
> - A small change to this work allowed for distributed algorithms and 
> for outside work on distributed algorithms to continue in parallel.
>
>
>
> - We have another original work that started primarily as a 
> distributed algorithm
>
>(draft-cc-ospf-flooding-reduction)
>
>
>
> - Finally we also have:
>
>- Cross-pollination of ideas.
>
>- Failed attempts at merging.
>
>- An authors list "Arms-Race".
>
>
>
> Moving forward:
>
>
>
> - During IETF 103 I proposed we have no conflict if we:
>
>
>
>1) adopt draft-li-lsr-dyanmic-flooding as the base WG document.
>
>2) have 

[Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-13 Thread Acee Lindem (acee)
This begins a two week adoption poll for the subject draft. Please send your 
comments to this list before 12:00 AM UTC on Thursday, February 28th, 2019.

All authors have responded to the IPR poll and there is one 

  
https://datatracker.ietf.org/ipr/search/?submit=draft=draft-wang-lsr-ospf-prefix-originator-ext
It is listed multiple times but references the same CN201810650141.

Thanks,
Acee

___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr


Re: [Lsr] IPR Poll on "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-13 Thread Ketan Talaulikar (ketant)
Hi Acee,

I am not aware of any IPR other than the one disclosed below.

Thanks,
Ketan

From: Aijun Wang 
Sent: 13 February 2019 07:19
To: Acee Lindem (acee) ; 
draft-wang-lsr-ospf-prefix-originator-...@ietf.org
Cc: lsr@ietf.org
Subject: 答复: [Lsr] IPR Poll on "OSPF Extension for Prefix Originator" - 
draft-wang-lsr-ospf-prefix-originator-ext-01

Hi, Acee:

Apart from the IPR declared in https://datatracker.ietf.org/ipr/3420/ , I am 
not aware of any other IPR.
Thanks for your efforts.


Best Regards.

Aijun Wang
Network R and Operation Support Department
China Telecom Corporation Limited Beijing Research Institute,Beijing, China.
发件人: Acee Lindem (acee) [mailto:a...@cisco.com]
发送时间: 2019年2月9日 1:01
收件人: 
draft-wang-lsr-ospf-prefix-originator-...@ietf.org
抄送: lsr@ietf.org
主题: [Lsr] IPR Poll on "OSPF Extension for Prefix Originator" - 
draft-wang-lsr-ospf-prefix-originator-ext-01

Authors,

In preparation for a WG adoption call:

Are you aware of any IPR relating to 
https://datatracker.ietf.org/doc/draft-wang-lsr-ospf-prefix-originator-ext? If 
so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 
3979, 4879, 3669 and 5378 for more details). If you are listed as a document 
author or contributor please respond to this email regardless of whether or not 
you are aware of any relevant IPR. *The response needs to be sent to the LSR WG 
mailing list.* The document will not advance to the next stage until a response 
has been received from each author and contributor. If you are on the LSR WG 
email list but are not listed as an author or contributor, then please 
explicitly respond only if you are aware of any IPR that has not yet been 
disclosed in conformance with IETF rules.

Thanks,
Acee


___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr