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

[Jeff Tantsura]

Yes/support

Cheers,
Jeff
On Feb 11, 2019, 2:47 AM -0800, Christian Hopps , wrote:
>
> 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.

[Les Ginsberg (ginsberg)]

Support adoption (as co-author).

I am not aware of any relevant IPR.

   Les


> -Original Message-
> From: Lsr  On Behalf Of Christian Hopps
> Sent: Monday, February 11, 2019 2:45 AM
> To: lsr@ietf.org
> Cc: lsr-cha...@ietf.org; lsr-...@ietf.org; cho...@chopps.org
> Subject: [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] WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.

[Naiming Shen (naiming)]

Support the adoption of the draft.

Regards,
- Naiming

> On Feb 11, 2019, at 2:44 AM, Christian Hopps  wrote:
> 
> 
> 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.

[Peter Psenak]

Hi Chris,

support as coauthor.

Not aware of any IPR at this point.

thanks,
Peter

On 11/02/2019 11:44 , Christian Hopps wrote:


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.

[steve ulrich]

support.

On Mon, Feb 11, 2019 at 4:47 AM Christian Hopps  wrote:

>
> 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
>


-- 
steve ulrich (sulrich@botwerks.*)
___
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.

[David Allan I]

Support

-Original Message-
From: Lsr  On Behalf Of Acee Lindem (acee)
Sent: Monday, February 11, 2019 5:23 AM
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.

Speaking as a WG member:

I support adoption of draft-li-lsr-dynamic-flooding-02 as infrastructure for 
flooding reduction mechanisms based on a separate flooding topology. Work on 
individual flooding reduction/topology determination algorithms can proceed in 
separate drafts.

Thanks,
Acee

On 2/11/19, 5:47 AM, "Christian Hopps"  wrote:


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.

[Christian Hopps]

> On Feb 11, 2019, at 10:19 AM, Lizhenbin  wrote:
> 
> Hi Chris,
> 1. I have doubt about "The aim of this document is to describe the problem 
> space and standardize a way to signal dynamic flooding information.". Does 
> the aim mean the draft describes the problem space and standardize the way 
> for the centralized solution or mean the draft will standardize the way used 
> for both the centralized solutions and the distributed solutions?

It does not standardize any algorithms. For a centralized algorithm 
(unspecified) use one has to distribute the flooding topology it does specify 
this. It also supplies the means to signal what distributed algorithm is in use 
(a value).

> 2. I explained in the previous mail the distributed solution includes more 
> than the algorithms defined in the draft-cc-lsr-flooding-reduction-00  and 
> the overlapped signallings  defined in the 
> draft-cc-lsr-flooding-reduction-00/draft-li-dynamic-flooding-03. For example, 
> it may define the standardized procedures for the distributed solutions. If 
> there is such part, is it defined by draft-li-lsr-dynamic-flooding-02 or 
> draft-cc-lsr-flooding-reduction?

How a distributed algorithm decides to implement itself is up to that 
algorithm. This is not part of the signaled information. Again, the only thing 
that I am aware of in draft-li-dynamic-flooding in regards to distributed 
algorithms is what's required for us to use them as they get defined in the 
future, i.e., a way to signal which one is in use.

Thanks,
Chris.

> 
> I hope you could clarify the above issues firstly for the adoption.
> 
> 
> Thanks & Regards,
> Zhenbin (Robin)
> 
> 
> 
> 
> 
> 发件人: Lsr [lsr-boun...@ietf.org] 代表 Christian Hopps [cho...@chopps.org]
> 发送时间: 2019年2月11日 18:44
> 收件人: 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.



signature.asc
Description: Message signed with OpenPGP
___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr

[Lsr] Flooding Reduction Draft Discussion - a naive question

[Susan Hares]

In working through the emails on the flooding reduction concepts,  I have a
few question:   Is this work is simply for the spine-leaf topologies or for
multiple topologies?   . Does this work consider all of the following
networks: spine-leaf data centers, 802.1 Provider Bridging, IPRAN
topologies, banking networks, and IoT sensor networks?  

 

If this technology is for multiple topologies, it is useful to have a
discussion of convergence problems within these diverse networks.   I have
observed in WG meetings and on-list the following problem scenarios: a)
spine-leaf convergence problem descriptions and b) Dave Allan's description
of the 802.1 Provider Bridging (PBB) convergence issues.   Did I miss other
problem convergence discussions?  

 

Sue

 

PS -  As part of some research for IPRAN topologies, I wrote-up a
description of convergence problems for the IPRAN ring-grid topologies.  I
am looking for something like: 

https://www.ietf.org/internet-drafts/draft-hares-lsr-grid-ring-convergence-0
0.txt

 

___
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.

[Edward]

Support.

On Mon, Feb 11, 2019 at 2:47 AM Christian Hopps  wrote:

>
> 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.

[Lizhenbin]

