> On Feb 11, 2019, at 10:19 AM, Lizhenbin <[email protected]> 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 [[email protected]] 代表 Christian Hopps [[email protected]] > 发送时间: 2019年2月11日 18:44 > 收件人: [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.
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
