Chris,

Well put.

Yours Irrespectively,

John

> -----Original Message-----
> From: Lsr <[email protected]> On Behalf Of Christian Hopps
> Sent: Thursday, February 14, 2019 10:56 AM
> To: [email protected]
> Cc: [email protected]; [email protected]; 'Christian Hopps'
> <[email protected]>; Aijun Wang <[email protected]>
> Subject: Re: [Lsr] 答复: WG Adoption Call for draft-li-lsr-dynamic-flooding-02 +
> IPR poll.
> 
> 
> Hi folks,
> 
> It's not useful for people to be adding a bunch of extra qualifications and
> caveats to the adoption poll.
> 
> This is not a dual adoption poll. We are not calling for adoption of an 
> unwritten,
> unfinished algorithm document. That makes no sense; we adopt reviewed
> acceptable work, not the promise of it. We're also not going to hold up
> standardizing the signaling work waiting on unfinished algorithm work, that's
> literally the opposite of the goal here which is to un-tie these two things 
> so we
> can make progress on both in parallel.
> 
> Thanks,
> Chris.
> 
> Aijun Wang <[email protected]> writes:
> 
> > 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&D and Operation Support Department China Telecom Corporation
> > Limited Beijing Research Institute,Beijing, China.
> >
> > -----邮件原件-----
> > 发件人: Christian Hopps [mailto:[email protected]]
> > 发送时间: 2019年2月11日 18:45
> > 收件人: [email protected]
> > 抄送: [email protected]; [email protected]; [email protected]
> > 主题: [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
[email protected]
https://www.ietf.org/mailman/listinfo/lsr

Reply via email to