Hi Chris,
1. I have doubt about "The aim of this document is to describe the problem 
space and standardize a way to signal dynamic flooding information.". Does the 
aim mean the draft describes the problem space and standardize the way for the 
centralized solution or mean the draft will standardize the way used for both 
the centralized solutions and the distributed solutions?
2. I explained in the previous mail the distributed solution includes more than 
the algorithms defined in the draft-cc-lsr-flooding-reduction-00  and the 
overlapped signallings  defined in the 
draft-cc-lsr-flooding-reduction-00/draft-li-dynamic-flooding-03. For example, 
it may define the standardized procedures for the distributed solutions. If 
there is such part, is it defined by draft-li-lsr-dynamic-flooding-02 or 
draft-cc-lsr-flooding-reduction?

I hope you could clarify the above issues firstly for the adoption.


Thanks & Regards,
Zhenbin (Robin) 





发件人: Lsr [lsr-boun...@ietf.org] 代表 Christian Hopps [cho...@chopps.org]
发送时间: 2019年2月11日 18:44
收件人: 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] WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.

[Robert Raszuk]

Support.

r.

On Mon, Feb 11, 2019 at 11:47 AM Christian Hopps  wrote:

>
> 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.

[tony . li]

+1 as author.

There is an IPR filing on this technology, specifying the “don’t sue us, we 
won’t sue you” language.  See https://datatracker.ietf.org/ipr/3361/ 


We are very interested in moving forward together on this work.

Regards,
Tony


> On Feb 11, 2019, at 2:44 AM, Christian Hopps  wrote:
> 
> 
> 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.

[Acee Lindem (acee)]

Speaking as a WG member:

I support adoption of draft-li-lsr-dynamic-flooding-02 as infrastructure for 
flooding reduction mechanisms based on a separate flooding topology. Work on 
individual flooding reduction/topology determination algorithms can proceed in 
separate drafts. 

Thanks,
Acee

On 2/11/19, 5:47 AM, "Christian Hopps"  wrote:


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] WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.

[Christian Hopps]

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.


signature.asc
Description: PGP signature
___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr

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

[Huzhibo]

Support to promote the centralized and distributed solutions in two separated 
drafts.

Best regards,
Zhibo
-Original Message-
From: Lsr [mailto:lsr-boun...@ietf.org] On Behalf Of Dongjie (Jimmy)
Sent: Monday, February 11, 2019 4:47 PM
To: Lizhenbin ; Christian Hopps ; 
lsr@ietf.org
Subject: Re: [Lsr] 答复: Moving Forward [Re: Flooding Reduction Draft Redux]

Support moving forward with the centralized and distributed solutions specified 
in separated drafts. As discussed in previous mails, the procedure and protocol 
extensions needed for the two modes could be different, and a particular 
network may only want to use one mode.

As for the centralized solution, maybe it could be refined with the advantage 
of the centralized part in both existing drafts.

Best regards,
Jie

> -Original Message-
> From: Lsr [mailto:lsr-boun...@ietf.org] On Behalf Of Lizhenbin
> Sent: Monday, February 04, 2019 5:36 PM
> To: Christian Hopps ; lsr@ietf.org
> Subject: [Lsr] 答复: Moving Forward [Re: Flooding Reduction Draft Redux]
> 
> Hi Chris & Acee,
> 
> > - Jan 2, 2018 Publication: draft-li-dynamic-flooding and
> drfat-li-dynamic-flooding-isis
> >   published centralized solution.
> >
> > - Mar 5, 2018 Publication: draft-cc-isis-flooding-reduction and
> draft-cc-ospf-flooding-reduction
> >   published distributed solution
> 
> Thanks for your summary we know the fact that at beginning there was 
> not any confliction between the two drafts.
> 
> 
> > - Jun 28, 2018 draft-li-dynamic-flooding-05 published (2 authors)
> >   - *SMALL CHANGE TO SUPPORT DISTRIBUTED ALGORITHM*.
> >   - Does not specify distributed algorithm only how to indicate one 
> > in use,
> small change.
> 
> I do not think it is a small change. It is to introduced the totally 
> new solution which was already defined in the other existing draft. It 
> is not an appropariate behavior and the root cause of the potential 
> confliction.
> 
> 
> I also think the distributed solution includes more than the 
> algorithms defined in the draft-cc-lsr-flooding-reduction-00  and the 
> overlapped signallings  defined in the 
> draft-cc-lsr-flooding-reduction-00/draft-li-dynamic-flooding-03. Since 
> the co-authors could not merge the draft, though the existing 
> suggestion proposed is try to separate the two drafts, there is still 
> overlap on the distributed solution between the two drafts which may 
> be the source of continuous confliction in the future. In order to 
> avoid the situation I would like to propose following
> suggestions:
> - move both the two drafts forward in parallel 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 distibuted solutions.
> - draft-cc-lsr-flooding-reduction can keep on refining the distributed 
> solutions.
> For the sigalling which can be shared by the two modes, the draft can 
> indicate the distributed solutions reuse the signalling defined in 
> draft-li-dynamic-flooding without defining new signalling.
> - both drafts change the draft names to reflect different solutions 
> without causing confusion.
> 
> 
> Thanks & Regards,
> Zhenbin (Robin)
> 
> 
> 
> 
> 
> 
> 发件人: Lsr [lsr-boun...@ietf.org] 代表 Christian Hopps [cho...@chopps.org]
> 发送时间: 2019年2月1日 20:25
> 收件人: lsr@ietf.org
> 抄送: cho...@chopps.org
> 主题: [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 authors of draft-cc-lsr-flooding-reduction work on a 
> distributed algorithm as they started with.
> 
> - Acee agreed during the meeting (as chair) that this was the best way 
> forward.
> We had some agreement form the floor as well.
> 
> - Any good ideas regarding the distribution of a centralized topology 
> can be debated and added (with appropriate attribution) to the base 
> document after we adopt one.
> 
> - This is what happens when we adopt a document as WG work, we work on it.
> 
> - The original authors of the distributed solution can continue to 
> wor

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

[Dongjie (Jimmy)]

Support moving forward with the centralized and distributed solutions specified 
in separated drafts. As discussed in previous mails, the procedure and protocol 
extensions needed for the two modes could be different, and a particular 
network may only want to use one mode.

As for the centralized solution, maybe it could be refined with the advantage 
of the centralized part in both existing drafts.

Best regards,
Jie

> -Original Message-
> From: Lsr [mailto:lsr-boun...@ietf.org] On Behalf Of Lizhenbin
> Sent: Monday, February 04, 2019 5:36 PM
> To: Christian Hopps ; lsr@ietf.org
> Subject: [Lsr] 答复: Moving Forward [Re: Flooding Reduction Draft Redux]
> 
> Hi Chris & Acee,
> 
> > - Jan 2, 2018 Publication: draft-li-dynamic-flooding and
> drfat-li-dynamic-flooding-isis
> >   published centralized solution.
> >
> > - Mar 5, 2018 Publication: draft-cc-isis-flooding-reduction and
> draft-cc-ospf-flooding-reduction
> >   published distributed solution
> 
> Thanks for your summary we know the fact that at beginning there was not any
> confliction between the two drafts.
> 
> 
> > - Jun 28, 2018 draft-li-dynamic-flooding-05 published (2 authors)
> >   - *SMALL CHANGE TO SUPPORT DISTRIBUTED ALGORITHM*.
> >   - Does not specify distributed algorithm only how to indicate one in use,
> small change.
> 
> I do not think it is a small change. It is to introduced the totally new 
> solution which
> was already defined in the other existing draft. It is not an appropariate 
> behavior
> and the root cause of the potential confliction.
> 
> 
> I also think the distributed solution includes more than the algorithms 
> defined in
> the draft-cc-lsr-flooding-reduction-00  and the overlapped signallings  
> defined
> in the draft-cc-lsr-flooding-reduction-00/draft-li-dynamic-flooding-03. Since 
> the
> co-authors could not merge the draft, though the existing suggestion proposed 
> is
> try to separate the two drafts, there is still overlap on the distributed 
> solution
> between the two drafts which may be the source of continuous confliction in 
> the
> future. In order to avoid the situation I would like to propose following
> suggestions:
> - move both the two drafts forward in parallel 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 distibuted solutions.
> - draft-cc-lsr-flooding-reduction can keep on refining the distributed 
> solutions.
> For the sigalling which can be shared by the two modes, the draft can 
> indicate the
> distributed solutions reuse the signalling defined in 
> draft-li-dynamic-flooding
> without defining new signalling.
> - both drafts change the draft names to reflect different solutions without
> causing confusion.
> 
> 
> Thanks & Regards,
> Zhenbin (Robin)
> 
> 
> 
> 
> 
> 
> 发件人: Lsr [lsr-boun...@ietf.org] 代表 Christian Hopps [cho...@chopps.org]
> 发送时间: 2019年2月1日 20:25
> 收件人: lsr@ietf.org
> 抄送: cho...@chopps.org
> 主题: [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 authors of draft-cc-lsr-flooding-reduction work on a distributed
> algorithm as they started with.
> 
> - Acee agreed during the meeting (as chair) that this was the best way 
> forward.
> We had some agreement form the floor as well.
> 
> - Any good ideas regarding the distribution of a centralized topology can be
> debated and added (with appropriate attribution) to the base document after
> we adopt one.
> 
> - This is what happens when we adopt a document as WG work, we work on it.
> 
> - The original authors of the distributed solution can continue to work on 
> their
> distributed algorithm in a separate document which would also need
> standardization.
> 
> Does anyone see a serious problem with this path forward?
> 
> Thanks,
> Chris & Acee.
> LSR Chairs.
> 
> Christian Hopps  writes:
> 
> > We've had the authors of the individual conflicting drafts take a shot at 
> > merging
> their work.
> >
> >This has fa